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

Bug#1112375: marked as done (transition: mongo-c-driver)

Your message dated Wed, 3 Dec 2025 13:55:29 +0100
with message-id <a530af2e-7898-4acd-99ad-d6ffd6aa6f5e@debian.org>
and subject line Re: Bug#1112375: transition: mongo-c-driver
has caused the Debian Bug report #1112375,
regarding transition: mongo-c-driver
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
1112375: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1112375
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: normal
Control: affects -1 + src:mongo-c-driver
Control: block -1 by 1111162 1112052 1112311 1111777 1111779
Control: severity 1111779 serious
Control: tags 1111779 ftbfs sid forky
Control: submitter -1 "Roberto C. Sanchez" <roberto@debian.org>
User: release.debian.org@packages.debian.org
Usertags: transition


On 2025-08-19 10:00:08 -0400, Roberto C. Sánchez wrote:
> Hi again Michael and Bastian and Release Team,
> 
> On Mon, Aug 18, 2025 at 01:50:54PM -0400, Roberto C. Sánchez wrote:
> > > 
> > Yes, I'm really sorry about that.
> > 
> > I had uploaded 2.x to experimental a little while back (during the
> > freeze) and in thinking through my plan for uploading to unstable I
> > completely and entirely forgot to think about reverse dependencies.
> > 
> > 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?
> > 
> This morning it was brought to my attention that I was not being
> sufficiently responsive to this problem that I've created and that my
> communication came across as unconcerned.
> 
> Let me be the first to say that I would like to resolve this as quickly
> as painlessly as possible. It was suggested to me that I make a new
> upload with a version number like 2.1.0-1+really1.30.4.
> 
> This is something that I can do ASAP, and then restart by actually
> following the established transition process. Would that be
> OK/acceptable to the release team and to others affected by my mistake?

For the next time: please file a transition bug before uploading SONAME
changes to unstable. See also
https://wiki.debian.org/Teams/ReleaseTeam/Transitions. I am now turning
this into a transition bug report so that it is on our radar.

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.

Cheers
-- 
Sebastian Ramacher

--- End Message ---
--- Begin Message --- 
On 03/10/2025 08:49, Emilio Pozuelo Monfort wrote:

On 02/10/2025 15:17, Roberto C. Sánchez wrote:

On Mon, Sep 22, 2025 at 02:34:15PM +0200, Emilio Pozuelo Monfort wrote:


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


I have uploaded mongo-c-driver 2.1.1-1 yesterday and libmongocrypt
1.16.0-1 today, which should complete the transition. The libmongocrypt
builds only finished about an hour ago, so the transition tracker
doesn't show the updated status yet.

Is anything else needed in order to close this bug?


Probably just waiting at this point. If we find any blocker, we'll mention it.

Note that mongo-c-driver has migrated to testing, but not all the rdeps have
done it, so the old libs can't be removed yet. Let's see what happens once
libmongocrypt migrates.
The old library packages were removed from testing sometime ago, finishing the transition. 

Cheers,
Emilio

--- End Message ---
Reply to: