Dear maintainer, I would like to request a stable-backport of the passt package. We have been using pasta for rootless Podman networking on GitLab runners, and have found that when using the version currently packaged for trixie, on very busy runners with many containers spawning and despawning, the process will eventually starts leave unclosed TCP sockets that accumulate until we're plagued with connection errors from within containers. Using the package from unstable allows us to work around the issue, but we would prefer using a proper backport. Thanks!
Hi Jérôme, Thanks for the report. Did you already identify a set of patches that would fix this? This smells like https://bugs.passt.top/show_bug.cgi?id=179, which would be fixed by these commits: https://passt.top/passt/log/?qt=range&q=eb3babf7b4cf3793e0ed48030db958ace6546d7e..d2f7c21cfb949f2b1587b9475917efdd6ac549fd I haven't checked how involved a backport would be in this case, even though at a glance I'd say it should be doable.
Hi Jérôme, Thanks for the report. Did you already identify a set of patches that would fix this? This smells like https://bugs.passt.top/show_bug.cgi?id=179, which would be fixed by these commits: https://passt.top/passt/log/?qt=range&q=eb3babf7b4cf3793e0ed48030db958ace6546d7e..d2f7c21cfb949f2b1587b9475917efdd6ac549fd I haven't checked how involved a backport would be in this case, even though at a glance I'd say it should be doable.
Hi Stefano, Unfortunately I didn't bisect the upstream repo so I haven't identified any commits or patchsets that fix the problem. I can only say with confidence that the package from unstable doesn't exhibit the problem. Thanks. Le 2026-08-13 à 07 h 29, Stefano Brivio a écrit :
Hi Stefano, Unfortunately I didn't bisect the upstream repo so I haven't identified any commits or patchsets that fix the problem. I can only say with confidence that the package from unstable doesn't exhibit the problem. Thanks. Le 2026-08-13 à 07 h 29, Stefano Brivio a écrit :
Hello, Le 2026-08-13 à 07 h 29, Stefano Brivio a écrit : I can confirm this is a trivial backport. I've pushed an debian/trixie-backport branch with a prepared NMU here: https://salsa.debian.org/lavamind/passt/-/tree/debian/trixie-backports/ If you're OK with it I can handle the upload itself. Thanks,
Hello, Le 2026-08-13 à 07 h 29, Stefano Brivio a écrit : I can confirm this is a trivial backport. I've pushed an debian/trixie-backport branch with a prepared NMU here: https://salsa.debian.org/lavamind/passt/-/tree/debian/trixie-backports/ If you're OK with it I can handle the upload itself. Thanks,
Hi Jérôme, Just one question: on that branch, I can only find a changelog commit, but not the actual backport. Is it on another branch, or not committed yet, perhaps?
Hi Jérôme, Just one question: on that branch, I can only find a changelog commit, but not the actual backport. Is it on another branch, or not committed yet, perhaps?
Hi Stefano, Le 2026-09-09 à 13 h 46, Stefano Brivio a écrit : are satisfiable in stable, and the package builds correctly in a stable chroot. In such cases, there are no patches nor modifications to d/control to implement, just a changelog entry and an upload.
Hi Stefano, Le 2026-09-09 à 13 h 46, Stefano Brivio a écrit : are satisfiable in stable, and the package builds correctly in a stable chroot. In such cases, there are no patches nor modifications to d/control to implement, just a changelog entry and an upload.
On Wed, 9 Sep 2026 14:29:09 -0400 Jérôme Charaoui <jerome@riseup.net> wrote: Hah, sorry, I misread, I see what you mean now. Thanks for making it obvious for me. I thought you wanted to backport the specific fix, instead of making an updated version available in trixie-backports. By all means, please go ahead!
On Wed, 9 Sep 2026 14:29:09 -0400 Jérôme Charaoui <jerome@riseup.net> wrote: Hah, sorry, I misread, I see what you mean now. Thanks for making it obvious for me. I thought you wanted to backport the specific fix, instead of making an updated version available in trixie-backports. By all means, please go ahead!