Bug#1068637: apt does not always install Recommends
On 2024-04-08 19:26:42 +0200, David Kalnischkies wrote:
> On Mon, Apr 08, 2024 at 01:05:40PM +0200, Vincent Lefevre wrote:
> > On 2024-04-08 12:29:17 +0200, Julian Andres Klode wrote:
> > > On Mon, Apr 08, 2024 at 11:50:04AM +0200, Vincent Lefevre wrote:
> > > > The lvm2 package is installed, but not thin-provisioning-tools,
> > > > though lvm2 recommends it. This can yield a broken system:
> […]
> > It is not mandatory in all cases, but it some cases. In any case,
> > the "Recommends:" must be honored.
>
> You haven't mentioned AT ALL if we are talking about upgrade or a fresh
> install of lvm2, for the later see below. For the former:
It was not an upgrade. For one of the machines, this was the status
a bit after the installation of bookworm. For the other machine, this
was the status just a bit after the installation of a weekly build on
2024-01-05.
Then, I don't know the internals. But according to Bastian Blank[*]:
"It is installed like everything else." (but see the details below).
[*] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068560#22
> > No, lvm2 was installed before the time_t transition. It actually
> > affects plain bookworm installations (on a machine where I installed
> > Debian 12.1 on 2023-10-07); you can see with the attached
> > "dpkg --get-selections" output I had at that time.
> ^^^^
>
> What time? Before you installed lvm2? That output says lvm2 is
> installed. So after it, but what are you trying to tell us then?
A few hours after the installation of bookworm. You can see that lvm2
is installed, but not thin-provisioning-tools (which is the bug).
I mean that this has always been like that (so, if you think that
thin-provisioning-tools could have been installed as a Recommends,
then removed later, this is not the case).
> I just bootstrapped a minimal stable chroot with mmdebstrap and behold:
> | # apt install --install-recommends lvm2
> | Reading package lists... Done
> | Building dependency tree... Done
> | Reading state information... Done
> | The following additional packages will be installed:
> | dmeventd dmsetup libaio1 libdevmapper-event1.02.1 libdevmapper1.02.1 liblvm2cmd2.03 thin-provisioning-tools
> | The following NEW packages will be installed:
> | dmeventd dmsetup libaio1 libdevmapper-event1.02.1 libdevmapper1.02.1 liblvm2cmd2.03 lvm2 thin-provisioning-tools
> | 0 upgraded, 8 newly installed, 0 to remove and 0 not upgraded.
> | Need to get 2662 kB of archives.
> | After this operation, 9729 kB of additional disk space will be used.
> | Do you want to continue? [Y/n] n
> | Abort.
>
> In other words your issue with a "plain bookworm" install is
> unreproducible
But what about the usual Debian installation on a real machine?
For the first machine (bookworm), I used an image via
https://cdimage.debian.org/debian-cd/current/amd64/jigdo-cd/
namely, debian-12.1.0-amd64-netinst.iso, and I did the installation
by using a USB memory stick.
> So, if you want to have any chance of us investigating your problem as
> a bug rather than as a user-error you will have to tell us what you did
> exactly, preferably with easy to follow steps and output. Failing that,
> on your bookworm install you might be lucky and still have the
> installation/upgrade and such of lvm2 in your history.log(s).
> That might shine some light on it as well.
Indeed, in /var/log/apt/history.log.6.gz (note that I did not type
this command; so it came from the Debian installer):
Start-Date: 2023-10-07 13:43:22
Commandline: apt-get -o APT::Status-Fd=4 -o APT::Keep-Fds::=5 -o APT::Keep-Fds::=6 -q -y --no-remove install lvm2
Install: dmeventd:amd64 (2:1.02.185-2, automatic), libaio1:amd64 (0.3.113-4, automatic), liblvm2cmd2.03:amd64 (2.03.16-2, automatic), lvm2:amd64 (2.03.16-2), libdevmapper-event1.02.1:amd64 (2:1.02.185-2, automatic)
End-Date: 2023-10-07 13:43:28
And for the second machine (weekly build):
Start-Date: 2024-01-05 16:54:09
Commandline: apt-get -o APT::Status-Fd=4 -o APT::Keep-Fds::=5 -o APT::Keep-Fds::=6 -q -y --no-remove install lvm2
Install: dmeventd:amd64 (2:1.02.185-2, automatic), libaio1:amd64 (0.3.113-5, automatic), liblvm2cmd2.03:amd64 (2.03.16-2, automatic), lvm2:amd64 (2.03.16-2), libdevmapper-event1.02.1:amd64 (2:1.02.185-2, automatic)
End-Date: 2024-01-05 16:54:14
Now, this is clear that the recommended thin-provisioning-tools
package was not installed together with lvm2.
--
Vincent Lefèvre <vincent@vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
Reply to: