On Wed 17 Feb 2021 at 20:45:02 (+0800), Kevin Shell wrote:
> On Tue, Feb 16, 2021 at 07:19:52PM -0500, Stefan Monnier wrote:
> >
> [...]
> > It'd be work in the DPKG/APT code, yes. But it would require no extra
> > work from the people doing the packaging.
>
> I know little technical details about the Debian package manager,
> from an end user's perspective, the package manager should give the user
> the choise not to uninstall a wanted package,
Call that 1.
> if the user don't give a choise, the package manager can perform the
> default action to remove the package.
Call that 2.
> I think this method is a better default behavior for the package manager
> for some similar packages.
Is that not true now?
$ apt-get -s install busybox-static
NOTE: This is only a simulation!
[…]
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be REMOVED: ← case 2 ----------
busybox
The following NEW packages will be installed:
busybox-static
0 upgraded, 1 newly installed, 1 to remove and 2 not upgraded.
Remv busybox [1:1.30.1-4] [cryptsetup-initramfs:amd64 ]
Inst busybox-static (1:1.30.1-4 Debian:10.8/stable [amd64])
Conf busybox-static (1:1.30.1-4 Debian:10.8/stable [amd64])
$
~# aptitude hold busybox
~#
$ apt-get -s install busybox-static
NOTE: This is only a simulation!
[…]
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
busybox : Conflicts: busybox-static but 1:1.30.1-4 is to be installed
busybox-static : Conflicts: busybox ← case 1 ----------
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by
held packages.
100 $
~# aptitude unhold busybox
~#
Cheers,
David.
