Dimitri, thank you for laying out the rationale behind the package name.
Since there is good reason for things to be the way they are here, I've
opened a bug on the Debian side for them to address the naming
inconsistency:
https://bugs.debian.org/904152
** Bug watch added: Debian Bug tracker #904152
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904152
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/1782641
Title:
Request: Rename "ubuntu-keyring" package to "ubuntu-archive-keyring"
for consistency with Debian
Status in ubuntu-keyring package in Ubuntu:
Opinion
Bug description:
The package that Ubuntu calls "ubuntu-keyring" is present in Debian as
"ubuntu-archive-keyring".
Debian has separate "debian-keyring" and "debian-archive-keyring"
packages, described as follows:
d-k: GnuPG keys of Debian Developers and Maintainers
d-a-k: GnuPG archive keys of the Debian archive
IMO this is a reasonable distinction, as the keys of
developers/maintainers are rarely needed by end users, and the d-k
package is significantly larger (on the order of 30 MB).
Thus, the current "ubuntu-keyring" package would be better named
"ubuntu-archive-keyring", not only so that the equivalent package has
the same name in both distros, but also to maintain the same
distinction between developer keys and archive keys. (Ubuntu could
potentially decide to ship a package containing Ubuntu developer keys
in the future, and it would be awkward if this needed to be named e.g.
"ubuntu-devel-keyring" or the like.)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyring/+bug/1782641/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
