** Tags removed: rls-jj-notfixing rls-kk-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960749
Title:
dpkg incorrectly installs singular-doc in jammy Docker container
To manage notificatio
** Tags removed: rls-jj-incoming
** Tags added: rls-jj-notfixing rls-kk-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960749
Title:
dpkg incorrectly installs singular-doc in jammy Docker c
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 c
Sorry but a symlink is just a symlink, it points to another name. It
does not contain a flag saying whether it points to a file or a
directory, so you can't know.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
In this case the links are not pointing to directories, they are
pointing to files in the same directory. So there is no excuse to
install them.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960749
T
** Changed in: dpkg (Debian)
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960749
Title:
dpkg incorrectly installs singular-doc in jammy Docker container
To manage no
So the reason why the symlinks are there is because they could be
pointing to directories and then if you had a file extracted in there,
you'd get not found if you'd skip the symlink. Like consider
/usr/share/doc/foo/bar as a symlink to /usr/share/foo/bar
and another package installs a file into
Sure, when I was filing the report I had no idea what's really going on
- the only indications were `dpkg -V` reporting missing files, and
broken links in /usr/share/doc.
** Description changed:
Also reported on https://github.com/tianon/docker-brew-ubuntu-
core/issues/230
Using official
Note that it was not clear from the bug report that it was installing
broken symlinks that it should not have. I assumed it was installing
expected broken symlinks, like a /usr/share/singular/doc symlink to
/usr/share/doc/singular, that's why I provided the information so you
know what's going on,
I have verified that the symlinks somehow end up getting installed
although they should have been excluded. This also happens upstream in
Debian.
If we just have path-exclude=/usr/share/doc/*, it gets excluded. Once we
add path-include=/usr/share/doc/*/copyright, the symlinks in
/usr/share/doc/sin
Yes, lxd containers are full-fledged system containers which also target
interactive users. The focus of the docker community is vastly
different, focusing on the smallest possible containers:
https://ubuntu.com/blog/minimal-ubuntu-released
It's odd you end up with anything inside /usr/share/doc,
And if you want to keep this behaviour, at least make sure `dpkg -V`
reports that files are missing due to a policy, not cause it's a bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960749
Title:
This was discovered during the run of a CI, and interactive steps are
provided for the ease of reproduction, not because it's the way it was
found. If you don't know how to use Docker images interactively, it
doesn't mean they are not used this way.
Also, even if I'd agree that Docker containers a
This is a feature, not a bug.
Docker images are not intended for interactive use, as such use
minimized images, and dpkg is configured to not install any
documentation.
A script 'unminize' is provided to convert a minimized image into a full
one.
root@3a7cdb2c772b:/# cat /etc/dpkg/dpkg.cfg.d/exc
This is a feature, not a bug.
Docker images are not intended for interactive use, as such use
minimized images, and dpkg is configured to not install any
documentation.
A script 'unminize' is provided to convert a minimized image into a full
one.
root@3a7cdb2c772b:/# cat /etc/dpkg/dpkg.cfg.d/exc
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
16 matches
Mail list logo