** Description changed:
Binary package hint: debian-archive-keyring
The Lucid and Maverick package of d-a-k doesn't include the new Sid and
Squeeze keys being used for signing on the Debian archives.
The major symptom of this bug is that creating a pbuilder Debian chroot
fails with an Authentication failure since the required keys aren't in
the keyring.
+
+ The fixed version of the package has been uploaded to maverick-proposed
+ (I will upload to lucid-proposed soon). The package is actually a full
+ package backport from Natty. This had to be done because the
+ Lucid/Maverick package had pre-created .gpg trustsigs which could be
+ modified only by a member of the Debian Release team. Moreover, every
+ part of the package was digitally signed and the signatures were tested
+ on every build. All this made the backport from Natty the only solution.
+
+ Regressions aren't likely because:
+ 1) The bug fix is small
+ 2) Other structural changes in package are highly proven
+
+ TEST CASE: 1) Install ubuntu-dev-tools, and run the command: pbuilder-dist
sid create
+ 2) The above command should fail, with a message saying that the release file
was signed with an unknown key.
+ 3) Install the -proposed version of debian-archive-keyring
+ 4) Run pbuilder-dist sid create (No need to wait for the command to finish,
if it says 'I: Valid signature key' you can press <Control>+C and stop
pbuilder-dist). If you get the 'I: Valid signature key' message, then it means
you just successfully verified this SRU.
** Changed in: debian-archive-keyring (Ubuntu Maverick)
Status: In Progress => Fix Committed
** Changed in: debian-archive-keyring (Ubuntu Lucid)
Status: In Progress => Fix Committed
** Description changed:
Binary package hint: debian-archive-keyring
The Lucid and Maverick package of d-a-k doesn't include the new Sid and
Squeeze keys being used for signing on the Debian archives.
The major symptom of this bug is that creating a pbuilder Debian chroot
fails with an Authentication failure since the required keys aren't in
the keyring.
The fixed version of the package has been uploaded to maverick-proposed
- (I will upload to lucid-proposed soon). The package is actually a full
- package backport from Natty. This had to be done because the
- Lucid/Maverick package had pre-created .gpg trustsigs which could be
- modified only by a member of the Debian Release team. Moreover, every
- part of the package was digitally signed and the signatures were tested
- on every build. All this made the backport from Natty the only solution.
+ as well as lucid-proposed. The package is actually a full package
+ backport from Natty. This had to be done because the Lucid/Maverick
+ package had pre-created .gpg trustsigs which could be modified only by a
+ member of the Debian Release team. Moreover, every part of the package
+ was digitally signed and the signatures were tested on every build. All
+ this made the backport from Natty the only solution.
Regressions aren't likely because:
1) The bug fix is small
2) Other structural changes in package are highly proven
TEST CASE: 1) Install ubuntu-dev-tools, and run the command: pbuilder-dist
sid create
2) The above command should fail, with a message saying that the release file
was signed with an unknown key.
3) Install the -proposed version of debian-archive-keyring
4) Run pbuilder-dist sid create (No need to wait for the command to finish,
if it says 'I: Valid signature key' you can press <Control>+C and stop
pbuilder-dist). If you get the 'I: Valid signature key' message, then it means
you just successfully verified this SRU.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/722521
Title:
Lucid/Maverick package doesn't contain new Sid/Squeeze keys
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
