** Branch linked: lp:~ubuntu-core-dev/ubuntu-release-upgrader/yakkety
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1645906
Title:
new dist-upgrader tarballs necessary so they are signed with 4k key
** No longer affects: update-manager (Ubuntu)
** No longer affects: update-manager (Ubuntu Trusty)
** No longer affects: update-manager (Ubuntu Xenial)
** No longer affects: update-manager (Ubuntu Yakkety)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This bug was fixed in the package update-manager - 1:0.156.14.21
---
update-manager (1:0.156.14.21) precise-proposed; urgency=medium
* No change rebuild so the dist-upgrader tarball will be signed with the new
method. (LP: #1645906)
-- Brian Murray Wed, 30 Nov 2016 10:54:24
This bug was fixed in the package ubuntu-release-upgrader - 1:0.220.9
---
ubuntu-release-upgrader (1:0.220.9) trusty-proposed; urgency=medium
* No change rebuild so the dist-upgrader tarball will be signed with the new
method. (LP: #1645906)
-- Brian Murray Wed, 30 Nov 2016
This bug was fixed in the package ubuntu-release-upgrader - 1:16.04.19
---
ubuntu-release-upgrader (1:16.04.19) xenial; urgency=medium
* No change rebuild so the dist-upgrader tarball will be signed with the new
method. (LP: #1645906)
-- Brian Murray Wed, 30 Nov 2016 08:26:5
This bug was fixed in the package ubuntu-release-upgrader - 1:16.10.9
---
ubuntu-release-upgrader (1:16.10.9) yakkety-proposed; urgency=medium
* No change rebuild so the dist-upgrader tarball will be signed with the new
method. (LP: #1645906)
-- Brian Murray Tue, 29 Nov 2016
Bug 1647014 is not a regression related to the key signing, I'll remove
the tag.
** Tags removed: verification-failed
** Tags removed: verification-needed
** Tags added: verification-done-precise
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** No longer affects: ubuntu-release-upgrader (Ubuntu Precise)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1645906
Title:
new dist-upgrader tarballs necessary so they are signed with 4k key
To ma
** Tags added: verification-done-trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1645906
Title:
new dist-upgrader tarballs necessary so they are signed with 4k key
To manage notifications abou
zesty, yakkety, xenial are correctly signed with 4k, sha512.
trusty, precise are correctly signed with 1k, sha1.
Everything is as expected.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1645906
Title
Ah, for precise the key signing date was wrong. Tried it again with the
same results.
(precise2-amd64)root@impulse:/home/bdmurray/source-trees/ubuntu-archive-tools/upstream#
gpg --list-packets /tmp/update-manager-TEgnXk/trusty.tar.gz.gpg
:signature packet: algo 17, keyid 40976EAF437D05B5
I think that's correct for precise.
(precise2-amd64)root@impulse:/home/bdmurray/source-trees/update-notifier/trunk#
do-release-upgrade -p --frontend DistUpgradeViewText
Checking for a new Ubuntu release
Get:1 Upgrade tool signature [198 B]
Get:2 Upgrade tool [1156 kB]
Fetched 1156 kB in 0s (0 B/s
Looks good for xenial too:
bdmurray@upgrade-trusty-amd64:~$ do-release-upgrade -p --frontend
DistUpgradeViewText
Checking for a new Ubuntu release
Get:1 Upgrade tool signature [836 B]
Get:2 Upgrade tool [1,266 kB]
Fetched 1,267 kB in 0s (0 B/s)
authenticate 'xenial.tar.gz' against 'xenial.tar.gz.
Hello Brian, or anyone else affected,
Accepted ubuntu-release-upgrader into xenial-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/ubuntu-release-upgrader/1:16.04.19 in a few hours, and then in the
-proposed repository.
Please help us by testing this
I've uploaded an update to ubuntu-release-upgrader to zesty, but its
autopkgtest is failing because it can't verify the xenial tarball. Once
the xenial update is released, we should rerun the zesty autopkgtests.
** Also affects: update-manager (Ubuntu)
Importance: Undecided
Status: New
** Branch linked: lp:ubuntu/trusty-proposed/ubuntu-release-upgrader
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1645906
Title:
new dist-upgrader tarballs necessary so they are signed with 4k key
** Changed in: ubuntu-release-upgrader (Ubuntu Trusty)
Status: New => In Progress
** Changed in: ubuntu-release-upgrader (Ubuntu Trusty)
Assignee: (unassigned) => Brian Murray (brian-murray)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
This looks good to me for yakkety.
bdmurray@clean-xenial-amd64:~$ do-release-upgrade -p --frontend
DistUpgradeViewText
Checking for a new Ubuntu release
Get:1 Upgrade tool signature [836 B]
Get:2 Upgrade tool [1,258 kB]
Fetched 1,259 kB in 0s (0 B/s)
authenticate 'yakkety.tar.gz' against 'yakkety
Hello Brian, or anyone else affected,
Accepted ubuntu-release-upgrader into yakkety-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/ubuntu-release-upgrader/1:16.10.9 in a few hours, and then in the
-proposed repository.
Please help us by testing this
19 matches
Mail list logo