severity 1105067 serious tags 1105067 - unreproducible thanks
I'm removing the unreproducible tag because I see you were finally able to reproduce it here: https://github.com/sni/Monitoring-Livestatus/issues/9#issuecomment-2869534907 I'm also restoring the serious severity because packages in trixie must build in trixie. I'm going to answer to your emails from yesterday in the hope you can see now what went wrong here: El 11/5/25 a las 6:53, Sebastiaan Couwenberg escribió:
provide the steps to reproduce the issue ourselves
I did that in the very first email, I'll quote myself:
This is the first time I'm doing an archive rebuild with autobuilders running trixie, not sure if this is a variable to consider.
So, I was running trixie, and I *specifically* said so, it was not until you tried trixie as well (as noted in the github issue) that you were able to reproduce the bug as well.
the package also builds fine in the schroot environments on the porterboxes.
The porter boxes are running the kernel of bookworm, which explains why you were unable to reproduce the problem there. But once we release trixie as stable, the porter boxes and the official buildds will also be upgraded to trixie, and then the package would fail to build in stable, which is a violation of Release Policy when it says that packages in stable must build in stable. And that's why this bug should be fixed in unstable. I'm not reopening again because we have version tracking. Please note that this is the last time I fix the wrong metadata. If you still disagree that this should be fixed in unstable to be part of trixie, I will probably have to call the TC or the Release Managers. Thanks.
