From debian-bts-link at lists.debian.org Wed May 13 03:41:26 2026 From: debian-bts-link at lists.debian.org (debian-bts-link at lists.debian.org) Date: Wed, 13 May 2026 02:41:26 +0000 Subject: [pkg-go] [bts-link] source package debos Message-ID: <177864008683.612821.2997220751478962600.btslink@sonntag.debian.org> # # bts-link upstream status pull for source package debos # see http://lists.debian.org/debian-devel-announce/2006/05/msg00001.html # https://bts-link-team.pages.debian.net/bts-link/ # user debian-bts-link at lists.debian.org # remote status report for #1070762 (http://bugs.debian.org/1070762) # Bug title: debos: unhelpful error message "Modules path couldn't be determined" # * https://github.com/go-debos/fakemachine/pull/298 # * remote status changed: (?) -> closed # * closed upstream tags 1070762 + fixed-upstream usertags 1070762 + status-closed thanks From owner at bugs.debian.org Wed May 13 03:45:20 2026 From: owner at bugs.debian.org (Debian Bug Tracking System) Date: Wed, 13 May 2026 02:45:20 +0000 Subject: [pkg-go] Processed: [bts-link] source package debos References: <177864008683.612821.2997220751478962600.btslink@sonntag.debian.org> Message-ID: Processing commands for control at bugs.debian.org: > # > # bts-link upstream status pull for source package debos > # see http://lists.debian.org/debian-devel-announce/2006/05/msg00001.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-link at lists.debian.org Setting user to debian-bts-link at lists.debian.org (was debian-bts-link at lists.debian.org). > # remote status report for #1070762 (http://bugs.debian.org/1070762) > # Bug title: debos: unhelpful error message "Modules path couldn't be determined" > # * https://github.com/go-debos/fakemachine/pull/298 > # * remote status changed: (?) -> closed > # * closed upstream > tags 1070762 + fixed-upstream Bug #1070762 [debos] debos: unhelpful error message "Modules path couldn't be determined" Added tag(s) fixed-upstream. > usertags 1070762 + status-closed There were no usertags set. Usertags are now: status-closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 1070762: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070762 Debian Bug Tracking System Contact owner at bugs.debian.org with problems From debian-bts-link at lists.debian.org Wed May 13 03:41:27 2026 From: debian-bts-link at lists.debian.org (debian-bts-link at lists.debian.org) Date: Wed, 13 May 2026 02:41:27 +0000 Subject: [pkg-go] [bts-link] source package podman Message-ID: <177864008740.612821.1093540400187762435.btslink@sonntag.debian.org> # # bts-link upstream status pull for source package podman # see http://lists.debian.org/debian-devel-announce/2006/05/msg00001.html # https://bts-link-team.pages.debian.net/bts-link/ # user debian-bts-link at lists.debian.org # remote status report for #1133420 (http://bugs.debian.org/1133420) # Bug title: podman: PublishPort= on ::1 doesn't work # * https://github.com/containers/netavark/issues/790 # * remote status changed: (?) -> closed # * closed upstream tags 1133420 + fixed-upstream usertags 1133420 + status-closed thanks From owner at bugs.debian.org Wed May 13 03:47:36 2026 From: owner at bugs.debian.org (Debian Bug Tracking System) Date: Wed, 13 May 2026 02:47:36 +0000 Subject: [pkg-go] Processed: [bts-link] source package podman References: <177864008740.612821.1093540400187762435.btslink@sonntag.debian.org> Message-ID: Processing commands for control at bugs.debian.org: > # > # bts-link upstream status pull for source package podman > # see http://lists.debian.org/debian-devel-announce/2006/05/msg00001.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-link at lists.debian.org Setting user to debian-bts-link at lists.debian.org (was debian-bts-link at lists.debian.org). > # remote status report for #1133420 (http://bugs.debian.org/1133420) > # Bug title: podman: PublishPort= on ::1 doesn't work > # * https://github.com/containers/netavark/issues/790 > # * remote status changed: (?) -> closed > # * closed upstream > tags 1133420 + fixed-upstream Bug #1133420 [podman] podman: PublishPort= on ::1 doesn't work Added tag(s) fixed-upstream. > usertags 1133420 + status-closed There were no usertags set. Usertags are now: status-closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 1133420: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1133420 Debian Bug Tracking System Contact owner at bugs.debian.org with problems From postmaster at europeanwatercommunity.pt Wed May 13 08:12:54 2026 From: postmaster at europeanwatercommunity.pt (Aok.de) Date: Wed, 13 May 2026 16:12:54 +0900 (JST) Subject: [pkg-go] Ihre Rueckerstattung steht bereit Message-ID: <20260513071254.93AEAE27FD@off.europeanwatercommunity.pt> An HTML attachment was scrubbed... URL: From gioele at debian.org Thu May 14 00:30:53 2026 From: gioele at debian.org (Gioele Barabucci) Date: Thu, 14 May 2026 01:30:53 +0200 Subject: [pkg-go] Bug#1136557: podman uses pidof but does not depend on procps Message-ID: <1bd4685363bf0b70bcf97515313d7a3d@debian.org> Source: podman Version: 5.8.2+ds1-1 Usertags: pidof-without-procps Dear maintainer(s) of podman, it appears that podman uses `pidof` in its testsuite, or that at least one of its binary packages uses `pidof` at runtime. Historically, `pidof` was provided by the Essential package `sysvinit-tools`, making an explicit dependency unnecessary. However `pidof` will soon be moved to `procps` and will no longer be part of the Essential set. Please add an explicit dependency on `procps`: * via the `Depends:` field of all binary packages of podman that use `pidof` at runtime; * via the `Build-Depends:` field of podman, if `pidof` is used in tests run at build-time; * via the `Depends:` field of `debian/control/tests`, if `pidof` is used in autopkgtests. To prevent any disruption for users of podman, please add this dependency now, before `pidof` is moved from `sysvinit-utils` to `procps`. Alternatively, you could remove all uses of `pidof`. It is believed that podman uses `pidof` due to the following code snippets: ``` path: podman_5.7.0+ds2-3/test/apiv2/python/rest_api/test_v2_0_0_container.py out = r.json() self.assertIsNotNone(out["State"].get("Health")) self.assertListEqual(["CMD", "pidof", "top"], out["Config"]["Healthcheck"]["Test"]) self.assertEqual(5000000000, out["Config"]["Healthcheck"]["Interval"]) self.assertEqual(2000000000, out["Config"]["Healthcheck"]["Timeout"]) path: podman_5.7.0+ds2-3/test/apiv2/python/rest_api/test_v2_0_0_container.py out = r.json() hc = out["Config"]["Healthcheck"]["Test"] self.assertListEqual(["CMD", "pidof", "top"], hc) r = requests.post(self.podman_url + f"/v1.40/containers/{container_id}/start") path: podman_5.7.0+ds2-3/test/apiv2/python/rest_api/test_v2_0_0_container.py "Image": "alpine:latest", "Healthcheck": { "Test": ["CMD", "pidof", "top"], "Interval": 5000000000, "Timeout": 2000000000, ``` Feel free to close this issue if this is a false positive (for example if this code is in an unreachable code path). Regards, -- Gioele Barabucci