Hi On 2022-09-21 10:13:42 -0500, Christian Barcenas wrote: > Hi. > > I am not an expert on Debian policy, so the following may be incorrect, > but this was my reasoning for re-opening the bug: > > On Wed, Sep 21, 2022 at 2:21 AM Sebastian Ramacher <sramac...@debian.org> > wrote: > > Please don't reopen it. We have version tracking to track this kind of > > thinks. For the bullseye version, the bug was still open. Reclosing. > > As far as I can see, this issue is fixed in bookworm because 1:1.3.2-1 > has an upstream fix, there is no fix at all to this issue in > stable 1:1.2.1-4+deb11u1. > > Aren't FTBFS, and other critical software bugs that prevent runtime > use of the library entirely, considered a serious Debian policy violation > that should be fixed with an upload to stable-proposed-updates?
Yes, that's all correct. But as you can see from the version graph at the top of the bug report at https://bugs.debian.org/1011716, the version in stable is not marked as fixed. There is no need to reopen this bug report because it is still open in stable. Cheers -- Sebastian Ramacher
