On 11/27/25 01:04, Gabriel Filion wrote:
..
Since you disagree with my closing of this bug, please
address update in bookworm separately.
ah oops, I must admit that I don't understand quite well how BTS should
handle these cases where more than one release is affected.
I understand from your response that you'd prefer I close this issue
again and open a new one aimed specifically? I'm OK with that plan!
Umh meh.
You don't understand how BTS should handle stuff but you try
to correct the maintainer. That's rather interesting way to
do things.
For the BTS, the bug is closed once a fix is uploaded to unstable.
This is exactly what we have here.
Sometimes, in rare cases, a bug can be open just for (old)stable,
if it isn't applicable for unstable. But these are rare. Maybe
this is the case here, - I guess it was your intention to file it
especially for bookworm, but I didn't understand it at the time.
In this case, I noticed this bug report, added a local note telling
me this bug should be dealt with in bookworm, and closed it, so I
wont spend more time analyzing it the next time I look for bugs, -
it is fixed in sid and in trixie already.
I don't prefer to close this issue again or open a new issue - it
is THE issue you reported and it's the one issue. I just noted
that it's fixed as far as BTS and sid and even stable are concerned,
with an internal note it should - maybe - be dealt with when/if
there's time for oldstable.
Either way.
Since there are a few security issuses in bookworm version of
unbound, I prepared a new release for oldstable, and included a
fix for this bug too. Hopefully it'll be accepted. So you don't
have to do anything with this bug report anymore.
But in any case, I'd strongly suggest to move on to the current
debian stable. Supporting old stuff in bookworm becomes more and
more a burden and less and less issues are fixed in there.
Thanks,
/mjt
