[Group.of.nepali.translators] [Bug 1645906] Re: new dist-upgrader tarballs necessary so they are signed with 4k key

2016-12-07 Thread Mathew Hodson 
** 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 नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1645906

Title:
  new dist-upgrader tarballs necessary so they are signed with 4k key

Status in ubuntu-release-upgrader package in Ubuntu:
  New
Status in update-manager source package in Precise:
  Fix Released
Status in ubuntu-release-upgrader source package in Trusty:
  Fix Released
Status in ubuntu-release-upgrader source package in Xenial:
  Fix Released
Status in ubuntu-release-upgrader source package in Yakkety:
  Fix Released

Bug description:
  With the ubuntu-archive-publishing change in
  https://code.launchpad.net/~xnox/ubuntu-archive-publishing/migrate-
  dist-upgrade-to-4k/+merge/311181 the signing process for the dist-
  upgrader tarball has been changed.  This change should be tested now,
  rather than doing an ubuntu-release-upgrader change months from now
  and wondering why things aren't working (if they are broken).

  Due to the way the gpg signature is generated we can't just remove it
  and have it regenerated as the timestamp for the signature will not
  change, so the change will not propogate to the mirrors.  Hence the
  need for a mostly no change (mirrors and demotions may change) upload
  of ubuntu-release-upgrader.

  Test Case
  -
  1) run do-release-upgrade -p --frontend DistUpgradeViewText
  2) ensure the tarball for the next release e.g. xenial.tar.gz is downloaded 
and the signature verification passes

  Regression Potential
  
  It's possible the signing is wrong and the verification of the signature will 
fail thereby causing release upgrades to be impossible.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1645906/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1645906] Re: new dist-upgrader tarballs necessary so they are signed with 4k key

2016-12-07 Thread Launchpad Bug Tracker 
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 09:53:35 -0800

** Changed in: update-manager (Ubuntu Precise)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1645906

Title:
  new dist-upgrader tarballs necessary so they are signed with 4k key

Status in ubuntu-release-upgrader package in Ubuntu:
  New
Status in update-manager package in Ubuntu:
  Invalid
Status in update-manager source package in Precise:
  Fix Released
Status in ubuntu-release-upgrader source package in Trusty:
  Fix Released
Status in update-manager source package in Trusty:
  Invalid
Status in ubuntu-release-upgrader source package in Xenial:
  Fix Released
Status in update-manager source package in Xenial:
  Invalid
Status in ubuntu-release-upgrader source package in Yakkety:
  Fix Released
Status in update-manager source package in Yakkety:
  Invalid

Bug description:
  With the ubuntu-archive-publishing change in
  https://code.launchpad.net/~xnox/ubuntu-archive-publishing/migrate-
  dist-upgrade-to-4k/+merge/311181 the signing process for the dist-
  upgrader tarball has been changed.  This change should be tested now,
  rather than doing an ubuntu-release-upgrader change months from now
  and wondering why things aren't working (if they are broken).

  Due to the way the gpg signature is generated we can't just remove it
  and have it regenerated as the timestamp for the signature will not
  change, so the change will not propogate to the mirrors.  Hence the
  need for a mostly no change (mirrors and demotions may change) upload
  of ubuntu-release-upgrader.

  Test Case
  -
  1) run do-release-upgrade -p --frontend DistUpgradeViewText
  2) ensure the tarball for the next release e.g. xenial.tar.gz is downloaded 
and the signature verification passes

  Regression Potential
  
  It's possible the signing is wrong and the verification of the signature will 
fail thereby causing release upgrades to be impossible.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1645906/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1645906] Re: new dist-upgrader tarballs necessary so they are signed with 4k key

2016-12-07 Thread Launchpad Bug Tracker 
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:54 -0800

** Changed in: ubuntu-release-upgrader (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

** Changed in: ubuntu-release-upgrader (Ubuntu Trusty)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1645906

Title:
  new dist-upgrader tarballs necessary so they are signed with 4k key

Status in ubuntu-release-upgrader package in Ubuntu:
  New
Status in update-manager package in Ubuntu:
  Invalid
Status in update-manager source package in Precise:
  Fix Released
Status in ubuntu-release-upgrader source package in Trusty:
  Fix Released
Status in update-manager source package in Trusty:
  Invalid
Status in ubuntu-release-upgrader source package in Xenial:
  Fix Released
Status in update-manager source package in Xenial:
  Invalid
Status in ubuntu-release-upgrader source package in Yakkety:
  Fix Released
Status in update-manager source package in Yakkety:
  Invalid

Bug description:
  With the ubuntu-archive-publishing change in
  https://code.launchpad.net/~xnox/ubuntu-archive-publishing/migrate-
  dist-upgrade-to-4k/+merge/311181 the signing process for the dist-
  upgrader tarball has been changed.  This change should be tested now,
  rather than doing an ubuntu-release-upgrader change months from now
  and wondering why things aren't working (if they are broken).

  Due to the way the gpg signature is generated we can't just remove it
  and have it regenerated as the timestamp for the signature will not
  change, so the change will not propogate to the mirrors.  Hence the
  need for a mostly no change (mirrors and demotions may change) upload
  of ubuntu-release-upgrader.

  Test Case
  -
  1) run do-release-upgrade -p --frontend DistUpgradeViewText
  2) ensure the tarball for the next release e.g. xenial.tar.gz is downloaded 
and the signature verification passes

  Regression Potential
  
  It's possible the signing is wrong and the verification of the signature will 
fail thereby causing release upgrades to be impossible.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1645906/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1645906] Re: new dist-upgrader tarballs necessary so they are signed with 4k key

2016-12-07 Thread Launchpad Bug Tracker 
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 14:59:34 -0800

** Changed in: ubuntu-release-upgrader (Ubuntu Yakkety)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1645906

Title:
  new dist-upgrader tarballs necessary so they are signed with 4k key

Status in ubuntu-release-upgrader package in Ubuntu:
  New
Status in update-manager package in Ubuntu:
  Invalid
Status in update-manager source package in Precise:
  Fix Released
Status in ubuntu-release-upgrader source package in Trusty:
  Fix Released
Status in update-manager source package in Trusty:
  Invalid
Status in ubuntu-release-upgrader source package in Xenial:
  Fix Released
Status in update-manager source package in Xenial:
  Invalid
Status in ubuntu-release-upgrader source package in Yakkety:
  Fix Released
Status in update-manager source package in Yakkety:
  Invalid

Bug description:
  With the ubuntu-archive-publishing change in
  https://code.launchpad.net/~xnox/ubuntu-archive-publishing/migrate-
  dist-upgrade-to-4k/+merge/311181 the signing process for the dist-
  upgrader tarball has been changed.  This change should be tested now,
  rather than doing an ubuntu-release-upgrader change months from now
  and wondering why things aren't working (if they are broken).

  Due to the way the gpg signature is generated we can't just remove it
  and have it regenerated as the timestamp for the signature will not
  change, so the change will not propogate to the mirrors.  Hence the
  need for a mostly no change (mirrors and demotions may change) upload
  of ubuntu-release-upgrader.

  Test Case
  -
  1) run do-release-upgrade -p --frontend DistUpgradeViewText
  2) ensure the tarball for the next release e.g. xenial.tar.gz is downloaded 
and the signature verification passes

  Regression Potential
  
  It's possible the signing is wrong and the verification of the signature will 
fail thereby causing release upgrades to be impossible.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1645906/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1645906] Re: new dist-upgrader tarballs necessary so they are signed with 4k key

2016-12-02 Thread Mathew Hodson 
** No longer affects: ubuntu-release-upgrader (Ubuntu Precise)

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1645906

Title:
  new dist-upgrader tarballs necessary so they are signed with 4k key

Status in ubuntu-release-upgrader package in Ubuntu:
  New
Status in update-manager package in Ubuntu:
  Invalid
Status in update-manager source package in Precise:
  Fix Committed
Status in ubuntu-release-upgrader source package in Trusty:
  Fix Committed
Status in update-manager source package in Trusty:
  Invalid
Status in ubuntu-release-upgrader source package in Xenial:
  Fix Committed
Status in update-manager source package in Xenial:
  Invalid
Status in ubuntu-release-upgrader source package in Yakkety:
  Fix Committed
Status in update-manager source package in Yakkety:
  Invalid

Bug description:
  With the ubuntu-archive-publishing change in
  https://code.launchpad.net/~xnox/ubuntu-archive-publishing/migrate-
  dist-upgrade-to-4k/+merge/311181 the signing process for the dist-
  upgrader tarball has been changed.  This change should be tested now,
  rather than doing an ubuntu-release-upgrader change months from now
  and wondering why things aren't working (if they are broken).

  Due to the way the gpg signature is generated we can't just remove it
  and have it regenerated as the timestamp for the signature will not
  change, so the change will not propogate to the mirrors.  Hence the
  need for a mostly no change (mirrors and demotions may change) upload
  of ubuntu-release-upgrader.

  Test Case
  -
  1) run do-release-upgrade -p --frontend DistUpgradeViewText
  2) ensure the tarball for the next release e.g. xenial.tar.gz is downloaded 
and the signature verification passes

  Regression Potential
  
  It's possible the signing is wrong and the verification of the signature will 
fail thereby causing release upgrades to be impossible.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1645906/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1645906] Re: new dist-upgrader tarballs necessary so they are signed with 4k key

2016-11-30 Thread Brian Murray 
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

** Changed in: ubuntu-release-upgrader (Ubuntu Precise)
   Status: New => Invalid

** Changed in: update-manager (Ubuntu)
   Status: New => Invalid

** Changed in: update-manager (Ubuntu Precise)
   Status: New => In Progress

** Changed in: update-manager (Ubuntu Precise)
 Assignee: (unassigned) => Brian Murray (brian-murray)

** Changed in: update-manager (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: update-manager (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: update-manager (Ubuntu Yakkety)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1645906

Title:
  new dist-upgrader tarballs necessary so they are signed with 4k key

Status in ubuntu-release-upgrader package in Ubuntu:
  New
Status in update-manager package in Ubuntu:
  Invalid
Status in ubuntu-release-upgrader source package in Precise:
  Invalid
Status in update-manager source package in Precise:
  In Progress
Status in ubuntu-release-upgrader source package in Trusty:
  In Progress
Status in update-manager source package in Trusty:
  Invalid
Status in ubuntu-release-upgrader source package in Xenial:
  In Progress
Status in update-manager source package in Xenial:
  Invalid
Status in ubuntu-release-upgrader source package in Yakkety:
  Fix Committed
Status in update-manager source package in Yakkety:
  Invalid

Bug description:
  With the ubuntu-archive-publishing change in
  https://code.launchpad.net/~xnox/ubuntu-archive-publishing/migrate-
  dist-upgrade-to-4k/+merge/311181 the signing process for the dist-
  upgrader tarball has been changed.  This change should be tested now,
  rather than doing an ubuntu-release-upgrader change months from now
  and wondering why things aren't working (if they are broken).

  Due to the way the gpg signature is generated we can't just remove it
  and have it regenerated as the timestamp for the signature will not
  change, so the change will not propogate to the mirrors.  Hence the
  need for a mostly no change (mirrors and demotions may change) upload
  of ubuntu-release-upgrader.

  Test Case
  -
  1) run do-release-upgrade -p --frontend DistUpgradeViewText
  2) ensure the tarball for the next release e.g. xenial.tar.gz is downloaded 
and the signature verification passes

  Regression Potential
  
  It's possible the signing is wrong and the verification of the signature will 
fail thereby causing release upgrades to be impossible.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1645906/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp