remove assumption of lp chroot extension

Bug #1858458 reported by dann frazier
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
sbuild-launchpad-chroot (Ubuntu)
Fix Released
Undecided
Unassigned
Bionic
Fix Released
Undecided
dann frazier
Disco
Won't Fix
Undecided
dann frazier
Eoan
Fix Released
Undecided
Unassigned
Focal
Fix Released
Undecided
Unassigned

Bug Description

[Impact]
s-l-c is unable to consume LP chroots. Launchpad appears to have changed the extension of stored chroots, presumably in https://git.launchpad.net/launchpad/commit/?id=3d107db183c22f6653412291bf1d66c3a2edf984

[Test Case]
Current bionic (0.14):

$ sudo sbuild-launchpad-chroot create -n bionic-amd64-sbuild -s bionic -a amd64
[bionic-amd64-sbuild] Creating config
Reading package lists... Done
Building dependency tree
Reading state information... Done
qemu-user-static is already the newest version (1:2.11+dfsg-1ubuntu7.21).
The following package was automatically installed and is no longer required:
  grub-pc-bin
Use 'sudo apt autoremove' to remove it.
0 upgraded, 0 newly installed, 0 to remove and 96 not upgraded.
[bionic-amd64-sbuild] Initial download
[bionic-amd64-sbuild] Processing config
[bionic-amd64-sbuild] Remote tarball isn't .tar.bz2.
[bionic-amd64-sbuild] Done creating

While it says "Done creating" - it actual has only created the config, not the chroot.

[Regression Risk]
A fix for this is simple, and has shipped since Eoan:
https://launchpadlibrarian.net/422109450/sbuild-launchpad-chroot_0.14_0.15.diff.gz

dann frazier (dannf)
Changed in sbuild-launchpad-chroot (Ubuntu Focal):
status: New → Fix Released
Changed in sbuild-launchpad-chroot (Ubuntu Eoan):
status: New → Fix Released
Changed in sbuild-launchpad-chroot (Ubuntu Disco):
status: New → In Progress
Changed in sbuild-launchpad-chroot (Ubuntu Bionic):
status: New → In Progress
dann frazier (dannf)
Changed in sbuild-launchpad-chroot (Ubuntu Bionic):
assignee: nobody → dann frazier (dannf)
Changed in sbuild-launchpad-chroot (Ubuntu Disco):
assignee: nobody → dann frazier (dannf)
Revision history for this message
Timo Aaltonen (tjaalton) wrote : Please test proposed package

Hello dann, or anyone else affected,

Accepted sbuild-launchpad-chroot into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/sbuild-launchpad-chroot/0.14ubuntu0.18.04.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 on 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-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed.

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

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Changed in sbuild-launchpad-chroot (Ubuntu Disco):
status: In Progress → Won't Fix
Changed in sbuild-launchpad-chroot (Ubuntu Bionic):
status: In Progress → Fix Committed
tags: added: verification-needed verification-needed-bionic
Revision history for this message
dann frazier (dannf) wrote :

Verified:

ubuntu@dannf-bionic:~$ sudo dpkg -i sbuild-launchpad-chroot_0.14ubuntu0.18.04.1_all.deb
(Reading database ... 54978 files and directories currently installed.)
Preparing to unpack sbuild-launchpad-chroot_0.14ubuntu0.18.04.1_all.deb ...
Unpacking sbuild-launchpad-chroot (0.14ubuntu0.18.04.1) over (0.14) ...
Setting up sbuild-launchpad-chroot (0.14ubuntu0.18.04.1) ...
Processing triggers for man-db (2.8.3-2ubuntu0.1) ...
ubuntu@dannf-bionic:~$ sudo sbuild-launchpad-chroot create -n bionic-amd64-sbuild -s bionic -a amd64
[bionic-amd64-sbuild] Creating config
Reading package lists... Done
Building dependency tree
Reading state information... Done
qemu-user-static is already the newest version (1:2.11+dfsg-1ubuntu7.22).
0 upgraded, 0 newly installed, 0 to remove and 9 not upgraded.
[bionic-amd64-sbuild] Initial download
[bionic-amd64-sbuild] Processing config
[bionic-amd64-sbuild] Downloading new Launchpad chroot.
tar: dev/full: Cannot mknod: Operation not permitted
tar: dev/null: Cannot mknod: Operation not permitted
tar: dev/ptmx: Cannot mknod: Operation not permitted
tar: dev/random: Cannot mknod: Operation not permitted
tar: dev/tty: Cannot mknod: Operation not permitted
tar: dev/urandom: Cannot mknod: Operation not permitted
tar: dev/zero: Cannot mknod: Operation not permitted
tar: Exiting with failure status due to previous errors
[bionic-amd64-sbuild] Done updating from Launchpad
[bionic-amd64-sbuild] Done creating
ubuntu@dannf-bionic:~$

tags: added: verification-done verification-done-bionic
removed: verification-needed verification-needed-bionic
Revision history for this message
Scott Moser (smoser) wrote :

Also verified here.
Thanks for doing this Dannf.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package sbuild-launchpad-chroot - 0.14ubuntu0.18.04.1

---------------
sbuild-launchpad-chroot (0.14ubuntu0.18.04.1) bionic; urgency=medium

  * Don't enforce .tar.bz2 suffix for the tarball, just use what Launchpad
    gives us; tar will handle it just fine. (LP: #1858458)

 -- dann frazier <email address hidden> Mon, 06 Jan 2020 10:13:55 -0700

Changed in sbuild-launchpad-chroot (Ubuntu Bionic):
status: Fix Committed → Fix Released
Revision history for this message
Łukasz Zemczak (sil2100) wrote : Update Released

The verification of the Stable Release Update for sbuild-launchpad-chroot has completed successfully and the package is now being 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.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.