<div dir="ltr"><pre class="gmail-message" style="padding-top:8px;margin-top:0px;border-top:0px;white-space:pre-wrap;color:rgb(0,0,0)">Package: podman<br>Version: 4.0.1+ds1-3<br><div><span style="font-family:Arial,Helvetica,sans-serif">Severity: normal</span></div><div><br></div><div>I was working at backporting this to bullseye.</div><div><br></div><div>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.</div><div><br></div><div>Runing with --debug=7777</div><div><br></div><div>D000010: cu_installnew '/usr/lib/systemd/user/podman.socket' flags=602<br>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'<br>D000100: cu_installnew not restoring<br>D000100: secure_remove '/usr/lib/systemd/user/podman.socket.dpkg-new' rmdir No such file or directory<br></div><div><br></div><div>Apparently something thinks the socket config should be a directory(?)</div><div><br></div><div>Also, is there a reason there are several systemd files in /lib/systemd/user, but there's also (and only) a socket in /us<span style="font-family:Arial,Helvetica,sans-serif">r/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 :))</span></div><div><br></div><div>The result of installing 4.0.1 in a container:</div><div><br></div><div>```</div><div>root@1464c55fb39d /w/b/libpod-4.0.1+ds1# ls /lib/systemd/user/<br>podman-auto-update.service podman-restart.service podman.socket<br>podman-auto-update.timer podman.service<br></div><div><br></div><div>root@1464c55fb39d /w/b/libpod-4.0.1+ds1 [2]# ls /usr/lib/systemd/user/<br>app.slice graphical-session.target<br>background.slice paths.target<br>basic.target podman.socket<br>bluetooth.target printer.target<br>dbus.service session.slice<br></div><div>.....</div><div><br></div><div>```</div><div><br></div><div>I will try patching the package for /usr/lib and see if it improves it or breaks things.</div><div><span style="font-family:Arial,Helvetica,sans-serif"><br></span></div><div><span style="font-family:Arial,Helvetica,sans-serif"><br></span></div><div><span style="font-family:Arial,Helvetica,sans-serif">Cheers</span></div><div><br></div><div>--------------------------------------------------------------------------------</div><div> </div><blockquote>Package: podman<br>Version: 4.0.1+ds1-3<br>Severity: normal<br>X-Debbugs-Cc: <a href="mailto:himdel@gmail.com">himdel@gmail.com</a>
Dear Maintainer,
when upgrading podman from 4.0.1+ds1-1 to 4.0.1+ds1-3, install failed.<br>Purging podman and trying to install again gives me the same error:
Unpacking podman (4.0.1+ds1-3) ...<br> dpkg: error processing archive /var/cache/apt/archives/podman_4.0.1+ds1-3_amd64.deb (--unpack):<br> unable to open '/usr/lib/systemd/user/podman.socket.dpkg-new': No such file or directory<br> Errors were encountered while processing:<br> /var/cache/apt/archives/podman_4.0.1+ds1-3_amd64.deb
Notes:<br>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,<br>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) ...<br> dpkg: error processing archive /var/cache/apt/archives/podman_4.0.1+ds1-3_amd64.deb (--unpack):<br> unable to open '/usr/lib/systemd/user/podman.socket.dpkg-new': No such file or directory<br> /usr/bin/deb-systemd-helper: error: unable to read podman.socket<br> Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 142.<br> Errors were encountered while processing:<br> /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,<br>Regards,<br>Martin Hradil
-- System Information:<br>Debian Release: bookworm/sid<br> APT prefers testing<br> APT policy: (990, 'testing'), (500, 'stable-updates'), (500, 'stable-security'), (400, 'unstable'), (400, 'stable'), (101, 'experimental')<br>Architecture: amd64 (x86_64)<br>Foreign Architectures: i386
Kernel: Linux 5.16.0-3-amd64 (SMP w/8 CPU threads; PREEMPT)<br>Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE<br>Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set<br>Shell: /bin/sh linked to /usr/bin/dash<br>Init: systemd (via /run/systemd/system)
Versions of packages podman depends on:<br>ii conmon 2.0.25+ds1-1.1<br>ii containernetworking-plugins 1.1.0+ds1-1<br>ii golang-github-containers-common 0.47.2+ds1-1<br>ii init-system-helpers 1.62<br>ii iptables 1.8.7-1<br>ii libc6 2.33-7<br>ii libdevmapper1.02.1 2:1.02.175-2.1<br>ii libgpgme11 1.16.0-1.2<br>ii libseccomp2 2.5.3-2<br>ii runc 1.1.0+ds1-1
Versions of packages podman recommends:<br>ii buildah 1.24.1+ds1-1<br>ii fuse-overlayfs 1.7.1-1<br>ii golang-github-containernetworking-plugin-dnsname 1.3.1+ds1-2<br>ii slirp4netns 1.0.1-2<br>ii tini 0.19.0-1<br>ii uidmap 1:4.11.1+dfsg1-1
Versions of packages podman suggests:<br>ii containers-storage 1.36.0+ds1-3<br>ii docker-compose 1.29.2-1<br>ii iptables 1.8.7-1</blockquote></pre><br class="gmail-Apple-interchange-newline"></div>