1. Forum
  2. Usenet
  3. LINUX.DEBIAN.DEVEL.MENTOR

  • Re: Package does not migrate to testing

    From Soren Stoutner@21:1/5 to Debian Mentors on Tue Jul 23 14:07:02 2024
    Copy: [email protected] (=?ISO-8859-1?Q?Preu=DFe=2C?= Hilmar)

    This is a multi-part message in MIME format.

    --nextPart15240937.g4l9VFMi3W
    Content-Transfer-Encoding: quoted-printable
    Content-Type: text/plain; charset="UTF-8"

    Preuße,

    Somehow the system didn’t pick up on the closure in the 1.0-0.1 changelog. I would
    suggest you manually mark it as fixed in 1.0-0.1 using:

    https://www.debian.org/Bugs/server-control#fixed[1]

    On Tuesday, July 23, 2024 1:12:42 PM MST Preuße, Hilmar wrote:
    Hi,

    for nq the excuse [1] currently reads

    Migration status for nq (- to 1.0-0.2): BLOCKED: Rejected/violates
    migration policy/introduces a regression
    Issues preventing migration:
    Updating nq would introduce bugs in testing: #1005961

    The bug has been closed in latest upload. What needs to be done?

    Hilmar

    https://qa.debian.org/excuses.php?package=nq
    --
    sigfault



    --
    Soren Stoutner
    [email protected]

    --------
    [1] https://www.debian.org/Bugs/server-control#fixed

    --nextPart15240937.g4l9VFMi3W
    Content-Transfer-Encoding: quoted-printable
    Content-Type: text/html; charset="UTF-8"

    <html>
    <head>
    <meta http-equiv="content-type" content="text/html; charset=UTF-8">
    </head>
    <body><p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">Preuße,</p>
    <br /><p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">Somehow the system didn’t pick up on the closure in the 1.0-0.1 changelog.&nbsp; I would suggest you manually mark it as fixed in 1.0-0.1 using:</p>
    <br /><p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;"><a href="https://www.debian.org/Bugs/server-control#fixed">https://www.debian.org/Bugs/server-control#fixed</a></p>
    <br /><p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">On Tuesday, July 23, 2024 1:12:42 PM MST Preuße, Hilmar wrote:</p>
    <p style="margin-top:0;margin-bottom:0;margin-l
  • From Soren Stoutner@21:1/5 to Debian Mentors on Tue Jul 23 14:33:07 2024
    Copy: [email protected] (=?ISO-8859-1?Q?Preu=DFe=2C?= Hilmar)

    On Tuesday, July 23, 2024 2:23:44 PM MST Preuße, Hilmar wrote:
    On 23.07.2024 23:07, Soren Stoutner wrote:

    Hello,


    Somehow the system didn’t pick up on the closure in the 1.0-0.1 changelog. I would suggest you manually mark it as fixed in 1.0-0.1
    using:


    The bug page itself [1] looks good and states:

    Found in versions fq/0.9.0-2, nq/0.3.1-4, fq/0.0.4-2
    Fixed in version nq/1.0-0.1
    Done: Hilmar Preuße <[email protected]>

    I can try again to close it, but I guess that won't help.

    [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005961

    Good catch.

    Looking more closely at the bug report, my guess is that the problem is the bug is reported against both the fq and nq packages. It is marked as fixed in nq, but not in fq. Debian ought to be smart enough to figure out this means that allowing nq into testing would resolve the problem for both packages, but it appears to not be.

    If I were you, I would just send an email to [email protected] with an explanation that the current version of nq resolves the issue for both packages. This would close the bug for all packages, which is different than marking it as fixed for one package.

    Alternately, you could mark it as fixed in the current version of fq.

    Soren

    --
    Soren Stoutner
    [email protected]
    -----BEGIN PGP SIGNATURE-----

    iQIzBAABCgAdFiEEJKVN2yNUZnlcqOI+wufLJ66wtgMFAmagIZMACgkQwufLJ66w tgMIHhAAnW5L1wSGp2DtxdsoyIwqyUm3C86sqUqhgFYdX/aM/jzQoPw8AXKk0KRb GJGUszUsnvNpG8sxDTCCYON3pbpMVbZW9GVrdesf0UpzCBqP12ikSGzRGl6MEnJ6 KA1UtOkYPTGh72+RNXR4zcOzSKE9LKyGwUshm7RosrFQfvv+KNCBhIX1xQFYkAFs 9/aNX7pPUL9L95s37e9TN0XssRIl6VFE+Xtxzy68kJ+tamTvI/QRdL0BsX+SXShM iicqA+dE0sttWYEZjTNheemZcBqzLJNAb+2MkOcBRgJE9gzaZN55/GntmoQKnerJ 2WNEzpbCzNPZxZfu7lrELH8wuDds3mlmc1TPtJpoPjf5xsX83l8ERlWhuYHDvmbE CDQmKgrWl6tGYc/kielmgSwgyjImbfrUWfvezF/YkZpaxepeiE2jU4NQPHqVbiM9 K6fxn7Tqjybhwn1wpW/2mqAtAxKEPgAEpHfdqbQeYOozWd2W89lnkY4iwEMHOPPs c0NbcXsNFDLAfAxv1Et8rqe/8Hfj6B3xghAfEnOYoMnY/IgM5LmW8dRmxaNlw6pL Y4LafH/6Jmp8qRBsCajvGbiHAnf5KJEZK7IzVQeqHTV6LAPqQWRhIUce27eJrN2l DPUFnUtSycYIgXJEQz6u/f2Nvq4rfW5NusWIT1BFOR+916gaT7U=
    =YkWM
    -----END PGP SIGNATURE-----

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