On Tue, Aug 19, 2025 at 02:08:59PM +0200, Michael Biebl wrote: > Am 18.08.25 um 19:50 schrieb Roberto C. Sánchez: > > > At this point, I've already caused the damage (again, apologies for > > that), so I think that the best thing is to get some patches sent out. > > I'll start working on those ASAP. > > > > Would the release team like to provide any specific guidance that I > > should observe here? Or perhaps suggest an alternate approach? > > Thanks Roberto. > > Not speaking for the release team here, btw, just a common bystander who is > affected by this change. > Ack. My question was aimed more generally than just at you. It may have helped if I had been a bit more careful with how I structured my reply.
> I've updated rsyslog to build with both v1 and v2 of mongo-c-driver > > https://salsa.debian.org/debian/rsyslog/-/commit/8ea8f59756eccfae4471e7482460e922750f169c > > This was basically all I needed to make rsyslog compile against against v2. > Is there more that I need to consider (deprecated APIs etc.), if so, do you > have recommendations, links to a migration guide, etc. > That change looks right to me. Basically, if something was already successfully building against 1.30.x (without using any deprecated APIs) then building against 2.x is a matter of just using the new module name (whether via pkg-config or CMake). The SONAME bump was about finally dropping a bunch of long deprecated things from the API. Apart from the module name change (and some minor reshulffling of headers), there weren't any really notable changes to the API. Regards, -Roberto -- Roberto C. Sánchez
