On Tue, Apr 12, 2022 at 02:33:50PM -0300, Antonio Terceiro wrote:
> Package: podman
> Version: 4.0.1+ds1-3
> Severity: serious
> Justification: fails to install
> 
> I wanted to try podman 4.0 from experimental, but I can't install it:
> This is on a testing machine, with unstable and experimental available,
> but with testing at a higher priority:
> 
> ----------------8<----------------8<----------------8<-----------------
> $ sudo LANG=C apt install -t experimental -qy podman
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Suggested packages:
>   containers-storage
> The following packages will be upgraded:
>   podman
> 1 upgraded, 0 newly installed, 0 to remove and 306 not upgraded.
> Need to get 0 B/10.5 MB of archives.
> After this operation, 3781 kB of additional disk space will be used.
> (Reading database ... 774204 files and directories currently installed.)
> Preparing to unpack .../podman_4.0.1+ds1-3_amd64.deb ...
> 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
> Errors were encountered while processing:
>  /var/cache/apt/archives/podman_4.0.1+ds1-3_amd64.deb
> needrestart is being skipped since dpkg has failed
> E: Sub-process /usr/bin/dpkg returned an error code (1)
> ----------------8<----------------8<----------------8<-----------------

This is because podman is shipping both /lib/systemd/user/podman.socket
and /usr/lib/systemd/user/podman.socket:

$ dpkg --contents podman_4.0.1+ds1-3_amd64.deb  | grep socket
-rw-r--r-- root/root       176 2022-02-23 23:41 
./lib/systemd/system/podman.socket
-rw-r--r-- root/root       176 2022-03-06 19:16 ./lib/systemd/user/podman.socket
-rw-r--r-- root/root       176 2022-02-23 23:41 
./usr/lib/systemd/user/podman.socket

You can either ship one of the other, because if /lib is a symlink to
/usr/lib, one will overwrite the other. Indeed, If I revert the test VM
to unmerged-usr filesystem, then podman installs just fine.

I'm pushing a change (commit 699e6f68cd) that fixes this, I hope the
maintainers don't mind.

Attachment: signature.asc
Description: PGP signature

Reply via email to