SRU: Add zesty series link

Bug #1636583 reported by Joshua Powers on 2016-10-25
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
debootstrap (Ubuntu)
High
Joshua Powers
Precise
High
Joshua Powers
Trusty
High
Joshua Powers
Xenial
High
Joshua Powers
Yakkety
High
Joshua Powers

Bug Description

Add new link for Zesty Zapus.

[Impact]

 * Users are unable to create Zesty Zapus chroots on older series.
 * Restricts and slows development.

[Test Case]

 * sudo debootstrap zesty /tmp/zesty

[Regression Potential]

 * Configuration only change, low chance of regression of existing functionality.
 * Change to packaging involves a new change log entry and an additional symlink to enable zesty.

Joshua Powers (powersj) on 2016-10-25
Changed in debootstrap (Ubuntu):
assignee: nobody → Joshua Powers (powersj)
status: New → In Progress
importance: Undecided → High
Joshua Powers (powersj) wrote :

Initial set of packages uploaded to:
https://launchpad.net/~powersj/+archive/ubuntu/debootstrap-1636583

This is literally my first upload to a PPA so a review would be greatly appreciated. As this is an SRU I made only the following two changes:

* Updated change log
* Added symlink from gutsy to zesty

Things I know need to be verified:

1) Put my name in change log + signed with my key -- is this correct?
2) Versions updated correctly? Used dch's suggestions
3) I put ~ppa in the version so I do not have to up the version in case this are incorrect

Changed in debootstrap (Ubuntu Precise):
assignee: nobody → Joshua Powers (powersj)
Changed in debootstrap (Ubuntu Trusty):
assignee: nobody → Joshua Powers (powersj)
Changed in debootstrap (Ubuntu Xenial):
assignee: nobody → Joshua Powers (powersj)
Changed in debootstrap (Ubuntu Yakkety):
assignee: nobody → Joshua Powers (powersj)
Changed in debootstrap (Ubuntu Precise):
status: New → In Progress
Changed in debootstrap (Ubuntu Trusty):
status: New → In Progress
Changed in debootstrap (Ubuntu Xenial):
status: New → In Progress
Changed in debootstrap (Ubuntu Yakkety):
status: New → In Progress
Joshua Powers (powersj) wrote :
Joshua Powers (powersj) wrote :
Joshua Powers (powersj) wrote :
Joshua Powers (powersj) wrote :

Hello Joshua, or anyone else affected,

Accepted debootstrap into yakkety-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/debootstrap/1.0.81ubuntu2.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Changed in debootstrap (Ubuntu Yakkety):
status: In Progress → Fix Committed
tags: added: verification-needed
Changed in debootstrap (Ubuntu Xenial):
status: In Progress → Fix Committed
Andy Whitcroft (apw) wrote :

Hello Joshua, or anyone else affected,

Accepted debootstrap into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/debootstrap/1.0.78+nmu1ubuntu1.2 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Changed in debootstrap (Ubuntu Trusty):
status: In Progress → Fix Committed
Andy Whitcroft (apw) wrote :

Hello Joshua, or anyone else affected,

Accepted debootstrap into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/debootstrap/1.0.59ubuntu0.6 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Changed in debootstrap (Ubuntu):
status: In Progress → Fix Released
Changed in debootstrap (Ubuntu Precise):
status: In Progress → Fix Committed
Andy Whitcroft (apw) wrote :

Hello Joshua, or anyone else affected,

Accepted debootstrap into precise-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/debootstrap/1.0.40~ubuntu0.11 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Joshua Powers (powersj) wrote :

Validation completed successfully.

In amd64 VMs of precise, trusty, xenial, and yakkety I installed the packages from proposed and rebooted and then preformed the following tests:

> sudo debootstrap zesty /tmp/zesty
> sudo debootstrap $RELEASE /tmp/$RELEASE

Release and dpkg info (output truncated)
---
ubuntu@precise:~$ cat /etc/os-release | grep PRETTY_NAME
PRETTY_NAME="Ubuntu precise (12.04.5 LTS)"
ubuntu@precise:~$ dpkg -l | grep debootstrap
ii debootstrap 1.0.40~ubuntu0.11

ubuntu@trusty:~$ cat /etc/os-release | grep PRETTY_NAME
PRETTY_NAME="Ubuntu 14.04.5 LTS"
ubuntu@trusty:~$ dpkg -l | grep debootstrap
ii debootstrap 1.0.59ubuntu0.6

ubuntu@xenial:~$ cat /etc/os-release | grep PRETTY_NAME
PRETTY_NAME="Ubuntu 16.04.1 LTS"
ubuntu@xenial:~$ dpkg -l | grep debootstrap
ii debootstrap 1.0.78+nmu1ubuntu1.2

ubuntu@yakkety:~$ cat /etc/os-release | grep PRETTY_NAME
PRETTY_NAME="Ubuntu 16.10"
ubuntu@yakkety:~$ dpkg -l | grep debootstrap
ii debootstrap 1.0.81ubuntu2.1

rmadison
---
$ rmadison debootstrap | grep proposed
 debootstrap | 1.0.40~ubuntu0.11 | precise-proposed | source, all
 debootstrap | 1.0.59ubuntu0.6 | trusty-proposed | source, all
 debootstrap | 1.0.78+nmu1ubuntu1.2 | xenial-proposed | source, all
 debootstrap | 1.0.81ubuntu2.1 | yakkety-proposed | source, all

tags: added: verification-done
removed: verification-needed
Changed in debootstrap (Ubuntu Precise):
importance: Undecided → High
Changed in debootstrap (Ubuntu Trusty):
importance: Undecided → High
Changed in debootstrap (Ubuntu Xenial):
importance: Undecided → High
Changed in debootstrap (Ubuntu Yakkety):
importance: Undecided → High
Joshua Powers (powersj) wrote :
Download full text (3.2 KiB)

There were 5 regression failures:

pbuilder xenial armhf [1]
pbuilder yakkety armhf [2]
lxc yakkety ppc64el [3]
lxc yakkety i386 [4]
lxc yakkety amd64 [5]

The pbuilder failure on both tests was:

+ debootstrap --include=apt --variant=buildd --force-check-gpg --keyring=/usr/share/keyrings/ubuntu-archive-keyring.gpg zesty /var/cache/pbuilder/build/3033 http://ports.ubuntu.com
mknod: /var/cache/pbuilder/build/3033/test-dev-null: Operation not permitted
E: Cannot install into target '/var/cache/pbuilder/build/3033' mounted with noexec or nodev

The lxc failures on all tests were:

FAIL: lxc-tests: /usr/bin/lxc-test-apparmor-mount
---
/usr/sbin/deluser: The user `lxcunpriv' does not exist.
Setting up the GPG keyring
ERROR: Unable to fetch GPG key from keyserver.
lxc-create: lxccontainer.c: create_run_template: 1290 container creation template for tmp.wh4fX3mL73 failed
lxc-create: tools/lxc_create.c: main: 318 Error creating container tmp.wh4fX3mL73
Container is not defined
umount: /sys/kernel/security/apparmor/features/mount: not mounted
---

FAIL: lxc-tests: /usr/bin/lxc-test-autostart
---
Setting up the GPG keyring
ERROR: Unable to fetch GPG key from keyserver.
lxc-create: lxccontainer.c: create_run_template: 1290 container creation template for lxc-test-auto failed
lxc-create: tools/lxc_create.c: main: 318 Error creating container lxc-test-auto
FAIL
---

FAIL: lxc-tests: /usr/bin/lxc-test-unpriv
---
Removing user `lxcunpriv' ...
Warning: group `lxcunpriv' has no more members.
userdel: user lxcunpriv is currently used by process 5094
/usr/sbin/deluser: `/usr/sbin/userdel lxcunpriv' returned error code 8. Exiting.
useradd: user 'lxcunpriv' already exists
c2 is not running
c1 is not running
---

FAIL: lxc-tests: /usr/bin/lxc-test-usernic
---
/usr/sbin/deluser: The user `usernic-user' does not exist.
Setting up the GPG keyring
ERROR: Unable to fetch GPG key from keyserver.
lxc-create: lxccontainer.c: create_run_template: 1290 container creation template for b1 failed
lxc-create: tools/lxc_create.c: main: 318 Error creating container b1
---

FAIL: python3: API
---
Setting up the GPG keyring
ERROR: Unable to fetch GPG key from keyserver.
Getting instance for '3418f024-9bca-11e6-b8a6-fa163e7381ec'
Creating rootfs using 'download', arch=ppc64el
Traceback (most recent call last):
  File "/tmp/tmp.U2pTs7YjpB", line 71, in <module>
    assert(container.defined)
AssertionError
---

[1] https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/armhf/p/pbuilder/20161026_210549_97cde@/log.gz
[2] https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-yakkety/yakkety/armhf/p/pbuilder/20161026_210422_68aad@/log.gz
[3] https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-yakkety/yakkety/ppc64el/l/lxc/20161026_224531_0bfb9@/log.gz
[4] https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-yakkety/yakkety/i386/l/lxc/20161026_225237_0bfb9@/log.gz
[5] https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-yakkety/yakket...

Read more...

Launchpad Janitor (janitor) wrote :

This bug was fixed in the package debootstrap - 1.0.40~ubuntu0.11

---------------
debootstrap (1.0.40~ubuntu0.11) precise; urgency=medium

  * Add (Ubuntu) zesty as a symlink to gutsy. (LP: #1636583)

 -- Joshua Powers <email address hidden> Tue, 25 Oct 2016 15:46:11 -0600

Changed in debootstrap (Ubuntu Precise):
status: Fix Committed → Fix Released

The verification of the Stable Release Update for debootstrap has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

Launchpad Janitor (janitor) wrote :

This bug was fixed in the package debootstrap - 1.0.59ubuntu0.6

---------------
debootstrap (1.0.59ubuntu0.6) trusty; urgency=medium

  * Add (Ubuntu) zesty as a symlink to gutsy. (LP: #1636583)

 -- Joshua Powers <email address hidden> Tue, 25 Oct 2016 15:55:02 -0600

Changed in debootstrap (Ubuntu Trusty):
status: Fix Committed → Fix Released
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package debootstrap - 1.0.78+nmu1ubuntu1.2

---------------
debootstrap (1.0.78+nmu1ubuntu1.2) xenial; urgency=medium

  * Add (Ubuntu) zesty as a symlink to gutsy. (LP: #1636583)

 -- Joshua Powers <email address hidden> Tue, 25 Oct 2016 13:37:00 -0600

Changed in debootstrap (Ubuntu Xenial):
status: Fix Committed → Fix Released
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package debootstrap - 1.0.81ubuntu2.1

---------------
debootstrap (1.0.81ubuntu2.1) yakkety; urgency=medium

  * Add (Ubuntu) zesty as a symlink to gutsy. (LP: #1636583)

 -- Joshua Powers <email address hidden> Tue, 25 Oct 2016 15:59:15 -0600

Changed in debootstrap (Ubuntu Yakkety):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers