This bug was fixed with the following upload, and the package ubuntu-
dbgsym-keyring can now be installed.
ubuntu-keyring (2018.02.05) bionic; urgency=medium
* Ship the current ubuntu-cloudimage-keyring in the ubuntu-keyring
package. LP: #1331057
* Ship ubuntu-cloud-keyring for Cloud Archive signing keys, as a
separate keyring in /etc/apt/trusted.gpg.d/, and remove it from the
trusted.gpg keyring as no longer needed to be there.
* Ship ubuntu-dgbsym key
* Specify udeb Package-Type and bump priority to standard.
* Bump standards version
-- Dimitri John Ledkov <x...@ubuntu.com> Wed, 17 Jan 2018 16:01:45
+0000
** Changed in: ubuntu-keyring (Ubuntu)
Status: Confirmed => Fix Released
--
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/643623
Title:
Should ubuntu-keyring include the debug archive key?
Status in ubuntu-keyring package in Ubuntu:
Fix Released
Bug description:
Binary package hint: ubuntu-keyring
Currently there doesn't seem to be a good way for developers who
haven't been to many keysignings to establish trust in the Ubuntu
Debug Symbol Archive Automatic Signing Key (428D7C01)
SIgning this key with with Ubuntu Archive Automatic Signing Key (or
equivalent) and/or including the Ubuntu Debug Symbol Archive Automatic
Signing Key in ubuntu-keyring could help to solve this problem.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyring/+bug/643623/+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
