Bug#1035983: temporarily lower libsoup bug severity

Santiago Vila sanvila at debian.org
Sat Oct 24 00:46:34 BST 2026


tags 1035983 patch
severity 1035983 serious
thanks

On Fri, Oct 23, 2026 at 09:32:56PM +0200, Jeremy Bícha wrote:
> I have temporarily lowered the severity of these two RC bugs. I
> renamed the source package libsoup3 to libsoup. Once libsoup migrates
> to Testing, I'll raise the severity of these bugs to serious.

Hmm, but bugs are made RC precisely to prevent a buggy package to
propagate to testing, which is *exactly* the case here.

Moreover, Release Policy says this:

>   Tests must not be so flaky that they often cause others to waste
>   time investigating. A failure rate of > 20% on any release
>   architecture is not ok.

and I can definitely offer a VM running amd64 (a release architecture)
where this fails more than 20% of the time.

So: What about actually fixing the bug instead of allowing the buggy
package to be in testing again? I think it is about time.

The attached patch (to be applied with "git am") makes those "Address
already in use" errors not to happen anymore. It would be great if you
could test it and forward it upstream if it also works for you.

[ BTW: Please push the pending changes for 3.8.0-6 to salsa ].

Thanks.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-Fix-Address-already-in-use-AH00072-make_sock-could-n.patch
Type: text/x-diff
Size: 10055 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-gnome-maintainers/attachments/20261024/faab4aaa/attachment.patch>


More information about the pkg-gnome-maintainers mailing list