Your message dated Fri, 19 Aug 2022 13:54:54 +0200
with message-id
<caj0ccebmhndkmqyh3wry701heb5mfofkshhhafbvwma8uqr...@mail.gmail.com>
and subject line Re: Bug#1015317:
/lib/systemd/system/podman-auto-update.service: podman-auto-update.service
broken - can't find /bin/podman
has caused the Debian Bug report #1015317,
regarding /lib/systemd/system/podman-auto-update.service:
podman-auto-update.service broken - can't find /bin/podman
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1015317: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015317
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: podman
Version: 4.1.1+ds1-2
Severity: normal
File: /lib/systemd/system/podman-auto-update.service
Jul 18 00:15:01 systemd[1]: Starting Podman auto-update service...
Jul 18 00:15:01 systemd[3185620]: podman-auto-update.service: Failed to locate
executable /bin/podman: No such file or directory
Jul 18 00:15:01 systemd[3185620]: podman-auto-update.service: Failed at step
EXEC spawning /bin/podman: No such file or directory
Jul 18 00:15:01 systemd[1]: podman-auto-update.service: Main process exited,
code=exited, status=203/EXEC
Jul 18 00:15:01 systemd[1]: podman-auto-update.service: Failed with result
'exit-code'.
The service file should reference /usr/bin/podman, not /bin/podman.
-- System Information:
Debian Release: bookworm/sid
APT prefers testing
APT policy: (530, 'testing'), (520, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 5.18.0-1-amd64 (SMP w/2 CPU threads; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages podman depends on:
ii conmon 2.1.0+ds1-1
ii containernetworking-plugins 1.1.0+ds1-1+b1
ii crun 0.17+dfsg-1.1+b1
ii golang-github-containers-common 0.48.0+ds1-1
ii libc6 2.33-7
ii libdevmapper1.02.1 2:1.02.183-2
ii libgpgme11 1.17.1-4
ii libseccomp2 2.5.4-1
ii systemd [systemd-tmpfiles] 251.2-7
Versions of packages podman recommends:
ii buildah 1.26.1+ds1-1
ii catatonit 0.1.7-1
ii fuse-overlayfs 1.9-1
ii golang-github-containernetworking-plugin-dnsname 1.3.1+ds1-2+b1
ii slirp4netns 1.0.1-2
ii uidmap 1:4.11.1+dfsg1-2
Versions of packages podman suggests:
ii containers-storage 1.37.2+ds1-1+b1
pn docker-compose <none>
ii iptables 1.8.8-1
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 4.2.0+ds1-3
Forgot to mention that this issue should be fixed in package
version 4.2.0+ds1-3 and higher, here is the commit in salsa:
https://salsa.debian.org/debian/libpod/-/commit/f9a046ebb2276c624edd08d2b5e921ab3c2c1d53
Thanks for your report
On Tue, Jul 19, 2022 at 3:15 PM Sam Morris <s...@robots.org.uk> wrote:
> Package: podman
> Version: 4.1.1+ds1-2
> Severity: normal
> File: /lib/systemd/system/podman-auto-update.service
>
> Jul 18 00:15:01 systemd[1]: Starting Podman auto-update service...
> Jul 18 00:15:01 systemd[3185620]: podman-auto-update.service: Failed to
> locate executable /bin/podman: No such file or directory
> Jul 18 00:15:01 systemd[3185620]: podman-auto-update.service: Failed at
> step EXEC spawning /bin/podman: No such file or directory
> Jul 18 00:15:01 systemd[1]: podman-auto-update.service: Main process
> exited, code=exited, status=203/EXEC
> Jul 18 00:15:01 systemd[1]: podman-auto-update.service: Failed with result
> 'exit-code'.
>
> The service file should reference /usr/bin/podman, not /bin/podman.
>
>
> -- System Information:
> Debian Release: bookworm/sid
> APT prefers testing
> APT policy: (530, 'testing'), (520, 'unstable'), (1, 'experimental')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 5.18.0-1-amd64 (SMP w/2 CPU threads; PREEMPT)
> Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE
> not set
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
>
> Versions of packages podman depends on:
> ii conmon 2.1.0+ds1-1
> ii containernetworking-plugins 1.1.0+ds1-1+b1
> ii crun 0.17+dfsg-1.1+b1
> ii golang-github-containers-common 0.48.0+ds1-1
> ii libc6 2.33-7
> ii libdevmapper1.02.1 2:1.02.183-2
> ii libgpgme11 1.17.1-4
> ii libseccomp2 2.5.4-1
> ii systemd [systemd-tmpfiles] 251.2-7
>
> Versions of packages podman recommends:
> ii buildah 1.26.1+ds1-1
> ii catatonit 0.1.7-1
> ii fuse-overlayfs 1.9-1
> ii golang-github-containernetworking-plugin-dnsname 1.3.1+ds1-2+b1
> ii slirp4netns 1.0.1-2
> ii uidmap 1:4.11.1+dfsg1-2
>
> Versions of packages podman suggests:
> ii containers-storage 1.37.2+ds1-1+b1
> pn docker-compose <none>
> ii iptables 1.8.8-1
>
> -- no debconf information
>
>
--
regards,
Reinhard
--- End Message ---
_______________________________________________
Pkg-go-maintainers mailing list
Pkg-go-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-go-maintainers
