[Touch-packages] [Bug 1693897] [NEW] It seems like sometimes 'archive' can't be found for a package
Public bug reported: This is for: python-apt 1.4.0~beta2 I wrote a script to find the latest kernel available for each major.minor, per Ubuntu release (that I configure) and sometimes it spits out: Unknown distro for package: linux-image-3.2.0-23-generic - [] precise: 3.13: 3.13.0-117 3.11: 3.11.0-26 3.8: 3.8.0-44 3.5: 3.5.0-54 3.2: 3.2.0-126 xenial: 4.10: 4.10.0-14 4.8: 4.8.0-53 4.4: 4.4.0-78 zesty: 4.10: 4.10.0-21 Where archive is blank. Other times it works... Please advise. ** Affects: python-apt (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1693897 Title: It seems like sometimes 'archive' can't be found for a package Status in python-apt package in Ubuntu: New Bug description: This is for: python-apt 1.4.0~beta2 I wrote a script to find the latest kernel available for each major.minor, per Ubuntu release (that I configure) and sometimes it spits out: Unknown distro for package: linux-image-3.2.0-23-generic - [] precise: 3.13: 3.13.0-117 3.11: 3.11.0-26 3.8: 3.8.0-44 3.5: 3.5.0-54 3.2: 3.2.0-126 xenial: 4.10: 4.10.0-14 4.8: 4.8.0-53 4.4: 4.4.0-78 zesty: 4.10: 4.10.0-21 Where archive is blank. Other times it works... Please advise. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1693897/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1693930] [NEW] python-apt complains even if trusted=yes in sources.list
Public bug reported:
Any help would be appreciated.
python-apt - 1.1.0~beta1build1
--- Python Code ---
import apt
import re
import sys
from distutils.version import LooseVersion
cache = apt.Cache(memonly=True, rootdir='/home/seitz/tmp/apt_root')
try:
cache.update(sources_list='/home/seitz/tmp/apt_root/etc/apt/sources.list',
raise_on_error=False)
except Exception as e:
print e
pass
cache.open(None)
kernel_versions = {}
for pkg_name in cache.keys():
kernel_version = re.search(r'linux-image-([\d\-\.]+)-generic', pkg_name)
if kernel_version:
distro_re = re.search(r'^([A-Za-z]+)-?',
cache[pkg_name].candidate.origins[0].archive)
if distro_re:
distro = distro_re.group(1)
else:
distro = 'custom'
major_minor = re.search(r'^(\d+.\d+)', kernel_version.group(1))
kernel_versions.setdefault(distro, {})
kernel_versions[distro].setdefault(major_minor.group(1), [])
kernel_versions[distro][major_minor.group(1)].append(kernel_version.group(1))
for distro in sorted(kernel_versions):
print "{}:".format(distro)
for major_minor in sorted(kernel_versions[distro], key=lambda s: map(int,
s.split('.')), reverse=True):
kernel_versions[distro][major_minor].sort(key=LooseVersion)
print "\t{}:".format(major_minor)
print "\t\t{}".format(kernel_versions[distro][major_minor].pop())
--- Output ---
seitz@host ~ % python apt-get-latest.py
W:GPG error: http://infra-mirror/ubuntu artful-backports InRelease: The
following signatures couldn't be verified because the public key is not
available: NO_PUBKEY 3B4FE6ACC0B21F32, W:GPG error: http://infra-mirror/ubuntu
artful InRelease: The following signatures couldn't be verified because the
public key is not available: NO_PUBKEY 3B4FE6ACC0B21F32, W:GPG error:
http://infra-mirror/ubuntu artful-security InRelease: The following signatures
couldn't be verified because the public key is not available: NO_PUBKEY
3B4FE6ACC0B21F32, W:GPG error: http://infra-mirror/ubuntu artful-updates
InRelease: The following signatures couldn't be verified because the public key
is not available: NO_PUBKEY 3B4FE6ACC0B21F32, W:GPG error:
http://infra-mirror/ubuntu zesty-backports InRelease: The following signatures
couldn't be verified because the public key is not available: NO_PUBKEY
3B4FE6ACC0B21F32, W:GPG error: http://infra-mirror/ubuntu zesty InRelease: The
following signatures couldn't be ver
ified because the public key is not available: NO_PUBKEY 3B4FE6ACC0B21F32,
W:http://host/annex-apt-precise/apt/precise/dists/precise/Release.gpg:
Signature by key 630239CC130E1A7FD81A27B140976EAF437D05B5 uses weak digest
algorithm (SHA1), W:GPG error: http://infra-mirror/ubuntu zesty-security
InRelease: The following signatures couldn't be verified because the public key
is not available: NO_PUBKEY 3B4FE6ACC0B21F32, W:GPG error:
http://infra-mirror/ubuntu zesty-updates InRelease: The following signatures
couldn't be verified because the public key is not available: NO_PUBKEY
3B4FE6ACC0B21F32,
W:http://host/annex-apt-precise/apt/precise/dists/precise-backports/Release.gpg:
Signature by key 630239CC130E1A7FD81A27B140976EAF437D05B5 uses weak digest
algorithm (SHA1),
W:http://host/annex-apt-precise/apt/precise/dists/precise-security/Release.gpg:
Signature by key 630239CC130E1A7FD81A27B140976EAF437D05B5 uses weak digest
algorithm (SHA1), W:http://host/annex-apt-precise/apt/precise/dists/
precise-updates/Release.gpg: Signature by key
630239CC130E1A7FD81A27B140976EAF437D05B5 uses weak digest algorithm (SHA1),
E:Failed to fetch
http://host/annex-apt-precise/apt/precise/dists/precise-backports/main/i18n/Translation-en
404 Not Found [IP: 10.40.25.157 80], E:Failed to fetch
http://host/annex-apt-precise/apt/precise/dists/precise-security/main/i18n/Translation-en
404 Not Found [IP: 10.40.25.157 80], E:Failed to fetch
http://host/annex-apt-precise/apt/precise/dists/precise-updates/main/i18n/Translation-en
404 Not Found [IP: 10.40.25.157 80], E:Some index files failed to download.
They have been ignored, or old ones used instead.
artful:
4.10:
4.10.0-21
custom:
3.16:
3.16.0-77
precise:
3.2:
3.2.0-23
xenial:
4.10:
4.10.0-14
4.8:
4.8.0-36
4.4:
4.4.0-78
yakkety:
4.8:
4.8.0-53
zesty:
4.10:
4.10.0-20
--- Sources.list ---
deb [arch=amd64 trusted=yes] http://infra-mirror/ubuntu artful-backports main
universe restricted
deb [arch=amd64 trusted=yes] http://infra-mirror/ubuntu artful main universe
restricted
deb [arch=amd64 trusted=yes] http://infra-mirror/ubuntu artful-security main
universe restricted
deb [arch=amd64 trusted=yes] http://infra-mirror/ubuntu artful-updates main
universe restricted
deb [arch=amd64 trusted=yes] http://host/apt-kernel/apt/3.16.0-77 3.16.0-77
[Touch-packages] [Bug 1693941] [NEW] passing an absolute path for sources_list to cache.update does not work
Public bug reported: Using python-apt 1.1.0~beta1build1. Calling cache like such: cache = apt.Cache(memonly=True, rootdir='/home/seitz/tmp/apt_root') cache.update(sources_list='/home/seitz/tmp/apt_root/etc/apt/sources-zesty.list') Would produce an empty cache :( If I copy the contents of sources- zesty.list to sources.list in that same directory and pass that path as an argument, it functions properly. I am looping over several Ubuntu releases as including them all in one sources.list caused conflicts. Please advise. ** Affects: python-apt (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1693941 Title: passing an absolute path for sources_list to cache.update does not work Status in python-apt package in Ubuntu: New Bug description: Using python-apt 1.1.0~beta1build1. Calling cache like such: cache = apt.Cache(memonly=True, rootdir='/home/seitz/tmp/apt_root') cache.update(sources_list='/home/seitz/tmp/apt_root/etc/apt/sources-zesty.list') Would produce an empty cache :( If I copy the contents of sources- zesty.list to sources.list in that same directory and pass that path as an argument, it functions properly. I am looping over several Ubuntu releases as including them all in one sources.list caused conflicts. Please advise. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1693941/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1753572] Re: cpio in Busybox 1.27 ingnores "unsafe links"
This does look good now, thanks! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to busybox in Ubuntu. https://bugs.launchpad.net/bugs/1753572 Title: cpio in Busybox 1.27 ingnores "unsafe links" Status in busybox package in Ubuntu: Confirmed Status in debirf package in Ubuntu: Confirmed Status in busybox source package in Bionic: Confirmed Status in debirf source package in Bionic: New Status in busybox source package in Cosmic: Confirmed Status in debirf source package in Cosmic: Confirmed Bug description: Description:Ubuntu Bionic Beaver (development branch) Release:18.04 busybox: Installed: 1:1.27.2-2ubuntu3 Candidate: 1:1.27.2-2ubuntu3 3) Expected my CPIO archive to be fully extracted with proper symlinks Command: unxz < /rootfs.cxz | cpio -i 4) 'Unsafe' symlinks were ignored such as: sbin/init -> /lib/systemd/systemd With the broken 1.27 sbin/init does not get created at all and my debirf initrd fails to load/boot properly. 1.22 from Xenial works. GNU Cpio also works. It looks like 1.28 adds an env var to override this behavior: libarchive: do not extract unsafe symlinks unless $EXTRACT_UNSAFE_SYMLINKS=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/1753572/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1753572] [NEW] cpio in Busybox 1.27 ingnores "unsafe links"
Public bug reported: Description:Ubuntu Bionic Beaver (development branch) Release:18.04 busybox: Installed: 1:1.27.2-2ubuntu3 Candidate: 1:1.27.2-2ubuntu3 3) Expected my CPIO archive to be fully extracted with proper symlinks Command: unxz < /rootfs.cxz | cpio -i 4) 'Unsafe' symlinks were ignored such as: sbin/init -> /lib/systemd/systemd With the broken 1.27 sbin/init does not get created at all and my debirf initrd fails to load/boot properly. 1.22 from Xenial works. GNU Cpio also works. It looks like 1.28 adds an env var to override this behavior: libarchive: do not extract unsafe symlinks unless $EXTRACT_UNSAFE_SYMLINKS=1 ** Affects: busybox (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: busybox cpio -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to busybox in Ubuntu. https://bugs.launchpad.net/bugs/1753572 Title: cpio in Busybox 1.27 ingnores "unsafe links" Status in busybox package in Ubuntu: Confirmed Bug description: Description:Ubuntu Bionic Beaver (development branch) Release:18.04 busybox: Installed: 1:1.27.2-2ubuntu3 Candidate: 1:1.27.2-2ubuntu3 3) Expected my CPIO archive to be fully extracted with proper symlinks Command: unxz < /rootfs.cxz | cpio -i 4) 'Unsafe' symlinks were ignored such as: sbin/init -> /lib/systemd/systemd With the broken 1.27 sbin/init does not get created at all and my debirf initrd fails to load/boot properly. 1.22 from Xenial works. GNU Cpio also works. It looks like 1.28 adds an env var to override this behavior: libarchive: do not extract unsafe symlinks unless $EXTRACT_UNSAFE_SYMLINKS=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/1753572/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1753572] Re: cpio in Busybox 1.27 ingnores "unsafe links"
Proposed solution: back port the env var patch or upgrade to 1.28. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to busybox in Ubuntu. https://bugs.launchpad.net/bugs/1753572 Title: cpio in Busybox 1.27 ingnores "unsafe links" Status in busybox package in Ubuntu: Confirmed Bug description: Description:Ubuntu Bionic Beaver (development branch) Release:18.04 busybox: Installed: 1:1.27.2-2ubuntu3 Candidate: 1:1.27.2-2ubuntu3 3) Expected my CPIO archive to be fully extracted with proper symlinks Command: unxz < /rootfs.cxz | cpio -i 4) 'Unsafe' symlinks were ignored such as: sbin/init -> /lib/systemd/systemd With the broken 1.27 sbin/init does not get created at all and my debirf initrd fails to load/boot properly. 1.22 from Xenial works. GNU Cpio also works. It looks like 1.28 adds an env var to override this behavior: libarchive: do not extract unsafe symlinks unless $EXTRACT_UNSAFE_SYMLINKS=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/1753572/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1753572] Re: cpio in Busybox 1.27 ingnores "unsafe links"
** Also affects: busybox Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to busybox in Ubuntu. https://bugs.launchpad.net/bugs/1753572 Title: cpio in Busybox 1.27 ingnores "unsafe links" Status in busybox package in Ubuntu: Confirmed Status in debirf package in Ubuntu: Confirmed Bug description: Description:Ubuntu Bionic Beaver (development branch) Release:18.04 busybox: Installed: 1:1.27.2-2ubuntu3 Candidate: 1:1.27.2-2ubuntu3 3) Expected my CPIO archive to be fully extracted with proper symlinks Command: unxz < /rootfs.cxz | cpio -i 4) 'Unsafe' symlinks were ignored such as: sbin/init -> /lib/systemd/systemd With the broken 1.27 sbin/init does not get created at all and my debirf initrd fails to load/boot properly. 1.22 from Xenial works. GNU Cpio also works. It looks like 1.28 adds an env var to override this behavior: libarchive: do not extract unsafe symlinks unless $EXTRACT_UNSAFE_SYMLINKS=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/1753572/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1753572] Re: cpio in Busybox 1.27 ingnores "unsafe links"
** Project changed: busybox => debirf (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to busybox in Ubuntu. https://bugs.launchpad.net/bugs/1753572 Title: cpio in Busybox 1.27 ingnores "unsafe links" Status in busybox package in Ubuntu: Confirmed Status in debirf package in Ubuntu: Confirmed Bug description: Description:Ubuntu Bionic Beaver (development branch) Release:18.04 busybox: Installed: 1:1.27.2-2ubuntu3 Candidate: 1:1.27.2-2ubuntu3 3) Expected my CPIO archive to be fully extracted with proper symlinks Command: unxz < /rootfs.cxz | cpio -i 4) 'Unsafe' symlinks were ignored such as: sbin/init -> /lib/systemd/systemd With the broken 1.27 sbin/init does not get created at all and my debirf initrd fails to load/boot properly. 1.22 from Xenial works. GNU Cpio also works. It looks like 1.28 adds an env var to override this behavior: libarchive: do not extract unsafe symlinks unless $EXTRACT_UNSAFE_SYMLINKS=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/1753572/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1753572] Re: cpio in Busybox 1.27 ingnores "unsafe links"
I was using it to build a U18 debirf image when I saw this issue. I can generate one in a bit for you. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to busybox in Ubuntu. https://bugs.launchpad.net/bugs/1753572 Title: cpio in Busybox 1.27 ingnores "unsafe links" Status in busybox package in Ubuntu: Fix Released Status in debirf package in Ubuntu: Confirmed Status in busybox source package in Bionic: In Progress Status in debirf source package in Bionic: Confirmed Status in busybox source package in Cosmic: Fix Released Status in debirf source package in Cosmic: Confirmed Bug description: Description:Ubuntu Bionic Beaver (development branch) Release:18.04 busybox: Installed: 1:1.27.2-2ubuntu3 Candidate: 1:1.27.2-2ubuntu3 3) Expected my CPIO archive to be fully extracted with proper symlinks Command: unxz < /rootfs.cxz | cpio -i 4) 'Unsafe' symlinks were ignored such as: sbin/init -> /lib/systemd/systemd With the broken 1.27 sbin/init does not get created at all and my debirf initrd fails to load/boot properly. 1.22 from Xenial works. GNU Cpio also works. It looks like 1.28 adds an env var to override this behavior: libarchive: do not extract unsafe symlinks unless $EXTRACT_UNSAFE_SYMLINKS=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/1753572/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1753572] Re: cpio in Busybox 1.27 ingnores "unsafe links"
Yeah apologies, I have to allocate another U18 host and build one. Will aim for tomorrow. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to busybox in Ubuntu. https://bugs.launchpad.net/bugs/1753572 Title: cpio in Busybox 1.27 ingnores "unsafe links" Status in busybox package in Ubuntu: Fix Released Status in debirf package in Ubuntu: Confirmed Status in busybox source package in Bionic: In Progress Status in debirf source package in Bionic: Confirmed Status in busybox source package in Cosmic: Fix Released Status in debirf source package in Cosmic: Confirmed Bug description: Description:Ubuntu Bionic Beaver (development branch) Release:18.04 busybox: Installed: 1:1.27.2-2ubuntu3 Candidate: 1:1.27.2-2ubuntu3 3) Expected my CPIO archive to be fully extracted with proper symlinks Command: unxz < /rootfs.cxz | cpio -i 4) 'Unsafe' symlinks were ignored such as: sbin/init -> /lib/systemd/systemd With the broken 1.27 sbin/init does not get created at all and my debirf initrd fails to load/boot properly. 1.22 from Xenial works. GNU Cpio also works. It looks like 1.28 adds an env var to override this behavior: libarchive: do not extract unsafe symlinks unless $EXTRACT_UNSAFE_SYMLINKS=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/1753572/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1753572] Re: cpio in Busybox 1.27 ingnores "unsafe links"
Yes, 1.27.2-2ubuntu3.1 looks to fix the issue with 1.27.2-2ubuntu3! Thanks! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to busybox in Ubuntu. https://bugs.launchpad.net/bugs/1753572 Title: cpio in Busybox 1.27 ingnores "unsafe links" Status in busybox package in Ubuntu: Fix Released Status in debirf package in Ubuntu: Confirmed Status in busybox source package in Bionic: Fix Committed Status in debirf source package in Bionic: Confirmed Status in busybox source package in Cosmic: Fix Released Status in debirf source package in Cosmic: Confirmed Bug description: Description:Ubuntu Bionic Beaver (development branch) Release:18.04 busybox: Installed: 1:1.27.2-2ubuntu3 Candidate: 1:1.27.2-2ubuntu3 3) Expected my CPIO archive to be fully extracted with proper symlinks Command: unxz < /rootfs.cxz | cpio -i 4) 'Unsafe' symlinks were ignored such as: sbin/init -> /lib/systemd/systemd With the broken 1.27 sbin/init does not get created at all and my debirf initrd fails to load/boot properly. 1.22 from Xenial works. GNU Cpio also works. It looks like 1.28 adds an env var to override this behavior: libarchive: do not extract unsafe symlinks unless $EXTRACT_UNSAFE_SYMLINKS=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/1753572/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1753572] Re: cpio in Busybox 1.27 ingnores "unsafe links"
Creating image now. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to busybox in Ubuntu. https://bugs.launchpad.net/bugs/1753572 Title: cpio in Busybox 1.27 ingnores "unsafe links" Status in busybox package in Ubuntu: Fix Released Status in debirf package in Ubuntu: Confirmed Status in busybox source package in Bionic: In Progress Status in debirf source package in Bionic: Confirmed Status in busybox source package in Cosmic: Fix Released Status in debirf source package in Cosmic: Confirmed Bug description: Description:Ubuntu Bionic Beaver (development branch) Release:18.04 busybox: Installed: 1:1.27.2-2ubuntu3 Candidate: 1:1.27.2-2ubuntu3 3) Expected my CPIO archive to be fully extracted with proper symlinks Command: unxz < /rootfs.cxz | cpio -i 4) 'Unsafe' symlinks were ignored such as: sbin/init -> /lib/systemd/systemd With the broken 1.27 sbin/init does not get created at all and my debirf initrd fails to load/boot properly. 1.22 from Xenial works. GNU Cpio also works. It looks like 1.28 adds an env var to override this behavior: libarchive: do not extract unsafe symlinks unless $EXTRACT_UNSAFE_SYMLINKS=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/1753572/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1753572] Re: cpio in Busybox 1.27 ingnores "unsafe links"
I have the image, how can I get it to you privately to test? (Or alternatively, I can test it with the new version if you have a link?) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to busybox in Ubuntu. https://bugs.launchpad.net/bugs/1753572 Title: cpio in Busybox 1.27 ingnores "unsafe links" Status in busybox package in Ubuntu: Fix Released Status in debirf package in Ubuntu: Confirmed Status in busybox source package in Bionic: In Progress Status in debirf source package in Bionic: Confirmed Status in busybox source package in Cosmic: Fix Released Status in debirf source package in Cosmic: Confirmed Bug description: Description:Ubuntu Bionic Beaver (development branch) Release:18.04 busybox: Installed: 1:1.27.2-2ubuntu3 Candidate: 1:1.27.2-2ubuntu3 3) Expected my CPIO archive to be fully extracted with proper symlinks Command: unxz < /rootfs.cxz | cpio -i 4) 'Unsafe' symlinks were ignored such as: sbin/init -> /lib/systemd/systemd With the broken 1.27 sbin/init does not get created at all and my debirf initrd fails to load/boot properly. 1.22 from Xenial works. GNU Cpio also works. It looks like 1.28 adds an env var to override this behavior: libarchive: do not extract unsafe symlinks unless $EXTRACT_UNSAFE_SYMLINKS=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/1753572/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
