Christian Marillat wrote:
> A transitional debian-multimedia-keyring package has been already
> uploaded. This package install a new deb-multimedia-keyring package and
> thus debian-multimedia-keyring can be removed.
>
Some apt-get/aptitude confusion:
# aptitude purge debian-multimedia-keyring
The following packages will be REMOVED:
deb-multimedia-keyring{u} debian-multimedia-keyring{p}
0 packages upgraded, 0 newly installed, 2 to remove and 0 not upgraded.
Need to get 0 B of archives. After unpacking 71.7 kB will be freed.
Do you want to continue? [Y/n/?]n
# aptitude remove debian-multimedia-keyring
The following packages will be REMOVED:
deb-multimedia-keyring{u} debian-multimedia-keyring
0 packages upgraded, 0 newly installed, 2 to remove and 0 not upgraded.
Need to get 0 B of archives. After unpacking 71.7 kB will be freed.
Do you want to continue? [Y/n/?]n
# apt-get purge debian-multimedia-keyring
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following package was automatically installed and is no longer required:
deb-multimedia-keyring
Use 'apt-get autoremove' to remove them.
The following packages will be REMOVED:
debian-multimedia-keyring*
0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
After this operation, 26.6 kB disk space will be freed.
Do you want to continue [Y/n]?n
The package deb-multimedia-keyring was indeed automatically installed
so it's the expected result that aptitude wants to remove it?
That shouldn't happen if deb-multimedia-keyring would contain 'Replaces:
debian-multimedia-keyring'? Or maybe a combination with 'Provides:' and
'Conflicts:' would be even better?
http://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces
Bye,
Manne
