• Bug#1106898: mongo-c-driver: Needs unblock to migrate, blocks syslog-ng

    From Roberto =?iso-8859-1?Q?C=2E_S=E1nch@21:1/5 to All on Sat May 31 23:00:01 2025
    On Sat, May 31, 2025 at 06:58:54PM +0200, Chris Hofstädtler wrote:
    Source: mongo-c-driver
    Version: 1.30.4-1
    Severity: serious
    Control: affects -1 src:syslog-ng
    X-Debbugs-CC: syslog-ng@packages.debian.org

    Hi,

    mongo-c-driver was uploaded over 23days ago, but cannot migrate to
    trixie as it has no autopkgtest. Instead an unblock request needs to
    be filed.

    That is really quite surprising to me. When I uploaded to unstable last
    on 2025-05-07 we were still in the soft freeze. I checked the PTS 2 or 3
    days following the upload and it showed a 10 day migration delay.
    Nothing in the freeze policy seems to suggest that I would have needed
    to request an unblock.

    Then, it seems, on 2025-05-18, the hard freeze was announced. But in
    past release cycles the implementation of a new stage of the freeze
    would only apply to packages uploaded *after* that stage of the freeze
    had been entered. Packages uploaded prior would still be handled
    according to the policy of the stage in effect when the upload was made.
    At least that's my recollection.

    In the meantime syslog-ng was uploaded to unstable, and was built
    against the newer mongo-c-driver. The syslog-ng upload fixes a
    security bug, and now cannot migrate until mongo-c-driver migrates.

    Please do something about this situation.


    In any event, I will shortly request an unblock.

    Regards,

    -Roberto
    --
    Roberto C. Sánchez
    http://people.connexer.com/~roberto
    http://www.connexer.com

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Chris Hofstaedtler@21:1/5 to All on Sun Jun 1 13:20:01 2025
    On Sat, May 31, 2025 at 04:49:25PM -0400, Roberto C. Sánchez wrote:
    Then, it seems, on 2025-05-18, the hard freeze was announced. But in
    past release cycles the implementation of a new stage of the freeze
    would only apply to packages uploaded *after* that stage of the freeze
    had been entered. Packages uploaded prior would still be handled
    according to the policy of the stage in effect when the upload was made.
    At least that's my recollection.

    My memory tells me this was never how it worked. Paul also mentioned
    a number of times (to me / in public) that britney has no support
    to apply different timeline policies based on the upload date or
    similar.

    Thanks for taking care of it.

    Chris

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)