[pkg-go] Bug#1070727: reportbug: podman does not run wasm/wasi images because of missing crun-wasm - easy fix

Thanks for looking into this, On Sat, May 11, 2024 at 6:00 AM Faidon Liambotis wrote: > Control: tags -1 confirmed > > On Wed, May 08, 2024 at 03:10:40AM +0300, Eugen Stan wrote: > > I followed the guide to run wasm images on my system and it failed with > > errors. > > > > I believe the issue

[pkg-go] Bug#1069310: FTBFS: tests failed

I spent about half an hour looking at this, and wanted to share my thoughts: - the build / tests succeed on all architectures but mips64el - the panic in question appears to come from here: https://sources.debian.org/src/golang-github-hanwen-go-fuse/2.4.2-2/fuse/print_linux.go/#L13 -- a

[pkg-go] Bug#1067186: Fwd: [Podman] Podman v5.0.0 Released

Package: libpod Severity: wishlist -- Forwarded message - From: Matt Heon Date: Tue, Mar 19, 2024, 19:13 Subject: [Podman] Podman v5.0.0 Released To: , Podman List Hi all, Podman v5.0.0 has just been released. This is our first major version bump in two years, and comes with

[pkg-go] Bug#1062598: libpod: Add support for LoongArch

Control: forwarded -1 https://github.com/containers/podman/pull/21481 Control: severity -1 minor On Mon, Feb 5, 2024 at 5:51 AM Faidon Liambotis wrote: > On Mon, Feb 05, 2024 at 02:13:50PM +0800, 张家岭 wrote: > > Hi, this can support loong64 build , Ｉ build this in my local . and > I'll submit

[pkg-go] Bug#1062529: Fwd: [containers/podman] Release v4.9.1 - v4.9.1

Package: libpod Severity: wishlist -- Forwarded message - From: Ashley Cui Date: Thu, Feb 1, 2024, 09:12 Subject: [containers/podman] Release v4.9.1 - v4.9.1 To: containers/podman Cc: Subscribed v4.9.1 Repository:

[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

[pkg-go] Bug#1057618: Fwd: [containers/podman] Release v4.8.1 - v4.8.1

I'm currently blocked on packaging this new upstrema version because of a new dependency that was added in https://github.com/containers/podman/commit/289e59ee1fbbf95dc5d6b370adf9e951acf157bf I've packaged github.com/containers/gvisor-tap-vsock and as soon as #1057435 passes NEW, expect an upload

[pkg-go] Bug#1057618: Fwd: [containers/podman] Release v4.8.1 - v4.8.1

Package: libpod -- Forwarded message - From: Lokesh Mandvekar Date: Tue, Dec 5, 2023 at 6:49 AM Subject: [containers/podman] Release v4.8.1 - v4.8.1 To: containers/podman Cc: Subscribed v4.8.1 Repository:

[pkg-go] Bug#1053131: Status Update

I've started packaging all dependencies up to buildah and have updated the repository for 4.7.1 in the branch debian/experimental, commit e71d62879 Here is where I'm currently at: src/github.com/containers/podman/pkg/machine/fcos.go:17:2: cannot find package

[pkg-go] Bug#1053131: Fwd: [containers/podman] Release v4.7.0 - v4.7.0

Package: libpod severity: wishlist -- Forwarded message - From: Lokesh Mandvekar Date: Wed, Sep 27, 2023 at 2:02 PM Subject: [containers/podman] Release v4.7.0 - v4.7.0 To: containers/podman Cc: Subscribed v4.7.0

[pkg-go] Bug#1034590: precedence of /etc/containers/storage.conf should higher than /usr/share/containers/storage.conf

Control: tag -1 upstream Hi, Thanks for taking the time to report this. It doesn't sound like a problem that we could fix in the packaging, but needs some code changes. For this, I'd like to ask you a favor. Can you please check if this was reported before at

[pkg-go] Bug#1042090: podman: fails to start container with userns mapping

Control: tag -1 +upstream +moreinfo Hi Hristo, Thanks for taking the time to report this issue. In the meantime, podman 4.5 is now in debian/testing (and 4.6.2 in debian/experimental). Can you please upgrade your package and give it another try? If you're right, you shouldn't see this issue

[pkg-go] Bug#1037091: podman run fails because of missing ~/.config/docker/config.json

Control: tag -1 +moreinfo +unreproducible Hi Felix, thanks for taking the time to write a bug report to Debian. I'm sorry to hear that podman does not work for you as you'd expect. It seems to me that you may have an old, possibly modified installation of podman on your system, and I'd expect

[pkg-go] Bug#1050993: podman: Podman should use overlay storage driver by default instead of vfs

Hi Gregor, On Wed, Sep 13, 2023 at 3:03 AM Gregor Riepl wrote: > As mentioned in the upstream bug report[1], the fix is actually in > containers/storage 1.48, included with podman 4.6 and not 4.5. > > So, the bug can (hopefully) be fixed for good when this version is > packaged. > I've now

[pkg-go] Bug#1051409: podman: Podman man pages use en-dash instead of dash

Control: reassign -1 go-md2man-v2 stop Thanks for your report Guy, All manpages in podman are written in markdown, and you can review the sources at https://github.com/containers/podman/blob/main/docs/source/Introduction.rst -- as you can see the sources do not contain any unicode characters. I

[pkg-go] Bug#1034871: podman: "sudo podman system reset" can delete current working directory

Control: tag -1 +upstream Control: forwarded -1 https://github.com/containers/podman/issues/18349 Control: severity -1 important On Wed, Apr 26, 2023 at 6:48 AM Jan Hendrik Farr wrote: > Package: podman > Version: 4.3.1+ds1-6+b2 > Severity: normal > Tags: newcomer > X-Debbugs-Cc:

[pkg-go] Bug#1034026: podman-docker: missing /usr/share/user-tmpfiles.d/podman-docker.conf

Control: tag -1 help On Thu, Apr 6, 2023 at 2:06 PM Scott Edlund wrote: > podman-docker.conf was configured for use with rootless podman starting > in 4.3.0rc1 . Please install the tmpfiles configuration also in > user-tmpfiles. > > See > >

[pkg-go] Bug#1033826: podman: Cannot load gzip compressed images

Control: reassign -1 golang-github-klauspost-pgzip 1.2.5-2 Control: affects -1 libpod Control: forwarded -1 https://github.com/containers/podman/issues/15944 Control: severity -1 important Hi Antonio, Thanks for your report. I've looked through the source code, and while the exact error message

[pkg-go] Bug#1030930: podman: DNS resolution fails in 'podman build' but works in 'podman run'

Control: tag -1 + unreproducible moreinfo Hi Kevin, great to hear from you in this space! On Thu, Feb 9, 2023 at 8:36 AM Kevin P. Fleming wrote: > Package: podman > Version: 4.3.1+ds1-5+b1 > Severity: important > > Dear Maintainer, > > I am seeing DNS resolution fail when using 'podman build'

[pkg-go] Bug#1024809: podman systemd service running as user deletes socket file on termination

Control: tag -1 upstream Hi Antoine, Thanks for testing the podman package. On Fri, Nov 25, 2022 at 12:15 PM Antoine Musso wrote: > Package: podman > Version: 3.0.1+dfsg1-3+deb11u1 > Severity: normal > > Dear Maintainer, > > I went to try running podman as a normal user using the systemd

[pkg-go] Bug#1020540: podman-remote should be built and offered as seperate package

On Thu, Sep 22, 2022 at 7:00 PM Norbert Lange wrote: > Package: podman > Version: 4.2.1-0.1 > Severity: minor > Tags: patch > X-Debbugs-Cc: nolang...@gmail.com > > Hello, > > I am aware of #1000521, I dont see it as resolved. > > The problem is that you can run podman as service, and clients >

[pkg-go] Bug#1017766: podman: Failed to activate DNS. Missing dependency on golang-github-containernetworking-plugin-dnsname

Hi Michael, On Sat, Aug 20, 2022 at 5:47 PM Michael Musenbrock < michael.musenbr...@gmx.at> wrote: > > > Now a dns-server is active in the network, but the other pods attached to > the network > still can't be resolved. But this may be just some config issue. I will > check. > > just checking

[pkg-go] Bug#1017766: podman: Failed to activate DNS. Missing dependency on golang-github-containernetworking-plugin-dnsname

>From the list of packages in your big report i see that the packages netavark and aardvark-dns are absent. Does installing them work for your without the golang-github-containernetworking-plugin-dnsname package? One of the main major changes in podman 4 is the rust based networking stack. It

[pkg-go] Bug#1009776: podman: Packages uidmap and slirp4netns should be full dependencies

Control: tag -1 wontfix On Fri, May 6, 2022 at 7:03 PM Andrej Shadura < andrew.shad...@collabora.co.uk> wrote: > > > Indeed. When I ran into this in #983395, I was told here I’m supposed to > use sudo (or install Recommends, which IIRC are disabled in Docker > images), while the upstream told me

[pkg-go] Bug#1009747:

Hi Anatoli, Sorry to hear that you had bad surprises with the podman package, but I'm happy to read in https://github.com/containers/podman/issues/12983#issuecomment-1119662438 that you managed to get the software working by rebooting. This tells me that those warnings correctly indicated a

[pkg-go] Bug#1012030: (no subject)

shortly. On Tue, May 31, 2022 at 12:10 AM Shengjing Zhu wrote: > On Tue, May 31, 2022 at 3:33 AM Reinhard Tartler > wrote: > > > > > > I wonder whether this may be related to upstream report at > https://github.com/containers/common/issues/631 > > > > I

[pkg-go] Bug#1011875: golang-github-opencontainers-runtime-tools: FTBFS unreproducible

My hunch might have been correct, the fresh upload did build successfully on buildds. yay! On Sun, Jun 5, 2022 at 7:12 AM Reinhard Tartler wrote: > Just a hunch, is it possible that your build environment did not have the > package 'ca-certificates' present whereas mine does? > &

[pkg-go] Bug#1011875: golang-github-opencontainers-runtime-tools: FTBFS unreproducible

Just a hunch, is it possible that your build environment did not have the package 'ca-certificates' present whereas mine does? I wonder whether I need to add 'ca-certificates' to "Build-Depends". What do you think? On Sun, Jun 5, 2022 at 7:10 AM Reinhard Tartler wrote: >

[pkg-go] Bug#1011875: golang-github-opencontainers-runtime-tools: FTBFS unreproducible

Please find the buildlog of my attempt attached to this email As far as I can tell, the tests are executing in the same way as in your logs, but I may be missing something. golang-github-opencontainers-runtime-tools_0.9.0+git20220423.g0105384-1_amd64-2022-06-05T02:02:05Z.build Description:

[pkg-go] Bug#1011875: golang-github-opencontainers-runtime-tools: FTBFS unreproducible

Control: tags -1 = moreinfo unreproducible Hi Lucas, Thank you for reaching out. I've been looking into this report and am a bit confused. I'm trying to reproduce it on my laptop, but it builds just fine for me. Can you please help me understand why it would fail on your end? -- regards,

[pkg-go] Bug#1012030: (no subject)

I wonder whether this may be related to upstream report at https://github.com/containers/common/issues/631 It seems that in debian/bullseye, podman is only able to work in crun, since the version of runc we have in stable seems to have issues with seccomp. Can you please try the following for me

[pkg-go] Bug#1009776: podman: Packages uidmap and slirp4netns should be full dependencies

Control: tag -1 upstream Control: severity -1 minor On Sun, Apr 17, 2022 at 9:09 AM Giuseppe wrote: > Package: podman > Version: 3.0.1+dfsg1-3+deb11u1 > Severity: important > X-Debbugs-Cc: peppecal+debianb...@gmail.com > > Dear Maintainer, > > I really think packages uidmap and slirp4netns

[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] Bug#1005839: undefined reference to `reflect.unsafe_New' #21

Package: golang-github-modern-go-concurrent-dev Version: 1.0.3-1.1_all Affects: golang-github-containers-buildah The package golang-github-containers-buildah 1.24.1+ds1-1 fails to build in experimental with undefined references. This appears to affect all architectures that use gccgo instead fo

[pkg-go] Bug#1004289: libpod package stops buld at override_dh_auto_build

Can you reproduce this in a sid chroot? May I ask you why you marked this issue as 'important'? -- Unfortunately I do not have the capacity to support builds for backports. Best regards, -rt On Mon, Jan 24, 2022 at 7:33 AM Elimar Riesebieter wrote: > Source: libpod > Version: 3.4.4=ds1 >

[pkg-go] Bug#1000521: libpod: please provide podman-remote binary

Hi Antonio, thanks for reaching out, On Wed, Nov 24, 2021 at 8:45 AM Antonio Terceiro wrote: > Source: libpod > Version: 3.4.1+ds1-2 > Severity: wishlist > > Dear Maintainer, > > Recent podman upstream releases provide a new podman-remote binary, but > the Debian package does not even build

[pkg-go] Bug#1003486: Fwd: [containers/podman] Pre-release v4.0.0-rc1 - v4.0.0-RC1

Package: libpod Severity: wishlist -- Forwarded message - From: Matthew Heon Date: Mon, Jan 10, 2022 at 4:50 PM Subject: [containers/podman] Pre-release v4.0.0-rc1 - v4.0.0-RC1 To: containers/podman Cc: Subscribed v4.0.0-RC1

[pkg-go] Bug#1002997: podman: Please provide a default /etc/containers/storage.conf

Control: reassign -1 storage-common Control: affects -1 podman Hi Philip, Thank you for your bug report. The Debian equivalent to Fedora's package 'containers-common' has the same name in debian, and does ship a 'storage.conf' file in /usr/share/containers/storage.conf. This is so that the

[pkg-go] Bug#1001321: Fwd: [containers/podman] Release v3.4.3 - v3.4.3

Package: libpod -- Forwarded message - From: Matthew Heon Date: Tue, Dec 7, 2021 at 10:09 AM Subject: [containers/podman] Release v3.4.3 - v3.4.3 To: containers/podman Cc: Subscribed v3.4.3 Repository:

[pkg-go] Bug#998055: Problem actually in conmon, not podman

Control: reassign -1 common 2.0.25+ds1-1.1 Control: affects -1 podman According to the referenced redhat bug entry, this is actually an issue in the conmon package. Reassigning accordingly. https://bugzilla.redhat.com/show_bug.cgi?id=1952698 -- regards, Reinhard

[pkg-go] Bug#999846: golang-dbus: Please update to upstream version 5.0.6 or later to pickup SessionBusPrivateNoAutoStartup function

Source: golang-dbus Version: 5.0.3-2 Severity: normal Podman 3.4.2 started using a function that was introduced in this commit: https://github.com/godbus/dbus/commit/2ece603a3b742642e388ba947c276189fae90b73 Please upgrade to package 5.0.6 or later which would allow me to update the podman

[pkg-go] Bug#997133: More information in the ubuntu bugtracker

the ubuntu tracker claims this is golang 1.16 related: https://bugs.launchpad.net/debian/+source/consul/+bug/1940152 not sure how to proceed here, though... -- regards, Reinhard ___ Pkg-go-maintainers mailing list

[pkg-go] Bug#997133: Relevant part of the consul log

Here is the actual relevant part of the build log: === RUN TestDynamicTLSConfig tls_test.go:263: Error Trace: tls_test.go:263 tls_test.go:339 Error: Not equal: expected:

[pkg-go] Bug#997976: podman suggests iptables, but "podman run" does not appear to work without it

Control: forwarded -1 https://github.com/containers/podman/issues/12134 Control: reassign -1 containernetworking-plugins On Thu, Oct 28, 2021 at 11:26 AM Reinhard Tartler wrote: > I'd like to hear upstream's opinion on this. > Thanks for reaching out to upstream. I agree with

[pkg-go] Bug#997976: podman suggests iptables, but "podman run" does not appear to work without it

Hi Ian, Thank you for reaching out. On Thu, Oct 28, 2021 at 1:39 AM Ian Wienand wrote: > > > --- > 2021-10-28 03:35:56.042 | ++ podman run -d dib-work-image /bin/sh > 2021-10-28 03:35:56.241 | time="2021-10-28T03:35:56Z" level=error > msg="error > loading cached network config: network

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

Control: fixed -1 3.3.1+ds2-1 Control: tags -1 bullseye Thank you for your bugreport. On Tue, Oct 5, 2021 at 10:51 AM Will Thompson wrote: > Package: podman > Version: 3.0.1+dfsg1-3+b2 > Severity: important > > podman embeds a default seccomp policy, which based on my research is > identical

[pkg-go] Bug#994601: Fwd: [containers/podman] Pre-release v3.4.0-rc1 - v3.4.0-RC1

Package: libpod Severity: wishlist -- Forwarded message - From: Matthew Heon Date: Thu, Sep 16, 2021, 18:16 Subject: [containers/podman] Pre-release v3.4.0-rc1 - v3.4.0-RC1 To: containers/podman Cc: Subscribed v3.4.0-RC1

[pkg-go] Bug#992138: Fwd: [containers/podman] Pre-release v3.3.0-rc2 - v3.3.0-rc2

Package: libpod -- Forwarded message - From: Lokesh Mandvekar Date: Thu, Aug 12, 2021 at 4:34 PM Subject: [containers/podman] Pre-release v3.3.0-rc2 - v3.3.0-rc2 To: containers/podman Cc: Subscribed v3.3.0-rc2

[pkg-go] Bug#991197: Fwd: [containers/podman] Release v3.2.3 - v3.2.3

Package: libpod Severity: wishlist -- Forwarded message - From: Ashley Date: Fri, Jul 16, 2021, 16:03 Subject: [containers/podman] Release v3.2.3 - v3.2.3 To: containers/podman Cc: Subscribed v3.2.3 Repository:

[pkg-go] Bug#990333: Fwd: [containers/podman] Release v3.2.2 - v3.2.2

Package: libpod Please update package in experimental -- Forwarded message - From: Matthew Heon Date: Fri, Jun 25, 2021, 17:04 Subject: [containers/podman] Release v3.2.2 - v3.2.2 To: containers/podman Cc: Subscribed v3.2.2

[pkg-go] Bug#989803: podman 3.0.1 rootless network issues: Connection reset by peer

Hi Alexander, thank you for reporting this issue. I've prepared a fix for this that adds the referenced commit as a distro patch. Can you please try to build https://salsa.debian.org/debian/libpod/-/merge_requests/4 and let me know if that fixes the issue? Thanks! On Sun, Jun 13, 2021 at 12:27

[pkg-go] Bug#987207: podman not running out-of-the-box as root

Control: tag -1 pending Control: severity -1 important Control: retitle -1 Missing dependency on "iptables" On Wed, Apr 21, 2021 at 6:07 AM Laurent Bigonville wrote: > So the problem here is, again, linked to the fact that I'm using a test > SELinux policy that doesn't contain all the needed

[pkg-go] Bug#987207: podman not running out-of-the-box as root

Control: tag -1 moreinfo Hi Laurent, I've downloaded the Bullseye Alpha 3 debian installer and installed using kvm to have a super clean new system. Unfortunately, I was unable to reproduce the issue that you described below. (I did find some issues with rootless podman outside of a

[pkg-go] Bug#985379: podman: fails to run on freshly installed Bullseye, runtime "crun" not found: invalid argument

Thank you for your report. I have to admit that I'm a bit confused, according to attached data, it seems you have both 'runc' as well as 'crun' installed. In that case, changing the order of the dependencies won't make a difference. Please confirm what packages of 'crun' and 'runc' you have

[pkg-go] Bug#983395: podman lacks a runtime dependency on rootlesskit

Control: retitle -1 Please print nicer error message if newuidmap is not installed Control: severity -1 wishlist Control: tag -1 upstream Andrey, please stop this bug ping-pong. Feel free to escalate this to the TC, but I don't think you are being reasonable here. -- regards, Reinhard

[pkg-go] Bug#983395: podman lacks a runtime dependency on rootlesskit

Control: retitle -1 Please print nicer error message if newuidmap is not installed Control: severity -1 wishlist Control: tag -1 upstream On Wed, Mar 10, 2021 at 11:07 AM Andrej Shadura wrote: > Hi, > > On Wed, 10 Mar 2021, at 17:04, Shengjing Zhu wrote: > > > 2) Docker doesn’t require

[pkg-go] Bug#983395: podman lacks a runtime dependency on rootlesskit

Control: tag -1 unreproducible On Wed, Mar 10, 2021 at 10:28 AM Andrej Shadura wrote: > Control: reopen -1 > > On Wed, 10 Mar 2021, at 16:23, Reinhard Tartler wrote: > > > > On Wed, Feb 24, 2021 at 12:33 AM Shengjing Zhu wrote: > > On Wed, Feb 24, 2021 at 06:47:20AM

[pkg-go] Bug#978650: podman: please provide a default container registry for looking up short image names

1+dfsg1-1 > > > > On Thu, Dec 31, 2020 at 08:14:08AM -0500, Reinhard Tartler wrote: > > > Can you please try the podman version in experimental? I believe what > you > > > describe (the shortnames) should work with version 2.2 just fine > thanks to > > >

[pkg-go] Bug#982288: podman: Can't run caontainers - failed to connect to container's attach socket

Control: tag -1 upstream Control: severity important Control: retitle -1 rootless podman fails with very long uids On Mon, Feb 8, 2021 at 6:09 AM Sam Morris wrote: > Package: podman > Version: 3.0.0~rc2+dfsg1-2+b1 > Severity: grave > Justification: renders package unusable > X-Debbugs-Cc:

[pkg-go] Bug#981849: podman build does not use the cache

Control: reassign -1 buildah 1.19.3+dfsg1-1 Control: affects -1 podman On Thu, Feb 4, 2021 at 12:55 PM Antonio Terceiro wrote: > Control: forwarded -1 https://github.com/containers/podman/issues/9233 > > There. > Awesome. As it turns out, this is actually an issue in buildah and needs to be

[pkg-go] Bug#981849: podman build does not use the cache

Control: tags -1 upstream On Thu, Feb 4, 2021 at 10:33 AM Antonio Terceiro wrote: > > After upgrading from 3.0.0~rc1+dfsg1-1, which was in experimental, to the > version that was just uploaded to unstable, `podman build` stopped using > the > cache when building images. I've checked with

[pkg-go] Bug#981708: io.podman.{socket, service} symlinks not cleaned up on upgrades

Hi Michael, On Tue, Feb 2, 2021 at 8:15 PM Michael Biebl wrote: > it seems, podman no longer ships the following two units: > io.podman.socket and io.podman.service > would you mind having a look at https://salsa.debian.org/debian/libpod/-/merge_requests/3 I'm not sure if it is complete to

[pkg-go] Bug#980480: Bug#980480: autopkgtest always fail

On Tue, Jan 26, 2021 at 10:44 AM Shengjing Zhu wrote: > So for podman, it can either keep this line and drop > autopkgtest-pkg-go, or write Makefile in a way that autopkgtest-pkg-go > can recognize. > I suppose the issue is around here:

[pkg-go] Bug#978650: podman: please provide a default container registry for looking up short image names

On Sun, Jan 24, 2021 at 9:12 AM Reinhard Tartler wrote: > > > On Sun, Jan 24, 2021 at 7:54 AM Shengjing Zhu wrote: > >> On Sun, Jan 24, 2021 at 8:44 PM Reinhard Tartler >> wrote: >> > >> > Context is what version of podman to ship in Debian bullseye &

[pkg-go] Bug#978650: podman: please provide a default container registry for looking up short image names

On Sun, Jan 24, 2021 at 1:44 PM Antoine Beaupré wrote: > > Could we still upload 2.1 or 2.2 to unstable in the meantime to have at > least an update on that front that's solid? > > Debian testing (bullseye)/unstable currently ship with version 2.1.1. cf.

Re: [pkg-go] podman (2.1.1+dfsg1-4) - search not working on new install

Hi Imran, thanks for reaching out On 1/24/21 12:04 PM, Imran Ibrahim wrote: > I needed to manually add: > > |[registries.search]| > |registries = ['docker.io ']| > > to etc/containers/registries.conf > > As container search was not working out of the box. Would it be

[pkg-go] Bug#978650: podman: please provide a default container registry for looking up short image names

On Sun, Jan 24, 2021 at 7:54 AM Shengjing Zhu wrote: > On Sun, Jan 24, 2021 at 8:44 PM Reinhard Tartler > wrote: > > > > Context is what version of podman to ship in Debian bullseye > [...] > > > > One could be to let's go straight for podman 3.0. Since Deb

[pkg-go] Bug#978650: podman: please provide a default container registry for looking up short image names

Context is what version of podman to ship in Debian bullseye On Thu, Jan 14, 2021 at 11:29 AM Antonio Terceiro wrote: > On Sat, Jan 09, 2021 at 12:58:05PM +0200, Faidon Liambotis wrote: > > Hi there, > > > > On Thu, Dec 31, 2020 at 01:39:52PM -0500, Reinhard Tartler wrot

[pkg-go] Bug#978650: podman: please provide a default container registry for looking up short image names

Yes, exactly. On Mon, Jan 4, 2021 at 3:47 PM Antonio Terceiro wrote: > On Thu, Dec 31, 2020 at 11:26:49AM -0300, Antonio Terceiro wrote: > > Control: done -1 2.2.1+dfsg1-1 > > > > On Thu, Dec 31, 2020 at 08:14:08AM -0500, Reinhard Tartler wrote: > > > Can you

[pkg-go] Bug#978650: podman: please provide a default container registry for looking up short image names

On Thu, Dec 31, 2020 at 9:26 AM Antonio Terceiro wrote: > Control: done -1 2.2.1+dfsg1-1 > > On Thu, Dec 31, 2020 at 08:14:08AM -0500, Reinhard Tartler wrote: > > Can you please try the podman version in experimental? I believe what you > > describe (the shortnames) should

[pkg-go] Bug#978650: podman: please provide a default container registry for looking up short image names

Can you please try the podman version in experimental? I believe what you describe (the shortnames) should work with version 2.2 just fine thanks to the shortnames.conf file. Also, what version of podman did you use in Fedora for this test? -rt On Tue, Dec 29, 2020 at 12:45 PM Antonio Terceiro

[pkg-go] Bug#976924: Test timeouts on ppc64el not RC

Control: severity -1 normal Looking at the logs, it really looks like timeouts in the testsuite. We could disable the tests on problematic architectures, patches welcome. As a workaround, I'd suggest building the package with export DEB_BUILD_OPTIONS=notest. With this, I'm downgrading the

[pkg-go] Bug#977717: podman: Images can't be run with non-root USER after upgrade to 2.1.1 due to wrong permissions of / inside the container

Control: fixed -1 2.2.0+dfsg1-1 Control: forwarded -1 https://github.com/containers/podman/issues/7747 Thanks for the clarification. With this, I was able to reproduce the issue in unstable, and confirm its absence with the podma 2.2 package in experimental. I've found a patch on the github issue

[pkg-go] Bug#977717: podman: Images can't be run with non-root USER after upgrade to 2.1.1 due to wrong permissions of / inside the container

Control: tag -1 moreinfo unreproducible On Sat, Dec 19, 2020 at 9:15 AM Andreas Maus < 023a305472eca90cd389e9dd4a9f30f71a6cf...@ypbind.de> wrote: > After the upgrade of podman to 2.1.1 container images > can't be run if the Dockerfile specify a non-root USER. > I'm sorry, but I can't reproduce

[pkg-go] Bug#977502: podman, golang-github-containers-common: both ship /usr/share/man/man5/containers-mounts.conf.5.gz

Hi Valentin, I just received the bug below. It seems that the manpage duplication is actually upstream: - https://github.com/containers/common/blob/master/docs/containers-mounts.conf.5.md - https://github.com/containers/podman/blob/master/docs/source/markdown/containers-mounts.conf.5.md They

[pkg-go] Bug#976943: golang-github-seccomp-libseccomp-golang: FTBFS on ppc64el (arch:all-only src pkg): dh_auto_test: error: cd obj-powerpc64le-linux-gnu && go test -vet=off -v -p 160 github.com/secco

> === RUN TestRuleAddAndLoad > seccomp_test.go:588: Syscall should have returned error code! > --- FAIL: TestRuleAddAndLoad (0.00s) Source code is here: https://sources.debian.org/src/golang-github-seccomp-libseccomp-golang/0.9.1-2/seccomp_test.go/#L529-L589 This test is basically

Re: [pkg-go] Comments regarding libpod_2.1.1+dfsg1-1_multi.changes

On 12/6/20 4:03 PM, Joerg Jaspert wrote: > Hi Maintainer, > > the following are comments from a review one ftp trainee has done on > your package. While I will accept your package (nothing warrants a > reject), please fix them in your next upload. > [...] Thank you again to whoever did this

[pkg-go] Bug#976410: glibc breaks libpod autopkgtest: dh_auto_build: error: cd _output && go install -trimpath ...

On Fri, Dec 4, 2020 at 3:24 PM Aurelien Jarno wrote: > > I have tried and for me the issue is reproducible with both old and new > glibc. I am therefore reassign the bug to libpod. > This is because of an upstream update in a dependency. It should be very straight-forward to fix. Unfortunately,

[pkg-go] Bug#971815: podman: --init is broken: /usr/libexec/podman/catatonit not found

Awesome, thanks! On Sat, Nov 28, 2020, 15:50 Antonio Terceiro wrote: > Hello Reinhard, > > On Sat, Nov 28, 2020 at 10:57:52AM -0500, Reinhard Tartler wrote: > > please go ahead with packaging catatonit. Regarding the symlink, I don't > > have a strong preference, your p

[pkg-go] Bug#971815: podman: --init is broken: /usr/libexec/podman/catatonit not found

Hi Antonio, sorry for taking so long to get back to you On Thu, Nov 5, 2020 at 1:15 PM Antonio Terceiro wrote: > On Wed, Oct 07, 2020 at 06:39:43PM -0300, Antonio Terceiro wrote: > > Package: podman > > Version: 2.0.6+dfsg1-1 > > Severity: normal > > Tags: patch > > > > I was testing some

[pkg-go] Bug#975602: golang-github-seccomp-libseccomp-golang-dev: Please backport upstream patch adding ActKillProcess and ActKillThread

Package: golang-github-seccomp-libseccomp-golang-dev Severity: normal X-Debbugs-Cc: Reinhard Tartler For packaging a newer upstream version of buildah, the following upstream patch is required: https://github.com/seccomp/libseccomp-golang/commit/24f29379854785de68bbd44630cc093b22b4dc29

[pkg-go] Bug#970352: unprivileged podman dies with gibberish

Control: close -1 Control: tag -1 unreproducible Hi Harald, On Sun, Sep 20, 2020 at 11:32 AM Reinhard Tartler wrote: > Control: tag -1 upstream > > On Sun, Sep 20, 2020 at 9:28 AM Harald Dunkel wrote: > >> I think there is a misunderstanding: The problem is not the error

[pkg-go] Bug#970352: unprivileged podman dies with gibberish

Control: tag -1 upstream On Sun, Sep 20, 2020 at 9:28 AM Harald Dunkel wrote: > I think there is a misunderstanding: The problem is not the error, > but the error *message*. Can you do without complaining about bad > HTTP code and URLs that don't work? Surely they don't give a hint > about what

[pkg-go] Bug#970352: unprivileged podman dies with gibberish

Control: tag -1 moreinfo Hi Harald, On Tue, Sep 15, 2020 at 1:51 AM Harald Dunkel wrote: > Package: podman > Version: 2.0.6+dfsg1-1 > > Unprivileged podman dies with some gibberish instead of a readable > error message: > > % podman run -it debian /bin/bash > Trying to pull quay.io/debian...

[pkg-go] Bug#962427: golang-github-klauspost-pgzip: Please update to upstream version 1.2.3 or later

Package: golang-github-klauspost-pgzip Severity: wishlist Needed by container/storage v1.16 branch thanks -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing'), (50, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.6.0-1-amd64 (SMP w/4

[pkg-go] Bug#947617: golang-github-coreos-bbolt: Please update package to version 1.3.3

Source: golang-github-coreos-bbolt Version: 1.3.1-coreos.5-3 Severity: normal There is a new upstream version available: https://github.com/etcd-io/bbolt/releases/tag/v1.3.3 This is likely the cause for bug #947486, which affects experimental only at this point. -- System Information: Debian

[pkg-go] Bug#926824: go-md2man: Produced manpages contain many warnings "manpage-has-bad-whatis-entry" lintian warnings

Source: go-md2man Severity: normal I'm using this tool in the golang-github-containers-storage. At the end of the package build, I see lots of warnings like this: , | W: containers-storage: manpage-has-bad-whatis-entry usr/share/man/man1/containers-storage-mounted.1.gz | W:

[pkg-go] Bug#923722: golang-github-appc-cni: Please upgrade to new upstream 0.7.0-alpha1

Package: golang-github-appc-cni Severity: wishlist Hi, Please update to new upstream version of 0.7.0-alpha1. I need it as a build dependency of http://github.com/containers/buildah In fact, I've done so locally, and would be happy to upload it as a Team Upload. I was running into issues while

[pkg-go] Bug#921849: restic 0.9.4 `-q` outputs `open repository`

Package: restic Version: 0.9.4+ds-1 Severity: important Tags: upstream When used for instance in a cron job for backup, I would get emails that have this content: /etc/cron.hourly/backup_restic: open repository open repository open repository This has been reported upstream at:

[pkg-go] Bug#909032: Additional build failures

Seems that additional issues have shown up: dh_auto_configure make[1]: Leaving directory '/<>/cadvisor-0.27.1+dfsg2' dh_auto_build -a -O--buildsystem=golang -O--builddirectory=_build cd _build && go install -gcflags=all=\"-trimpath=/<>/cadvisor-0.27.1\+dfsg2/_build/src\"