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 <hill...@debian.org> > > 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 1005961-d...@bugs.debian.org 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 so...@debian.org
signature.asc
Description: This is a digitally signed message part.
