sbuild-launchpad-chroot does not notice tar extract failures

[Scott Moser]

Nothing is checking exit code of tar when the downloaded tarball is extracted.

Tar could fail for many reasons including permission or
filesystem full.

If tar failed, sbuild-launchpad-chroot would just continue on.
The user would likely fail in a less obvious way later on.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: sbuild-launchpad-chroot 0.17ubuntu0.20.10.1~20.04.1
ProcVersionSignature: Ubuntu 5.11.0-46.51~20.04.1-generic 5.11.22
Uname: Linux 5.11.0-46-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Jan 27 12:22:26 2022
InstallationDate: Installed on 2020-01-15 (742 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: sbuild-launchpad-chroot
UpgradeStatus: Upgraded to focal on 2020-04-17 (650 days ago)

[Launchpad Janitor (janitor)]

This bug was fixed in the package sbuild-launchpad-chroot - 0.19

---------------
sbuild-launchpad-chroot (0.19) jammy; urgency=medium

  * Check the exit code of tar when extracting a root file system.
    Thanks to Scott Moser. (LP: #1959324)

 -- dann frazier <email address hidden> Mon, 31 Jan 2022 12:38:07 -0700

[Brian Murray (brian-murray)]

Ubuntu 21.10 (Impish Indri) has reached end of life, so this bug will not be fixed for that specific release.