dpkg incorrectly installs singular-doc in jammy Docker container
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
dpkg (Debian) |
New
|
Unknown
|
|||
dpkg (Ubuntu) |
Triaged
|
Undecided
|
Unassigned |
Bug Description
Also reported on https:/
Using official Jammy image in Docker (macOS) and Podman (Fedora).
In both cases, using CLI in the image and running
apt install singular-doc
dpkg -V singular-doc
reports a lot of missing files. In fact, the only present files are dangling links to missing files in the package.
(EDIT: the latter should not be there, it contradics `exclude` policy for dpkg installed in the Docker image)
The package itself is not broken - extracting it in Jammy not in Docker/Podman (say, in an lxc container) works.
And extracting it in Debian/bookworm CLI run in Docker works too.
As well, the same behaviour is observed using the corresponding singular-
Changed in dpkg (Debian): | |
status: | Unknown → New |
tags: |
added: rls-jj-notfixing rls-kk-incoming removed: rls-jj-incoming |
tags: | removed: rls-jj-notfixing rls-kk-incoming |
What's unusual about singular- doc_4.2. 1-p3+ds- 1_all.deb ? I suppose
* data.tar is compressed using zst
* it contains symbolic links within the tarball.
The data.tar.zst tarball extracted from .deb works fine in Docker image CLI (assuming zstd is installed), so I presume it's something to do with dpkg expaning the file by itself.
This was found while working on https:/ /trac.sagemath. org/ticket/ 32789