[pkg-go] libpod 4.8.3+ds1-2 MIGRATED to testing
FYI: The status of the libpod source package in Debian's testing distribution has changed. Previous version: 4.7.2+ds1-2 Current version: 4.8.3+ds1-2 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will receive later changes on the next day. See https://release.debian.org/testing-watch/ for more information. ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-go-maintainers
[pkg-go] Bug#1061383: Fwd: [Podman] Podman v4.9.0 Released
Package: libpod Severity: wishlist -- Forwarded message - From: Ashley Cui Date: Mon, Jan 22, 2024, 21:00 Subject: [Podman] Podman v4.9.0 Released To: , We’re excited to announce that Podman v4.9.0 has been released! Here's what's new: Features - The podman farm suite of commands for multi-architecture builds is now fully enabled and documented. - Add a network recovery service to Podman Machine VMs using the QEMU backend to detect and recover from an inoperable host networking issues experienced by Mac users when running for long periods of time. Bugfixes - Fixed a bug where the HyperV provider for podman machine did not forward the API socket to the host machine. - Fixed a bug where improperly formatted annotations passed to podman kube play could cause Podman to panic. - Fixed a bug where podman system reset could fail if non-Podman containers (e.g. containers created by Buildah) were present. Misc - Containers run in podman machine VMs now default to a PID limit of unlimited, instead of 2048. Try it out and let us know what you think! -- Ashley Cui ___ Podman mailing list -- pod...@lists.podman.io To unsubscribe send an email to podman-le...@lists.podman.io ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-go-maintainers
[pkg-go] Processed: Re: Bug#1061194: podman: cannot run rootful containers with many layers using overlay driver
Processing control commands: > reassign -1 src:golang-github-containers-storage 1.43.0+ds1-8 Bug #1061194 [podman] podman: cannot run rootful containers with many layers using overlay driver Bug reassigned from package 'podman' to 'src:golang-github-containers-storage'. No longer marked as found in versions libpod/4.3.1+ds1-8. No longer marked as fixed in versions 4.4.0. Bug #1061194 [src:golang-github-containers-storage] podman: cannot run rootful containers with many layers using overlay driver Marked as found in versions golang-github-containers-storage/1.43.0+ds1-8. > fixed -1 1.45.1+ds1-1 Bug #1061194 [src:golang-github-containers-storage] podman: cannot run rootful containers with many layers using overlay driver Marked as fixed in versions golang-github-containers-storage/1.45.1+ds1-1. > affects -1 src:libpod Bug #1061194 [src:golang-github-containers-storage] podman: cannot run rootful containers with many layers using overlay driver Added indication that 1061194 affects src:libpod -- 1061194: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061194 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-go-maintainers
[pkg-go] Bug#1061194: podman: cannot run rootful containers with many layers using overlay driver
Control: reassign -1 src:golang-github-containers-storage 1.43.0+ds1-8 Control: fixed -1 1.45.1+ds1-1 Control: affects -1 src:libpod On Sun, Jan 21, 2024 at 01:17:46AM +0800, Tee Hao Wei wrote: > Oh. I just noticed how Debian handles Go dependencies.. > > I guess this will actually need to be a cherry-pick to > golang-github-containers-storage-dev followed by a rebuild of podman. That's right, this is technically a golang-github-containers-storage-dev bug, so reassigning there. FWIW: $ git describe --contains 7c5964df95c892cfbdbce594cf5a8e2973c70fd7 v1.44.0~28^2 $ git describe --contains d232b36652d55b42a21f1713db7f7d455b837b3c v1.44.0~9^2 $ git checkout v1.43.0 HEAD is now at 04d8b90f9 Bump to v1.43.0 $ git cherry-pick 7c5964df95c892cfbdbce594cf5a8e2973c70fd7 d232b36652d55b42a21f1713db7f7d455b837b3c [...] $ $ git diff --stat v1.43.0.. drivers/overlay/mount.go | 97 - drivers/overlay/overlay.go | 50 tests/layers.bats | 40 +-- 3 files changed, 143 insertions(+), 44 deletions(-) I think that's big enough to make me at least a bit uncomfortable about a cherry-pick to stable. Could you elaborate on your use case? It sounds like this manifests only with a large number of layers, and I'm not sure how common this is. The alternative to a stable update is a backport of the latest podman version (currently 4.8.3), plus associated packages like containers/storage, of course. It's a moderate amount of work; Reinhard who's been doing the version updates in unstable could speak more to the work he's been putting into package updates etc. It would help with bringing in a lot of more fixes from what I'd consider a very active upstream. We also have #1059496, as another recent, concrete example. I'm still unsure and debating targeted s-p-u fixes vs. a backport. My concern is basically that we may start playing whack-a-mole. A quick peek at the upstream changelog reveals tons of fixed bugs in every release, and us trying to keep up by cherry-picking fixes to two years of upstream development may prove futile... Thoughts? Thanks, Faidon ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-go-maintainers
