[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1112375: transition: mongo-c-driver



Control: tags -1 = confirmed pending

On 30/08/2025 22:51, Roberto C. Sánchez wrote:
Hi Sebastian,

On Fri, Aug 29, 2025 at 10:06:09AM +0200, Sebastian Ramacher wrote:

For the next time: please file a transition bug before uploading SONAME
changes to unstable. See also
https://wiki.debian.org/Teams/ReleaseTeam/Transitions.

Yes. Sadly, I was aware of the need for a transition and yet for some
reason that I cannot comprehend at the moment I prepared the upload to
unstable I completely forgot about it.

I am now turning
this into a transition bug report so that it is on our radar.

Thanks!

In any case, the mongo-c-driver version already migrated to testing, so
I think helping to fix the remaining build issues with patches/uploads
is the best course of action to finish this transition as soon as
possible. If the blocking bugs do not already have patches, please check
if upstream already has fixes or help getting it fixed.


So, based on the auto transition tracker [0], here is the current status
of the packages that are still unfixed:

gambas3: I submitted #1111779 with a patch (though I see that the
maintainer downgraded to wishlist and indicated that mongodb support has
been disabled because upstream considers it unstable)

libmongocrypt: this is my package and the upstream version that I need
to upload will support the new libmongoc version; I thought it better to
wait and clean up the mess I created in others' packages before dealing
with this one

fastnetmon: I submitted #1111777 with a patch

hydra: dropped off the tracker, since the build automatically disables
libmongoc support if the expected module isn't found; I submitted
#1112344 with a patch to make the build work w/ the new version

nextepc: I uploaded to DELAYED/5 (and sent the patch to #1112311)

reflect-cpp: I submitted patches to #1112052 (though I discovered a
different FTBFS in the process and filed #1112554)

syslog-ng: I submitted patches to #1111162 (the maintainers are quite
active, so I expect them to pick up the patches, prepare a new upstream
release, soon)

My remaining actions are:

- deal with libmongocrypt (planned for this week)
- check back in on #1111777 in a week or so and prepare an NMU if there
   is no action/response by the maintainer

[0] https://release.debian.org/transitions/html/auto-mongo-c-driver.html


This is ongoing and already in testing (although not finished yet due to a couple of rdeps). Tagging as such.

Cheers,
Emilio


Reply to: