[Bug 1960749] [NEW] dpkg incorrectly installs singular-doc in jammy Docker container

Dima Pasechnik 1960749 at bugs.launchpad.net
Sun Feb 13 17:30:04 UTC 2022


Public bug reported:

Also reported on https://github.com/tianon/docker-brew-ubuntu-
core/issues/230

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.
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-doc_4.2.1-p3+ds-1_all.deb file, and installing it using dpkg
-i. This points to dpkg as the culprit.

** Affects: dpkg (Ubuntu)
     Importance: Undecided
         Status: New

** Bug watch added: trac.sagemath.org/ #32789
   https://trac.sagemath.org/ticket/32789

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to dpkg in Ubuntu.
https://bugs.launchpad.net/bugs/1960749

Title:
  dpkg incorrectly installs singular-doc in jammy Docker container

Status in dpkg package in Ubuntu:
  New

Bug description:
  Also reported on https://github.com/tianon/docker-brew-ubuntu-
  core/issues/230

  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.
  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-doc_4.2.1-p3+ds-1_all.deb file, and installing it using dpkg
  -i. This points to dpkg as the culprit.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1960749/+subscriptions




More information about the foundations-bugs mailing list