Control: reassign -1 synaptic 0.91.3 On Sun, Apr 21, 2024 at 03:50:27AM +0200, Vincent Lefevre wrote: > "apt: autoremoval keeps all branches of an OR on the system even if > I don't want one". > > While I can understand the reason why this is wontfix, this reason > makes no sense on transitional packages.
Instead of asking apt (and all other applications) to come up with a complex set of rules what a transitional package might be (case in point: policykit-1 is not in section oldlibs[0]) you should focus your energy on making that transition actually happen if you care that much about it. [0] https://wiki.debian.org/RenamingPackages > As an example: > > qaa:~> apt autoremove -s > NOTE: This is only a simulation! > apt needs root privileges for real execution. > Keep also in mind that locking is deactivated, > so don't depend on the relevance to the real current situation! > Summary: > Upgrading: 0, Installing: 0, Removing: 0, Not Upgrading: 82 > > but policykit-1 (marked as automatically installed) could be removed: > > qaa:~> aptitude remove -s policykit-1 > The following packages will be REMOVED: > policykit-1 > 0 packages upgraded, 0 newly installed, 1 to remove and 82 not upgraded. > Need to get 0 B of archives. After unpacking 34.8 kB will be freed. > Would download/install/remove packages. > > I suppose that "apt autoremove" doesn't remove it because of > the OR dependency: > > qaa:~> aptitude why policykit-1 > i synaptic Depends pkexec | policykit-1 > > (at least, this seems to be one of the reasons). synaptics could drop the or on policykit-1 – or if for some reason keeping it is desirable make it a versioned on, like: | pkexec | policykit-1 (<< first-transitional-version~) Best regards David Kalnischkies
signature.asc
Description: PGP signature
