[pkg-go] consul 1.8.7+dfsg1-5 MIGRATED to testing

FYI: The status of the consul source package in Debian's testing distribution has changed. Previous version: 1.8.7+dfsg1-3 Current version: 1.8.7+dfsg1-5 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you

[pkg-go] libpod is marked for autoremoval from testing

libpod 3.4.4+ds1-1 is marked for autoremoval from testing on 2022-05-10 It (build-)depends on packages with these RC bugs: 1008396: consul: FTBFS: 2022/03/26 19:15:04 internal error: package "fmt" without types was imported from "github.com/hashicorp/consul/agent/cache-types"

[pkg-go] golang-github-opencontainers-runtime-tools_0.9.0+dfsg-4_source.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 15 Apr 2022 20:06:55 -0400 Source: golang-github-opencontainers-runtime-tools Architecture: source Version: 0.9.0+dfsg-4 Distribution: unstable Urgency: medium Maintainer: Debian Go Packaging Team Changed-By:

[pkg-go] Processing of golang-github-opencontainers-runtime-tools_0.9.0+dfsg-4_source.changes

golang-github-opencontainers-runtime-tools_0.9.0+dfsg-4_source.changes uploaded successfully to localhost along with the files: golang-github-opencontainers-runtime-tools_0.9.0+dfsg-4.dsc golang-github-opencontainers-runtime-tools_0.9.0+dfsg-4.debian.tar.xz Greetings, Your Debian

[pkg-go] Processed: reassign 1007022 to runc, affects 1007022

Processing commands for cont...@bugs.debian.org: > reassign 1007022 runc Bug #1007022 [podman] podman: starting rootless container fails with: can't get final child's PID from pipe: EOF Bug reassigned from package 'podman' to 'runc'. No longer marked as found in versions libpod/3.4.4+ds1-1.

[pkg-go] Bug#1009376: running foreign architecture containers hits the network every time and confuses future `podman run` invocations

Control: tag -1 upstream Hi Antonio, Can you please file a report upstream here: https://github.com/containers/podman/issues -- upstream is really friendly with reports from other Distros, in particular from Debian. I'm not sure what value I can bring as a package maintainer here. Thanks.

[pkg-go] Processed: Re: Bug#1009376: running foreign architecture containers hits the network every time and confuses future `podman run` invocations

Processing control commands: > tag -1 upstream Bug #1009376 [podman] running foreign architecture containers hits the network every time and confuses future `podman run` invocations Ignoring request to alter tags of bug #1009376 to the same tags previously set -- 1009376:

[pkg-go] Processed: Re: Bug#1009376: running foreign architecture containers hits the network every time and confuses future `podman run` invocations

Processing control commands: > tag -1 upstream Bug #1009376 [podman] running foreign architecture containers hits the network every time and confuses future `podman run` invocations Added tag(s) upstream. -- 1009376: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009376 Debian Bug Tracking

[pkg-go] Bug#1005258: marked as done (podman: current podman version does not pass seccomp options to buildah)

Your message dated Fri, 15 Apr 2022 17:19:36 -0400 with message-id and subject line Stable update should fix this as well has caused the Debian Bug report #1005258, regarding podman: current podman version does not pass seccomp options to buildah to be marked as done. This means that you claim

[pkg-go] Bug#995777: marked as done (podman: Cannot (effectively) use containers with glibc 2.33.9000 or newer)

Your message dated Fri, 15 Apr 2022 17:17:08 -0400 with message-id and subject line Re: Bug#995777: podman: Cannot (effectively) use containers with glibc 2.33.9000 or newer has caused the Debian Bug report #995777, regarding podman: Cannot (effectively) use containers with glibc 2.33.9000 or