[pkg-go] Bug#1006882: podman fails to install - unable to open podman.socket.dpkg-new

stellarpower at googlemail.com stellarpower at googlemail.com
Sat Mar 19 20:11:37 GMT 2022


Package: podman
Version: 4.0.1+ds1-3
Severity: normal

I was working at backporting this to bullseye.

Interestingly, this error doesn't crop up when I install the package
inside a podman container (which was where I was building the
package), but does in a vagrant box or on metal - not much of a
surprise if it's simply because systemd doesn't really run inside the
container, but I don't konw if it's of any use.

Runing with --debug=7777

D000010: cu_installnew '/usr/lib/systemd/user/podman.socket' flags=602
D000100: setupvnamevbs main='/usr/lib/systemd/user/podman.socket'
tmp='/usr/lib/systemd/user/podman.socket.dpkg-tmp'
new='/usr/lib/systemd/user/podman.socket.dpkg-new'
D000100: cu_installnew not restoring
D000100: secure_remove '/usr/lib/systemd/user/podman.socket.dpkg-new'
rmdir No such file or directory

Apparently something thinks the socket config should be a directory(?)

Also, is there a reason there are several systemd files in
/lib/systemd/user, but there's also (and only) a socket in
/usr/lib/systemd/usr? Possibly by design, am just wondering. On my
ubuntu host as I type this, all the files are in /usr/lib/systemd and
it seems where I have installed the package in a VM, the only contents
of /lib/systemd/user are podman's stuff. IDK if a typo or difference
in design with debian upstream (I'm a ubuntu guy really :))

The result of installing 4.0.1 in a container:

```
root at 1464c55fb39d /w/b/libpod-4.0.1+ds1# ls /lib/systemd/user/
podman-auto-update.service  podman-restart.service  podman.socket
podman-auto-update.timer    podman.service

root at 1464c55fb39d /w/b/libpod-4.0.1+ds1 [2]# ls /usr/lib/systemd/user/
app.slice                            graphical-session.target
background.slice                     paths.target
basic.target                         podman.socket
bluetooth.target                     printer.target
dbus.service                         session.slice
.....

```

I will try patching the package for /usr/lib and see if it improves it
or breaks things.


Cheers

--------------------------------------------------------------------------------


Package: podman
Version: 4.0.1+ds1-3
Severity: normal
X-Debbugs-Cc: himdel at gmail.com
Dear Maintainer,
when upgrading podman from 4.0.1+ds1-1 to 4.0.1+ds1-3, install failed.
Purging podman and trying to install again gives me the same error:
    Unpacking podman (4.0.1+ds1-3) ...
    dpkg: error processing archive
/var/cache/apt/archives/podman_4.0.1+ds1-3_amd64.deb (--unpack):
     unable to open '/usr/lib/systemd/user/podman.socket.dpkg-new': No
such file or directory
    Errors were encountered while processing:
     /var/cache/apt/archives/podman_4.0.1+ds1-3_amd64.deb
Notes:
the file indeed doesn't exist, and if I create it before install, it
gets deleted.
Installing podman bookworm version (3.4.4+ds1-1) works,
upgrading from that to 4.0.1+ds1-3 still fails with the same error,
except for extra lines...
    Unpacking podman (4.0.1+ds1-3) over (3.4.4+ds1-1) ...
    dpkg: error processing archive
/var/cache/apt/archives/podman_4.0.1+ds1-3_amd64.deb (--unpack):
     unable to open '/usr/lib/systemd/user/podman.socket.dpkg-new': No
such file or directory
    /usr/bin/deb-systemd-helper: error: unable to read podman.socket
    Could not execute systemctl:  at /usr/bin/deb-systemd-invoke line 142.
    Errors were encountered while processing:
     /var/cache/apt/archives/podman_4.0.1+ds1-3_amd64.deb
Not sure what the cause is, this seems to be coming from dpkg-deb and
not the postrm/prerm/postinstall scripts.
Hope it helps,
Regards,
Martin Hradil
-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'stable-updates'), (500,
'stable-security'), (400, 'unstable'), (400, 'stable'), (101,
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.16.0-3-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages podman depends on:
ii  conmon                           2.0.25+ds1-1.1
ii  containernetworking-plugins      1.1.0+ds1-1
ii  golang-github-containers-common  0.47.2+ds1-1
ii  init-system-helpers              1.62
ii  iptables                         1.8.7-1
ii  libc6                            2.33-7
ii  libdevmapper1.02.1               2:1.02.175-2.1
ii  libgpgme11                       1.16.0-1.2
ii  libseccomp2                      2.5.3-2
ii  runc                             1.1.0+ds1-1
Versions of packages podman recommends:
ii  buildah                                           1.24.1+ds1-1
ii  fuse-overlayfs                                    1.7.1-1
ii  golang-github-containernetworking-plugin-dnsname  1.3.1+ds1-2
ii  slirp4netns                                       1.0.1-2
ii  tini                                              0.19.0-1
ii  uidmap                                            1:4.11.1+dfsg1-1
Versions of packages podman suggests:
ii  containers-storage  1.36.0+ds1-3
ii  docker-compose      1.29.2-1
ii  iptables            1.8.7-1
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-go-maintainers/attachments/20220319/3d9b3439/attachment.htm>


More information about the Pkg-go-maintainers mailing list