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

[Dima Pasechnik]

All these links points to names like foobar.png, but what's important
that they point to locations excluded by the policy (actually, the same
directory where the links reside!).

As long as the policy is in force, nothing can be installed to locations
they point to - besides more broken links, of course.

I actually don't understand the rationale of all this - even if these
links are pointing somewhere else, there should be nothing in that
directory, by policy!

-- 
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:
  Triaged
Status in dpkg package in Debian:
  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.
  (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-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