[Touch-packages] [Bug 1700814] Re: Default capability of cap_setfcap+i should be set on setcap
@serge-hallyn I'm not sure why I got this bug assigned. :-) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libcap2 in Ubuntu. https://bugs.launchpad.net/bugs/1700814 Title: Default capability of cap_setfcap+i should be set on setcap Status in libcap2 package in Ubuntu: New Bug description: If I grant a user (via pam_cap) cap_setfcap+i, I would then expect them to be able to use setcap without sudo. setcap is not provided with any default file capabilities however, so either the user has to sudo, or I have to grant the setfcap capability to setcap with setcap. In my mind, it would be reasonable to grant setfcap+i to setcap by default on installation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcap2/+bug/1700814/+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 1923845] Re: Please compress packages with zstd by default
** Changed in: apt (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1923845
Title:
Please compress packages with zstd by default
Status in appstream-glib package in Ubuntu:
New
Status in apt package in Ubuntu:
New
Status in aptly package in Ubuntu:
New
Status in boinc package in Ubuntu:
New
Status in busybox package in Ubuntu:
New
Status in cdebootstrap package in Ubuntu:
New
Status in cdist package in Ubuntu:
New
Status in debdelta package in Ubuntu:
New
Status in debian-el package in Ubuntu:
New
Status in debootstrap package in Ubuntu:
In Progress
Status in debsig-verify package in Ubuntu:
New
Status in debsigs package in Ubuntu:
New
Status in diffoscope package in Ubuntu:
New
Status in dpkg package in Ubuntu:
New
Status in dpkg-sig package in Ubuntu:
New
Status in file package in Ubuntu:
New
Status in libsolv package in Ubuntu:
New
Status in lintian package in Ubuntu:
New
Status in lutris package in Ubuntu:
New
Status in obs-build package in Ubuntu:
New
Status in osc package in Ubuntu:
New
Status in radare2 package in Ubuntu:
New
Status in reprepro package in Ubuntu:
New
Status in vim-scripts package in Ubuntu:
New
Status in zeroinstall-injector package in Ubuntu:
New
Bug description:
https://people.canonical.com/~rbalint/zstd-debs/ contains a .deb built
on Hirsute having both data and control members of the .deb being
compressed with zstd. It can be handy for testing various tools.
[dpkg]
Decompression support in dpkg landed first in Bionic and is being SRUd to
Xenial in LP: #1764220 enable Launchpad's Xenial systems to process the
zstd-compressed binary packages.
From dpkg's perspective the upgrade path is cleared.
The original plan was compressing only the internal data.tar .deb
member, but dpkg uses uniform compression by default since dpkg 1.19.0
thus I'm collecting all the changes to support control.tar.zst, too,
in this bug.
Reviewed packages from:
https://codesearch.debian.net/search?q=data.tar.xz&literal=1&perpkg=1
https://codesearch.debian.net/search?q=control.tar.xz&literal=1&perpkg=1
appstream-glib - needs fix: libappstream-builder/asb-package-deb.c
aptly - needs fix: deb/deb.go
boinc - needs fix: debian/fetch_example_applications.sh
busybox - needs fix: archival/dpkg_deb.c archival/dpkg.c
cdebootstrap- needs fix: src/package.c
cdist - may need fix, can use dpkg-deb:
cdist/preos/debootstrap/files/devuan-debootstrap/functions
debdelta- needs fix: debdelta debpatch.sh
debian-el - needs fix: deb-view.el
debian-handbook - needs fix, maybe later, for Debian
debootstrap - needs fix,
https://salsa.debian.org/installer-team/debootstrap/-/merge_requests/54
debsigs - needs fix, debsigs
debsig-verify - needs fix, src/debsig-verify.c
diffoscope - needs fix, diffoscope/comparators/deb.py
dpkg- needs fix, change default
dpkg-sig- needs fix, dpkg-sig
dpmb- needs fix, maybe later, for Debian
elfutils- may need fix, uses dpkg-deb if it is available, does not
handle .gz either
file- needs fix, magic/Magdir/archive
libsolv - needs fix, ext/repo_deb.c
lintian - needs fix malformed-deb-archive
lutris - needs fix, lutris/util/extract.py
obs-build - needs fix Build/Deb.pm
osc - needs fix osc/util/debquery.py control.tar.zst only
python-apt - needs fix
apt_inst.DebFile("glibc-doc-reference_2.33-0ubuntu2~zstd1_all.deb").control.extractall()
radare2 - needs fix
reprepro- needs fix, debfile.c
vim-scripts - needs fix debPlugin/autoload/deb.vim
winetricks - needs fix when Debian switches src/winetricks
zeroinstall-injector - needs fix src/zeroinstall/archive.ml
acr - skip, does not _have to_ be fixed, just creates packages,
see dist/deb_hand.mak
alien - skip, uses dpkg-deb to extract .deb
ansible - not affected, just test data in dbdata.tar.xz
anthy - not affected, just changelog entry
apt - seems fixed already
ceph- not affected in Ubuntu's version
circlator - not affected, just test data
cowdancer - not affected, just documentation
eccodes - skip, just orig-data.tar.xz
eckit - skip, just ...orig-data.tar.xz
firefox - skip, profdata.tar.xz
firefox-esr - skip, profdata.tar.xz
galculator - skip, just changelog
grads - skip, ...orig-data.tar.xz
gvmd- skip, just creates xz compressed .deb
insighttoolkit4 - skip, ...orig-data.tar.xz
jdeb- skip, just creates compressed .deb packages
jmol- skip, just local data archive
jq
[Touch-packages] [Bug 1923845] Re: Please compress packages with zstd by default
@juliank Xenial's apt/python3-apt does not work even with zstd
installed:
root@x-zstd:~# python3
Python 3.5.2 (default, Jan 26 2021, 13:30:48)
[GCC 5.4.0 20160609] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import apt_inst, apt_pkg
>>> apt_inst.DebFile("glibc-doc-reference_2.33-0ubuntu2~zstd1_all.deb").control.extractall()
Traceback (most recent call last):
File "", line 1, in
SystemError: E:Internal error, could not locate member
control.tar.{lz4gzxzbz2lzma}
>>>
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture
Description
+++-=-===-===-
ii zstd 1.3.1+dfsg-1~ubuntu0.16 amd64
fast lossless compression algorithm -- CLI tool
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1923845
Title:
Please compress packages with zstd by default
Status in appstream-glib package in Ubuntu:
New
Status in apt package in Ubuntu:
New
Status in aptly package in Ubuntu:
New
Status in boinc package in Ubuntu:
New
Status in busybox package in Ubuntu:
New
Status in cdebootstrap package in Ubuntu:
New
Status in cdist package in Ubuntu:
New
Status in debdelta package in Ubuntu:
New
Status in debian-el package in Ubuntu:
New
Status in debootstrap package in Ubuntu:
In Progress
Status in debsig-verify package in Ubuntu:
New
Status in debsigs package in Ubuntu:
New
Status in diffoscope package in Ubuntu:
New
Status in dpkg package in Ubuntu:
New
Status in dpkg-sig package in Ubuntu:
New
Status in file package in Ubuntu:
New
Status in libsolv package in Ubuntu:
New
Status in lintian package in Ubuntu:
New
Status in lutris package in Ubuntu:
New
Status in obs-build package in Ubuntu:
New
Status in osc package in Ubuntu:
New
Status in radare2 package in Ubuntu:
New
Status in reprepro package in Ubuntu:
New
Status in vim-scripts package in Ubuntu:
New
Status in zeroinstall-injector package in Ubuntu:
New
Bug description:
https://people.canonical.com/~rbalint/zstd-debs/ contains a .deb built
on Hirsute having both data and control members of the .deb being
compressed with zstd. It can be handy for testing various tools.
[dpkg]
Decompression support in dpkg landed first in Bionic and is being SRUd to
Xenial in LP: #1764220 enable Launchpad's Xenial systems to process the
zstd-compressed binary packages.
From dpkg's perspective the upgrade path is cleared.
The original plan was compressing only the internal data.tar .deb
member, but dpkg uses uniform compression by default since dpkg 1.19.0
thus I'm collecting all the changes to support control.tar.zst, too,
in this bug.
Reviewed packages from:
https://codesearch.debian.net/search?q=data.tar.xz&literal=1&perpkg=1
https://codesearch.debian.net/search?q=control.tar.xz&literal=1&perpkg=1
appstream-glib - needs fix: libappstream-builder/asb-package-deb.c
aptly - needs fix: deb/deb.go
boinc - needs fix: debian/fetch_example_applications.sh
busybox - needs fix: archival/dpkg_deb.c archival/dpkg.c
cdebootstrap- needs fix: src/package.c
cdist - may need fix, can use dpkg-deb:
cdist/preos/debootstrap/files/devuan-debootstrap/functions
debdelta- needs fix: debdelta debpatch.sh
debian-el - needs fix: deb-view.el
debian-handbook - needs fix, maybe later, for Debian
debootstrap - needs fix,
https://salsa.debian.org/installer-team/debootstrap/-/merge_requests/54
debsigs - needs fix, debsigs
debsig-verify - needs fix, src/debsig-verify.c
diffoscope - needs fix, diffoscope/comparators/deb.py
dpkg- needs fix, change default
dpkg-sig- needs fix, dpkg-sig
dpmb- needs fix, maybe later, for Debian
elfutils- may need fix, uses dpkg-deb if it is available, does not
handle .gz either
file- needs fix, magic/Magdir/archive
libsolv - needs fix, ext/repo_deb.c
lintian - needs fix malformed-deb-archive
lutris - needs fix, lutris/util/extract.py
obs-build - needs fix Build/Deb.pm
osc - needs fix osc/util/debquery.py control.tar.zst only
python-apt - needs fix
apt_inst.DebFile("glibc-doc-reference_2.33-0ubuntu2~zstd1_all.deb").control.extractall()
radare2 - needs fix
reprepro- needs fix, debfile.c
vim-scripts - needs fix debPlugin/autoload/deb.vim
winetricks - needs fix when Debian switches src/w
[Touch-packages] [Bug 1923845] Re: Please compress packages with zstd by default
@juliank IMO it would be better to add the zstd-related changes, too, to
the planned SRU if those are not risky and the delay due to adding them
is acceptable for ESM's perspective.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1923845
Title:
Please compress packages with zstd by default
Status in appstream-glib package in Ubuntu:
New
Status in apt package in Ubuntu:
New
Status in aptly package in Ubuntu:
New
Status in boinc package in Ubuntu:
New
Status in busybox package in Ubuntu:
New
Status in cdebootstrap package in Ubuntu:
New
Status in cdist package in Ubuntu:
New
Status in debdelta package in Ubuntu:
New
Status in debian-el package in Ubuntu:
New
Status in debootstrap package in Ubuntu:
In Progress
Status in debsig-verify package in Ubuntu:
New
Status in debsigs package in Ubuntu:
New
Status in diffoscope package in Ubuntu:
New
Status in dpkg package in Ubuntu:
New
Status in dpkg-sig package in Ubuntu:
New
Status in file package in Ubuntu:
New
Status in libsolv package in Ubuntu:
New
Status in lintian package in Ubuntu:
New
Status in lutris package in Ubuntu:
New
Status in obs-build package in Ubuntu:
New
Status in osc package in Ubuntu:
New
Status in radare2 package in Ubuntu:
New
Status in reprepro package in Ubuntu:
New
Status in vim-scripts package in Ubuntu:
New
Status in zeroinstall-injector package in Ubuntu:
New
Bug description:
https://people.canonical.com/~rbalint/zstd-debs/ contains a .deb built
on Hirsute having both data and control members of the .deb being
compressed with zstd. It can be handy for testing various tools.
[dpkg]
Decompression support in dpkg landed first in Bionic and is being SRUd to
Xenial in LP: #1764220 enable Launchpad's Xenial systems to process the
zstd-compressed binary packages.
From dpkg's perspective the upgrade path is cleared.
The original plan was compressing only the internal data.tar .deb
member, but dpkg uses uniform compression by default since dpkg 1.19.0
thus I'm collecting all the changes to support control.tar.zst, too,
in this bug.
Reviewed packages from:
https://codesearch.debian.net/search?q=data.tar.xz&literal=1&perpkg=1
https://codesearch.debian.net/search?q=control.tar.xz&literal=1&perpkg=1
appstream-glib - needs fix: libappstream-builder/asb-package-deb.c
aptly - needs fix: deb/deb.go
boinc - needs fix: debian/fetch_example_applications.sh
busybox - needs fix: archival/dpkg_deb.c archival/dpkg.c
cdebootstrap- needs fix: src/package.c
cdist - may need fix, can use dpkg-deb:
cdist/preos/debootstrap/files/devuan-debootstrap/functions
debdelta- needs fix: debdelta debpatch.sh
debian-el - needs fix: deb-view.el
debian-handbook - needs fix, maybe later, for Debian
debootstrap - needs fix,
https://salsa.debian.org/installer-team/debootstrap/-/merge_requests/54
debsigs - needs fix, debsigs
debsig-verify - needs fix, src/debsig-verify.c
diffoscope - needs fix, diffoscope/comparators/deb.py
dpkg- needs fix, change default
dpkg-sig- needs fix, dpkg-sig
dpmb- needs fix, maybe later, for Debian
elfutils- may need fix, uses dpkg-deb if it is available, does not
handle .gz either
file- needs fix, magic/Magdir/archive
libsolv - needs fix, ext/repo_deb.c
lintian - needs fix malformed-deb-archive
lutris - needs fix, lutris/util/extract.py
obs-build - needs fix Build/Deb.pm
osc - needs fix osc/util/debquery.py control.tar.zst only
python-apt - needs fix
apt_inst.DebFile("glibc-doc-reference_2.33-0ubuntu2~zstd1_all.deb").control.extractall()
radare2 - needs fix
reprepro- needs fix, debfile.c
vim-scripts - needs fix debPlugin/autoload/deb.vim
winetricks - needs fix when Debian switches src/winetricks
zeroinstall-injector - needs fix src/zeroinstall/archive.ml
acr - skip, does not _have to_ be fixed, just creates packages,
see dist/deb_hand.mak
alien - skip, uses dpkg-deb to extract .deb
ansible - not affected, just test data in dbdata.tar.xz
anthy - not affected, just changelog entry
apt - seems fixed already
ceph- not affected in Ubuntu's version
circlator - not affected, just test data
cowdancer - not affected, just documentation
eccodes - skip, just orig-data.tar.xz
eckit - skip, just ...orig-data.tar.xz
firefox - skip, profdata.tar.xz
firefox-esr - skip, profdata.tar.xz
galculator - skip, just changelog
grads - skip, ...orig-data.tar.xz
gvmd- skip, just creates xz compressed .deb
insighttoolkit4 - skip, ...orig-data.tar.xz
jdeb
[Touch-packages] [Bug 1926547] Re: Add Dell Privacy Mic Mute Key mapping
** Changed in: systemd (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1926547 Title: Add Dell Privacy Mic Mute Key mapping Status in OEM Priority Project: New Status in systemd package in Ubuntu: Triaged Bug description: [Impact] * Dell introduces new function called Dell Privacy, it utilizes hardware mute to control audio and camera. The commit map the reported key event to mic mute for making userspace can work as before, "Mic Mute" dialog pop-up while the mic mute button is pressed. [Test Plan] * Use a Dell machine, which has Dell privacy function, and press mic mute key. GUI will pop up "Mic Mute" icon. [Where problems could occur] * This change adds key event mapping in hwdb, which won't impact other hardware. [Other Info] * The change can only work with kernel commit on some specific hardware, ex. Latitude 9520. The commit series is "hardware-privacy-implementation-for-dell-laptop" in alsa-devel kernel tree. https://patchwork.kernel.org/project/alsa-devel/list/?series=465445 * This change has been verified on Dell machine. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1926547/+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 1926547] Re: Add Dell Privacy Mic Mute Key mapping
I've picked up the fix for the next upload to Impish, then it can be SRUd together with other fixes. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1926547 Title: Add Dell Privacy Mic Mute Key mapping Status in OEM Priority Project: New Status in systemd package in Ubuntu: Triaged Bug description: [Impact] * Dell introduces new function called Dell Privacy, it utilizes hardware mute to control audio and camera. The commit map the reported key event to mic mute for making userspace can work as before, "Mic Mute" dialog pop-up while the mic mute button is pressed. [Test Plan] * Use a Dell machine, which has Dell privacy function, and press mic mute key. GUI will pop up "Mic Mute" icon. [Where problems could occur] * This change adds key event mapping in hwdb, which won't impact other hardware. [Other Info] * The change can only work with kernel commit on some specific hardware, ex. Latitude 9520. The commit series is "hardware-privacy-implementation-for-dell-laptop" in alsa-devel kernel tree. https://patchwork.kernel.org/project/alsa-devel/list/?series=465445 * This change has been verified on Dell machine. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1926547/+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 1915126] Re: autopkgtest times out (or fails before that) in hirsute on test infra, passes locally
I've split the upstream test in 247.3-5ubuntu1 and also forwarded the change: https://salsa.debian.org/systemd-team/systemd/-/merge_requests/128 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1915126 Title: autopkgtest times out (or fails before that) in hirsute on test infra, passes locally Status in Auto Package Testing: Incomplete Status in systemd package in Ubuntu: Fix Released Bug description: Hi, I've asked yesterday on IRC but so far got no answer. I think it is right to file a bug about the current state of systemd autopkgtest to unite the efforts in regard to it. I was looking at the systemd tests for a no-change rebuild that really had no reason to now make it fail. While checking I found that as of this month (first bad test on 1st of February) most of the systemd test runs on amd64 will not pass/fail but instead in most cases time out. I've seen various people retry the case as it shows the typical symptoms of a "not the fault of the package, let us retry this" case. But it seems that won't help as the test history is rather clear. * Watch this in monospace to make more sense of it * $ check-autopkgtest-stats.sh -c 50 -p systemd -r "hirsute" -a "amd64" Check last 50 test results for src:systemd on releases 'hirsute' on architectures 'amd64' Of the 50 last tests, we had these subtest failing per release/arch: hirsute amd64 tests-in-lxd (F 2% f 0% S 0% B 12% => P 52%/) .BTTTBTT.BTBTTTBBTTT..F.. hostnamed (F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT. build-login(F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT. unit-config(F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT. networkd-testpy(F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT. localed-locale (F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT. boot-and-services (F 4% f 0% S 0% B 12% => P 50%/) .BTTTBTT.BTBTTTBBTTT...F.F... timedated (F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT. boot-smoke (F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT. logind (F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT. storage(F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT. upstream (F 12% f 0% S 0% B 12% => P 42%/) .BTTTBTT.BTBTTTBBTTTF.F.F..FF..F. udev (F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT. systemd-fsckd (F 8% f 0% S 0% B 12% => P 46%/) FBTTTBTTFBTBTTTBBTTT.F..F root-unittests (F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT. localed-x11-keymap (F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT. We see that formerly we had the known to be somewhat flaky, but otherwise working test (time goes from right to left). So we had the usual suspects of tests like upstream/systemd-fsck that failed a few times, but also working runs in between. But since February 22/24 runs failed very bad. 6 (=B) of those cases are aborting mid execution autopkgtest [22:08:58]: ERROR: testbed failure: testbed auxverb failed with exit code 255 And 16 of them timed out : failure: Timed out on waiting for ssh connection Sadly the 2/24 that didn't hard fail by that where broken by the known flaky systemd-fsckd test. Something drives this test crazy that we have to find and resolve, at the current rate nothing depending on it is likely to migrate. To manage notifications about this bug go to: https://bugs.launchpad.net/auto-package-testing/+bug/1915126/+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 1923845] Re: Please compress packages with zstd by default
Verified 1.6.5ubuntu0.6 on Bionic.
root@bb-lp1926437:~# wget
https://people.canonical.com/~rbalint/zstd-debs/glibc-doc-reference_2.33-0ubuntu2~zstd1_all.deb
--2021-05-13 19:29:17--
https://people.canonical.com/~rbalint/zstd-debs/glibc-doc-reference_2.33-0ubuntu2~zstd1_all.deb
Resolving people.canonical.com (people.canonical.com)... 91.189.89.62
Connecting to people.canonical.com (people.canonical.com)|91.189.89.62|:443...
connected.
HTTP request sent, awaiting response... 200 OK
Length: 5618446 (5.4M) [application/x-debian-package]
Saving to: ‘glibc-doc-reference_2.33-0ubuntu2~zstd1_all.deb’
glibc-doc-reference_2.33-0ubuntu2~zstd1_all
100%[=>]
5.36M 4.80MB/sin 1.1s
2021-05-13 19:29:18 (4.80 MB/s) - ‘glibc-doc-
reference_2.33-0ubuntu2~zstd1_all.deb’ saved [5618446/5618446]
root@bb-lp1926437:~# python3
Python 3.6.9 (default, Jan 26 2021, 15:33:00)
[GCC 8.4.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import apt_inst
>>> import apt_pkg
>>> apt_pkg.init_config()
>>> apt_inst.DebFile("glibc-doc-reference_2.33-0ubuntu2~zstd1_all.deb").control.extractall()
True
>>>
root@bb-lp1926437:~# dpkg -l python3-apt python-apt-common
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture
Description
+++-=-===-===-
ii python-apt-common 1.6.5ubuntu0.6 all
Python interface to libapt-pkg (locales)
ii python3-apt 1.6.5ubuntu0.6 amd64
Python 3 interface to libapt-pkg
root@bb-lp1926437:~#
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1923845
Title:
Please compress packages with zstd by default
Status in appstream-glib package in Ubuntu:
New
Status in apt package in Ubuntu:
New
Status in aptly package in Ubuntu:
New
Status in boinc package in Ubuntu:
New
Status in busybox package in Ubuntu:
New
Status in cdebootstrap package in Ubuntu:
New
Status in cdist package in Ubuntu:
New
Status in debdelta package in Ubuntu:
New
Status in debian-el package in Ubuntu:
New
Status in debootstrap package in Ubuntu:
Fix Released
Status in debsig-verify package in Ubuntu:
New
Status in debsigs package in Ubuntu:
New
Status in diffoscope package in Ubuntu:
New
Status in dpkg package in Ubuntu:
New
Status in dpkg-sig package in Ubuntu:
New
Status in file package in Ubuntu:
New
Status in libsolv package in Ubuntu:
New
Status in lintian package in Ubuntu:
New
Status in lutris package in Ubuntu:
New
Status in obs-build package in Ubuntu:
New
Status in osc package in Ubuntu:
New
Status in radare2 package in Ubuntu:
New
Status in reprepro package in Ubuntu:
New
Status in vim-scripts package in Ubuntu:
New
Status in zeroinstall-injector package in Ubuntu:
New
Bug description:
https://people.canonical.com/~rbalint/zstd-debs/ contains a .deb built
on Hirsute having both data and control members of the .deb being
compressed with zstd. It can be handy for testing various tools.
[dpkg]
Decompression support in dpkg landed first in Bionic and is being SRUd to
Xenial in LP: #1764220 enable Launchpad's Xenial systems to process the
zstd-compressed binary packages.
From dpkg's perspective the upgrade path is cleared.
The original plan was compressing only the internal data.tar .deb
member, but dpkg uses uniform compression by default since dpkg 1.19.0
thus I'm collecting all the changes to support control.tar.zst, too,
in this bug.
Reviewed packages from:
https://codesearch.debian.net/search?q=data.tar.xz&literal=1&perpkg=1
https://codesearch.debian.net/search?q=control.tar.xz&literal=1&perpkg=1
appstream-glib - needs fix: libappstream-builder/asb-package-deb.c
aptly - needs fix: deb/deb.go
boinc - needs fix: debian/fetch_example_applications.sh
busybox - needs fix: archival/dpkg_deb.c archival/dpkg.c
cdebootstrap- needs fix: src/package.c
cdist - may need fix, can use dpkg-deb:
cdist/preos/debootstrap/files/devuan-debootstrap/functions
debdelta- needs fix: debdelta debpatch.sh
debian-el - needs fix: deb-view.el
debian-handbook - needs fix, maybe later, for Debian
debootstrap - needs fix,
https://salsa.debian.org/installer-team/debootstrap/-/merge_requests/54
debsigs - needs fix, debsigs
debsig-verify - needs fix, src/debsig-verify.c
diffoscope -
[Touch-packages] [Bug 1923845] Re: Please compress packages with zstd by default
Verified 2.2.0~ubuntu0.21.04.1 on Hirsute.
root@hh-lp1926437:~# wget
https://people.canonical.com/~rbalint/zstd-debs/glibc-doc-reference_2.33-0ubuntu2~zstd1_all.deb
--2021-05-13 19:42:59--
https://people.canonical.com/~rbalint/zstd-debs/glibc-doc-reference_2.33-0ubuntu2~zstd1_all.deb
Resolving people.canonical.com (people.canonical.com)... 91.189.89.62
Connecting to people.canonical.com (people.canonical.com)|91.189.89.62|:443...
connected.
HTTP request sent, awaiting response... 200 OK
Length: 5618446 (5.4M) [application/x-debian-package]
Saving to: ‘glibc-doc-reference_2.33-0ubuntu2~zstd1_all.deb’
glibc-doc-reference_2.33-0ubuntu2~zstd1_all
100%[=>]
5.36M 4.78MB/sin 1.1s
2021-05-13 19:43:00 (4.78 MB/s) - ‘glibc-doc-
reference_2.33-0ubuntu2~zstd1_all.deb’ saved [5618446/5618446]
root@hh-lp1926437:~# python3 -c 'import apt_inst; import apt_pkg;
apt_pkg.init_config();
print(apt_inst.DebFile("glibc-doc-reference_2.33-0ubuntu2~zstd1_all.deb").control.extractall())'
True
root@hh-lp1926437:~# dpkg -l python3-apt python-apt-common
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-=-=--
ii python-apt-common 2.2.0~ubuntu0.21.04.1 all Python interface to
libapt-pkg (locales)
ii python3-apt 2.2.0~ubuntu0.21.04.1 amd64Python 3 interface to
libapt-pkg
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1923845
Title:
Please compress packages with zstd by default
Status in appstream-glib package in Ubuntu:
New
Status in apt package in Ubuntu:
New
Status in aptly package in Ubuntu:
New
Status in boinc package in Ubuntu:
New
Status in busybox package in Ubuntu:
New
Status in cdebootstrap package in Ubuntu:
New
Status in cdist package in Ubuntu:
New
Status in debdelta package in Ubuntu:
New
Status in debian-el package in Ubuntu:
New
Status in debootstrap package in Ubuntu:
Fix Released
Status in debsig-verify package in Ubuntu:
New
Status in debsigs package in Ubuntu:
New
Status in diffoscope package in Ubuntu:
New
Status in dpkg package in Ubuntu:
New
Status in dpkg-sig package in Ubuntu:
New
Status in file package in Ubuntu:
New
Status in libsolv package in Ubuntu:
New
Status in lintian package in Ubuntu:
New
Status in lutris package in Ubuntu:
New
Status in obs-build package in Ubuntu:
New
Status in osc package in Ubuntu:
New
Status in radare2 package in Ubuntu:
New
Status in reprepro package in Ubuntu:
New
Status in vim-scripts package in Ubuntu:
New
Status in zeroinstall-injector package in Ubuntu:
New
Bug description:
https://people.canonical.com/~rbalint/zstd-debs/ contains a .deb built
on Hirsute having both data and control members of the .deb being
compressed with zstd. It can be handy for testing various tools.
[dpkg]
Decompression support in dpkg landed first in Bionic and is being SRUd to
Xenial in LP: #1764220 enable Launchpad's Xenial systems to process the
zstd-compressed binary packages.
From dpkg's perspective the upgrade path is cleared.
The original plan was compressing only the internal data.tar .deb
member, but dpkg uses uniform compression by default since dpkg 1.19.0
thus I'm collecting all the changes to support control.tar.zst, too,
in this bug.
Reviewed packages from:
https://codesearch.debian.net/search?q=data.tar.xz&literal=1&perpkg=1
https://codesearch.debian.net/search?q=control.tar.xz&literal=1&perpkg=1
appstream-glib - needs fix: libappstream-builder/asb-package-deb.c
aptly - needs fix: deb/deb.go
boinc - needs fix: debian/fetch_example_applications.sh
busybox - needs fix: archival/dpkg_deb.c archival/dpkg.c
cdebootstrap- needs fix: src/package.c
cdist - may need fix, can use dpkg-deb:
cdist/preos/debootstrap/files/devuan-debootstrap/functions
debdelta- needs fix: debdelta debpatch.sh
debian-el - needs fix: deb-view.el
debian-handbook - needs fix, maybe later, for Debian
debootstrap - needs fix,
https://salsa.debian.org/installer-team/debootstrap/-/merge_requests/54
debsigs - needs fix, debsigs
debsig-verify - needs fix, src/debsig-verify.c
diffoscope - needs fix, diffoscope/comparators/deb.py
dpkg- needs fix, change default
dpkg-sig- needs fix, dpkg-sig
dpmb- needs fix, maybe later, for Debian
elfutils- may need fix, uses dpkg-deb if it is available, does not
handle .gz either
file- needs fix, magic/Magdir/archiv
[Touch-packages] [Bug 1923845] Re: Please compress packages with zstd by default
Verified 2.1.3ubuntu1.4 on Groovy.
root@gg-lp1926437:~# wget
https://people.canonical.com/~rbalint/zstd-debs/glibc-doc-reference_2.33-0ubuntu2~zstd1_all.deb
--2021-05-13 19:51:34--
https://people.canonical.com/~rbalint/zstd-debs/glibc-doc-reference_2.33-0ubuntu2~zstd1_all.deb
Resolving people.canonical.com (people.canonical.com)... 91.189.89.62
Connecting to people.canonical.com (people.canonical.com)|91.189.89.62|:443...
connected.
HTTP request sent, awaiting response... 200 OK
Length: 5618446 (5.4M) [application/x-debian-package]
Saving to: ‘glibc-doc-reference_2.33-0ubuntu2~zstd1_all.deb’
glibc-doc-reference_2.33-0ubuntu2~zstd1_all
100%[=>]
5.36M 4.70MB/sin 1.1s
2021-05-13 19:51:36 (4.70 MB/s) - ‘glibc-doc-
reference_2.33-0ubuntu2~zstd1_all.deb’ saved [5618446/5618446]
root@gg-lp1926437:~# python3 -c 'import apt_inst; import apt_pkg;
apt_pkg.init_config();
print(apt_inst.DebFile("glibc-doc-reference_2.33-0ubuntu2~zstd1_all.deb").control.extractall())'
True
root@gg-lp1926437:~# dpkg -l python3-apt python-apt-common
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name VersionArchitecture Description
+++-=-==--
ii python-apt-common 2.1.3ubuntu1.4 all Python interface to
libapt-pkg (locales)
ii python3-apt 2.1.3ubuntu1.4 amd64Python 3 interface to
libapt-pkg
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1923845
Title:
Please compress packages with zstd by default
Status in appstream-glib package in Ubuntu:
New
Status in apt package in Ubuntu:
New
Status in aptly package in Ubuntu:
New
Status in boinc package in Ubuntu:
New
Status in busybox package in Ubuntu:
New
Status in cdebootstrap package in Ubuntu:
New
Status in cdist package in Ubuntu:
New
Status in debdelta package in Ubuntu:
New
Status in debian-el package in Ubuntu:
New
Status in debootstrap package in Ubuntu:
Fix Released
Status in debsig-verify package in Ubuntu:
New
Status in debsigs package in Ubuntu:
New
Status in diffoscope package in Ubuntu:
New
Status in dpkg package in Ubuntu:
New
Status in dpkg-sig package in Ubuntu:
New
Status in file package in Ubuntu:
New
Status in libsolv package in Ubuntu:
New
Status in lintian package in Ubuntu:
New
Status in lutris package in Ubuntu:
New
Status in obs-build package in Ubuntu:
New
Status in osc package in Ubuntu:
New
Status in radare2 package in Ubuntu:
New
Status in reprepro package in Ubuntu:
New
Status in vim-scripts package in Ubuntu:
New
Status in zeroinstall-injector package in Ubuntu:
New
Bug description:
https://people.canonical.com/~rbalint/zstd-debs/ contains a .deb built
on Hirsute having both data and control members of the .deb being
compressed with zstd. It can be handy for testing various tools.
[dpkg]
Decompression support in dpkg landed first in Bionic and is being SRUd to
Xenial in LP: #1764220 enable Launchpad's Xenial systems to process the
zstd-compressed binary packages.
From dpkg's perspective the upgrade path is cleared.
The original plan was compressing only the internal data.tar .deb
member, but dpkg uses uniform compression by default since dpkg 1.19.0
thus I'm collecting all the changes to support control.tar.zst, too,
in this bug.
Reviewed packages from:
https://codesearch.debian.net/search?q=data.tar.xz&literal=1&perpkg=1
https://codesearch.debian.net/search?q=control.tar.xz&literal=1&perpkg=1
appstream-glib - needs fix: libappstream-builder/asb-package-deb.c
aptly - needs fix: deb/deb.go
boinc - needs fix: debian/fetch_example_applications.sh
busybox - needs fix: archival/dpkg_deb.c archival/dpkg.c
cdebootstrap- needs fix: src/package.c
cdist - may need fix, can use dpkg-deb:
cdist/preos/debootstrap/files/devuan-debootstrap/functions
debdelta- needs fix: debdelta debpatch.sh
debian-el - needs fix: deb-view.el
debian-handbook - needs fix, maybe later, for Debian
debootstrap - needs fix,
https://salsa.debian.org/installer-team/debootstrap/-/merge_requests/54
debsigs - needs fix, debsigs
debsig-verify - needs fix, src/debsig-verify.c
diffoscope - needs fix, diffoscope/comparators/deb.py
dpkg- needs fix, change default
dpkg-sig- needs fix, dpkg-sig
dpmb- needs fix, maybe later, for Debian
elfutils- may need fix, uses dpkg-deb if it is available, does not
handle .gz either
file- needs fix, magic/Magdir/archive
libsolv - needs fix, e
[Touch-packages] [Bug 1923845] Re: Please compress packages with zstd by default
Verified 2.0.0ubuntu0.20.04.5 on Focal.
root@f-lp1926437:~# wget
https://people.canonical.com/~rbalint/zstd-debs/glibc-doc-reference_2.33-0ubuntu2~zstd1_all.deb
--2021-05-13 19:56:02--
https://people.canonical.com/~rbalint/zstd-debs/glibc-doc-reference_2.33-0ubuntu2~zstd1_all.deb
Resolving people.canonical.com (people.canonical.com)... 91.189.89.62
Connecting to people.canonical.com (people.canonical.com)|91.189.89.62|:443...
connected.
HTTP request sent, awaiting response... 200 OK
Length: 5618446 (5.4M) [application/x-debian-package]
Saving to: ‘glibc-doc-reference_2.33-0ubuntu2~zstd1_all.deb’
glibc-doc-reference_2.33-0ubuntu2~zstd1_all
100%[=>]
5.36M 4.61MB/sin 1.2s
2021-05-13 19:56:03 (4.61 MB/s) - ‘glibc-doc-
reference_2.33-0ubuntu2~zstd1_all.deb’ saved [5618446/5618446]
root@f-lp1926437:~# python3 -c 'import apt_inst; import apt_pkg;
apt_pkg.init_config();
print(apt_inst.DebFile("glibc-doc-reference_2.33-0ubuntu2~zstd1_all.deb").control.extractall())'
True
root@f-lp1926437:~# dpkg -l python3-apt python-apt-common
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-=---
ii python-apt-common 2.0.0ubuntu0.20.04.5 all Python interface to
libapt-pkg (locales)
ii python3-apt 2.0.0ubuntu0.20.04.5 amd64Python 3 interface to
libapt-pkg
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1923845
Title:
Please compress packages with zstd by default
Status in appstream-glib package in Ubuntu:
New
Status in apt package in Ubuntu:
New
Status in aptly package in Ubuntu:
New
Status in boinc package in Ubuntu:
New
Status in busybox package in Ubuntu:
New
Status in cdebootstrap package in Ubuntu:
New
Status in cdist package in Ubuntu:
New
Status in debdelta package in Ubuntu:
New
Status in debian-el package in Ubuntu:
New
Status in debootstrap package in Ubuntu:
Fix Released
Status in debsig-verify package in Ubuntu:
New
Status in debsigs package in Ubuntu:
New
Status in diffoscope package in Ubuntu:
New
Status in dpkg package in Ubuntu:
New
Status in dpkg-sig package in Ubuntu:
New
Status in file package in Ubuntu:
New
Status in libsolv package in Ubuntu:
New
Status in lintian package in Ubuntu:
New
Status in lutris package in Ubuntu:
New
Status in obs-build package in Ubuntu:
New
Status in osc package in Ubuntu:
New
Status in radare2 package in Ubuntu:
New
Status in reprepro package in Ubuntu:
New
Status in vim-scripts package in Ubuntu:
New
Status in zeroinstall-injector package in Ubuntu:
New
Bug description:
https://people.canonical.com/~rbalint/zstd-debs/ contains a .deb built
on Hirsute having both data and control members of the .deb being
compressed with zstd. It can be handy for testing various tools.
[dpkg]
Decompression support in dpkg landed first in Bionic and is being SRUd to
Xenial in LP: #1764220 enable Launchpad's Xenial systems to process the
zstd-compressed binary packages.
From dpkg's perspective the upgrade path is cleared.
The original plan was compressing only the internal data.tar .deb
member, but dpkg uses uniform compression by default since dpkg 1.19.0
thus I'm collecting all the changes to support control.tar.zst, too,
in this bug.
Reviewed packages from:
https://codesearch.debian.net/search?q=data.tar.xz&literal=1&perpkg=1
https://codesearch.debian.net/search?q=control.tar.xz&literal=1&perpkg=1
appstream-glib - needs fix: libappstream-builder/asb-package-deb.c
aptly - needs fix: deb/deb.go
boinc - needs fix: debian/fetch_example_applications.sh
busybox - needs fix: archival/dpkg_deb.c archival/dpkg.c
cdebootstrap- needs fix: src/package.c
cdist - may need fix, can use dpkg-deb:
cdist/preos/debootstrap/files/devuan-debootstrap/functions
debdelta- needs fix: debdelta debpatch.sh
debian-el - needs fix: deb-view.el
debian-handbook - needs fix, maybe later, for Debian
debootstrap - needs fix,
https://salsa.debian.org/installer-team/debootstrap/-/merge_requests/54
debsigs - needs fix, debsigs
debsig-verify - needs fix, src/debsig-verify.c
diffoscope - needs fix, diffoscope/comparators/deb.py
dpkg- needs fix, change default
dpkg-sig- needs fix, dpkg-sig
dpmb- needs fix, maybe later, for Debian
elfutils- may need fix, uses dpkg-deb if it is available, does not
handle .gz either
file- needs fix, magic/Magdir/archive
libso
[Touch-packages] [Bug 1926437] Re: [SRU] Backport zstd support, fix bug in python-apt
Verified 1.6.5ubuntu0.6 on Bionic.
root@bb-lp1926437:~# wget
https://people.canonical.com/~rbalint/zstd-debs/glibc-doc-reference_2.33-0ubuntu2~zstd1_all.deb
--2021-05-13 19:29:17--
https://people.canonical.com/~rbalint/zstd-debs/glibc-doc-reference_2.33-0ubuntu2~zstd1_all.deb
Resolving people.canonical.com (people.canonical.com)... 91.189.89.62
Connecting to people.canonical.com (people.canonical.com)|91.189.89.62|:443...
connected.
HTTP request sent, awaiting response... 200 OK
Length: 5618446 (5.4M) [application/x-debian-package]
Saving to: ‘glibc-doc-reference_2.33-0ubuntu2~zstd1_all.deb’
glibc-doc-reference_2.33-0ubuntu2~zstd1_all
100%[=>]
5.36M 4.80MB/s in 1.1s
2021-05-13 19:29:18 (4.80 MB/s) - ‘glibc-doc-
reference_2.33-0ubuntu2~zstd1_all.deb’ saved [5618446/5618446]
root@bb-lp1926437:~# python3
Python 3.6.9 (default, Jan 26 2021, 15:33:00)
[GCC 8.4.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import apt_inst
>>> import apt_pkg
>>> apt_pkg.init_config()
>>> apt_inst.DebFile("glibc-doc-reference_2.33-0ubuntu2~zstd1_all.deb").control.extractall()
True
>>>
root@bb-lp1926437:~# dpkg -l python3-apt python-apt-common
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-=-===-===-
ii python-apt-common 1.6.5ubuntu0.6 all Python interface to libapt-pkg (locales)
ii python3-apt 1.6.5ubuntu0.6 amd64 Python 3 interface to libapt-pkg
root@bb-lp1926437:~#
Verified 2.0.0ubuntu0.20.04.5 on Focal.
root@f-lp1926437:~# wget
https://people.canonical.com/~rbalint/zstd-debs/glibc-doc-reference_2.33-0ubuntu2~zstd1_all.deb
--2021-05-13 19:56:02--
https://people.canonical.com/~rbalint/zstd-debs/glibc-doc-reference_2.33-0ubuntu2~zstd1_all.deb
Resolving people.canonical.com (people.canonical.com)... 91.189.89.62
Connecting to people.canonical.com (people.canonical.com)|91.189.89.62|:443...
connected.
HTTP request sent, awaiting response... 200 OK
Length: 5618446 (5.4M) [application/x-debian-package]
Saving to: ‘glibc-doc-reference_2.33-0ubuntu2~zstd1_all.deb’
glibc-doc-reference_2.33-0ubuntu2~zstd1_all
100%[=>]
5.36M 4.61MB/s in 1.2s
2021-05-13 19:56:03 (4.61 MB/s) - ‘glibc-doc-
reference_2.33-0ubuntu2~zstd1_all.deb’ saved [5618446/5618446]
root@f-lp1926437:~# python3 -c 'import apt_inst; import apt_pkg;
apt_pkg.init_config();
print(apt_inst.DebFile("glibc-doc-reference_2.33-0ubuntu2~zstd1_all.deb").control.extractall())'
True
root@f-lp1926437:~# dpkg -l python3-apt python-apt-common
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-=---
ii python-apt-common 2.0.0ubuntu0.20.04.5 all Python interface to libapt-pkg
(locales)
ii python3-apt 2.0.0ubuntu0.20.04.5 amd64 Python 3 interface to libapt-pkg
Verified 2.1.3ubuntu1.4 on Groovy.
root@gg-lp1926437:~# wget
https://people.canonical.com/~rbalint/zstd-debs/glibc-doc-reference_2.33-0ubuntu2~zstd1_all.deb
--2021-05-13 19:51:34--
https://people.canonical.com/~rbalint/zstd-debs/glibc-doc-reference_2.33-0ubuntu2~zstd1_all.deb
Resolving people.canonical.com (people.canonical.com)... 91.189.89.62
Connecting to people.canonical.com (people.canonical.com)|91.189.89.62|:443...
connected.
HTTP request sent, awaiting response... 200 OK
Length: 5618446 (5.4M) [application/x-debian-package]
Saving to: ‘glibc-doc-reference_2.33-0ubuntu2~zstd1_all.deb’
glibc-doc-reference_2.33-0ubuntu2~zstd1_all
100%[=>]
5.36M 4.70MB/s in 1.1s
2021-05-13 19:51:36 (4.70 MB/s) - ‘glibc-doc-
reference_2.33-0ubuntu2~zstd1_all.deb’ saved [5618446/5618446]
root@gg-lp1926437:~# python3 -c 'import apt_inst; import apt_pkg;
apt_pkg.init_config();
print(apt_inst.DebFile("glibc-doc-reference_2.33-0ubuntu2~zstd1_all.deb").control.extractall())'
True
root@gg-lp1926437:~# dpkg -l python3-apt python-apt-common
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-=-==--
ii python-apt-common 2.1.3ubuntu1.4 all Python interface to libapt-pkg (locales)
ii python3-apt 2.1
[Touch-packages] [Bug 1923845] Re: Please compress packages with zstd by default
Sorry, those comments were for LP: #1926437, which is at least related.
:-)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1923845
Title:
Please compress packages with zstd by default
Status in appstream-glib package in Ubuntu:
New
Status in apt package in Ubuntu:
New
Status in aptly package in Ubuntu:
New
Status in boinc package in Ubuntu:
New
Status in busybox package in Ubuntu:
New
Status in cdebootstrap package in Ubuntu:
New
Status in cdist package in Ubuntu:
New
Status in debdelta package in Ubuntu:
New
Status in debian-el package in Ubuntu:
New
Status in debootstrap package in Ubuntu:
Fix Released
Status in debsig-verify package in Ubuntu:
New
Status in debsigs package in Ubuntu:
New
Status in diffoscope package in Ubuntu:
New
Status in dpkg package in Ubuntu:
New
Status in dpkg-sig package in Ubuntu:
New
Status in file package in Ubuntu:
New
Status in libsolv package in Ubuntu:
New
Status in lintian package in Ubuntu:
New
Status in lutris package in Ubuntu:
New
Status in obs-build package in Ubuntu:
New
Status in osc package in Ubuntu:
New
Status in radare2 package in Ubuntu:
New
Status in reprepro package in Ubuntu:
New
Status in vim-scripts package in Ubuntu:
New
Status in zeroinstall-injector package in Ubuntu:
New
Bug description:
https://people.canonical.com/~rbalint/zstd-debs/ contains a .deb built
on Hirsute having both data and control members of the .deb being
compressed with zstd. It can be handy for testing various tools.
[dpkg]
Decompression support in dpkg landed first in Bionic and is being SRUd to
Xenial in LP: #1764220 enable Launchpad's Xenial systems to process the
zstd-compressed binary packages.
From dpkg's perspective the upgrade path is cleared.
The original plan was compressing only the internal data.tar .deb
member, but dpkg uses uniform compression by default since dpkg 1.19.0
thus I'm collecting all the changes to support control.tar.zst, too,
in this bug.
Reviewed packages from:
https://codesearch.debian.net/search?q=data.tar.xz&literal=1&perpkg=1
https://codesearch.debian.net/search?q=control.tar.xz&literal=1&perpkg=1
appstream-glib - needs fix: libappstream-builder/asb-package-deb.c
aptly - needs fix: deb/deb.go
boinc - needs fix: debian/fetch_example_applications.sh
busybox - needs fix: archival/dpkg_deb.c archival/dpkg.c
cdebootstrap- needs fix: src/package.c
cdist - may need fix, can use dpkg-deb:
cdist/preos/debootstrap/files/devuan-debootstrap/functions
debdelta- needs fix: debdelta debpatch.sh
debian-el - needs fix: deb-view.el
debian-handbook - needs fix, maybe later, for Debian
debootstrap - needs fix,
https://salsa.debian.org/installer-team/debootstrap/-/merge_requests/54
debsigs - needs fix, debsigs
debsig-verify - needs fix, src/debsig-verify.c
diffoscope - needs fix, diffoscope/comparators/deb.py
dpkg- needs fix, change default
dpkg-sig- needs fix, dpkg-sig
dpmb- needs fix, maybe later, for Debian
elfutils- may need fix, uses dpkg-deb if it is available, does not
handle .gz either
file- needs fix, magic/Magdir/archive
libsolv - needs fix, ext/repo_deb.c
lintian - needs fix malformed-deb-archive
lutris - needs fix, lutris/util/extract.py
obs-build - needs fix Build/Deb.pm
osc - needs fix osc/util/debquery.py control.tar.zst only
python-apt - needs fix
apt_inst.DebFile("glibc-doc-reference_2.33-0ubuntu2~zstd1_all.deb").control.extractall()
radare2 - needs fix
reprepro- needs fix, debfile.c
vim-scripts - needs fix debPlugin/autoload/deb.vim
winetricks - needs fix when Debian switches src/winetricks
zeroinstall-injector - needs fix src/zeroinstall/archive.ml
acr - skip, does not _have to_ be fixed, just creates packages,
see dist/deb_hand.mak
alien - skip, uses dpkg-deb to extract .deb
ansible - not affected, just test data in dbdata.tar.xz
anthy - not affected, just changelog entry
apt - seems fixed already
ceph- not affected in Ubuntu's version
circlator - not affected, just test data
cowdancer - not affected, just documentation
eccodes - skip, just orig-data.tar.xz
eckit - skip, just ...orig-data.tar.xz
firefox - skip, profdata.tar.xz
firefox-esr - skip, profdata.tar.xz
galculator - skip, just changelog
grads - skip, ...orig-data.tar.xz
gvmd- skip, just creates xz compressed .deb
insighttoolkit4 - skip, ...orig-data.tar.xz
jdeb- skip, just creates compressed .deb packages
jmol- skip, just local data archiv
[Touch-packages] [Bug 1850667] Re: Switch to "unified" cgroup hierarchy (cgroupv2)
@mvo Please keep this bug updated and/or notify me when snapd is ready for the switch. Ideally way before 21.10 Feature Freeze. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1850667 Title: Switch to "unified" cgroup hierarchy (cgroupv2) Status in lxc: Fix Released Status in lxd: Fix Released Status in snapd: Confirmed Status in docker.io package in Ubuntu: Confirmed Status in lxc package in Ubuntu: Fix Released Status in snapd package in Ubuntu: In Progress Status in systemd package in Ubuntu: New Status in lxc package in Debian: Fix Released Status in systemd package in Debian: Fix Released Bug description: Systemd upstream switched the default cgroup hierarchy to unified with v243. This change is reverted by the Ubuntu systemd packages, but as unified is the way to go per upstream support should be added to all relevant Ubuntu packges (and snaps): https://github.com/systemd/systemd/blob/v243/NEWS#L56 * systemd now defaults to the "unified" cgroup hierarchy setup during build-time, i.e. -Ddefault-hierarchy=unified is now the build-time default. Previously, -Ddefault-hierarchy=hybrid was the default. This change reflects the fact that cgroupsv2 support has matured substantially in both systemd and in the kernel, and is clearly the way forward. Downstream production distributions might want to continue to use -Ddefault-hierarchy=hybrid (or even =legacy) for their builds as unfortunately the popular container managers have not caught up with the kernel API changes. Systemd is rebuilt using the new default and is available from the following PPA for testing: https://launchpad.net/~rbalint/+archive/ubuntu/systemd-unified-cgh The autopkgtest results against other packges are available here: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-eoan-rbalint-systemd-unified-cgh/?format=plain https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-focal-rbalint-systemd-unified-cgh/?format=plain lxc autopkgtest failing: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-eoan-rbalint-systemd-unified- cgh/eoan/amd64/d/docker.io/20191030_155944_2331e@/log.gz snapd autopkgtest failing: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-eoan-rbalint-systemd-unified- cgh/eoan/amd64/s/snapd/20191030_161354_94b26@/log.gz docker.io autopkgtest failing: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-eoan-rbalint-systemd-unified- cgh/eoan/amd64/d/docker.io/20191030_155944_2331e@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/lxc/+bug/1850667/+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 873072] Re: Postinst error: chown: invalid group: `root:messagebus'
Maybe you need to copy /etc/group as well? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/873072 Title: Postinst error: chown: invalid group: `root:messagebus' Status in dbus package in Ubuntu: Confirmed Bug description: In Ubuntu Core 11.10 daily in chroot environment with host's /etc/passwd and /etc/shadow copied in chroot I get the following error on installing dbus package: chown: invalid group: `root:messagebus' dpkg: error processing dbus (--configure): subprocess installed post-installation script returned error exit status 1 This error paralyzes any further attempts to install anything. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/873072/+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 1919177] Re: Azure: issues with accelerated networking on Hirsute
@gjolly There were networking-related changes in systemd which could have
caused this but I also see that the kernel packages also changed between the
Azure images:
-ii linux-image-azure 5.8.0.1017.19+21.04.14
...
+ii linux-image-5.8.0-1022-azure 5.8.0-1022.24+21.04.2
Could you please prepare an image that has the older kernel and newer
systemd to rule out kernel changes causing the issue?
Also do you still observe the issue in Impish? It has systemd 248 now.
** Changed in: systemd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1919177
Title:
Azure: issues with accelerated networking on Hirsute
Status in cloud-init:
Incomplete
Status in cloud-init package in Ubuntu:
Incomplete
Status in linux-azure package in Ubuntu:
New
Status in systemd package in Ubuntu:
Incomplete
Bug description:
[General]
On Azure, when provisioning a Hirsute VM with Accelerated Networking
enabled, sometimes part of the cloud-init configuration is not
applied.
Especially, in those cases, the public SSH key is not setup properly.
[how to reproduce]
Start a VM with AN enabled:
```
az vm create --name "$VM_NAME --resource-group "$GROUP" --location "UK South"
--image
'Canonical:0001-com-ubuntu-server-hirsute-daily:21_04-daily-gen2:latest' --size
Standard_F8s_v2 --admin-username ubuntu --ssh-key-value "$SSH_KEY"
--accelerated-networking
```
After a moment, try to SSH: if you succeed, delete and recreate a new
VM.
[troubleshooting]
To be able to connect into the VM, run:
az vm run-command invoke -g "$GROUP" -n "$VM_NAME" --command-id
RunShellScript --scripts "sudo -u ubuntu ssh-import-id $LP_USERNAME"
```
In "/run/cloud-init/instance-data.json", I can see:
```
"publicKeys": [
{
"keyData": "",
"path": "/home/ubuntu/.ssh/authorized_keys"
}
],
```
as expected.
[workaround]
As mentioned, Azure allows the user to run command into the VM without
SSH connection. To do so, one can use the Azure CLI:
az vm run-command invoke -g "$GROUP" -n "$VM_NAME" --command-id
RunShellScript --scripts "sudo -u ubuntu ssh-import-id $LP_USERNAME"
This example uses "ssh-import-id" but it's also possible to just echo
a given public key into /home/ubuntu/.ssh/authorized_keys
NOTE: this will only solves the SSH issue, I do not know if this bug
affects other things. If so the user would have to apply those things
manually.
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1919177/+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 1927192] Re: gdb ftbfs on armhf, testsuite timeouts
@doko Would fixing the symlink as suggested in LP: #1918035 help instead of not stripping ld-*? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdb in Ubuntu. https://bugs.launchpad.net/bugs/1927192 Title: gdb ftbfs on armhf, testsuite timeouts Status in gdb: Incomplete Status in gdb package in Ubuntu: Fix Released Status in glibc package in Ubuntu: Fix Committed Status in gdb source package in Focal: New Status in glibc source package in Focal: New Status in gdb source package in Groovy: New Status in glibc source package in Groovy: New Status in gdb source package in Hirsute: New Status in glibc source package in Hirsute: New Status in gdb source package in Impish: Fix Released Status in glibc source package in Impish: Fix Committed Bug description: see https://launchpad.net/ubuntu/+source/gdb/10.2-0ubuntu3 $ zcat buildlog_ubuntu-impish-armhf.gdb_10.2-0ubuntu3_BUILDING.txt.gz | fgrep '(timeout)'|wc -l 10451 To manage notifications about this bug go to: https://bugs.launchpad.net/gdb/+bug/1927192/+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 1878051] Re: unit-tests' test-execute and test-mount-utils fail in LXC
** Summary changed: - root-unittests' test-execute fails in LXC + unit-tests' test-execute and test-mount-utils fail in LXC -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1878051 Title: unit-tests' test-execute and test-mount-utils fail in LXC Status in systemd package in Ubuntu: New Bug description: ... exec-bindpaths.service: Child 1573 belongs to exec-bindpaths.service. exec-bindpaths.service: Main process exited, code=exited, status=0/SUCCESS exec-bindpaths.service: Running next main command for state start. exec-bindpaths.service: Passing 0 fds to service exec-bindpaths.service: About to execute: /usr/bin/test -f /tmp/thisisasimpletest exec-bindpaths.service: Forked /usr/bin/test as 1574 PR_SET_MM_ARG_START failed, attempting PR_SET_MM_ARG_END hack: Operation not permitted PR_SET_MM_ARG_END hack failed, proceeding without: Operation not permitted Applying namespace mount on /run/systemd/unit-root/tmp/test-exec-bindpaths Followed source symlinks /tmp → /tmp. Successfully mounted /tmp to /run/systemd/unit-root/tmp/test-exec-bindpaths Applying namespace mount on /run/systemd/unit-root/tmp/test-exec-bindreadonlypaths Followed source symlinks /tmp → /tmp. Successfully mounted /tmp to /run/systemd/unit-root/tmp/test-exec-bindreadonlypaths Failed to re-mount '/run/systemd/unit-root/tmp/test-exec-bindreadonlypaths' and its submounts: Permission denied exec-bindpaths.service: Failed to set up namespace, assuming containerized execution, ignoring: Permission denied exec-bindpaths.service: Executing: /usr/bin/test -f /tmp/thisisasimpletest Received SIGCHLD from PID 1574 (test). Child 1574 (test) died (code=exited, status=1/FAILURE) exec-bindpaths.service: Child 1574 belongs to exec-bindpaths.service. exec-bindpaths.service: Main process exited, code=exited, status=1/FAILURE exec-bindpaths.service: Failed with result 'exit-code'. exec-bindpaths.service: Changed start -> failed exec-bindpaths.service: Unit entered failed state. test_exec_bindpaths: exec-bindpaths.service: exit status 1, expected 0 FAIL: test-execute (code: 134) Aborted (core dumped) ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1878051/+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 1850667] Re: Switch to "unified" cgroup hierarchy (cgroupv2)
Docker supports cgroups v2 starting with version 20.10: https://www.docker.com/blog/introducing-docker-engine-20-10/ ** Changed in: docker.io (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1850667 Title: Switch to "unified" cgroup hierarchy (cgroupv2) Status in lxc: Fix Released Status in lxd: Fix Released Status in snapd: Confirmed Status in docker.io package in Ubuntu: Fix Released Status in lxc package in Ubuntu: Fix Released Status in snapd package in Ubuntu: In Progress Status in systemd package in Ubuntu: Confirmed Status in lxc package in Debian: Fix Released Status in systemd package in Debian: Fix Released Bug description: Systemd upstream switched the default cgroup hierarchy to unified with v243. This change is reverted by the Ubuntu systemd packages, but as unified is the way to go per upstream support should be added to all relevant Ubuntu packges (and snaps): https://github.com/systemd/systemd/blob/v243/NEWS#L56 * systemd now defaults to the "unified" cgroup hierarchy setup during build-time, i.e. -Ddefault-hierarchy=unified is now the build-time default. Previously, -Ddefault-hierarchy=hybrid was the default. This change reflects the fact that cgroupsv2 support has matured substantially in both systemd and in the kernel, and is clearly the way forward. Downstream production distributions might want to continue to use -Ddefault-hierarchy=hybrid (or even =legacy) for their builds as unfortunately the popular container managers have not caught up with the kernel API changes. Systemd is rebuilt using the new default and is available from the following PPA for testing: https://launchpad.net/~rbalint/+archive/ubuntu/systemd-unified-cgh The autopkgtest results against other packges are available here: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-eoan-rbalint-systemd-unified-cgh/?format=plain https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-focal-rbalint-systemd-unified-cgh/?format=plain lxc autopkgtest failing: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-eoan-rbalint-systemd-unified- cgh/eoan/amd64/d/docker.io/20191030_155944_2331e@/log.gz snapd autopkgtest failing: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-eoan-rbalint-systemd-unified- cgh/eoan/amd64/s/snapd/20191030_161354_94b26@/log.gz docker.io autopkgtest failing: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-eoan-rbalint-systemd-unified- cgh/eoan/amd64/d/docker.io/20191030_155944_2331e@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/lxc/+bug/1850667/+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 1928966] Re: Please merge procps 2:3.3.17-5 (main) from Debian unstable
Uploaded, thanks! ** Changed in: procps (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/1928966 Title: Please merge procps 2:3.3.17-5 (main) from Debian unstable Status in procps package in Ubuntu: Fix Committed Bug description: This requires a merge because there are changes in the Ubuntu version not present in the Debian version. Justification of new diff: - There is a new diff, which is an autopkgtest for the stack limit issue that was seen in bug 1874824. This test has been submitted to Debian so the patch can be dropped if they accept it. Justification of dropped patches - missing_potfiles_in: Debian has now added this code in POTFILES.in so the patch is no longer needed - pmap_test: This patch disables some tests that are not causing any problems. These tests are run in Debian so should be run in Ubuntu as well - top_config_file_bwcompat: Debian has applied this code upstream so the patch is no longer needed - tar-version: Debian has applied this code upstream so the patch is no longer needed - stack_limit: Debian has applied this code upstream so the patch is no longer needed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1928966/+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 1785383] Re: missing EDNS0 record confuses systemd-resolved
@brian-murray I've merged the fix to the git repository thus it will be
part of the next upload.
** Changed in: systemd (Ubuntu Impish)
Status: Triaged => Fix Committed
** Changed in: systemd (Ubuntu Impish)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1785383
Title:
missing EDNS0 record confuses systemd-resolved
Status in systemd:
Fix Released
Status in dnsmasq package in Ubuntu:
Fix Released
Status in systemd package in Ubuntu:
Fix Committed
Status in dnsmasq source package in Bionic:
Triaged
Status in systemd source package in Bionic:
In Progress
Status in dnsmasq source package in Focal:
Fix Released
Status in systemd source package in Focal:
In Progress
Status in dnsmasq source package in Groovy:
Fix Released
Status in systemd source package in Groovy:
In Progress
Status in dnsmasq source package in Hirsute:
Fix Released
Status in systemd source package in Hirsute:
Incomplete
Status in dnsmasq source package in Impish:
Fix Released
Status in systemd source package in Impish:
Fix Committed
Bug description:
[Impact]
dnsmasq 2.79 and below omits EDNS0 OPT records when returning an empty answer
for a domain it is authoritative for. systemd-resolved seems to get confused by
this in certain circumstances; when using the stub resolver and requesting an
address for which there are no records, there can sometimes be a five
second hang in resolution.
[Fix]
This is fixed by upstream commit
http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commit;h=1682d15a744880b0398af75eadf68fe66128af78
Not sure if it is worth cherry picking? I imagine the most likely
trigger will be dnsmasq on routers which are not likely to be running
Ubuntu, but maybe just in case.
I also think there are some logic issues in systemd-resolved, upstream
bug filed:
https://github.com/systemd/systemd/issues/9785
[Test Case]
Simple-ish test case for bionic:
---
IFACE=dummy0
SUBNET=10.0.0
ip link add $IFACE type dummy
ifconfig $IFACE ${SUBNET}.1/24
dnsmasq -h -R -d -C /dev/null -2 $IFACE -z -i $IFACE -I lo
--host-record=test.test,${SUBNET}.1 --server=/test/ &
dig -t a test.test @10.0.0.1 | grep EDNS
# should return "; EDNS ..."
dig -t test.test @10.0.0.1 | grep EDNS
# again, should return "; EDNS ..." but doesn't
---
To reproduce the systemd-resolved side of the problem
---
# as above, but
# now configure systemd-resolved to look at only 10.0.0.1, then
systemd-resolve --reset-server-features
# should exhibit five second delay then connect, assuming sshd is running :)
ssh test.test
---
More detailed test case for focal and later:
install dnsmasq on a bionic system and start it, listening to an
interface that is externally reachable, e.g. for a normal libvirt vm
with interface name 'ens3':
IFACE=ens3
dnsmasq -h -R -d -C /dev/null -2 $IFACE -z -i $IFACE -I lo
--host-record=test.test,1.2.3.4 --server=/test/
note that the '1.2.3.4' address doesn't matter, any addr is ok.
then setup a test system that can reach the dnsmasq system, and
configure networkd to use the dnsmasq server, e.g. using config like:
[Match]
Name=ens3
[Network]
DHCP=yes
DNS=DNSMASQ_IP_ADDRESS
Domains=test
[DHCPv4]
UseDNS=no
UseDomains=no
replace 'DNSMASQ_IP_ADDRESS' with the addr of the bionic system where
dnsmasq is running, and replace 'ens3' with whatever the test system
interface name is. Then restart systemd-networkd, and test:
systemd-resolve --reset-server-features
systemd-resolve --flush-caches
host test.test
The lookup using 'host' should complete immediately;.
[Discussion]
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: dnsmasq-base 2.79-1
ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
Uname: Linux 4.15.0-23-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
Date: Sat Aug 4 11:33:56 2018
InstallationDate: Installed on 2018-05-31 (64 days ago)
InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64
(20180426)
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_GB.UTF-8
SHELL=/bin/bash
SourcePackage: dnsmasq
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1785383/+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 1930295] [NEW] autopkgtest fails in Focal on armhf: kernel packages not matched: linux-tools-5.4.0-72-generic-lpae
Public bug reported: https://autopkgtest.ubuntu.com/packages/unattended-upgrades/focal/armhf https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/armhf/u /unattended-upgrades/20210513_204112_b792c@/log.gz == FAIL: test_versioned (__main__.TestKernelPatterns) kernel package patterns should cover versioned packages -- Traceback (most recent call last): File "test/autopkgtest_kernel_patterns.py", line 51, in test_versioned self.assertTrue(not not_matched, AssertionError: False is not true : kernel packages not matched: linux-tools-5.4.0-72-generic-lpae linux-modules-5.4.0-72-generic-lpae linux-image-5.4.0-72-generic-lpae linux-buildinfo-5.4.0-72-generic-lpae linux-image-unsigned-5.4.0-72-generic-lpae linux-headers-5.4.0-72-generic-lpae -- Ran 1 test in 1.277s FAILED (failures=1) ** Affects: unattended-upgrades (Ubuntu) Importance: Undecided Status: New ** Tags: update-excuse-focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1930295 Title: autopkgtest fails in Focal on armhf: kernel packages not matched: linux-tools-5.4.0-72-generic-lpae Status in unattended-upgrades package in Ubuntu: New Bug description: https://autopkgtest.ubuntu.com/packages/unattended- upgrades/focal/armhf https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/armhf/u /unattended-upgrades/20210513_204112_b792c@/log.gz == FAIL: test_versioned (__main__.TestKernelPatterns) kernel package patterns should cover versioned packages -- Traceback (most recent call last): File "test/autopkgtest_kernel_patterns.py", line 51, in test_versioned self.assertTrue(not not_matched, AssertionError: False is not true : kernel packages not matched: linux-tools-5.4.0-72-generic-lpae linux-modules-5.4.0-72-generic-lpae linux-image-5.4.0-72-generic-lpae linux-buildinfo-5.4.0-72-generic-lpae linux-image-unsigned-5.4.0-72-generic-lpae linux-headers-5.4.0-72-generic-lpae -- Ran 1 test in 1.277s FAILED (failures=1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1930295/+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 1927192] Re: gdb ftbfs on armhf, testsuite timeouts
@doko would it be enough keep ld-* unstripped on armhf and armel only? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdb in Ubuntu. https://bugs.launchpad.net/bugs/1927192 Title: gdb ftbfs on armhf, testsuite timeouts Status in gdb: Incomplete Status in gdb package in Ubuntu: Fix Released Status in glibc package in Ubuntu: Fix Committed Status in gdb source package in Focal: New Status in glibc source package in Focal: New Status in gdb source package in Groovy: New Status in glibc source package in Groovy: New Status in gdb source package in Hirsute: New Status in glibc source package in Hirsute: New Status in gdb source package in Impish: Fix Released Status in glibc source package in Impish: Fix Committed Bug description: see https://launchpad.net/ubuntu/+source/gdb/10.2-0ubuntu3 $ zcat buildlog_ubuntu-impish-armhf.gdb_10.2-0ubuntu3_BUILDING.txt.gz | fgrep '(timeout)'|wc -l 10451 To manage notifications about this bug go to: https://bugs.launchpad.net/gdb/+bug/1927192/+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 1927192] Re: gdb ftbfs on armhf, testsuite timeouts
@doko since the problem is arm-specific I don't want to deviate from the default stripping on architectures where it is not necessary. Not that the 28k would be so huge, but for the sake of not changing what was already good. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdb in Ubuntu. https://bugs.launchpad.net/bugs/1927192 Title: gdb ftbfs on armhf, testsuite timeouts Status in gdb: Incomplete Status in gdb package in Ubuntu: Fix Released Status in glibc package in Ubuntu: Fix Committed Status in gdb source package in Focal: New Status in glibc source package in Focal: New Status in gdb source package in Groovy: New Status in glibc source package in Groovy: New Status in gdb source package in Hirsute: New Status in glibc source package in Hirsute: New Status in gdb source package in Impish: Fix Released Status in glibc source package in Impish: Fix Committed Bug description: see https://launchpad.net/ubuntu/+source/gdb/10.2-0ubuntu3 $ zcat buildlog_ubuntu-impish-armhf.gdb_10.2-0ubuntu3_BUILDING.txt.gz | fgrep '(timeout)'|wc -l 10451 To manage notifications about this bug go to: https://bugs.launchpad.net/gdb/+bug/1927192/+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 1919177] Re: Azure: issues with accelerated networking on Hirsute
@ddstreed Could you please look into this SRU candidate?
@gjolly What is the importance/urgency of landing this fix?
** Also affects: cloud-init (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Also affects: linux-azure (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu)
Status: Incomplete => Fix Released
** Changed in: linux-azure (Ubuntu Hirsute)
Status: New => Invalid
** Changed in: cloud-init (Ubuntu Hirsute)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1919177
Title:
Azure: issues with accelerated networking on Hirsute
Status in cloud-init:
Incomplete
Status in cloud-init package in Ubuntu:
Incomplete
Status in linux-azure package in Ubuntu:
Invalid
Status in systemd package in Ubuntu:
Fix Released
Status in cloud-init source package in Hirsute:
Incomplete
Status in linux-azure source package in Hirsute:
Invalid
Status in systemd source package in Hirsute:
New
Bug description:
[General]
On Azure, when provisioning a Hirsute VM with Accelerated Networking
enabled, sometimes part of the cloud-init configuration is not
applied.
Especially, in those cases, the public SSH key is not setup properly.
[how to reproduce]
Start a VM with AN enabled:
```
az vm create --name "$VM_NAME --resource-group "$GROUP" --location "UK South"
--image
'Canonical:0001-com-ubuntu-server-hirsute-daily:21_04-daily-gen2:latest' --size
Standard_F8s_v2 --admin-username ubuntu --ssh-key-value "$SSH_KEY"
--accelerated-networking
```
After a moment, try to SSH: if you succeed, delete and recreate a new
VM.
[troubleshooting]
To be able to connect into the VM, run:
az vm run-command invoke -g "$GROUP" -n "$VM_NAME" --command-id
RunShellScript --scripts "sudo -u ubuntu ssh-import-id $LP_USERNAME"
```
In "/run/cloud-init/instance-data.json", I can see:
```
"publicKeys": [
{
"keyData": "",
"path": "/home/ubuntu/.ssh/authorized_keys"
}
],
```
as expected.
[workaround]
As mentioned, Azure allows the user to run command into the VM without
SSH connection. To do so, one can use the Azure CLI:
az vm run-command invoke -g "$GROUP" -n "$VM_NAME" --command-id
RunShellScript --scripts "sudo -u ubuntu ssh-import-id $LP_USERNAME"
This example uses "ssh-import-id" but it's also possible to just echo
a given public key into /home/ubuntu/.ssh/authorized_keys
NOTE: this will only solves the SSH issue, I do not know if this bug
affects other things. If so the user would have to apply those things
manually.
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1919177/+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 1927192] Re: gdb ftbfs on armhf, testsuite timeouts
** Description changed: + [Impact] + + * Gdb can't set some breakpoints in ld.so on armhf when libc6-dbg is not + installed. + + [Test Plan] + + * Check that ld.so is not stripped on armhf: + + * Check that ld.so is stripped on amd64: + + $ file /lib/x86_64-linux-gnu/ld-2.31.so + /lib/x86_64-linux-gnu/ld-2.31.so: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, BuildID[sha1]=ea85fcb25ee4c4c9e7b180924ab4a44257a9547a, stripped + + [Where problems could occur] + + * The fix is not stripping ld.so on armhf. Not stripping it comes with a + slight increase in file size but this should not be performance + critical. Accidentally ld.so could be left unstripped on other + architectures, but the test plan covers checking that, at least on + amd64. Other than those not stripping ld.so should not cause any issue. + + + [Original Bug Text] + see https://launchpad.net/ubuntu/+source/gdb/10.2-0ubuntu3 $ zcat buildlog_ubuntu-impish-armhf.gdb_10.2-0ubuntu3_BUILDING.txt.gz | fgrep '(timeout)'|wc -l 10451 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdb in Ubuntu. https://bugs.launchpad.net/bugs/1927192 Title: gdb ftbfs on armhf, testsuite timeouts Status in gdb: Incomplete Status in gdb package in Ubuntu: Fix Released Status in glibc package in Ubuntu: Fix Committed Status in gdb source package in Focal: New Status in glibc source package in Focal: New Status in gdb source package in Groovy: New Status in glibc source package in Groovy: New Status in gdb source package in Hirsute: New Status in glibc source package in Hirsute: New Status in gdb source package in Impish: Fix Released Status in glibc source package in Impish: Fix Committed Bug description: [Impact] * Gdb can't set some breakpoints in ld.so on armhf when libc6-dbg is not installed. [Test Plan] * Check that ld.so is not stripped on armhf: $ /lib/*/ld-2.31.so libc6/lib/arm-linux-gnueabihf/ld-2.31.so: ELF 32-bit LSB shared object, ARM, EABI5 version 1 (SYSV), dynamically linked, BuildID[sha1]=e20a43bff0c4d2aa7f508c93eadad973ea0c0af9, with debug_info, not stripped * Check that ld.so is stripped on amd64: $ file /lib/x86_64-linux-gnu/ld-2.31.so /lib/x86_64-linux-gnu/ld-2.31.so: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, BuildID[sha1]=ea85fcb25ee4c4c9e7b180924ab4a44257a9547a, stripped [Where problems could occur] * The fix is not stripping ld.so on armhf. Not stripping it comes with a notable increase in file size and it may be performance critical 109K stripped vs 1.3M unstripped. Accidentally ld.so could be left unstripped on other architectures, but the test plan covers checking that, at least on amd64. Other than those not stripping ld.so should not cause any issue. [Original Bug Text] see https://launchpad.net/ubuntu/+source/gdb/10.2-0ubuntu3 $ zcat buildlog_ubuntu-impish-armhf.gdb_10.2-0ubuntu3_BUILDING.txt.gz | fgrep '(timeout)'|wc -l 10451 To manage notifications about this bug go to: https://bugs.launchpad.net/gdb/+bug/1927192/+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 1927192] Re: gdb ftbfs on armhf, testsuite timeouts
@doko Not stripping ld.so on Focal came with an increase of ld.so from 110K to 1.3M. I don't think this is an acceptable increase when pulling in libc6-dbg also fixes the problem. See the test package here: https://launchpad.net/~ci-train-ppa- service/+archive/ubuntu/4570 ** Description changed: [Impact] * Gdb can't set some breakpoints in ld.so on armhf when libc6-dbg is not installed. [Test Plan] * Check that ld.so is not stripped on armhf: + $ /lib/*/ld-2.31.so + libc6/lib/arm-linux-gnueabihf/ld-2.31.so: ELF 32-bit LSB shared object, ARM, EABI5 version 1 (SYSV), dynamically linked, BuildID[sha1]=e20a43bff0c4d2aa7f508c93eadad973ea0c0af9, with debug_info, not stripped * Check that ld.so is stripped on amd64: $ file /lib/x86_64-linux-gnu/ld-2.31.so /lib/x86_64-linux-gnu/ld-2.31.so: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, BuildID[sha1]=ea85fcb25ee4c4c9e7b180924ab4a44257a9547a, stripped [Where problems could occur] * The fix is not stripping ld.so on armhf. Not stripping it comes with a - slight increase in file size but this should not be performance - critical. Accidentally ld.so could be left unstripped on other - architectures, but the test plan covers checking that, at least on - amd64. Other than those not stripping ld.so should not cause any issue. - + notable increase in file size and it may be performance critical 109K + stripped vs 1.3M unstripped. Accidentally ld.so could be left unstripped + on other architectures, but the test plan covers checking that, at least + on amd64. Other than those not stripping ld.so should not cause any + issue. [Original Bug Text] see https://launchpad.net/ubuntu/+source/gdb/10.2-0ubuntu3 $ zcat buildlog_ubuntu-impish-armhf.gdb_10.2-0ubuntu3_BUILDING.txt.gz | fgrep '(timeout)'|wc -l 10451 ** Changed in: glibc (Ubuntu Hirsute) Status: New => Opinion ** Changed in: glibc (Ubuntu Groovy) Status: New => Opinion ** Changed in: glibc (Ubuntu Focal) Status: New => Opinion -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdb in Ubuntu. https://bugs.launchpad.net/bugs/1927192 Title: gdb ftbfs on armhf, testsuite timeouts Status in gdb: Incomplete Status in gdb package in Ubuntu: Fix Released Status in glibc package in Ubuntu: Fix Committed Status in gdb source package in Focal: New Status in glibc source package in Focal: Opinion Status in gdb source package in Groovy: New Status in glibc source package in Groovy: Opinion Status in gdb source package in Hirsute: New Status in glibc source package in Hirsute: Opinion Status in gdb source package in Impish: Fix Released Status in glibc source package in Impish: Fix Committed Bug description: [Impact] * Gdb can't set some breakpoints in ld.so on armhf when libc6-dbg is not installed. [Test Plan] * Check that ld.so is not stripped on armhf: $ /lib/*/ld-2.31.so libc6/lib/arm-linux-gnueabihf/ld-2.31.so: ELF 32-bit LSB shared object, ARM, EABI5 version 1 (SYSV), dynamically linked, BuildID[sha1]=e20a43bff0c4d2aa7f508c93eadad973ea0c0af9, with debug_info, not stripped * Check that ld.so is stripped on amd64: $ file /lib/x86_64-linux-gnu/ld-2.31.so /lib/x86_64-linux-gnu/ld-2.31.so: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, BuildID[sha1]=ea85fcb25ee4c4c9e7b180924ab4a44257a9547a, stripped [Where problems could occur] * The fix is not stripping ld.so on armhf. Not stripping it comes with a notable increase in file size and it may be performance critical 109K stripped vs 1.3M unstripped. Accidentally ld.so could be left unstripped on other architectures, but the test plan covers checking that, at least on amd64. Other than those not stripping ld.so should not cause any issue. [Original Bug Text] see https://launchpad.net/ubuntu/+source/gdb/10.2-0ubuntu3 $ zcat buildlog_ubuntu-impish-armhf.gdb_10.2-0ubuntu3_BUILDING.txt.gz | fgrep '(timeout)'|wc -l 10451 To manage notifications about this bug go to: https://bugs.launchpad.net/gdb/+bug/1927192/+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 1927192] Re: gdb ftbfs on armhf, testsuite timeouts
IMO the change should be reverted later in Impish as well. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdb in Ubuntu. https://bugs.launchpad.net/bugs/1927192 Title: gdb ftbfs on armhf, testsuite timeouts Status in gdb: Incomplete Status in gdb package in Ubuntu: Fix Released Status in glibc package in Ubuntu: Fix Committed Status in gdb source package in Focal: New Status in glibc source package in Focal: Opinion Status in gdb source package in Groovy: New Status in glibc source package in Groovy: Opinion Status in gdb source package in Hirsute: New Status in glibc source package in Hirsute: Opinion Status in gdb source package in Impish: Fix Released Status in glibc source package in Impish: Fix Committed Bug description: [Impact] * Gdb can't set some breakpoints in ld.so on armhf when libc6-dbg is not installed. [Test Plan] * Check that ld.so is not stripped on armhf: $ /lib/*/ld-2.31.so libc6/lib/arm-linux-gnueabihf/ld-2.31.so: ELF 32-bit LSB shared object, ARM, EABI5 version 1 (SYSV), dynamically linked, BuildID[sha1]=e20a43bff0c4d2aa7f508c93eadad973ea0c0af9, with debug_info, not stripped * Check that ld.so is stripped on amd64: $ file /lib/x86_64-linux-gnu/ld-2.31.so /lib/x86_64-linux-gnu/ld-2.31.so: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, BuildID[sha1]=ea85fcb25ee4c4c9e7b180924ab4a44257a9547a, stripped [Where problems could occur] * The fix is not stripping ld.so on armhf. Not stripping it comes with a notable increase in file size and it may be performance critical 109K stripped vs 1.3M unstripped. Accidentally ld.so could be left unstripped on other architectures, but the test plan covers checking that, at least on amd64. Other than those not stripping ld.so should not cause any issue. [Original Bug Text] see https://launchpad.net/ubuntu/+source/gdb/10.2-0ubuntu3 $ zcat buildlog_ubuntu-impish-armhf.gdb_10.2-0ubuntu3_BUILDING.txt.gz | fgrep '(timeout)'|wc -l 10451 To manage notifications about this bug go to: https://bugs.launchpad.net/gdb/+bug/1927192/+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 1931088] Re: boot-and-services tests fails in impish on armhf (248.3)
Marking auto package testing as affected based on @paelzer's observation that it occurs only on Ubuntu's CI infra. I've also triggered the test with hello to see current status and for confirmation. ** Also affects: auto-package-testing Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1931088 Title: boot-and-services tests fails in impish on armhf (248.3) Status in Auto Package Testing: New Status in dnsmasq package in Ubuntu: Incomplete Status in gdm3 package in Ubuntu: Incomplete Status in glibc package in Ubuntu: Incomplete Status in isc-dhcp package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Incomplete Bug description: Systemd 248.3-1ubuntu1 is rather new, but had 5 successful tests on armhf before now slipping into a bad mode. Now it seems all tests failed in boot-and-services by hanging until killed by VirtSubproc.Timeout of autokgtest. The last [1] test log has a bit more, it shows a python stack overflow ``` VirtSubproc.Timeout Fatal Python error: Cannot recover from stack overflow. Python runtime state: initialized Current thread 0x7f108e840740 (most recent call first): File "/home/ubuntu/autopkgtest/lib/adtlog.py", line 36 in log File "/home/ubuntu/autopkgtest/lib/adtlog.py", line 86 in debug File "/home/ubuntu/autopkgtest/lib/adt_testbed.py", line 472 in send File "/home/ubuntu/autopkgtest/lib/adt_testbed.py", line 521 in command ``` I have seen a bunch of packages including even gdm3 and glibc being blocked by that so I wanted to at least track down the issue until we can put it on someones task list to resolve. No one replied to my pings yet, but maybe that means someone is already debugging this and had enabled some debugging? By running the same in armhf container on arm64 VM on canonistack I've seen no issues. The test worked fine and had no hang/issues. root@systemd-test-fail:~/systemd-248.3# ./debian/tests/boot-and-services lxc 1 test_profile (__main__.AppArmorTest) AppArmor confined unit ... skipped 'fails on armhf testbeds, see LP: #1842352' test_help (__main__.CLITest) --help works and succeeds ... ok test_invalid_option (__main__.CLITest) Calling with invalid option fails ... ok test_version (__main__.CLITest) --version works and succeeds ... ok test_cpushares (__main__.CgroupsTest) service with CPUShares ... ok test_simple (__main__.CgroupsTest) simple service ... ok test_bash_crash (__main__.CoredumpTest) ... skipped 'systemd-coredump does not work in containers' test_log_for_service (__main__.JournalTest) ... ok test_no_options (__main__.JournalTest) ... ok test_boot (__main__.NspawnTest) ... skipped 'nspawn does not work in most containers' test_service (__main__.NspawnTest) ... skipped 'nspawn does not work in most containers' test_failing (__main__.SeccompTest) ... ok test_0_init (__main__.ServicesTest) Verify that init is systemd ... ok test_cron (__main__.ServicesTest) ... ok test_dbus (__main__.ServicesTest) ... ok test_gdm3 (__main__.ServicesTest) ... skipped 'gdm3 not found' test_logind (__main__.ServicesTest) ... ok test_network_manager (__main__.ServicesTest) ... ok test_no_failed (__main__.ServicesTest) No failed units ... ok test_rsyslog (__main__.ServicesTest) ... ok test_tmp_cleanup (__main__.ServicesTest) ... ok test_tmp_mount (__main__.ServicesTest) ... ok test_udev (__main__.ServicesTest) ... skipped 'udev does not work in containers' -- Ran 23 tests in 5.589s OK (skipped=6) So I can not reproduce this on canonistack, but it blocks autopkgtests of various packages pretty reproducibly :-/ [1]: https://autopkgtest.ubuntu.com/results/autopkgtest- impish/impish/armhf/s/systemd/20210604_081326_d4319@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/auto-package-testing/+bug/1931088/+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 1931088] Re: boot-and-services tests fails in impish on armhf (248.3)
** Changed in: systemd (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1931088 Title: boot-and-services tests fails in impish on armhf (248.3) Status in Auto Package Testing: New Status in dnsmasq package in Ubuntu: Incomplete Status in gdm3 package in Ubuntu: Incomplete Status in glibc package in Ubuntu: Incomplete Status in isc-dhcp package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Incomplete Bug description: Systemd 248.3-1ubuntu1 is rather new, but had 5 successful tests on armhf before now slipping into a bad mode. Now it seems all tests failed in boot-and-services by hanging until killed by VirtSubproc.Timeout of autokgtest. The last [1] test log has a bit more, it shows a python stack overflow ``` VirtSubproc.Timeout Fatal Python error: Cannot recover from stack overflow. Python runtime state: initialized Current thread 0x7f108e840740 (most recent call first): File "/home/ubuntu/autopkgtest/lib/adtlog.py", line 36 in log File "/home/ubuntu/autopkgtest/lib/adtlog.py", line 86 in debug File "/home/ubuntu/autopkgtest/lib/adt_testbed.py", line 472 in send File "/home/ubuntu/autopkgtest/lib/adt_testbed.py", line 521 in command ``` I have seen a bunch of packages including even gdm3 and glibc being blocked by that so I wanted to at least track down the issue until we can put it on someones task list to resolve. No one replied to my pings yet, but maybe that means someone is already debugging this and had enabled some debugging? By running the same in armhf container on arm64 VM on canonistack I've seen no issues. The test worked fine and had no hang/issues. root@systemd-test-fail:~/systemd-248.3# ./debian/tests/boot-and-services lxc 1 test_profile (__main__.AppArmorTest) AppArmor confined unit ... skipped 'fails on armhf testbeds, see LP: #1842352' test_help (__main__.CLITest) --help works and succeeds ... ok test_invalid_option (__main__.CLITest) Calling with invalid option fails ... ok test_version (__main__.CLITest) --version works and succeeds ... ok test_cpushares (__main__.CgroupsTest) service with CPUShares ... ok test_simple (__main__.CgroupsTest) simple service ... ok test_bash_crash (__main__.CoredumpTest) ... skipped 'systemd-coredump does not work in containers' test_log_for_service (__main__.JournalTest) ... ok test_no_options (__main__.JournalTest) ... ok test_boot (__main__.NspawnTest) ... skipped 'nspawn does not work in most containers' test_service (__main__.NspawnTest) ... skipped 'nspawn does not work in most containers' test_failing (__main__.SeccompTest) ... ok test_0_init (__main__.ServicesTest) Verify that init is systemd ... ok test_cron (__main__.ServicesTest) ... ok test_dbus (__main__.ServicesTest) ... ok test_gdm3 (__main__.ServicesTest) ... skipped 'gdm3 not found' test_logind (__main__.ServicesTest) ... ok test_network_manager (__main__.ServicesTest) ... ok test_no_failed (__main__.ServicesTest) No failed units ... ok test_rsyslog (__main__.ServicesTest) ... ok test_tmp_cleanup (__main__.ServicesTest) ... ok test_tmp_mount (__main__.ServicesTest) ... ok test_udev (__main__.ServicesTest) ... skipped 'udev does not work in containers' -- Ran 23 tests in 5.589s OK (skipped=6) So I can not reproduce this on canonistack, but it blocks autopkgtests of various packages pretty reproducibly :-/ [1]: https://autopkgtest.ubuntu.com/results/autopkgtest- impish/impish/armhf/s/systemd/20210604_081326_d4319@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/auto-package-testing/+bug/1931088/+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 1930910] Re: Fix micmute hotkeys on HP ProBooks
** Changed in: systemd (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1930910
Title:
Fix micmute hotkeys on HP ProBooks
Status in HWE Next:
New
Status in systemd package in Ubuntu:
In Progress
Bug description:
[Impact]
Micmute hotkey on many HP ProBooks don't work.
[Fix]
Commit a7161e0288d1 ("hwdb: Add ProBook to use micmute hotkey"), to map AT
keyboard's scancode to micmute hotkey.
[Test]
With the one-liner fix, micmute hotkey works on all the ProBooks I tested.
[Where problems could occur]
The hwdb originally only matches a few ProBooks, the fix changes that to
match all ProBook models. So if there's any ProBook that uses the scancode for
another purpose, there will be a regression.
However, the risk is rather slim because HP explicitly states that all
ProBooks use the same scancode for mic mute hotkey.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1930910/+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 1930910] Re: Fix micmute hotkeys on HP ProBooks
I've queued the fix in the git packaging repository to be included in
the next upload.
** Changed in: systemd (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1930910
Title:
Fix micmute hotkeys on HP ProBooks
Status in HWE Next:
New
Status in systemd package in Ubuntu:
Fix Committed
Bug description:
[Impact]
Micmute hotkey on many HP ProBooks don't work.
[Fix]
Commit a7161e0288d1 ("hwdb: Add ProBook to use micmute hotkey"), to map AT
keyboard's scancode to micmute hotkey.
[Test]
With the one-liner fix, micmute hotkey works on all the ProBooks I tested.
[Where problems could occur]
The hwdb originally only matches a few ProBooks, the fix changes that to
match all ProBook models. So if there's any ProBook that uses the scancode for
another purpose, there will be a regression.
However, the risk is rather slim because HP explicitly states that all
ProBooks use the same scancode for mic mute hotkey.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1930910/+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 1823872] Re: Fixing fsfreeze-hook can break unattended upgrades
** Changed in: unattended-upgrades (Ubuntu Trusty) Assignee: Balint Reczey (rbalint) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1823872 Title: Fixing fsfreeze-hook can break unattended upgrades Status in qemu package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Trusty: Confirmed Status in unattended-upgrades source package in Xenial: Fix Released Status in unattended-upgrades source package in Bionic: Fix Released Status in unattended-upgrades source package in Cosmic: Fix Released Status in unattended-upgrades source package in Disco: Fix Released Bug description: [Impact] * If an update has a new conffile at a path that in a former version was a directory like old: /a/b/c new: a/b Here b is the new file name and was a directory in the old version. Then unattended upgrades breaks on installing such a package. * a recent qemu update has such a case and due to that triggered the issue in >=Bionic * The fix is to harden unattended upgrades to be able to handle the case without aborting. [Test Case] Get a qemu guest e.g. of Bionic before the update to 1:2.11+dfsg-1ubuntu7.12 That can be done with: $ time uvt-simplestreams-libvirt --verbose sync --source http://cloud-images.ubuntu.com/daily arch=amd64 label=daily release=bionic $ uvt-kvm create --password ubuntu bionic-testuu arch=amd64 release=bionic label=daily Log in and apt update & upgrade all packages, then Install the release level qemu in there. $ uvt-kvm ssh bionic-testuu $ sudo apt update $ sudo apt dist-upgrade $ sudo apt install unattended-upgrades $ sudo apt install qemu-guest-agent=1:2.11+dfsg-1ubuntu7 All before was preparation, now force the unattended upgrade to trigger the bug. $ sudo unattended-upgrade -d With the bug you'll find some error like: found pkg: qemu-guest-agent conffile line: /etc/init.d/qemu-guest-agent f61a64ac1e48993023018fd1cff85191 current md5: f61a64ac1e48993023018fd1cff85191 conffile line: /etc/qemu/fsfreeze-hook/fsfreeze-hook 15f6ff42cbc5550a07ee21c2a471d905 /etc/qemu/fsfreeze-hook/fsfreeze-hook not in package conffiles /etc/init.d/qemu-guest-agent /etc/qemu/fsfreeze-hook found conffile /etc/qemu/fsfreeze-hook in new pkg but on dpkg status Traceback (most recent call last): File "/usr/bin/unattended-upgrade", line 2057, in sys.exit(main(options)) File "/usr/bin/unattended-upgrade", line 1773, in main if conffile_prompt(item.destfile): File "/usr/bin/unattended-upgrade", line 988, in conffile_prompt with open(prefix + conf_file, 'rb') as fp: IsADirectoryError: [Errno 21] Is a directory: '/etc/qemu/fsfreeze-hook' [Regression Potential] * The fix is trying to detect moved conffiles by looking for /etc/foo/foo when the new package ships /etc/foo and /etc/foo is not a known conffile and also checking the renames in the opposite direction. The potential regression is breaking the logic for detecting changed conffiles and either holding back a package for no reason or trying to install a package with a modified conffile on the system and aborting the upgrade in the middle due to the appearing conffile prompt. To avoid such regressions the test_conffile.py tests are extended to cover rename scenarios. [Other Info] * n/a --- As reported on https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1820291/comments/20 We fixed an issue and we added workrounds since basic mv_conffile coudn't handle it and did all sort of upgrade tests. That all worked fine and moved the conffile. It was now reported that due to some pre-checks that unattended upgrades might do this might do some checks on its own. Next step: - check unattended upgrades through this change - check if it only affects cases were the former config was modified (minority) or the default file layout (majority) --- original report copied --- just wanted to add: This bug also crashes unattended-upgrade and thus prevents security updates on 18.04: root@mailin1:~# unattended-upgrade Traceback (most recent call last): File "/usr/bin/unattended-upgrade", line 1998, in sys.exit(main(options)) File "/usr/bin/unattended-upgrade", line 1714, in main if conffile_prompt(item.destfile): File "/usr/bin/unattended-upgrade", line 929, in conffile_prompt with open(prefix + conf_file, 'rb') as fp: IsADirectoryError: [Errno 21] Is a directory: '/etc/qemu/fsfreeze-hook' Basically, unattended-upgrade wants to compare old/new conffiles and doesn't like it w
[Touch-packages] [Bug 1923845] Re: Please compress packages with zstd by default
The attached dpkg patch has been tested in the following Bileto ticket:
https://bileto.ubuntu.com/#/ticket/4583
Lintian needs to be fixed first to ensure smooth migration. The
software-properties failure does not seem to be related at first glance.
** Patch added: "dpkg_1.20.9ubuntu2.patch"
https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1923845/+attachment/5504752/+files/dpkg_1.20.9ubuntu2.patch
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1923845
Title:
Please compress packages with zstd by default
Status in appstream-glib package in Ubuntu:
New
Status in apt package in Ubuntu:
Fix Released
Status in aptly package in Ubuntu:
New
Status in boinc package in Ubuntu:
New
Status in busybox package in Ubuntu:
New
Status in cdebootstrap package in Ubuntu:
New
Status in cdist package in Ubuntu:
New
Status in debdelta package in Ubuntu:
New
Status in debian-el package in Ubuntu:
New
Status in debootstrap package in Ubuntu:
Fix Released
Status in debsig-verify package in Ubuntu:
New
Status in debsigs package in Ubuntu:
New
Status in diffoscope package in Ubuntu:
New
Status in dpkg package in Ubuntu:
New
Status in dpkg-sig package in Ubuntu:
New
Status in file package in Ubuntu:
New
Status in libsolv package in Ubuntu:
New
Status in lintian package in Ubuntu:
New
Status in lutris package in Ubuntu:
New
Status in obs-build package in Ubuntu:
New
Status in osc package in Ubuntu:
New
Status in radare2 package in Ubuntu:
New
Status in reprepro package in Ubuntu:
New
Status in vim-scripts package in Ubuntu:
New
Status in zeroinstall-injector package in Ubuntu:
New
Bug description:
https://people.canonical.com/~rbalint/zstd-debs/ contains a .deb built
on Hirsute having both data and control members of the .deb being
compressed with zstd. It can be handy for testing various tools.
[dpkg]
Decompression support in dpkg landed first in Bionic and is being SRUd to
Xenial in LP: #1764220 enable Launchpad's Xenial systems to process the
zstd-compressed binary packages.
From dpkg's perspective the upgrade path is cleared.
The original plan was compressing only the internal data.tar .deb
member, but dpkg uses uniform compression by default since dpkg 1.19.0
thus I'm collecting all the changes to support control.tar.zst, too,
in this bug.
Reviewed packages from:
https://codesearch.debian.net/search?q=data.tar.xz&literal=1&perpkg=1
https://codesearch.debian.net/search?q=control.tar.xz&literal=1&perpkg=1
appstream-glib - needs fix: libappstream-builder/asb-package-deb.c
aptly - needs fix: deb/deb.go
boinc - needs fix: debian/fetch_example_applications.sh
busybox - needs fix: archival/dpkg_deb.c archival/dpkg.c
cdebootstrap- needs fix: src/package.c
cdist - may need fix, can use dpkg-deb:
cdist/preos/debootstrap/files/devuan-debootstrap/functions
debdelta- needs fix: debdelta debpatch.sh
debian-el - needs fix: deb-view.el
debian-handbook - needs fix, maybe later, for Debian
debootstrap - needs fix,
https://salsa.debian.org/installer-team/debootstrap/-/merge_requests/54
debsigs - needs fix, debsigs
debsig-verify - needs fix, src/debsig-verify.c
diffoscope - needs fix, diffoscope/comparators/deb.py
dpkg- needs fix, change default
dpkg-sig- needs fix, dpkg-sig
dpmb- needs fix, maybe later, for Debian
elfutils- may need fix, uses dpkg-deb if it is available, does not
handle .gz either
file- needs fix, magic/Magdir/archive
libsolv - needs fix, ext/repo_deb.c
lintian - needs fix malformed-deb-archive
lutris - needs fix, lutris/util/extract.py
obs-build - needs fix Build/Deb.pm
osc - needs fix osc/util/debquery.py control.tar.zst only
python-apt - needs fix
apt_inst.DebFile("glibc-doc-reference_2.33-0ubuntu2~zstd1_all.deb").control.extractall()
radare2 - needs fix
reprepro- needs fix, debfile.c
vim-scripts - needs fix debPlugin/autoload/deb.vim
winetricks - needs fix when Debian switches src/winetricks
zeroinstall-injector - needs fix src/zeroinstall/archive.ml
acr - skip, does not _have to_ be fixed, just creates packages,
see dist/deb_hand.mak
alien - skip, uses dpkg-deb to extract .deb
ansible - not affected, just test data in dbdata.tar.xz
anthy - not affected, just changelog entry
apt - seems fixed already
ceph- not affected in Ubuntu's version
circlator - not affected, just test data
cowdancer - not affected, just documentation
eccodes - skip, just orig-data.tar.xz
eckit - skip, just ...orig-data.tar.xz
firefox - skip, profdata.tar.xz
[Touch-packages] [Bug 1923845] Re: Please compress packages with zstd by default
** Patch removed: "dpkg_1.20.9ubuntu2.patch"
https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1923845/+attachment/5504752/+files/dpkg_1.20.9ubuntu2.patch
** Patch added: "dpkg_1.20.9ubuntu2.patch"
https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1923845/+attachment/5504779/+files/dpkg_1.20.9ubuntu2.patch
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1923845
Title:
Please compress packages with zstd by default
Status in appstream-glib package in Ubuntu:
New
Status in apt package in Ubuntu:
Fix Released
Status in aptly package in Ubuntu:
New
Status in boinc package in Ubuntu:
New
Status in busybox package in Ubuntu:
New
Status in cdebootstrap package in Ubuntu:
New
Status in cdist package in Ubuntu:
New
Status in debdelta package in Ubuntu:
New
Status in debian-el package in Ubuntu:
New
Status in debootstrap package in Ubuntu:
Fix Released
Status in debsig-verify package in Ubuntu:
New
Status in debsigs package in Ubuntu:
New
Status in diffoscope package in Ubuntu:
New
Status in dpkg package in Ubuntu:
New
Status in dpkg-sig package in Ubuntu:
New
Status in file package in Ubuntu:
New
Status in libsolv package in Ubuntu:
New
Status in lintian package in Ubuntu:
New
Status in lutris package in Ubuntu:
New
Status in obs-build package in Ubuntu:
New
Status in osc package in Ubuntu:
New
Status in radare2 package in Ubuntu:
New
Status in reprepro package in Ubuntu:
New
Status in vim-scripts package in Ubuntu:
New
Status in zeroinstall-injector package in Ubuntu:
New
Bug description:
https://people.canonical.com/~rbalint/zstd-debs/ contains a .deb built
on Hirsute having both data and control members of the .deb being
compressed with zstd. It can be handy for testing various tools.
[dpkg]
Decompression support in dpkg landed first in Bionic and is being SRUd to
Xenial in LP: #1764220 enable Launchpad's Xenial systems to process the
zstd-compressed binary packages.
From dpkg's perspective the upgrade path is cleared.
The original plan was compressing only the internal data.tar .deb
member, but dpkg uses uniform compression by default since dpkg 1.19.0
thus I'm collecting all the changes to support control.tar.zst, too,
in this bug.
Reviewed packages from:
https://codesearch.debian.net/search?q=data.tar.xz&literal=1&perpkg=1
https://codesearch.debian.net/search?q=control.tar.xz&literal=1&perpkg=1
appstream-glib - needs fix: libappstream-builder/asb-package-deb.c
aptly - needs fix: deb/deb.go
boinc - needs fix: debian/fetch_example_applications.sh
busybox - needs fix: archival/dpkg_deb.c archival/dpkg.c
cdebootstrap- needs fix: src/package.c
cdist - may need fix, can use dpkg-deb:
cdist/preos/debootstrap/files/devuan-debootstrap/functions
debdelta- needs fix: debdelta debpatch.sh
debian-el - needs fix: deb-view.el
debian-handbook - needs fix, maybe later, for Debian
debootstrap - needs fix,
https://salsa.debian.org/installer-team/debootstrap/-/merge_requests/54
debsigs - needs fix, debsigs
debsig-verify - needs fix, src/debsig-verify.c
diffoscope - needs fix, diffoscope/comparators/deb.py
dpkg- needs fix, change default
dpkg-sig- needs fix, dpkg-sig
dpmb- needs fix, maybe later, for Debian
elfutils- may need fix, uses dpkg-deb if it is available, does not
handle .gz either
file- needs fix, magic/Magdir/archive
libsolv - needs fix, ext/repo_deb.c
lintian - needs fix malformed-deb-archive
lutris - needs fix, lutris/util/extract.py
obs-build - needs fix Build/Deb.pm
osc - needs fix osc/util/debquery.py control.tar.zst only
python-apt - needs fix
apt_inst.DebFile("glibc-doc-reference_2.33-0ubuntu2~zstd1_all.deb").control.extractall()
radare2 - needs fix
reprepro- needs fix, debfile.c
vim-scripts - needs fix debPlugin/autoload/deb.vim
winetricks - needs fix when Debian switches src/winetricks
zeroinstall-injector - needs fix src/zeroinstall/archive.ml
acr - skip, does not _have to_ be fixed, just creates packages,
see dist/deb_hand.mak
alien - skip, uses dpkg-deb to extract .deb
ansible - not affected, just test data in dbdata.tar.xz
anthy - not affected, just changelog entry
apt - seems fixed already
ceph- not affected in Ubuntu's version
circlator - not affected, just test data
cowdancer - not affected, just documentation
eccodes - skip, just orig-data.tar.xz
eckit - skip, just ...orig-data.tar.xz
firefox - skip, profdata.tar.xz
firefox-esr - skip, profdata.tar.xz
galculator - skip, just changelog
grads
[Touch-packages] [Bug 1923845] Re: Please compress packages with zstd by default
@xnox Thanks! Please also SRU the reprepro changes. Ideally users of
reprepro on stable releases would be able to just upgrade reprepro from
-updates before the first zstd-compressed .deb lands in Impish to not
break their setup even when they maintain a local repository of the
devel series.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to file in Ubuntu.
https://bugs.launchpad.net/bugs/1923845
Title:
Please compress packages with zstd by default
Status in appstream-glib package in Ubuntu:
New
Status in apt package in Ubuntu:
Fix Released
Status in aptly package in Ubuntu:
New
Status in boinc package in Ubuntu:
New
Status in busybox package in Ubuntu:
New
Status in cdebootstrap package in Ubuntu:
New
Status in cdist package in Ubuntu:
New
Status in debdelta package in Ubuntu:
New
Status in debian-el package in Ubuntu:
New
Status in debootstrap package in Ubuntu:
Fix Released
Status in debsig-verify package in Ubuntu:
New
Status in debsigs package in Ubuntu:
New
Status in diffoscope package in Ubuntu:
New
Status in dpkg package in Ubuntu:
New
Status in dpkg-sig package in Ubuntu:
New
Status in file package in Ubuntu:
New
Status in libsolv package in Ubuntu:
New
Status in lintian package in Ubuntu:
Fix Released
Status in lutris package in Ubuntu:
New
Status in obs-build package in Ubuntu:
New
Status in osc package in Ubuntu:
New
Status in radare2 package in Ubuntu:
New
Status in reprepro package in Ubuntu:
New
Status in vim-scripts package in Ubuntu:
New
Status in zeroinstall-injector package in Ubuntu:
New
Bug description:
https://people.canonical.com/~rbalint/zstd-debs/ contains a .deb built
on Hirsute having both data and control members of the .deb being
compressed with zstd. It can be handy for testing various tools.
[dpkg]
Decompression support in dpkg landed first in Bionic and is being SRUd to
Xenial in LP: #1764220 enable Launchpad's Xenial systems to process the
zstd-compressed binary packages.
From dpkg's perspective the upgrade path is cleared.
The original plan was compressing only the internal data.tar .deb
member, but dpkg uses uniform compression by default since dpkg 1.19.0
thus I'm collecting all the changes to support control.tar.zst, too,
in this bug.
Reviewed packages from:
https://codesearch.debian.net/search?q=data.tar.xz&literal=1&perpkg=1
https://codesearch.debian.net/search?q=control.tar.xz&literal=1&perpkg=1
appstream-glib - needs fix: libappstream-builder/asb-package-deb.c
aptly - needs fix: deb/deb.go
boinc - needs fix: debian/fetch_example_applications.sh
busybox - needs fix: archival/dpkg_deb.c archival/dpkg.c
cdebootstrap- needs fix: src/package.c
cdist - may need fix, can use dpkg-deb:
cdist/preos/debootstrap/files/devuan-debootstrap/functions
debdelta- needs fix: debdelta debpatch.sh
debian-el - needs fix: deb-view.el
debian-handbook - needs fix, maybe later, for Debian
debootstrap - needs fix,
https://salsa.debian.org/installer-team/debootstrap/-/merge_requests/54
debsigs - needs fix, debsigs
debsig-verify - needs fix, src/debsig-verify.c
diffoscope - needs fix, diffoscope/comparators/deb.py
dpkg- needs fix, change default
dpkg-sig- needs fix, dpkg-sig
dpmb- needs fix, maybe later, for Debian
elfutils- may need fix, uses dpkg-deb if it is available, does not
handle .gz either
file- needs fix, magic/Magdir/archive
libsolv - needs fix, ext/repo_deb.c
lintian - needs fix malformed-deb-archive
lutris - needs fix, lutris/util/extract.py
obs-build - needs fix Build/Deb.pm
osc - needs fix osc/util/debquery.py control.tar.zst only
python-apt - needs fix
apt_inst.DebFile("glibc-doc-reference_2.33-0ubuntu2~zstd1_all.deb").control.extractall()
radare2 - needs fix
reprepro- needs fix, debfile.c
vim-scripts - needs fix debPlugin/autoload/deb.vim
winetricks - needs fix when Debian switches src/winetricks
zeroinstall-injector - needs fix src/zeroinstall/archive.ml
acr - skip, does not _have to_ be fixed, just creates packages,
see dist/deb_hand.mak
alien - skip, uses dpkg-deb to extract .deb
ansible - not affected, just test data in dbdata.tar.xz
anthy - not affected, just changelog entry
apt - seems fixed already
ceph- not affected in Ubuntu's version
circlator - not affected, just test data
cowdancer - not affected, just documentation
eccodes - skip, just orig-data.tar.xz
eckit - skip, just ...orig-data.tar.xz
firefox - skip, profdata.tar.xz
firefox-esr - skip, profdata.tar.xz
galculator - skip, just changelog
grads - skip,
[Touch-packages] [Bug 1923845] Re: Please compress packages with zstd by default
** Bug watch added: Debian Bug tracker #878900
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878900
** Also affects: debian-el (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878900
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to file in Ubuntu.
https://bugs.launchpad.net/bugs/1923845
Title:
Please compress packages with zstd by default
Status in appstream-glib package in Ubuntu:
New
Status in apt package in Ubuntu:
Fix Released
Status in aptly package in Ubuntu:
New
Status in boinc package in Ubuntu:
New
Status in busybox package in Ubuntu:
New
Status in cdebootstrap package in Ubuntu:
New
Status in cdist package in Ubuntu:
New
Status in debdelta package in Ubuntu:
New
Status in debian-el package in Ubuntu:
New
Status in debootstrap package in Ubuntu:
Fix Released
Status in debsig-verify package in Ubuntu:
New
Status in debsigs package in Ubuntu:
New
Status in diffoscope package in Ubuntu:
New
Status in dpkg package in Ubuntu:
New
Status in dpkg-sig package in Ubuntu:
New
Status in file package in Ubuntu:
New
Status in hello package in Ubuntu:
Fix Released
Status in libsolv package in Ubuntu:
New
Status in lintian package in Ubuntu:
Fix Released
Status in lutris package in Ubuntu:
New
Status in obs-build package in Ubuntu:
New
Status in osc package in Ubuntu:
New
Status in radare2 package in Ubuntu:
New
Status in reprepro package in Ubuntu:
Fix Released
Status in vim-scripts package in Ubuntu:
New
Status in zeroinstall-injector package in Ubuntu:
New
Status in debian-el package in Debian:
Unknown
Bug description:
https://people.canonical.com/~rbalint/zstd-debs/ contains a .deb built
on Hirsute having both data and control members of the .deb being
compressed with zstd. It can be handy for testing various tools.
[dpkg]
Decompression support in dpkg landed first in Bionic and is being SRUd to
Xenial in LP: #1764220 enable Launchpad's Xenial systems to process the
zstd-compressed binary packages.
From dpkg's perspective the upgrade path is cleared.
The original plan was compressing only the internal data.tar .deb
member, but dpkg uses uniform compression by default since dpkg 1.19.0
thus I'm collecting all the changes to support control.tar.zst, too,
in this bug.
Reviewed packages from:
https://codesearch.debian.net/search?q=data.tar.xz&literal=1&perpkg=1
https://codesearch.debian.net/search?q=control.tar.xz&literal=1&perpkg=1
appstream-glib - needs fix: libappstream-builder/asb-package-deb.c
aptly - needs fix: deb/deb.go
boinc - needs fix: debian/fetch_example_applications.sh
busybox - needs fix: archival/dpkg_deb.c archival/dpkg.c
cdebootstrap- needs fix: src/package.c
cdist - may need fix, can use dpkg-deb:
cdist/preos/debootstrap/files/devuan-debootstrap/functions
debdelta- needs fix: debdelta debpatch.sh
debian-el - needs fix: deb-view.el
debian-handbook - needs fix, maybe later, for Debian
debootstrap - needs fix,
https://salsa.debian.org/installer-team/debootstrap/-/merge_requests/54
debsigs - needs fix, debsigs
debsig-verify - needs fix, src/debsig-verify.c
diffoscope - needs fix, diffoscope/comparators/deb.py
dpkg- needs fix, change default
dpkg-sig- needs fix, dpkg-sig
dpmb- needs fix, maybe later, for Debian
elfutils- may need fix, uses dpkg-deb if it is available, does not
handle .gz either
file- needs fix, magic/Magdir/archive
libsolv - needs fix, ext/repo_deb.c
lintian - needs fix malformed-deb-archive
lutris - needs fix, lutris/util/extract.py
obs-build - needs fix Build/Deb.pm
osc - needs fix osc/util/debquery.py control.tar.zst only
python-apt - needs fix
apt_inst.DebFile("glibc-doc-reference_2.33-0ubuntu2~zstd1_all.deb").control.extractall()
radare2 - needs fix
reprepro- needs fix, debfile.c
vim-scripts - needs fix debPlugin/autoload/deb.vim
winetricks - needs fix when Debian switches src/winetricks
zeroinstall-injector - needs fix src/zeroinstall/archive.ml
acr - skip, does not _have to_ be fixed, just creates packages,
see dist/deb_hand.mak
alien - skip, uses dpkg-deb to extract .deb
ansible - not affected, just test data in dbdata.tar.xz
anthy - not affected, just changelog entry
apt - seems fixed already
ceph- not affected in Ubuntu's version
circlator - not affected, just test data
cowdancer - not affected, just documentation
eccodes - skip, just orig-data.tar.xz
eckit - skip, just ...orig-data.tar.xz
firefox - skip, profdata.tar.xz
firefox-esr - skip, profdata.tar.x
[Touch-packages] [Bug 1923845] Re: Please compress packages with zstd by default
Proposed diffoscope fix: https://salsa.debian.org/reproducible-
builds/diffoscope/-/merge_requests/83
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to file in Ubuntu.
https://bugs.launchpad.net/bugs/1923845
Title:
Please compress packages with zstd by default
Status in appstream-glib package in Ubuntu:
New
Status in apt package in Ubuntu:
Fix Released
Status in aptly package in Ubuntu:
New
Status in boinc package in Ubuntu:
New
Status in busybox package in Ubuntu:
New
Status in cdebootstrap package in Ubuntu:
New
Status in cdist package in Ubuntu:
New
Status in debdelta package in Ubuntu:
New
Status in debian-el package in Ubuntu:
New
Status in debootstrap package in Ubuntu:
Fix Released
Status in debsig-verify package in Ubuntu:
New
Status in debsigs package in Ubuntu:
New
Status in diffoscope package in Ubuntu:
New
Status in dpkg package in Ubuntu:
New
Status in dpkg-sig package in Ubuntu:
New
Status in file package in Ubuntu:
New
Status in hello package in Ubuntu:
Fix Released
Status in libsolv package in Ubuntu:
New
Status in lintian package in Ubuntu:
Fix Released
Status in lutris package in Ubuntu:
New
Status in obs-build package in Ubuntu:
New
Status in osc package in Ubuntu:
New
Status in radare2 package in Ubuntu:
New
Status in reprepro package in Ubuntu:
Fix Released
Status in vim-scripts package in Ubuntu:
New
Status in zeroinstall-injector package in Ubuntu:
New
Status in debian-el package in Debian:
Unknown
Bug description:
https://people.canonical.com/~rbalint/zstd-debs/ contains a .deb built
on Hirsute having both data and control members of the .deb being
compressed with zstd. It can be handy for testing various tools.
[dpkg]
Decompression support in dpkg landed first in Bionic and is being SRUd to
Xenial in LP: #1764220 enable Launchpad's Xenial systems to process the
zstd-compressed binary packages.
From dpkg's perspective the upgrade path is cleared.
The original plan was compressing only the internal data.tar .deb
member, but dpkg uses uniform compression by default since dpkg 1.19.0
thus I'm collecting all the changes to support control.tar.zst, too,
in this bug.
Reviewed packages from:
https://codesearch.debian.net/search?q=data.tar.xz&literal=1&perpkg=1
https://codesearch.debian.net/search?q=control.tar.xz&literal=1&perpkg=1
appstream-glib - needs fix: libappstream-builder/asb-package-deb.c
aptly - needs fix: deb/deb.go
boinc - needs fix: debian/fetch_example_applications.sh
busybox - needs fix: archival/dpkg_deb.c archival/dpkg.c
cdebootstrap- needs fix: src/package.c
cdist - may need fix, can use dpkg-deb:
cdist/preos/debootstrap/files/devuan-debootstrap/functions
debdelta- needs fix: debdelta debpatch.sh
debian-el - needs fix: deb-view.el
debian-handbook - needs fix, maybe later, for Debian
debootstrap - needs fix,
https://salsa.debian.org/installer-team/debootstrap/-/merge_requests/54
debsigs - needs fix, debsigs
debsig-verify - needs fix, src/debsig-verify.c
diffoscope - needs fix, diffoscope/comparators/deb.py
dpkg- needs fix, change default
dpkg-sig- needs fix, dpkg-sig
dpmb- needs fix, maybe later, for Debian
elfutils- may need fix, uses dpkg-deb if it is available, does not
handle .gz either
file- needs fix, magic/Magdir/archive
libsolv - needs fix, ext/repo_deb.c
lintian - needs fix malformed-deb-archive
lutris - needs fix, lutris/util/extract.py
obs-build - needs fix Build/Deb.pm
osc - needs fix osc/util/debquery.py control.tar.zst only
python-apt - needs fix
apt_inst.DebFile("glibc-doc-reference_2.33-0ubuntu2~zstd1_all.deb").control.extractall()
radare2 - needs fix
reprepro- needs fix, debfile.c
vim-scripts - needs fix debPlugin/autoload/deb.vim
winetricks - needs fix when Debian switches src/winetricks
zeroinstall-injector - needs fix src/zeroinstall/archive.ml
acr - skip, does not _have to_ be fixed, just creates packages,
see dist/deb_hand.mak
alien - skip, uses dpkg-deb to extract .deb
ansible - not affected, just test data in dbdata.tar.xz
anthy - not affected, just changelog entry
apt - seems fixed already
ceph- not affected in Ubuntu's version
circlator - not affected, just test data
cowdancer - not affected, just documentation
eccodes - skip, just orig-data.tar.xz
eckit - skip, just ...orig-data.tar.xz
firefox - skip, profdata.tar.xz
firefox-esr - skip, profdata.tar.xz
galculator - skip, just changelog
grads - skip, ...orig-data.tar.xz
gvmd- skip, just creates xz compressed .deb
ins
[Touch-packages] [Bug 1923845] Re: Please compress packages with zstd by default
Diffoscope already handles zstd compressed members well.
** Changed in: diffoscope (Ubuntu)
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to file in Ubuntu.
https://bugs.launchpad.net/bugs/1923845
Title:
Please compress packages with zstd by default
Status in appstream-glib package in Ubuntu:
New
Status in apt package in Ubuntu:
Fix Released
Status in aptly package in Ubuntu:
New
Status in boinc package in Ubuntu:
New
Status in busybox package in Ubuntu:
New
Status in cdebootstrap package in Ubuntu:
New
Status in cdist package in Ubuntu:
New
Status in debdelta package in Ubuntu:
New
Status in debian-el package in Ubuntu:
New
Status in debootstrap package in Ubuntu:
Fix Released
Status in debsig-verify package in Ubuntu:
New
Status in debsigs package in Ubuntu:
New
Status in diffoscope package in Ubuntu:
New
Status in dpkg package in Ubuntu:
New
Status in dpkg-sig package in Ubuntu:
New
Status in file package in Ubuntu:
New
Status in hello package in Ubuntu:
Fix Released
Status in libsolv package in Ubuntu:
New
Status in lintian package in Ubuntu:
Fix Released
Status in lutris package in Ubuntu:
New
Status in obs-build package in Ubuntu:
New
Status in osc package in Ubuntu:
New
Status in radare2 package in Ubuntu:
New
Status in reprepro package in Ubuntu:
Fix Released
Status in vim-scripts package in Ubuntu:
New
Status in zeroinstall-injector package in Ubuntu:
New
Status in debian-el package in Debian:
Unknown
Bug description:
https://people.canonical.com/~rbalint/zstd-debs/ contains a .deb built
on Hirsute having both data and control members of the .deb being
compressed with zstd. It can be handy for testing various tools.
[dpkg]
Decompression support in dpkg landed first in Bionic and is being SRUd to
Xenial in LP: #1764220 enable Launchpad's Xenial systems to process the
zstd-compressed binary packages.
From dpkg's perspective the upgrade path is cleared.
The original plan was compressing only the internal data.tar .deb
member, but dpkg uses uniform compression by default since dpkg 1.19.0
thus I'm collecting all the changes to support control.tar.zst, too,
in this bug.
Reviewed packages from:
https://codesearch.debian.net/search?q=data.tar.xz&literal=1&perpkg=1
https://codesearch.debian.net/search?q=control.tar.xz&literal=1&perpkg=1
appstream-glib - needs fix: libappstream-builder/asb-package-deb.c
aptly - needs fix: deb/deb.go
boinc - needs fix: debian/fetch_example_applications.sh
busybox - needs fix: archival/dpkg_deb.c archival/dpkg.c
cdebootstrap- needs fix: src/package.c
cdist - may need fix, can use dpkg-deb:
cdist/preos/debootstrap/files/devuan-debootstrap/functions
debdelta- needs fix: debdelta debpatch.sh
debian-el - needs fix: deb-view.el
debian-handbook - needs fix, maybe later, for Debian
debootstrap - needs fix,
https://salsa.debian.org/installer-team/debootstrap/-/merge_requests/54
debsigs - needs fix, debsigs
debsig-verify - needs fix, src/debsig-verify.c
diffoscope - needs fix, diffoscope/comparators/deb.py
dpkg- needs fix, change default
dpkg-sig- needs fix, dpkg-sig
dpmb- needs fix, maybe later, for Debian
elfutils- may need fix, uses dpkg-deb if it is available, does not
handle .gz either
file- needs fix, magic/Magdir/archive
libsolv - needs fix, ext/repo_deb.c
lintian - needs fix malformed-deb-archive
lutris - needs fix, lutris/util/extract.py
obs-build - needs fix Build/Deb.pm
osc - needs fix osc/util/debquery.py control.tar.zst only
python-apt - needs fix
apt_inst.DebFile("glibc-doc-reference_2.33-0ubuntu2~zstd1_all.deb").control.extractall()
radare2 - needs fix
reprepro- needs fix, debfile.c
vim-scripts - needs fix debPlugin/autoload/deb.vim
winetricks - needs fix when Debian switches src/winetricks
zeroinstall-injector - needs fix src/zeroinstall/archive.ml
acr - skip, does not _have to_ be fixed, just creates packages,
see dist/deb_hand.mak
alien - skip, uses dpkg-deb to extract .deb
ansible - not affected, just test data in dbdata.tar.xz
anthy - not affected, just changelog entry
apt - seems fixed already
ceph- not affected in Ubuntu's version
circlator - not affected, just test data
cowdancer - not affected, just documentation
eccodes - skip, just orig-data.tar.xz
eckit - skip, just ...orig-data.tar.xz
firefox - skip, profdata.tar.xz
firefox-esr - skip, profdata.tar.xz
galculator - skip, just changelog
grads - skip, ...orig-data.tar.xz
gvmd- skip, just crea
[Touch-packages] [Bug 1700814] Re: Default capability of cap_setfcap+i should be set on setcap
** Changed in: libcap2 (Ubuntu) Assignee: Balint Reczey (rbalint) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libcap2 in Ubuntu. https://bugs.launchpad.net/bugs/1700814 Title: Default capability of cap_setfcap+i should be set on setcap Status in libcap2 package in Ubuntu: New Bug description: If I grant a user (via pam_cap) cap_setfcap+i, I would then expect them to be able to use setcap without sudo. setcap is not provided with any default file capabilities however, so either the user has to sudo, or I have to grant the setfcap capability to setcap with setcap. In my mind, it would be reasonable to grant setfcap+i to setcap by default on installation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcap2/+bug/1700814/+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 1915126] Re: autopkgtest times out (or fails before that) in hirsute
** Merge proposal linked: https://code.launchpad.net/~rbalint/autopkgtest-cloud/+git/autopkgtest-cloud/+merge/383953 ** Summary changed: - autopkgtest times out (or fails before that) in hirsute + autopkgtest times out (or fails before that) in hirsute on test infra, passes locally -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1915126 Title: autopkgtest times out (or fails before that) in hirsute on test infra, passes locally Status in systemd package in Ubuntu: New Bug description: Hi, I've asked yesterday on IRC but so far got no answer. I think it is right to file a bug about the current state of systemd autopkgtest to unite the efforts in regard to it. I was looking at the systemd tests for a no-change rebuild that really had no reason to now make it fail. While checking I found that as of this month (first bad test on 1st of February) most of the systemd test runs on amd64 will not pass/fail but instead in most cases time out. I've seen various people retry the case as it shows the typical symptoms of a "not the fault of the package, let us retry this" case. But it seems that won't help as the test history is rather clear. * Watch this in monospace to make more sense of it * $ check-autopkgtest-stats.sh -c 50 -p systemd -r "hirsute" -a "amd64" Check last 50 test results for src:systemd on releases 'hirsute' on architectures 'amd64' Of the 50 last tests, we had these subtest failing per release/arch: hirsute amd64 tests-in-lxd (F 2% f 0% S 0% B 12% => P 52%/) .BTTTBTT.BTBTTTBBTTT..F.. hostnamed (F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT. build-login(F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT. unit-config(F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT. networkd-testpy(F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT. localed-locale (F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT. boot-and-services (F 4% f 0% S 0% B 12% => P 50%/) .BTTTBTT.BTBTTTBBTTT...F.F... timedated (F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT. boot-smoke (F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT. logind (F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT. storage(F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT. upstream (F 12% f 0% S 0% B 12% => P 42%/) .BTTTBTT.BTBTTTBBTTTF.F.F..FF..F. udev (F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT. systemd-fsckd (F 8% f 0% S 0% B 12% => P 46%/) FBTTTBTTFBTBTTTBBTTT.F..F root-unittests (F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT. localed-x11-keymap (F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT. We see that formerly we had the known to be somewhat flaky, but otherwise working test (time goes from right to left). So we had the usual suspects of tests like upstream/systemd-fsck that failed a few times, but also working runs in between. But since February 22/24 runs failed very bad. 6 (=B) of those cases are aborting mid execution autopkgtest [22:08:58]: ERROR: testbed failure: testbed auxverb failed with exit code 255 And 16 of them timed out : failure: Timed out on waiting for ssh connection Sadly the 2/24 that didn't hard fail by that where broken by the known flaky systemd-fsckd test. Something drives this test crazy that we have to find and resolve, at the current rate nothing depending on it is likely to migrate. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1915126/+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 1915126] Re: autopkgtest times out (or fails before that) in hirsute on test infra, passes locally
@paelzer I seems infra issues got worse, but there is a pending review to bump systemd to big which I linked. Even in the absence of the infra issues it would have made sense to make system run big test instances, but I expect the big instances would also improve the current situation. Instead of hinting system I'd like to give a try to running it on big instances to see it it makes any difference. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1915126 Title: autopkgtest times out (or fails before that) in hirsute on test infra, passes locally Status in systemd package in Ubuntu: New Bug description: Hi, I've asked yesterday on IRC but so far got no answer. I think it is right to file a bug about the current state of systemd autopkgtest to unite the efforts in regard to it. I was looking at the systemd tests for a no-change rebuild that really had no reason to now make it fail. While checking I found that as of this month (first bad test on 1st of February) most of the systemd test runs on amd64 will not pass/fail but instead in most cases time out. I've seen various people retry the case as it shows the typical symptoms of a "not the fault of the package, let us retry this" case. But it seems that won't help as the test history is rather clear. * Watch this in monospace to make more sense of it * $ check-autopkgtest-stats.sh -c 50 -p systemd -r "hirsute" -a "amd64" Check last 50 test results for src:systemd on releases 'hirsute' on architectures 'amd64' Of the 50 last tests, we had these subtest failing per release/arch: hirsute amd64 tests-in-lxd (F 2% f 0% S 0% B 12% => P 52%/) .BTTTBTT.BTBTTTBBTTT..F.. hostnamed (F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT. build-login(F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT. unit-config(F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT. networkd-testpy(F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT. localed-locale (F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT. boot-and-services (F 4% f 0% S 0% B 12% => P 50%/) .BTTTBTT.BTBTTTBBTTT...F.F... timedated (F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT. boot-smoke (F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT. logind (F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT. storage(F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT. upstream (F 12% f 0% S 0% B 12% => P 42%/) .BTTTBTT.BTBTTTBBTTTF.F.F..FF..F. udev (F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT. systemd-fsckd (F 8% f 0% S 0% B 12% => P 46%/) FBTTTBTTFBTBTTTBBTTT.F..F root-unittests (F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT. localed-x11-keymap (F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT. We see that formerly we had the known to be somewhat flaky, but otherwise working test (time goes from right to left). So we had the usual suspects of tests like upstream/systemd-fsck that failed a few times, but also working runs in between. But since February 22/24 runs failed very bad. 6 (=B) of those cases are aborting mid execution autopkgtest [22:08:58]: ERROR: testbed failure: testbed auxverb failed with exit code 255 And 16 of them timed out : failure: Timed out on waiting for ssh connection Sadly the 2/24 that didn't hard fail by that where broken by the known flaky systemd-fsckd test. Something drives this test crazy that we have to find and resolve, at the current rate nothing depending on it is likely to migrate. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1915126/+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 1915126] Re: autopkgtest times out (or fails before that) in hirsute on test infra, passes locally
** Merge proposal unlinked: https://code.launchpad.net/~rbalint/autopkgtest-cloud/+git/autopkgtest-cloud/+merge/383953 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1915126 Title: autopkgtest times out (or fails before that) in hirsute on test infra, passes locally Status in systemd package in Ubuntu: New Bug description: Hi, I've asked yesterday on IRC but so far got no answer. I think it is right to file a bug about the current state of systemd autopkgtest to unite the efforts in regard to it. I was looking at the systemd tests for a no-change rebuild that really had no reason to now make it fail. While checking I found that as of this month (first bad test on 1st of February) most of the systemd test runs on amd64 will not pass/fail but instead in most cases time out. I've seen various people retry the case as it shows the typical symptoms of a "not the fault of the package, let us retry this" case. But it seems that won't help as the test history is rather clear. * Watch this in monospace to make more sense of it * $ check-autopkgtest-stats.sh -c 50 -p systemd -r "hirsute" -a "amd64" Check last 50 test results for src:systemd on releases 'hirsute' on architectures 'amd64' Of the 50 last tests, we had these subtest failing per release/arch: hirsute amd64 tests-in-lxd (F 2% f 0% S 0% B 12% => P 52%/) .BTTTBTT.BTBTTTBBTTT..F.. hostnamed (F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT. build-login(F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT. unit-config(F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT. networkd-testpy(F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT. localed-locale (F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT. boot-and-services (F 4% f 0% S 0% B 12% => P 50%/) .BTTTBTT.BTBTTTBBTTT...F.F... timedated (F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT. boot-smoke (F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT. logind (F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT. storage(F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT. upstream (F 12% f 0% S 0% B 12% => P 42%/) .BTTTBTT.BTBTTTBBTTTF.F.F..FF..F. udev (F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT. systemd-fsckd (F 8% f 0% S 0% B 12% => P 46%/) FBTTTBTTFBTBTTTBBTTT.F..F root-unittests (F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT. localed-x11-keymap (F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT. We see that formerly we had the known to be somewhat flaky, but otherwise working test (time goes from right to left). So we had the usual suspects of tests like upstream/systemd-fsck that failed a few times, but also working runs in between. But since February 22/24 runs failed very bad. 6 (=B) of those cases are aborting mid execution autopkgtest [22:08:58]: ERROR: testbed failure: testbed auxverb failed with exit code 255 And 16 of them timed out : failure: Timed out on waiting for ssh connection Sadly the 2/24 that didn't hard fail by that where broken by the known flaky systemd-fsckd test. Something drives this test crazy that we have to find and resolve, at the current rate nothing depending on it is likely to migrate. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1915126/+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 1915126] Re: autopkgtest times out (or fails before that) in hirsute on test infra, passes locally
** Also affects: auto-package-testing Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1915126 Title: autopkgtest times out (or fails before that) in hirsute on test infra, passes locally Status in Auto Package Testing: New Status in systemd package in Ubuntu: New Bug description: Hi, I've asked yesterday on IRC but so far got no answer. I think it is right to file a bug about the current state of systemd autopkgtest to unite the efforts in regard to it. I was looking at the systemd tests for a no-change rebuild that really had no reason to now make it fail. While checking I found that as of this month (first bad test on 1st of February) most of the systemd test runs on amd64 will not pass/fail but instead in most cases time out. I've seen various people retry the case as it shows the typical symptoms of a "not the fault of the package, let us retry this" case. But it seems that won't help as the test history is rather clear. * Watch this in monospace to make more sense of it * $ check-autopkgtest-stats.sh -c 50 -p systemd -r "hirsute" -a "amd64" Check last 50 test results for src:systemd on releases 'hirsute' on architectures 'amd64' Of the 50 last tests, we had these subtest failing per release/arch: hirsute amd64 tests-in-lxd (F 2% f 0% S 0% B 12% => P 52%/) .BTTTBTT.BTBTTTBBTTT..F.. hostnamed (F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT. build-login(F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT. unit-config(F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT. networkd-testpy(F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT. localed-locale (F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT. boot-and-services (F 4% f 0% S 0% B 12% => P 50%/) .BTTTBTT.BTBTTTBBTTT...F.F... timedated (F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT. boot-smoke (F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT. logind (F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT. storage(F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT. upstream (F 12% f 0% S 0% B 12% => P 42%/) .BTTTBTT.BTBTTTBBTTTF.F.F..FF..F. udev (F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT. systemd-fsckd (F 8% f 0% S 0% B 12% => P 46%/) FBTTTBTTFBTBTTTBBTTT.F..F root-unittests (F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT. localed-x11-keymap (F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT. We see that formerly we had the known to be somewhat flaky, but otherwise working test (time goes from right to left). So we had the usual suspects of tests like upstream/systemd-fsck that failed a few times, but also working runs in between. But since February 22/24 runs failed very bad. 6 (=B) of those cases are aborting mid execution autopkgtest [22:08:58]: ERROR: testbed failure: testbed auxverb failed with exit code 255 And 16 of them timed out : failure: Timed out on waiting for ssh connection Sadly the 2/24 that didn't hard fail by that where broken by the known flaky systemd-fsckd test. Something drives this test crazy that we have to find and resolve, at the current rate nothing depending on it is likely to migrate. To manage notifications about this bug go to: https://bugs.launchpad.net/auto-package-testing/+bug/1915126/+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 1914062] Re: NetworkManager-wait-online.service in 1.28.0-2ubuntu1 fails to start in LXC
@seb128 I tried remounting /sys in systemd but it created other issues. I've fixed udevd to not start in lxc in systemd, but this is all systemd can do. Please detect running udev in network-manager without assuming that rw /sys implies running udev. @ LXD devs, please check if the init to start is systemd and if so please mount /sys ro to conform to systemd's https://systemd.io/CONTAINER_INTERFACE/ or sort convince systemd upstream to include LXC in the container interface with rw /sys. ** Also affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Also affects: lxd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1914062 Title: NetworkManager-wait-online.service in 1.28.0-2ubuntu1 fails to start in LXC Status in lxd package in Ubuntu: New Status in network-manager package in Ubuntu: New Status in systemd package in Ubuntu: Triaged Bug description: This regresses systemd's autopkgtest because it expects the system in the container to reach running state, but the system ends up in degraded state due to the service failing. https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute/hirsute/amd64/s/systemd/20210112_185712_ff570@/log.gz ... == FAIL: test_no_failed (__main__.ServicesTest) No failed units -- Traceback (most recent call last): File "/tmp/autopkgtest.fFC3Lw/build.xLc/real-tree/debian/tests/boot-and-services", line 68, in test_no_failed self.assertEqual(failed, []) AssertionError: Lists differ: ['● NetworkManager-wait-online.service loa[42 chars]ine'] != [] First list contains 1 additional elements. First extra element 0: '● NetworkManager-wait-online.service loaded failed failed Network Manager Wait Online' + [] - ['● NetworkManager-wait-online.service loaded failed failed Network Manager ' - 'Wait Online'] -- Ran 23 tests in 4.435s ... Reproducible locally by installing n-m from -proposed, then restarting the system in the LXC container. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1914062/+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 1915126] Re: autopkgtest times out (or fails before that) in hirsute on test infra, passes locally
There is not much to do about the failures on systemd's side. The tests are reliably passing in qemu on my i5-4670 testbed from 2013, also passing on @paelzer's presumably newer machine. This is an infra issue. The Release Team can decide if they want to hint the test and lose gating coverage, but I'm not filing the hint because IMO the test infra should be fixed. ** Changed in: systemd (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1915126 Title: autopkgtest times out (or fails before that) in hirsute on test infra, passes locally Status in Auto Package Testing: New Status in systemd package in Ubuntu: Invalid Bug description: Hi, I've asked yesterday on IRC but so far got no answer. I think it is right to file a bug about the current state of systemd autopkgtest to unite the efforts in regard to it. I was looking at the systemd tests for a no-change rebuild that really had no reason to now make it fail. While checking I found that as of this month (first bad test on 1st of February) most of the systemd test runs on amd64 will not pass/fail but instead in most cases time out. I've seen various people retry the case as it shows the typical symptoms of a "not the fault of the package, let us retry this" case. But it seems that won't help as the test history is rather clear. * Watch this in monospace to make more sense of it * $ check-autopkgtest-stats.sh -c 50 -p systemd -r "hirsute" -a "amd64" Check last 50 test results for src:systemd on releases 'hirsute' on architectures 'amd64' Of the 50 last tests, we had these subtest failing per release/arch: hirsute amd64 tests-in-lxd (F 2% f 0% S 0% B 12% => P 52%/) .BTTTBTT.BTBTTTBBTTT..F.. hostnamed (F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT. build-login(F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT. unit-config(F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT. networkd-testpy(F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT. localed-locale (F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT. boot-and-services (F 4% f 0% S 0% B 12% => P 50%/) .BTTTBTT.BTBTTTBBTTT...F.F... timedated (F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT. boot-smoke (F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT. logind (F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT. storage(F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT. upstream (F 12% f 0% S 0% B 12% => P 42%/) .BTTTBTT.BTBTTTBBTTTF.F.F..FF..F. udev (F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT. systemd-fsckd (F 8% f 0% S 0% B 12% => P 46%/) FBTTTBTTFBTBTTTBBTTT.F..F root-unittests (F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT. localed-x11-keymap (F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT. We see that formerly we had the known to be somewhat flaky, but otherwise working test (time goes from right to left). So we had the usual suspects of tests like upstream/systemd-fsck that failed a few times, but also working runs in between. But since February 22/24 runs failed very bad. 6 (=B) of those cases are aborting mid execution autopkgtest [22:08:58]: ERROR: testbed failure: testbed auxverb failed with exit code 255 And 16 of them timed out : failure: Timed out on waiting for ssh connection Sadly the 2/24 that didn't hard fail by that where broken by the known flaky systemd-fsckd test. Something drives this test crazy that we have to find and resolve, at the current rate nothing depending on it is likely to migrate. To manage notifications about this bug go to: https://bugs.launchpad.net/auto-package-testing/+bug/1915126/+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 1914062] Re: NetworkManager-wait-online.service in 1.28.0-2ubuntu1 fails to start in LXC
@stgraber nothing should break honoring https://systemd.io/CONTAINER_INTERFACE/ and we are in constant uphill battle with systemd and other upstreams checking /sys's ro status. Detecting the init system is easy, please do it in LXD. It may make sense to allow the user to override that and force /sys readonly in LXC config, but then it is up to the user to fix failing services, the user cares about, too. ** Changed in: lxd (Ubuntu) Status: Invalid => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1914062 Title: NetworkManager-wait-online.service in 1.28.0-2ubuntu1 fails to start in LXC Status in lxd package in Ubuntu: New Status in network-manager package in Ubuntu: New Status in systemd package in Ubuntu: Triaged Bug description: This regresses systemd's autopkgtest because it expects the system in the container to reach running state, but the system ends up in degraded state due to the service failing. https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute/hirsute/amd64/s/systemd/20210112_185712_ff570@/log.gz ... == FAIL: test_no_failed (__main__.ServicesTest) No failed units -- Traceback (most recent call last): File "/tmp/autopkgtest.fFC3Lw/build.xLc/real-tree/debian/tests/boot-and-services", line 68, in test_no_failed self.assertEqual(failed, []) AssertionError: Lists differ: ['● NetworkManager-wait-online.service loa[42 chars]ine'] != [] First list contains 1 additional elements. First extra element 0: '● NetworkManager-wait-online.service loaded failed failed Network Manager Wait Online' + [] - ['● NetworkManager-wait-online.service loaded failed failed Network Manager ' - 'Wait Online'] -- Ran 23 tests in 4.435s ... Reproducible locally by installing n-m from -proposed, then restarting the system in the LXC container. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1914062/+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 1914062] Re: NetworkManager-wait-online.service in 1.28.0-2ubuntu1 fails to start in LXC
@stgraber or work with systemd upstream to extend the container API. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1914062 Title: NetworkManager-wait-online.service in 1.28.0-2ubuntu1 fails to start in LXC Status in lxd package in Ubuntu: New Status in network-manager package in Ubuntu: New Status in systemd package in Ubuntu: Triaged Bug description: This regresses systemd's autopkgtest because it expects the system in the container to reach running state, but the system ends up in degraded state due to the service failing. https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute/hirsute/amd64/s/systemd/20210112_185712_ff570@/log.gz ... == FAIL: test_no_failed (__main__.ServicesTest) No failed units -- Traceback (most recent call last): File "/tmp/autopkgtest.fFC3Lw/build.xLc/real-tree/debian/tests/boot-and-services", line 68, in test_no_failed self.assertEqual(failed, []) AssertionError: Lists differ: ['● NetworkManager-wait-online.service loa[42 chars]ine'] != [] First list contains 1 additional elements. First extra element 0: '● NetworkManager-wait-online.service loaded failed failed Network Manager Wait Online' + [] - ['● NetworkManager-wait-online.service loaded failed failed Network Manager ' - 'Wait Online'] -- Ran 23 tests in 4.435s ... Reproducible locally by installing n-m from -proposed, then restarting the system in the LXC container. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1914062/+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 1915386] Re: package unattended-upgrades 1.1ubuntu1.18.04.7~16.04.6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
What happened here? Installing new version of config file /etc/logrotate.d/unattended-upgrades ... Installing new version of config file /etc/pm/sleep.d/10_unattended-upgrades-hibernate ... ]0;root@gilles-1215B-1215B: /root@gilles-1215B-1215B:/# ls[K[Kps -ef UIDPID PPID C STIME TTY TIME CMD root 1 0 0 21:32 ?00:00:09 /sbin/init I guess https://github.com/mvo5/unattended-upgrades/pull/288 will fix it if there were no local changes. ** Changed in: unattended-upgrades (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1915386 Title: package unattended-upgrades 1.1ubuntu1.18.04.7~16.04.6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in unattended-upgrades package in Ubuntu: Incomplete Bug description: erreur logiciel lors ouverture session ou pour upgrade ProblemType: Package DistroRelease: Ubuntu 16.04 Package: unattended-upgrades 1.1ubuntu1.18.04.7~16.04.6 ProcVersionSignature: Ubuntu 4.4.0-201.233-generic 4.4.247 Uname: Linux 4.4.0-201-generic i686 ApportVersion: 2.20.1-0ubuntu2.30 Architecture: i386 Date: Wed Feb 10 23:01:24 2021 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2021-02-10 (0 days ago) InstallationMedia: Lubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.2) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.6 apt 1.2.32ubuntu0.2 SourcePackage: unattended-upgrades Title: package unattended-upgrades 1.1ubuntu1.18.04.7~16.04.6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.apt.apt.conf.d.50unattended-upgrades: 2020-02-17T19:03:38 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1915386/+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 1915126] Re: autopkgtest times out (or fails before that) in hirsute on test infra, passes locally
** Tags added: update-excuse -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1915126 Title: autopkgtest times out (or fails before that) in hirsute on test infra, passes locally Status in Auto Package Testing: New Status in systemd package in Ubuntu: Invalid Bug description: Hi, I've asked yesterday on IRC but so far got no answer. I think it is right to file a bug about the current state of systemd autopkgtest to unite the efforts in regard to it. I was looking at the systemd tests for a no-change rebuild that really had no reason to now make it fail. While checking I found that as of this month (first bad test on 1st of February) most of the systemd test runs on amd64 will not pass/fail but instead in most cases time out. I've seen various people retry the case as it shows the typical symptoms of a "not the fault of the package, let us retry this" case. But it seems that won't help as the test history is rather clear. * Watch this in monospace to make more sense of it * $ check-autopkgtest-stats.sh -c 50 -p systemd -r "hirsute" -a "amd64" Check last 50 test results for src:systemd on releases 'hirsute' on architectures 'amd64' Of the 50 last tests, we had these subtest failing per release/arch: hirsute amd64 tests-in-lxd (F 2% f 0% S 0% B 12% => P 52%/) .BTTTBTT.BTBTTTBBTTT..F.. hostnamed (F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT. build-login(F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT. unit-config(F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT. networkd-testpy(F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT. localed-locale (F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT. boot-and-services (F 4% f 0% S 0% B 12% => P 50%/) .BTTTBTT.BTBTTTBBTTT...F.F... timedated (F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT. boot-smoke (F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT. logind (F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT. storage(F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT. upstream (F 12% f 0% S 0% B 12% => P 42%/) .BTTTBTT.BTBTTTBBTTTF.F.F..FF..F. udev (F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT. systemd-fsckd (F 8% f 0% S 0% B 12% => P 46%/) FBTTTBTTFBTBTTTBBTTT.F..F root-unittests (F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT. localed-x11-keymap (F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT. We see that formerly we had the known to be somewhat flaky, but otherwise working test (time goes from right to left). So we had the usual suspects of tests like upstream/systemd-fsck that failed a few times, but also working runs in between. But since February 22/24 runs failed very bad. 6 (=B) of those cases are aborting mid execution autopkgtest [22:08:58]: ERROR: testbed failure: testbed auxverb failed with exit code 255 And 16 of them timed out : failure: Timed out on waiting for ssh connection Sadly the 2/24 that didn't hard fail by that where broken by the known flaky systemd-fsckd test. Something drives this test crazy that we have to find and resolve, at the current rate nothing depending on it is likely to migrate. To manage notifications about this bug go to: https://bugs.launchpad.net/auto-package-testing/+bug/1915126/+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 1914062] Re: NetworkManager-wait-online.service in 1.28.0-2ubuntu1 fails to start in LXC
@stgraber Thank you for assisting with aligning udevs's behaviour with LXD. I've added the tests-in-lxd autopkgtests to ensure catching issues in LXD earlier. I'd be happy to add more tests in systemd's autopkgtest to not let udevd regress in LXD. @xnox I don't like to idea of letting services be failed in default installs in LXD because this would result bad user experience. @seb128 could you please patch network-manager 1.28 to behave in LXC like it did in 1.26 to let it migrate and not fail in LXC with systemd 247 until the udevd behaviour is fixed in LXC? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1914062 Title: NetworkManager-wait-online.service in 1.28.0-2ubuntu1 fails to start in LXC Status in lxd package in Ubuntu: Won't Fix Status in network-manager package in Ubuntu: Invalid Status in systemd package in Ubuntu: Triaged Bug description: This regresses systemd's autopkgtest because it expects the system in the container to reach running state, but the system ends up in degraded state due to the service failing. https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute/hirsute/amd64/s/systemd/20210112_185712_ff570@/log.gz ... == FAIL: test_no_failed (__main__.ServicesTest) No failed units -- Traceback (most recent call last): File "/tmp/autopkgtest.fFC3Lw/build.xLc/real-tree/debian/tests/boot-and-services", line 68, in test_no_failed self.assertEqual(failed, []) AssertionError: Lists differ: ['● NetworkManager-wait-online.service loa[42 chars]ine'] != [] First list contains 1 additional elements. First extra element 0: '● NetworkManager-wait-online.service loaded failed failed Network Manager Wait Online' + [] - ['● NetworkManager-wait-online.service loaded failed failed Network Manager ' - 'Wait Online'] -- Ran 23 tests in 4.435s ... Reproducible locally by installing n-m from -proposed, then restarting the system in the LXC container. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1914062/+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 1914939] Re: faccessat2 syscall needed for Docker (needs backported from libseccomp 2.4.4+)
The fix for https://github.com/seccomp/libseccomp/issues/314 seems to be needed, too, also for migrating glibc 2.33. ** Bug watch added: github.com/seccomp/libseccomp/issues #314 https://github.com/seccomp/libseccomp/issues/314 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/1914939 Title: faccessat2 syscall needed for Docker (needs backported from libseccomp 2.4.4+) Status in libseccomp package in Ubuntu: Incomplete Bug description: The next release of Alpine Linux intends to use the faccessat2(2) syscall for access(3). This currently fails under Ubuntu Docker, regardless of using the separate Docker package repository, since it forbids faccessat2. This bug is similar to bug #1876055, but requests backporting of 2.4.4 instead of 2.4.3. I believe this change is likely low risk and can be applied to all supported Ubuntu versions. Alternatively, I also see in bug #1891810 that libseccomp 2.5 is being considered for backporting. This would also be acceptable for our purposes, but is obviously a higher-risk change for Ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1914939/+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 1915874] [NEW] autopkgtest fails in hirsute on armhf with glibc 2.33
Public bug reported: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute/hirsute/armhf/libs/libseccomp/20210214_103448_4822f@/log.gz ... autopkgtest [10:33:19]: test test-filter: [--- = ./debian/tests/data/all-3.19.filter = DEBUG: seccomp_load_filters ./debian/tests/data/all-3.19.filter Bad system call (core dumped) FAIL: expected to pass ... The problem seems to be that with the new glibc upstream version the test binaries started using statx which is not listed in the .filter files. ** Affects: libseccomp (Ubuntu) Importance: Undecided Status: New ** Tags: update-excuse ** Attachment added: "0001-Permit-statx-syscall-in-test-filter-autopkgtest.patch" https://bugs.launchpad.net/bugs/1915874/+attachment/5464259/+files/0001-Permit-statx-syscall-in-test-filter-autopkgtest.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/1915874 Title: autopkgtest fails in hirsute on armhf with glibc 2.33 Status in libseccomp package in Ubuntu: New Bug description: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute/hirsute/armhf/libs/libseccomp/20210214_103448_4822f@/log.gz ... autopkgtest [10:33:19]: test test-filter: [--- = ./debian/tests/data/all-3.19.filter = DEBUG: seccomp_load_filters ./debian/tests/data/all-3.19.filter Bad system call (core dumped) FAIL: expected to pass ... The problem seems to be that with the new glibc upstream version the test binaries started using statx which is not listed in the .filter files. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1915874/+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 1915936] Re: systemd-coredump user is created by something other than its derived systemd packages
Yes, the user is created using /usr/lib/sysusers.d/systemd.conf . -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1915936 Title: systemd-coredump user is created by something other than its derived systemd packages Status in systemd package in Ubuntu: New Bug description: systemd-coredump binary package is instructed as follows: #debian/systemd-coredump.postinst: adduser --quiet --system --group --no-create-home --home /run/systemd \ --gecos "systemd Core Dumper" systemd-coredump But one doesn't need this package to be installed to have the systemd- coredump user created. This was taken from a focal 20.04.2 fresh installation (Right after a vanilla installation): # cat /etc/passwd: ... systemd-coredump:x:999:999:systemd Core Dumper:/:/usr/sbin/nologin ... # dpkg -l | grep -i systemd ii dbus-user-session1.12.16-2ubuntu2.1 amd64simple interprocess messaging system (systemd --user integration) ii libnss-systemd:amd64 245.4-4ubuntu3.4 amd64nss module providing dynamic user and group name resolution ii libpam-systemd:amd64 245.4-4ubuntu3.4 amd64system and service manager - PAM module ii libsystemd0:amd64245.4-4ubuntu3.4 amd64systemd utility library ii networkd-dispatcher 2.0.1-1 all Dispatcher service for systemd-networkd connection status changes ii python3-systemd 234-3build2 amd64Python 3 bindings for systemd ii systemd 245.4-4ubuntu3.4 amd64system and service manager ii systemd-sysv 245.4-4ubuntu3.4 amd64system and service manager - SysV links ii systemd-timesyncd245.4-4ubuntu3.4 amd64minimalistic service to synchronize local time with NTP servers # /var/log/syslog syslog:Feb 17 15:31:56 test systemd-sysusers[402]: Creating group systemd-coredump with gid 999. syslog:Feb 17 15:31:56 test systemd-sysusers[402]: Creating user systemd-coredump (systemd Core Dumper) with uid 999 and gid 999. Additionnally, you may notice the home directory during the user creation at installation sets it to "/" as opposed to "/run/systemd" directive in the appropriate postint. It is contradictory. * Why systemd-coredump user is created at installation time and/or without 'systemd-coredump' package installed ? * Why this early creation set the home directory to "/" ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1915936/+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 1914062] Re: NetworkManager-wait-online.service in 1.28.0-2ubuntu1 fails to start in LXC
@seb128 please also include the fix for n-m tests failing due to MAC changes to let systemd 247.1-4ubuntu1 migrate. ** Changed in: network-manager (Ubuntu) Status: Invalid => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1914062 Title: NetworkManager-wait-online.service in 1.28.0-2ubuntu1 fails to start in LXC Status in lxd package in Ubuntu: Won't Fix Status in network-manager package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Triaged Bug description: This regresses systemd's autopkgtest because it expects the system in the container to reach running state, but the system ends up in degraded state due to the service failing. https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute/hirsute/amd64/s/systemd/20210112_185712_ff570@/log.gz ... == FAIL: test_no_failed (__main__.ServicesTest) No failed units -- Traceback (most recent call last): File "/tmp/autopkgtest.fFC3Lw/build.xLc/real-tree/debian/tests/boot-and-services", line 68, in test_no_failed self.assertEqual(failed, []) AssertionError: Lists differ: ['● NetworkManager-wait-online.service loa[42 chars]ine'] != [] First list contains 1 additional elements. First extra element 0: '● NetworkManager-wait-online.service loaded failed failed Network Manager Wait Online' + [] - ['● NetworkManager-wait-online.service loaded failed failed Network Manager ' - 'Wait Online'] -- Ran 23 tests in 4.435s ... Reproducible locally by installing n-m from -proposed, then restarting the system in the LXC container. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1914062/+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 1915887] Re: systemd spams the syslog about lack of native systemd unit file
** Bug watch added: Debian Bug tracker #981407 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981407 ** Also affects: systemd (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981407 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1915887 Title: systemd spams the syslog about lack of native systemd unit file Status in apport package in Ubuntu: Incomplete Status in fam package in Ubuntu: Incomplete Status in freeradius package in Ubuntu: Incomplete Status in ipfm package in Ubuntu: Incomplete Status in n2n package in Ubuntu: Incomplete Status in pfm package in Ubuntu: Incomplete Status in shadowsocks package in Ubuntu: Incomplete Status in sysfsutils package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Incomplete Status in virtualbox package in Ubuntu: Incomplete Status in xl2tpd package in Ubuntu: Incomplete Status in systemd package in Debian: Unknown Bug description: systemd in hirsute spams the syslog file several times per second about services lacking native systemd unit files. Two things should happen. 1) a systemd unit file ought to be created 2) systemd should be slowed down with regards to these messages Feb 17 02:02:48 ubuntu-devel kernel: [ 289.794825] systemd-sysv-generator[7105]: SysV service '/etc/init.d/n2n' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:02:49 ubuntu-devel kernel: [ 290.165351] systemd-sysv-generator[7126]: SysV service '/etc/init.d/n2n' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:02:49 ubuntu-devel kernel: [ 291.111278] systemd-sysv-generator[7170]: SysV service '/etc/init.d/n2n' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:02:50 ubuntu-devel kernel: [ 291.507164] systemd-sysv-generator[7199]: SysV service '/etc/init.d/n2n' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:05:57 ubuntu-devel kernel: [ 478.386062] systemd-sysv-generator[9909]: SysV service '/etc/init.d/fam' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:05:57 ubuntu-devel kernel: [ 478.386321] systemd-sysv-generator[9909]: SysV service '/etc/init.d/xl2tpd' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:05:57 ubuntu-devel kernel: [ 478.386742] systemd-sysv-generator[9909]: SysV service '/etc/init.d/ipfm' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:05:57 ubuntu-devel kernel: [ 478.386767] systemd-sysv-generator[9909]: SysV service '/etc/init.d/shadowsocks' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:05:57 ubuntu-devel kernel: [ 478.387281] systemd-sysv-generator[9909]: SysV service '/etc/init.d/virtualbox' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:05:57 ubuntu-devel kernel: [ 478.388931] systemd-sysv-generator[9909]: SysV service '/etc/init.d/sysfsutils' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:05:57 ubuntu-devel kernel: [ 478.388955] systemd-sysv-generator[9909]: SysV service '/etc/init.d/apport' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:05:57 ubuntu-devel kernel: [ 478.389412] systemd-sysv-generator[9909]: SysV service '/etc/init.d/freeradius' lacks a native systemd unit file.
[Touch-packages] [Bug 1915126] Re: autopkgtest times out (or fails before that) in hirsute on test infra, passes locally
@paelzer I haven't made changes related to the failure rate. I guess the infra got lighter load for some time. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1915126 Title: autopkgtest times out (or fails before that) in hirsute on test infra, passes locally Status in Auto Package Testing: Incomplete Status in systemd package in Ubuntu: Invalid Bug description: Hi, I've asked yesterday on IRC but so far got no answer. I think it is right to file a bug about the current state of systemd autopkgtest to unite the efforts in regard to it. I was looking at the systemd tests for a no-change rebuild that really had no reason to now make it fail. While checking I found that as of this month (first bad test on 1st of February) most of the systemd test runs on amd64 will not pass/fail but instead in most cases time out. I've seen various people retry the case as it shows the typical symptoms of a "not the fault of the package, let us retry this" case. But it seems that won't help as the test history is rather clear. * Watch this in monospace to make more sense of it * $ check-autopkgtest-stats.sh -c 50 -p systemd -r "hirsute" -a "amd64" Check last 50 test results for src:systemd on releases 'hirsute' on architectures 'amd64' Of the 50 last tests, we had these subtest failing per release/arch: hirsute amd64 tests-in-lxd (F 2% f 0% S 0% B 12% => P 52%/) .BTTTBTT.BTBTTTBBTTT..F.. hostnamed (F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT. build-login(F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT. unit-config(F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT. networkd-testpy(F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT. localed-locale (F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT. boot-and-services (F 4% f 0% S 0% B 12% => P 50%/) .BTTTBTT.BTBTTTBBTTT...F.F... timedated (F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT. boot-smoke (F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT. logind (F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT. storage(F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT. upstream (F 12% f 0% S 0% B 12% => P 42%/) .BTTTBTT.BTBTTTBBTTTF.F.F..FF..F. udev (F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT. systemd-fsckd (F 8% f 0% S 0% B 12% => P 46%/) FBTTTBTTFBTBTTTBBTTT.F..F root-unittests (F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT. localed-x11-keymap (F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT. We see that formerly we had the known to be somewhat flaky, but otherwise working test (time goes from right to left). So we had the usual suspects of tests like upstream/systemd-fsck that failed a few times, but also working runs in between. But since February 22/24 runs failed very bad. 6 (=B) of those cases are aborting mid execution autopkgtest [22:08:58]: ERROR: testbed failure: testbed auxverb failed with exit code 255 And 16 of them timed out : failure: Timed out on waiting for ssh connection Sadly the 2/24 that didn't hard fail by that where broken by the known flaky systemd-fsckd test. Something drives this test crazy that we have to find and resolve, at the current rate nothing depending on it is likely to migrate. To manage notifications about this bug go to: https://bugs.launchpad.net/auto-package-testing/+bug/1915126/+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 1915126] Re: autopkgtest times out (or fails before that) in hirsute on test infra, passes locally
@laney Thank you for looking into the problem. I will mark systemd-fsckd as flaky and look into the root cause later. It used to be flaky before as well. I have checked the last 10 failed runs from http://autopkgtest.ubuntu.com/packages/systemd/hirsute/amd64 , with the last one being from 2021-02-24 09:15:57 UTC: $ cat logs https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute/hirsute/amd64/s/systemd/20210224_091557_d5731@/log.gz https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute/hirsute/amd64/s/systemd/20210224_044536_8d27f@/log.gz https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute/hirsute/amd64/s/systemd/20210224_021229_4c845@/log.gz https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute/hirsute/amd64/s/systemd/20210224_013702_2056d@/log.gz https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute/hirsute/amd64/s/systemd/20210223_232058_6bbff@/log.gz https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute/hirsute/amd64/s/systemd/20210223_212809_c332e@/log.gz https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute/hirsute/amd64/s/systemd/20210223_145406_d6565@/log.gz https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute/hirsute/amd64/s/systemd/20210223_140557_825b0@/log.gz https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute/hirsute/amd64/s/systemd/20210223_130532_340ec@/log.gz https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute/hirsute/amd64/s/systemd/20210223_115952_4304b@/log.gz $ wget -q -i logs $ for i in log.gz*; do zcat $i | tail -n 40 | grep -A 16 "@@@ summary" | grep -v PASS ; done autopkgtest [09:15:42]: summary upstream FAIL timed out systemd-fsckdSKIP exit status 77 and marked as skippable autopkgtest [04:45:21]: summary boot-and-servicesFAIL non-zero exit status 1 systemd-fsckdSKIP exit status 77 and marked as skippable autopkgtest [02:00:12]: summary upstream FAIL timed out systemd-fsckdSKIP exit status 77 and marked as skippable autopkgtest [01:23:55]: summary boot-and-servicesFAIL non-zero exit status 1 upstream FAIL timed out systemd-fsckdSKIP exit status 77 and marked as skippable autopkgtest [23:20:34]: summary boot-and-servicesFAIL non-zero exit status 1 upstream FAIL non-zero exit status 1 systemd-fsckdSKIP exit status 77 and marked as skippable autopkgtest [21:19:41]: summary boot-and-servicesFAIL non-zero exit status 1 upstream FAIL timed out systemd-fsckdSKIP exit status 77 and marked as skippable autopkgtest [14:53:35]: summary boot-and-servicesFAIL non-zero exit status 1 upstream FAIL timed out systemd-fsckdSKIP exit status 77 and marked as skippable autopkgtest [13:53:19]: summary upstream FAIL timed out systemd-fsckdSKIP exit status 77 and marked as skippable autopkgtest [13:03:15]: summary upstream FAIL timed out systemd-fsckdSKIP exit status 77 and marked as skippable autopkgtest [11:59:24]: summary boot-and-servicesFAIL non-zero exit status 1 upstream FAIL non-zero exit status 1 systemd-fsckdSKIP exit status 77 and marked as skippable As you can see systemd-fsckd has been skipped in 10 out of 10 runs, but "upstream" test timed out in 7 out of the 10 runs. If you would like to help improving the failure rate caused by the infrastructure please run the systemd autopkgtests on bigger VMs. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1915126 Title: autopkgtest times out (or fails before that) in hirsute on test infra, passes locally Status in Auto Package Testing: Incomplete Status in systemd package in Ubuntu: Invalid Bug description: Hi, I've asked yesterday on IRC but so far got no answer. I think it is right to file a bug about the current state of systemd autopkgtest to unite the efforts in regard to it. I was looking at the systemd tests for a no-change rebuild that really had no reason to now make it fail. While checking I found that as of this month (first bad test on 1st of February) most of the systemd test runs on amd64 will not pass/fail but ins
[Touch-packages] [Bug 1915547] Re: sru unattended-upgrades ( 1.1ubuntu1.18.04.7~16.04.6 update to 1.1ubuntu1.18.04.7~16.04.7 ) Xenial
Fixed in 2.8.
** Changed in: unattended-upgrades (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1915547
Title:
sru unattended-upgrades ( 1.1ubuntu1.18.04.7~16.04.6 update to
1.1ubuntu1.18.04.7~16.04.7 ) Xenial
Status in unattended-upgrades package in Ubuntu:
Fix Released
Status in unattended-upgrades source package in Xenial:
Triaged
Bug description:
== Begin SRU Template ==
[Impact]
When upgrading from trusty to xenial, we are prompted about config changes on
50unattended-upgrades with the following diff:
--- /etc/apt/apt.conf.d/50unattended-upgrades root.root 0644 2017-05-08
19:21:39
+++ /etc/apt/apt.conf.d/50unattended-upgrades.ucftmp root.root 0644
2020-02-17 18:03:38
@@ -1,11 +1,13 @@
// Automatically upgrade packages from these (origin:archive) pairs
Unattended-Upgrade::Allowed-Origins {
+ "${distro_id}:${distro_codename}";
"${distro_id}:${distro_codename}-security";
// Extended Security Maintenance; doesn't necessarily exist for
// every release and this system may not have it installed, but if
// available, the policy for updates is such that unattended-upgrades
// should also install from here by default.
- "${distro_id}ESM:${distro_codename}";
+ "${distro_id}ESMApps:${distro_codename}-apps-security";
+ "${distro_id}ESM:${distro_codename}-infra-security";
// "${distro_id}:${distro_codename}-updates";
// "${distro_id}:${distro_codename}-proposed";
// "${distro_id}:${distro_codename}-backports";
The reason we are presented with this diff is that the xenial package
does not contain a md5sum history file that informs ucf about all the
supported configs for 50unattended-upgrades. To fix that upgrade
problem, we are prosing the following changes on the xenial package of
unattended-upgrades:
- Add 50unattended-upgrades.md5sum file into the xenial package
- Add md5sum of the current xenial 50unattende-upgrades file into the
md5sum history file
- Modify ucf command in postinst to be aware of the md5sum history file
See the changelog entry below for a full list of changes and bugs.
[Test Case]
We have performed a manual test with a modified version of the xenial package:
https://launchpad.net/~lamoura/+archive/ubuntu/unattended-upgrades-ppa
Using that package, we were able to verify that the config change
prompt no longer happens from trusty to xenial.
[Regression Potential]
Since we are modifying are features on unattended-upgrades, just adding a new
file to package, we don't believe there is any regression potential
[Discussion]
== End SRU Template ==
== Changelog ==
* data: add md5sum history file on the data folder
- This file contains md5sum of several supported 50unattended-upgrades
config files
* data: add xenial md5sum of 50unattented-upgrades into md5sum file
* debian/postint: make ucf command reference the md5sum history file
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1915547/+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 1916935] Re: Major changes in sorting method upgrade 18.04->18.04.5 due to base-files change
** Tags added: regression-update -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1916935 Title: Major changes in sorting method upgrade 18.04->18.04.5 due to base- files change Status in base-files package in Ubuntu: New Status in glibc package in Ubuntu: Invalid Status in postgresql-10 package in Ubuntu: Invalid Status in base-files source package in Bionic: New Bug description: I had an Ubuntu 18.04.0 with Postgres 9.6. Before Ubuntu upgrade following command result was: [code] vodka@ubuntu140:~$ ( echo "1-1"; echo "11" ) | LC_COLLATE=en_US.UTF-8 sort 1-1 11 [/code] But after upgrading Ubuntu 18.04 to latest release via apt upgrade (18.04.5) result of the command above totally changed: [code] vodka@ubuntu140:~$ ( echo "1-1"; echo "11" ) | LC_COLLATE=en_US.UTF-8 sort 11 1-1 [/code] Due to this our production Postgres database started work very slowly and we had a long downtime for REINDEX. Sorting method is very important for Postgres database: https://wiki.postgresql.org/wiki/Locale_data_changes Please, read "Testing collation" part. Is it normal behavior for Ubuntu? Why glibc totally changed within LTS release without 'major upgrade'? I did not expect this... ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libc-bin 2.27-3ubuntu1.4 ProcVersionSignature: Ubuntu 4.15.0-136.140-generic 4.15.18 Uname: Linux 4.15.0-136-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.23 Architecture: amd64 Date: Thu Feb 25 13:13:03 2021 Dependencies: gcc-8-base 8.4.0-1ubuntu1~18.04 libc6 2.27-3ubuntu1.4 libgcc1 1:8.4.0-1ubuntu1~18.04 InstallationDate: Installed on 2021-02-25 (0 days ago) InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: glibc UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1916935/+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 1916935] Re: Major changes in sorting method upgrade 18.04->18.04.5 due to base-files change
@paelzer Thank you for the triaging and the detailed explanation. Since this change slipped in too long ago I don't think it should be reverted. I think Postresql could check if there was a change in sorting compared to the which the indices were created with, but this installation does not uses Postgresql from the archive so that would just be an unrelated improvement. Maybe Postgres already does that. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1916935 Title: Major changes in sorting method upgrade 18.04->18.04.5 due to base- files change Status in base-files package in Ubuntu: New Status in glibc package in Ubuntu: Invalid Status in postgresql-10 package in Ubuntu: Invalid Status in base-files source package in Bionic: New Bug description: I had an Ubuntu 18.04.0 with Postgres 9.6. Before Ubuntu upgrade following command result was: [code] vodka@ubuntu140:~$ ( echo "1-1"; echo "11" ) | LC_COLLATE=en_US.UTF-8 sort 1-1 11 [/code] But after upgrading Ubuntu 18.04 to latest release via apt upgrade (18.04.5) result of the command above totally changed: [code] vodka@ubuntu140:~$ ( echo "1-1"; echo "11" ) | LC_COLLATE=en_US.UTF-8 sort 11 1-1 [/code] Due to this our production Postgres database started work very slowly and we had a long downtime for REINDEX. Sorting method is very important for Postgres database: https://wiki.postgresql.org/wiki/Locale_data_changes Please, read "Testing collation" part. Is it normal behavior for Ubuntu? Why glibc totally changed within LTS release without 'major upgrade'? I did not expect this... ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libc-bin 2.27-3ubuntu1.4 ProcVersionSignature: Ubuntu 4.15.0-136.140-generic 4.15.18 Uname: Linux 4.15.0-136-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.23 Architecture: amd64 Date: Thu Feb 25 13:13:03 2021 Dependencies: gcc-8-base 8.4.0-1ubuntu1~18.04 libc6 2.27-3ubuntu1.4 libgcc1 1:8.4.0-1ubuntu1~18.04 InstallationDate: Installed on 2021-02-25 (0 days ago) InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: glibc UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1916935/+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 1134036] Re: Failure when using ssh with a locale that is not configured on the server
** Description changed: [impact] The setup: 1) The user has LC_ALL set to a locale on their machine (or some other LC_* variable but it's usually LC_ALL). 2) This locale does not exist on an Ubuntu server. 3) The user sshes into the server. ssh (at least with the settings that are default on Debian and Ubuntu and Fedora) send the value of LC_ALL to the remote server, where the default settings on Ubuntu allow this to be set in the environment of the process it launches. Because we are now in a situation where LC_ALL is set to a value that is not valid for the system, various undesirable things happen, including ugly messages from cloud-init and perl complaining every time a perl process starts and the bug that the original description below describes. [test case] Configure the setup as described above. Ssh into the server and run "perl < /dev/null" and check for warnings. [regression potential] This adds a step to the startup of every login shell, which obviously is not entirely trivial. However, the new executable being invoked is very simple and even if it fails, the startup of the shell should not be inhibited. - [original description] - - If LC_ALL is not set (which seems to be the default on a few server installations I've done now), mid way through installing, you get this backtrace and then the installation just hangs. You can ctrl-c out of it but the package is left half configured. + If LC_ALL is not set (which seems to be the default on a few server + installations I've done now), mid way through installing, you get this + backtrace and then the installation just hangs. You can ctrl-c out of + it but the package is left half configured. Traceback (most recent call last): File "/usr/bin/django-admin", line 5, in management.execute_from_command_line() File "/usr/lib/python2.7/dist-packages/django/core/management/__init__.py", line 443, in execute_from_command_line utility.execute() File "/usr/lib/python2.7/dist-packages/django/core/management/__init__.py", line 382, in execute self.fetch_command(subcommand).run_from_argv(self.argv) File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", line 196, in run_from_argv self.execute(*args, **options.__dict__) File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", line 232, in execute output = self.handle(*args, **options) File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", line 371, in handle return self.handle_noargs(**options) File "/usr/lib/python2.7/dist-packages/south/management/commands/syncdb.py", line 90, in handle_noargs syncdb.Command().execute(**options) File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", line 232, in execute output = self.handle(*args, **options) File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", line 371, in handle return self.handle_noargs(**options) File "/usr/lib/python2.7/dist-packages/django/core/management/commands/syncdb.py", line 57, in handle_noargs cursor = connection.cursor() File "/usr/lib/python2.7/dist-packages/django/db/backends/__init__.py", line 308, in cursor cursor = util.CursorWrapper(self._cursor(), self) File "/usr/lib/python2.7/dist-packages/django/db/backends/postgresql_psycopg2/base.py", line 177, in _cursor self.connection = Database.connect(**conn_params) File "/usr/lib/python2.7/dist-packages/psycopg2/__init__.py", line 179, in connect connection_factory=connection_factory, async=async) psycopg2.OperationalError: FATAL: password authentication failed for user "maas" FATAL: password authentication failed for user "maas" Related bugs: * bug 969462: [postgres] fails to start after install if invalid locale is set + * LP: #1916935 Major changes in sorting method upgrade 18.04->18.04.5 due to base-files change -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1134036 Title: Failure when using ssh with a locale that is not configured on the server Status in base-files package in Ubuntu: Fix Released Status in maas package in Ubuntu: Invalid Status in base-files source package in Bionic: Fix Released Status in maas source package in Bionic: Invalid Bug description: [impact] The setup: 1) The user has LC_ALL set to a locale on their machine (or some other LC_* variable but it's usually LC_ALL). 2) This locale does not exist on an Ubuntu server. 3) The user sshes into the server. ssh (at least with the settings that are default on Debian and Ubuntu and Fedora) send the value of LC_ALL to the remote server, where the default settings on Ubuntu allow this to be set in the environment of the process it launches. Because we
[Touch-packages] [Bug 1916485] Re: test -x fails inside shell scripts in containers
** Also affects: runc (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/1916485 Title: test -x fails inside shell scripts in containers Status in glibc package in Ubuntu: Triaged Status in libseccomp package in Ubuntu: Fix Committed Status in runc package in Ubuntu: New Status in glibc source package in Hirsute: Triaged Status in libseccomp source package in Hirsute: Fix Committed Status in runc source package in Hirsute: New Bug description: glibc regression causes test -x to fail inside scripts inside docker/podman, dash and bash are broken, mksh and zsh are fine: root@0df2ce5d7a46:/# test -x /usr/bin/gpg || echo Fail root@0df2ce5d7a46:/# dash -c "test -x /usr/bin/gpg || echo Fail" Fail root@0df2ce5d7a46:/# bash -c "test -x /usr/bin/gpg || echo Fail" Fail root@0df2ce5d7a46:/# mksh -c "test -x /usr/bin/gpg || echo Fail" root@0df2ce5d7a46:/# zsh -c "test -x /usr/bin/gpg || echo Fail" root@0df2ce5d7a46:/# root@0df2ce5d7a46:/# zsh -c "[ -x /usr/bin/gpg ] || echo Fail" root@0df2ce5d7a46:/# mksh -c "[ -x /usr/bin/gpg ] || echo Fail" root@0df2ce5d7a46:/# dash -c "[ -x /usr/bin/gpg ] || echo Fail" Fail root@0df2ce5d7a46:/# bash -c "[ -x /usr/bin/gpg ] || echo Fail" Fail The -f flag works, as does /usr/bin/test: # bash -c "test -f /usr/bin/gpg || echo Fail" # bash -c "/usr/bin/test -x /usr/bin/gpg || echo Fail" # [Original bug report] root@84b750e443f8:/# lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 root@84b750e443f8:/# dpkg -l gnupg apt Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==-===--== ii apt2.1.20 amd64commandline package manager ii gnupg 2.2.20-1ubuntu2 all GNU privacy guard - a free PGP replacement Hi, for 3 days our CI pipelines to recreate Docker images fails for the Hirsute images. From comparison this seems to be caused by apt 2.1.20. The build fails with: 0E: gnupg, gnupg2 and unupg1 do not seem to be installed, but one of them is required for this operation The simple Dockerfile to reproduce the error - "docker build -t foo ." FROM amd64/ubuntu:hirsute MAINTAINER Florian Lohoff USER root RUN apt-get update \ && DEBIAN_FRONTEND=noninteractive apt-get -y install curl gnupg apt \ && curl https://syncthing.net/release-key.txt | apt-key add - Breaking it down it this seems to be an issue that there is new functionality in apt/apt-key e.g. security hardening that docker prohibits in its containers. Running this manually works only in an --privileged container. So adding keys in unpriviledged container or possibly kubernetes will not work anymore. Flo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1916485/+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 1916485] Re: test -x fails inside shell scripts in containers
Following all the discussions fixing the container runtimes seems to be the way out of this. For runc https://github.com/opencontainers/runc/pull/2750 should be SRUd to all releases. ** Also affects: docker.io (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/1916485 Title: test -x fails inside shell scripts in containers Status in docker.io package in Ubuntu: New Status in glibc package in Ubuntu: Triaged Status in libseccomp package in Ubuntu: Fix Committed Status in runc package in Ubuntu: New Status in docker.io source package in Hirsute: New Status in glibc source package in Hirsute: Triaged Status in libseccomp source package in Hirsute: Fix Committed Status in runc source package in Hirsute: New Bug description: glibc regression causes test -x to fail inside scripts inside docker/podman, dash and bash are broken, mksh and zsh are fine: root@0df2ce5d7a46:/# test -x /usr/bin/gpg || echo Fail root@0df2ce5d7a46:/# dash -c "test -x /usr/bin/gpg || echo Fail" Fail root@0df2ce5d7a46:/# bash -c "test -x /usr/bin/gpg || echo Fail" Fail root@0df2ce5d7a46:/# mksh -c "test -x /usr/bin/gpg || echo Fail" root@0df2ce5d7a46:/# zsh -c "test -x /usr/bin/gpg || echo Fail" root@0df2ce5d7a46:/# root@0df2ce5d7a46:/# zsh -c "[ -x /usr/bin/gpg ] || echo Fail" root@0df2ce5d7a46:/# mksh -c "[ -x /usr/bin/gpg ] || echo Fail" root@0df2ce5d7a46:/# dash -c "[ -x /usr/bin/gpg ] || echo Fail" Fail root@0df2ce5d7a46:/# bash -c "[ -x /usr/bin/gpg ] || echo Fail" Fail The -f flag works, as does /usr/bin/test: # bash -c "test -f /usr/bin/gpg || echo Fail" # bash -c "/usr/bin/test -x /usr/bin/gpg || echo Fail" # [Original bug report] root@84b750e443f8:/# lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 root@84b750e443f8:/# dpkg -l gnupg apt Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==-===--== ii apt2.1.20 amd64commandline package manager ii gnupg 2.2.20-1ubuntu2 all GNU privacy guard - a free PGP replacement Hi, for 3 days our CI pipelines to recreate Docker images fails for the Hirsute images. From comparison this seems to be caused by apt 2.1.20. The build fails with: 0E: gnupg, gnupg2 and unupg1 do not seem to be installed, but one of them is required for this operation The simple Dockerfile to reproduce the error - "docker build -t foo ." FROM amd64/ubuntu:hirsute MAINTAINER Florian Lohoff USER root RUN apt-get update \ && DEBIAN_FRONTEND=noninteractive apt-get -y install curl gnupg apt \ && curl https://syncthing.net/release-key.txt | apt-key add - Breaking it down it this seems to be an issue that there is new functionality in apt/apt-key e.g. security hardening that docker prohibits in its containers. Running this manually works only in an --privileged container. So adding keys in unpriviledged container or possibly kubernetes will not work anymore. Flo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1916485/+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 1913763] Re: hyperv: unable to distinguish PTP devices
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Balint Reczey (rbalint)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1913763
Title:
hyperv: unable to distinguish PTP devices
Status in systemd package in Ubuntu:
New
Bug description:
Hyperv provides a PTP device. On system with multiple PTP devices,
services like Chrony don't have a way to know which one is which.
We would like to have a udev rule to create a symlink to the hyperv
clock. This way, services could be configured to always use this clock
no matter if it is ptp0, ptp1, etc..
For example:
```
SUBSYSTEM=="ptp", ATTR{clock_name}=="hyperv", SYMLINK += "ptp_hyperv"
```
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1913763/+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 1913763] Re: hyperv: unable to distinguish PTP devices
** Changed in: systemd (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1913763
Title:
hyperv: unable to distinguish PTP devices
Status in systemd package in Ubuntu:
Fix Committed
Bug description:
Hyperv provides a PTP device. On system with multiple PTP devices,
services like Chrony don't have a way to know which one is which.
We would like to have a udev rule to create a symlink to the hyperv
clock. This way, services could be configured to always use this clock
no matter if it is ptp0, ptp1, etc..
For example:
```
SUBSYSTEM=="ptp", ATTR{clock_name}=="hyperv", SYMLINK += "ptp_hyperv"
```
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1913763/+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 1914062] Re: NetworkManager-wait-online.service in 1.28.0-2ubuntu1 fails to start in LXC
** Changed in: systemd (Ubuntu) Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1914062 Title: NetworkManager-wait-online.service in 1.28.0-2ubuntu1 fails to start in LXC Status in lxd package in Ubuntu: Won't Fix Status in network-manager package in Ubuntu: Fix Released Status in systemd package in Ubuntu: In Progress Bug description: This regresses systemd's autopkgtest because it expects the system in the container to reach running state, but the system ends up in degraded state due to the service failing. https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute/hirsute/amd64/s/systemd/20210112_185712_ff570@/log.gz ... == FAIL: test_no_failed (__main__.ServicesTest) No failed units -- Traceback (most recent call last): File "/tmp/autopkgtest.fFC3Lw/build.xLc/real-tree/debian/tests/boot-and-services", line 68, in test_no_failed self.assertEqual(failed, []) AssertionError: Lists differ: ['● NetworkManager-wait-online.service loa[42 chars]ine'] != [] First list contains 1 additional elements. First extra element 0: '● NetworkManager-wait-online.service loaded failed failed Network Manager Wait Online' + [] - ['● NetworkManager-wait-online.service loaded failed failed Network Manager ' - 'Wait Online'] -- Ran 23 tests in 4.435s ... Reproducible locally by installing n-m from -proposed, then restarting the system in the LXC container. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1914062/+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 1914062] Re: NetworkManager-wait-online.service in 1.28.0-2ubuntu1 fails to start in LXC
@stgraber Thank you. I'm including the originally proposed patch in the next systemd upload and will switch to v248 when it is out to include the full fix. Most likely final v248 will be out in a few weeks. ** Changed in: systemd (Ubuntu) Assignee: (unassigned) => Balint Reczey (rbalint) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1914062 Title: NetworkManager-wait-online.service in 1.28.0-2ubuntu1 fails to start in LXC Status in lxd package in Ubuntu: Won't Fix Status in network-manager package in Ubuntu: Fix Released Status in systemd package in Ubuntu: In Progress Bug description: This regresses systemd's autopkgtest because it expects the system in the container to reach running state, but the system ends up in degraded state due to the service failing. https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute/hirsute/amd64/s/systemd/20210112_185712_ff570@/log.gz ... == FAIL: test_no_failed (__main__.ServicesTest) No failed units -- Traceback (most recent call last): File "/tmp/autopkgtest.fFC3Lw/build.xLc/real-tree/debian/tests/boot-and-services", line 68, in test_no_failed self.assertEqual(failed, []) AssertionError: Lists differ: ['● NetworkManager-wait-online.service loa[42 chars]ine'] != [] First list contains 1 additional elements. First extra element 0: '● NetworkManager-wait-online.service loaded failed failed Network Manager Wait Online' + [] - ['● NetworkManager-wait-online.service loaded failed failed Network Manager ' - 'Wait Online'] -- Ran 23 tests in 4.435s ... Reproducible locally by installing n-m from -proposed, then restarting the system in the LXC container. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1914062/+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 1917677] Re: ubuntu: ucf tracking of valid known md5sums should be limited to only those md5sums that affect a given distro release
** Changed in: unattended-upgrades (Ubuntu Bionic) Importance: Undecided => Low ** Changed in: unattended-upgrades (Ubuntu Hirsute) Importance: Undecided => Low ** Changed in: unattended-upgrades (Ubuntu Groovy) Importance: Undecided => Low ** Changed in: unattended-upgrades (Ubuntu Focal) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1917677 Title: ubuntu: ucf tracking of valid known md5sums should be limited to only those md5sums that affect a given distro release Status in unattended-upgrades package in Ubuntu: New Status in unattended-upgrades source package in Bionic: New Status in unattended-upgrades source package in Focal: New Status in unattended-upgrades source package in Groovy: New Status in unattended-upgrades source package in Hirsute: New Bug description: Currently the project tracks all valid md5sums of permutations of 50unattended-upgrades.conf in a single md5sum file that contains every md5sum of every historic version of all unique distros: 50unattended-upgrades.Debian 50unattended-upgrades.Devuan 50unattended-upgrades.Raspbian 50unattended-upgrades.Ubuntu Ultimately ucf for a given packaging release should only track the applicable md5sums which are expected to be seen on that particular distribution and release. For example: On Ubuntu Bionic: valid md5sums should be limited to the md5sum of the most recent Ubuntu Xenial 50unattended-upgrades.conf and the md5sums of previous Ubuntu Bionic releases to allow Xenial->Bionic and Bionic->Bionic upgrades without prompt. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1917677/+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 1917677] Re: ubuntu: ucf tracking of valid known md5sums should be limited to only those md5sums that affect a given distro release
It is highly unlikely that the configuration file on one distro is replaced with one that was shipped on a different one. It may be a bit more likely that a config file is overwritten by a variant from a previous release, but I think this is still unlikely and I believe trimming the md5sum list is not a general practice for UCF managed configuration files. As an example openssh-server ships the historical list, too: $ cat /usr/share/openssh/sshd_config.md5sum # Historical md5sums of the default /etc/ssh/sshd_config up to and including # 1:7.3p1-5. 0d06fc337cee10609d4833dc88df740f 10dc68360f6658910a98a051273de22c 11f9e107b4d13bbcabe7f8e8da734371 16c827adcff44efaca05ec5eea6383d7 2eeff28468576c3f2e538314e177687b 386c8b9079625b78f6d624ae506958ae 38fc7b31b3e3078848f0eec457d3e050 395c5e13801f9b4f17c2cb54aa634fbd ... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1917677 Title: ubuntu: ucf tracking of valid known md5sums should be limited to only those md5sums that affect a given distro release Status in unattended-upgrades package in Ubuntu: New Status in unattended-upgrades source package in Bionic: New Status in unattended-upgrades source package in Focal: New Status in unattended-upgrades source package in Groovy: New Status in unattended-upgrades source package in Hirsute: New Bug description: Currently the project tracks all valid md5sums of permutations of 50unattended-upgrades.conf in a single md5sum file that contains every md5sum of every historic version of all unique distros: 50unattended-upgrades.Debian 50unattended-upgrades.Devuan 50unattended-upgrades.Raspbian 50unattended-upgrades.Ubuntu Ultimately ucf for a given packaging release should only track the applicable md5sums which are expected to be seen on that particular distribution and release. For example: On Ubuntu Bionic: valid md5sums should be limited to the md5sum of the most recent Ubuntu Xenial 50unattended-upgrades.conf and the md5sums of previous Ubuntu Bionic releases to allow Xenial->Bionic and Bionic->Bionic upgrades without prompt. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1917677/+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 1916485] Re: test -x fails inside shell scripts in containers
** Also affects: glibc (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: libseccomp (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: docker.io (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: runc (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: glibc (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: libseccomp (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: docker.io (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: runc (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: glibc (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: libseccomp (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: docker.io (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: runc (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: glibc (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: libseccomp (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: docker.io (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: runc (Ubuntu Focal) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/1916485 Title: test -x fails inside shell scripts in containers Status in docker.io package in Ubuntu: New Status in glibc package in Ubuntu: Triaged Status in libseccomp package in Ubuntu: Fix Committed Status in runc package in Ubuntu: New Status in docker.io source package in Xenial: New Status in glibc source package in Xenial: New Status in libseccomp source package in Xenial: New Status in runc source package in Xenial: New Status in docker.io source package in Bionic: New Status in glibc source package in Bionic: New Status in libseccomp source package in Bionic: New Status in runc source package in Bionic: New Status in docker.io source package in Focal: New Status in glibc source package in Focal: New Status in libseccomp source package in Focal: New Status in runc source package in Focal: New Status in docker.io source package in Groovy: New Status in glibc source package in Groovy: New Status in libseccomp source package in Groovy: New Status in runc source package in Groovy: New Status in docker.io source package in Hirsute: New Status in glibc source package in Hirsute: Triaged Status in libseccomp source package in Hirsute: Fix Committed Status in runc source package in Hirsute: New Bug description: glibc regression causes test -x to fail inside scripts inside docker/podman, dash and bash are broken, mksh and zsh are fine: root@0df2ce5d7a46:/# test -x /usr/bin/gpg || echo Fail root@0df2ce5d7a46:/# dash -c "test -x /usr/bin/gpg || echo Fail" Fail root@0df2ce5d7a46:/# bash -c "test -x /usr/bin/gpg || echo Fail" Fail root@0df2ce5d7a46:/# mksh -c "test -x /usr/bin/gpg || echo Fail" root@0df2ce5d7a46:/# zsh -c "test -x /usr/bin/gpg || echo Fail" root@0df2ce5d7a46:/# root@0df2ce5d7a46:/# zsh -c "[ -x /usr/bin/gpg ] || echo Fail" root@0df2ce5d7a46:/# mksh -c "[ -x /usr/bin/gpg ] || echo Fail" root@0df2ce5d7a46:/# dash -c "[ -x /usr/bin/gpg ] || echo Fail" Fail root@0df2ce5d7a46:/# bash -c "[ -x /usr/bin/gpg ] || echo Fail" Fail The -f flag works, as does /usr/bin/test: # bash -c "test -f /usr/bin/gpg || echo Fail" # bash -c "/usr/bin/test -x /usr/bin/gpg || echo Fail" # [Original bug report] root@84b750e443f8:/# lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 root@84b750e443f8:/# dpkg -l gnupg apt Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==-===--== ii apt2.1.20 amd64commandline package manager ii gnupg 2.2.20-1ubuntu2 all GNU privacy guard - a free PGP replacement Hi, for 3 days our CI pipelines to recreate Docker images fails for the Hirsute images. From comparison this seems to be caused by apt 2.1.20. The build fails with: 0E: gnupg, gnupg2 and unupg1 do not seem to be installed, but one of them is required for this operation The simple Dockerfile to reproduce the error - "docker build -t foo ." FROM amd64/ubuntu:hirsute MAINTAINER Florian Lohoff USER root RUN apt-get update \ && DEBIAN_FRONTEND=noninteractive apt-get -y install curl gnupg apt \ && curl http
[Touch-packages] [Bug 1916485] Re: test -x fails inside shell scripts in containers
** Changed in: docker.io (Ubuntu Hirsute) Importance: Undecided => Critical ** Changed in: glibc (Ubuntu Hirsute) Status: Triaged => Opinion -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/1916485 Title: test -x fails inside shell scripts in containers Status in docker.io package in Ubuntu: New Status in glibc package in Ubuntu: Opinion Status in libseccomp package in Ubuntu: Fix Committed Status in runc package in Ubuntu: New Status in docker.io source package in Xenial: New Status in glibc source package in Xenial: New Status in libseccomp source package in Xenial: New Status in runc source package in Xenial: New Status in docker.io source package in Bionic: New Status in glibc source package in Bionic: New Status in libseccomp source package in Bionic: New Status in runc source package in Bionic: New Status in docker.io source package in Focal: New Status in glibc source package in Focal: New Status in libseccomp source package in Focal: New Status in runc source package in Focal: New Status in docker.io source package in Groovy: New Status in glibc source package in Groovy: New Status in libseccomp source package in Groovy: New Status in runc source package in Groovy: New Status in docker.io source package in Hirsute: New Status in glibc source package in Hirsute: Opinion Status in libseccomp source package in Hirsute: Fix Committed Status in runc source package in Hirsute: New Bug description: glibc regression causes test -x to fail inside scripts inside docker/podman, dash and bash are broken, mksh and zsh are fine: root@0df2ce5d7a46:/# test -x /usr/bin/gpg || echo Fail root@0df2ce5d7a46:/# dash -c "test -x /usr/bin/gpg || echo Fail" Fail root@0df2ce5d7a46:/# bash -c "test -x /usr/bin/gpg || echo Fail" Fail root@0df2ce5d7a46:/# mksh -c "test -x /usr/bin/gpg || echo Fail" root@0df2ce5d7a46:/# zsh -c "test -x /usr/bin/gpg || echo Fail" root@0df2ce5d7a46:/# root@0df2ce5d7a46:/# zsh -c "[ -x /usr/bin/gpg ] || echo Fail" root@0df2ce5d7a46:/# mksh -c "[ -x /usr/bin/gpg ] || echo Fail" root@0df2ce5d7a46:/# dash -c "[ -x /usr/bin/gpg ] || echo Fail" Fail root@0df2ce5d7a46:/# bash -c "[ -x /usr/bin/gpg ] || echo Fail" Fail The -f flag works, as does /usr/bin/test: # bash -c "test -f /usr/bin/gpg || echo Fail" # bash -c "/usr/bin/test -x /usr/bin/gpg || echo Fail" # [Original bug report] root@84b750e443f8:/# lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 root@84b750e443f8:/# dpkg -l gnupg apt Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==-===--== ii apt2.1.20 amd64commandline package manager ii gnupg 2.2.20-1ubuntu2 all GNU privacy guard - a free PGP replacement Hi, for 3 days our CI pipelines to recreate Docker images fails for the Hirsute images. From comparison this seems to be caused by apt 2.1.20. The build fails with: 0E: gnupg, gnupg2 and unupg1 do not seem to be installed, but one of them is required for this operation The simple Dockerfile to reproduce the error - "docker build -t foo ." FROM amd64/ubuntu:hirsute MAINTAINER Florian Lohoff USER root RUN apt-get update \ && DEBIAN_FRONTEND=noninteractive apt-get -y install curl gnupg apt \ && curl https://syncthing.net/release-key.txt | apt-key add - Breaking it down it this seems to be an issue that there is new functionality in apt/apt-key e.g. security hardening that docker prohibits in its containers. Running this manually works only in an --privileged container. So adding keys in unpriviledged container or possibly kubernetes will not work anymore. Flo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1916485/+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 1916705] Re: glib2.0 >=2.67.3 breaks include from an extern C context
** Also affects: wireshark (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1916705
Title:
glib2.0 >=2.67.3 breaks include from an extern C context
Status in glib2.0 package in Ubuntu:
Fix Released
Status in open-vm-tools package in Ubuntu:
New
Status in qemu package in Ubuntu:
Fix Released
Status in ukui-control-center package in Ubuntu:
Triaged
Status in wireshark package in Ubuntu:
New
Bug description:
qemu now breaks in Hirsute (it didn't 23h ago)
Broken:
https://launchpadlibrarian.net/524654684/buildlog_ubuntu-hirsute-amd64.qemu_1%3A5.2+dfsg-6ubuntu1_BUILDING.txt.gz
Good before:
https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4471/+packages
Error:
../../disas/arm-a64.cc
In file included from /usr/include/glib-2.0/glib/gmacros.h:241,
from
/usr/lib/x86_64-linux-gnu/glib-2.0/include/glibconfig.h:9,
from /usr/include/glib-2.0/glib/gtypes.h:32,
from /usr/include/glib-2.0/glib/galloca.h:32,
from /usr/include/glib-2.0/glib.h:30,
from /<>/qemu-5.2+dfsg/include/glib-compat.h:32,
from /<>/qemu-5.2+dfsg/include/qemu/osdep.h:126,
from ../../disas/arm-a64.cc:21:
/usr/include/c++/10/type_traits:56:3: error: template with C linkage
56 | template
| ^~~~
../../disas/arm-a64.cc:20:1: note: ‘extern "C"’ linkage started here
20 | extern "C" {
| ^~
Also in disas/nanomips.cpp, ...
And indeed disas/arm-a64.cc has:
20 extern "C" {
21 #include "qemu/osdep.h"
22 #include "disas/dis-asm.h"
23 }
Through the chain of headers as reported above this gets to the templates
in /usr/include/c++/10/type_traits which fails due to that.
So C++ constructs within a C scope which is this bug.
Upstream qemu has not recently changed yet for this.
The code is the same since 2016 via commit e78490c44: "disas/arm-a64.cc:
Include osdep.h first" by Peter Maydell.
But what was different before to break it now?
To find that I was comparing Hirsute vs Hirsute-proposed ...
It is indeed failing in -proposed but working in hirsute-release.
10.2.1-20ubuntu1 : bad
repro in broken build:
$ cd /root/qemu-5.2+dfsg/b/qemu
$ c++ -Ilibcommon.fa.p -I. -I../.. -Iqapi -Itrace -Iui -Iui/shader
-I/usr/include/pixman-1 -I/usr/include/virgl -I/usr/include/libpng16
-I/usr/include/spice-server -I/usr/include/spice-1 -I/usr/include/libusb-1.0
-I/usr/include/libmount -I/usr/include/blkid -I/usr/include/glib-2.0
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/gio-unix-2.0
-I/usr/include/cacard -I/usr/include/nss -I/usr/include/nspr
-I/usr/include/PCSC -I/usr/include/slirp -fdiagnostics-color=auto -pipe -Wall
-Winvalid-pch -Wnon-virtual-dtor -std=gnu++11 -O2 -g -D__STDC_LIMIT_MACROS
-D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -U_FORTIFY_SOURCE -m64 -mcx16
-D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -Wundef
-Wwrite-strings -fno-strict-aliasing -fno-common -fwrapv -g -O2
-ffile-prefix-map=/root/qemu-5.2+dfsg=. -fstack-protector-strong -Wformat
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wtype-limits
-Wformat-security -Wformat-y2k -Winit-self -Wignored-qualifiers -Wempty-body
-Wendif-labels -Wexpansion-to-defined -Wno-missing-include-dirs
-Wno-shift-negative-value -Wno-psabi -fstack-protector-strong -isystem
/root/qemu-5.2+dfsg/linux-headers -isystem linux-headers -iquote
/root/qemu-5.2+dfsg/tcg/i386 -iquote . -iquote /root/qemu-5.2+dfsg -iquote
/root/qemu-5.2+dfsg/accel/tcg -iquote /root/qemu-5.2+dfsg/include -iquote
/root/qemu-5.2+dfsg/disas/libvixl -pthread -fPIE -DSTRUCT_IOVEC_DEFINED
-D_DEFAULT_SOURCE -D_XOPEN_SOURCE=600 -DNCURSES_WIDECHAR -MD -MQ
libcommon.fa.p/disas_nanomips.cpp.o -MF libcommon.fa.p/disas_nanomips.cpp.o.d
-o libcommon.fa.p/disas_nanomips.cpp.o -c ../../disas/nanomips.cpp
With that I have a test env...
Doko asked me to test
https://launchpad.net/ubuntu/+source/gcc-10/10.2.1-19ubuntu1/+build/20995220/+files/g++-10_10.2.1-19ubuntu1_amd64.deb
That fails as well, but also good as well as bad case have 10.10.2.1-20ubuntu1
It must be something else.
The difference were ~340 packages I was upgrading them to spot what broke it.
I eventually found glib 2.66 -> 2.67 to break it.
libglib2.0-0/hirsute-proposed 2.67.4-1 amd64 [upgradable from: 2.66.4-1]
libglib2.0-bin/hirsute-proposed 2.67.4-1 amd64 [upgradable from: 2.66.4-1]
libglib2.0-data/hirsute-proposed 2.67.4-1 all [upgradable from: 2.66.4-1]
libglib2.0-dev-bin/hirsute-proposed 2.67.4-1 amd64 [upgradable from: 2.66.4-1]
libglib2.0-dev/hirsute-proposed 2.67.4-1 amd64 [upgradable from: 2.66.4-1]
Old:
/*
* We can only use __typeof__ on GCC >= 4.8, and not when compiling
[Touch-packages] [Bug 1917298] Re: dbus-daemon not started after reboot
** Also affects: dbus (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Focal) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1917298 Title: dbus-daemon not started after reboot Status in dbus package in Ubuntu: New Status in systemd package in Ubuntu: New Status in dbus source package in Focal: New Status in systemd source package in Focal: New Bug description: In the past weeks we experienced few systems coming up without started dbus-daemon after reboots due to updates. The first occurrence happens on January 21th 2021, since this time we were experiencing 0 up to 2 machines with this issue on each reboot cycle affecting all (approx 20) Ubuntu 20.4 (Focal Fossa) LTS machines. On January 21th the machines were rebooted due to a kernel update. On January 19th there were updates for systemd (systemd:amd64 from 245.4-4ubuntu3.3 undated to 245.4-4ubuntu3.4) installed. The Symptoms seem to be: ``` root@es1:~# systemctl status dbus ● dbus.service - D-Bus System Message Bus Loaded: loaded (/lib/systemd/system/dbus.service; static; vendor preset: enabled) Active: inactive (dead) TriggeredBy: ● dbus.socket Docs: man:dbus-daemon(1) ``` There is no `dbus-daemon` process running any more after reboot. The messages in /var/log/syslog: ``` Feb 24 09:21:52 runner1 kernel: [ 11.005391] systemd[1]: sockets.target: Found ordering cycle on dbus.socket/start [...] Feb 24 09:21:52 runner1 kernel: [ 11.012386] systemd[1]: sockets.target: Job dbus.socket/start deleted to break ordering cycle starting with sockets.target/start ``` Jounalctl output ends with the dbus-Shutdown before reboot, and it is not updated any more. When rebooting the affected machine again, this does'nt occur again, and the dbus-daemon is started and working again. We experienced this on 4 rather different machines on 6 reboot cycles across all Ubuntu 20.4 (Focal Fossa) LTS machines till now. We are not experiencing this on other LTS releases than 20.4. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1917298/+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 1916485] Re: test -x fails inside shell scripts in containers
Running "test -x ..." also fails in systemd-nspawn for systemd < 247, I think only the following patch needs to be SRU-d to earlier systemd versions: https://github.com/systemd/systemd/commit/bcf08acbffdee0d6360d3c31d268e73d0623e5dc ** Also affects: systemd (Ubuntu) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu Hirsute) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1916485 Title: test -x fails inside shell scripts in containers Status in docker.io package in Ubuntu: New Status in glibc package in Ubuntu: Opinion Status in libseccomp package in Ubuntu: Fix Committed Status in runc package in Ubuntu: New Status in systemd package in Ubuntu: Fix Released Status in docker.io source package in Xenial: New Status in glibc source package in Xenial: New Status in libseccomp source package in Xenial: New Status in runc source package in Xenial: New Status in systemd source package in Xenial: New Status in docker.io source package in Bionic: New Status in glibc source package in Bionic: New Status in libseccomp source package in Bionic: New Status in runc source package in Bionic: New Status in systemd source package in Bionic: New Status in docker.io source package in Focal: New Status in glibc source package in Focal: New Status in libseccomp source package in Focal: New Status in runc source package in Focal: New Status in systemd source package in Focal: New Status in docker.io source package in Groovy: New Status in glibc source package in Groovy: New Status in libseccomp source package in Groovy: New Status in runc source package in Groovy: New Status in systemd source package in Groovy: New Status in docker.io source package in Hirsute: New Status in glibc source package in Hirsute: Opinion Status in libseccomp source package in Hirsute: Fix Committed Status in runc source package in Hirsute: New Status in systemd source package in Hirsute: Fix Released Bug description: glibc regression causes test -x to fail inside scripts inside docker/podman, dash and bash are broken, mksh and zsh are fine: root@0df2ce5d7a46:/# test -x /usr/bin/gpg || echo Fail root@0df2ce5d7a46:/# dash -c "test -x /usr/bin/gpg || echo Fail" Fail root@0df2ce5d7a46:/# bash -c "test -x /usr/bin/gpg || echo Fail" Fail root@0df2ce5d7a46:/# mksh -c "test -x /usr/bin/gpg || echo Fail" root@0df2ce5d7a46:/# zsh -c "test -x /usr/bin/gpg || echo Fail" root@0df2ce5d7a46:/# root@0df2ce5d7a46:/# zsh -c "[ -x /usr/bin/gpg ] || echo Fail" root@0df2ce5d7a46:/# mksh -c "[ -x /usr/bin/gpg ] || echo Fail" root@0df2ce5d7a46:/# dash -c "[ -x /usr/bin/gpg ] || echo Fail" Fail root@0df2ce5d7a46:/# bash -c "[ -x /usr/bin/gpg ] || echo Fail" Fail The -f flag works, as does /usr/bin/test: # bash -c "test -f /usr/bin/gpg || echo Fail" # bash -c "/usr/bin/test -x /usr/bin/gpg || echo Fail" # [Original bug report] root@84b750e443f8:/# lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 root@84b750e443f8:/# dpkg -l gnupg apt Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==-===--== ii apt2.1.20 amd64commandline package manager ii gnupg 2.2.20-1ubuntu2 all GNU privacy guard - a free PGP replacement Hi, for 3 days our CI pipelines to recreate Docker images fails for the Hirsute images. From comparison this seems to be caused by apt 2.1.20. The build fails with: 0E: gnupg, gnupg2 and unupg1 do not seem to be installed, but one of them is required for this operation The simple Dockerfile to reproduce the error - "docker build -t foo ." FROM amd64/ubuntu:hirsute MAINTAINER Florian Lohoff USER root RUN apt-get update \ && DEBIAN_FRONTEND=noninteractive apt-get -y install curl gnupg apt \ && curl https://syncthing.net/release-key.txt | apt-key add - Breaking it down it this seems to be an issue that there is new functionality in apt/apt-key e.g. security hardening that docker prohibits in its containers. Running this manually works only in an --privileged container. So adding keys in unpriviledged container or possibly kubernetes will not work anymore. Flo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1916485/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More he
[Touch-packages] [Bug 1916485] Re: test -x fails inside shell scripts in containers
** Changed in: glibc (Ubuntu Xenial) Status: New => Invalid ** Changed in: glibc (Ubuntu Bionic) Status: New => Invalid ** Changed in: glibc (Ubuntu Focal) Status: New => Invalid ** Changed in: glibc (Ubuntu Groovy) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1916485 Title: test -x fails inside shell scripts in containers Status in docker.io package in Ubuntu: New Status in glibc package in Ubuntu: Opinion Status in libseccomp package in Ubuntu: Fix Committed Status in runc package in Ubuntu: New Status in systemd package in Ubuntu: Fix Released Status in docker.io source package in Xenial: New Status in glibc source package in Xenial: Invalid Status in libseccomp source package in Xenial: New Status in runc source package in Xenial: New Status in systemd source package in Xenial: New Status in docker.io source package in Bionic: New Status in glibc source package in Bionic: Invalid Status in libseccomp source package in Bionic: New Status in runc source package in Bionic: New Status in systemd source package in Bionic: New Status in docker.io source package in Focal: New Status in glibc source package in Focal: Invalid Status in libseccomp source package in Focal: New Status in runc source package in Focal: New Status in systemd source package in Focal: New Status in docker.io source package in Groovy: New Status in glibc source package in Groovy: Invalid Status in libseccomp source package in Groovy: New Status in runc source package in Groovy: New Status in systemd source package in Groovy: Fix Released Status in docker.io source package in Hirsute: New Status in glibc source package in Hirsute: Opinion Status in libseccomp source package in Hirsute: Fix Committed Status in runc source package in Hirsute: New Status in systemd source package in Hirsute: Fix Released Bug description: (SRU template for systemd) [impact] bash (and some other shells) builtin test command -x operation fails [test case] on any affected host system, start nspawn container, e.g.: $ sudo apt install systemd-container $ wget https://cloud-images.ubuntu.com/hirsute/current/hirsute-server-cloudimg-amd64-root.tar.xz $ mkdir h $ cd h $ tar xvf ../hirsute-server-cloudimg-amd64-root.tar.xz $ sudo systemd-nspawn Then from a bash shell, verify if test -x works: root@h:~# ls -l /usr/bin/gpg -rwxr-xr-x 1 1000 1000 1083472 Jan 16 09:53 /usr/bin/gpg root@h:~# test -x /usr/bin/gpg || echo "fail" fail [regression potential] any regression would likely occur during a syscall, most likely faccessat2(), or during other syscalls. [scope] this is needed for b/f this is fixed upstream by commit bcf08acbffdee0d6360d3c31d268e73d0623e5dc which is in 247 and later, so this is fixed in h this was pulled into Debian at version 246.2 in commit e80c5e5371ab77792bae94e0f8c5e85a4237e6eb, so this is fixed in g in x, the entire systemd seccomp code is completely different and the patch doesn't apply, nor does it appear to be needed, as the problem doesn't reproduce in a h container under x. [other info] this needs fixing in libseccomp as well [original description] glibc regression causes test -x to fail inside scripts inside docker/podman, dash and bash are broken, mksh and zsh are fine: root@0df2ce5d7a46:/# test -x /usr/bin/gpg || echo Fail root@0df2ce5d7a46:/# dash -c "test -x /usr/bin/gpg || echo Fail" Fail root@0df2ce5d7a46:/# bash -c "test -x /usr/bin/gpg || echo Fail" Fail root@0df2ce5d7a46:/# mksh -c "test -x /usr/bin/gpg || echo Fail" root@0df2ce5d7a46:/# zsh -c "test -x /usr/bin/gpg || echo Fail" root@0df2ce5d7a46:/# root@0df2ce5d7a46:/# zsh -c "[ -x /usr/bin/gpg ] || echo Fail" root@0df2ce5d7a46:/# mksh -c "[ -x /usr/bin/gpg ] || echo Fail" root@0df2ce5d7a46:/# dash -c "[ -x /usr/bin/gpg ] || echo Fail" Fail root@0df2ce5d7a46:/# bash -c "[ -x /usr/bin/gpg ] || echo Fail" Fail The -f flag works, as does /usr/bin/test: # bash -c "test -f /usr/bin/gpg || echo Fail" # bash -c "/usr/bin/test -x /usr/bin/gpg || echo Fail" # [Original bug report] root@84b750e443f8:/# lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 root@84b750e443f8:/# dpkg -l gnupg apt Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==-===--== ii apt2.1.20 amd64commandline package manager ii gnupg 2.2.20-1ubuntu2 all GNU privacy guard - a
[Touch-packages] [Bug 1806076] Re: unattended-upgrade --help raises UnicodeEncodeError when stdout encoding is ascii
** Changed in: unattended-upgrades (Ubuntu Xenial) Status: New => Won't Fix ** Changed in: unattended-upgrades (Ubuntu Bionic) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1806076 Title: unattended-upgrade --help raises UnicodeEncodeError when stdout encoding is ascii Status in apt package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Won't Fix Status in apt source package in Xenial: New Status in unattended-upgrades source package in Xenial: Won't Fix Status in apt source package in Bionic: Triaged Status in unattended-upgrades source package in Bionic: Won't Fix Bug description: [Test Case] rbalint@yogi:~$ lxc launch ubuntu:18.04 bb-lp-1806076 Creating bb-lp-1806076 Starting bb-lp-1806076 rbalint@yogi:~$ lxc shell bb-lp-1806076 mesg: ttyname failed: No such device root@bb-lp-1806076:~# apt install -yqq language-pack-ru-base The following package was automatically installed and is no longer required: libfreetype6 Use 'apt autoremove' to remove it. The following additional packages will be installed: language-pack-ru The following NEW packages will be installed: language-pack-ru language-pack-ru-base 0 upgraded, 2 newly installed, 0 to remove and 7 not upgraded. Need to get 2310 kB of archives. After this operation, 11.8 MB of additional disk space will be used. Selecting previously unselected package language-pack-ru-base. (Reading database ... 28536 files and directories currently installed.) Preparing to unpack .../language-pack-ru-base_1%3a18.04+20180712_all.deb ... Unpacking language-pack-ru-base (1:18.04+20180712) ... Selecting previously unselected package language-pack-ru. Preparing to unpack .../language-pack-ru_1%3a18.04+20180712_all.deb ... Unpacking language-pack-ru (1:18.04+20180712) ... Setting up language-pack-ru (1:18.04+20180712) ... Setting up language-pack-ru-base (1:18.04+20180712) ... Generating locales (this might take a while)... ru_RU.UTF-8... done ru_UA.UTF-8... done Generation complete. root@bb-lp-1806076:~# env LANG=ru_RU unattended-upgrade --help | cat Traceback (most recent call last): File "/usr/bin/unattended-upgrade", line 1983, in (options, args) = parser.parse_args() # type: ignore File "/usr/lib/python3.6/optparse.py", line 1387, in parse_args stop = self._process_args(largs, rargs, values) File "/usr/lib/python3.6/optparse.py", line 1427, in _process_args self._process_long_opt(rargs, values) File "/usr/lib/python3.6/optparse.py", line 1501, in _process_long_opt option.process(opt, value, values, self) File "/usr/lib/python3.6/optparse.py", line 785, in process self.action, self.dest, opt, value, values, parser) File "/usr/lib/python3.6/optparse.py", line 807, in take_action parser.print_help() File "/usr/lib/python3.6/optparse.py", line 1647, in print_help file.write(self.format_help()) UnicodeEncodeError: 'ascii' codec can't encode characters in position 126-133: ordinal not in range(128) root@bb-lp-1806076:~# env LANG=ru_RU.UTF-8 unattended-upgrade --help | cat Usage: unattended-upgrade [options] Options: -h, --helpshow this help message and exit -d, --debug print debug messages --apt-debug make apt/libapt print verbose debug messages -v, --verbose print info messages --dry-run Simulation, download but do not install --download-only Only download, do not even try to install. --minimal-upgrade-steps Upgrade in minimal steps (and allow interrupting with SIGTERM [Original Bug Text] The Ubuntu Error Tracker has been receiving reports about a problem regarding unattended-upgrades. This problem was most recently seen with package version 1.1ubuntu1.18.04.6, the problem page at https://errors.ubuntu.com/problem/b3e3265e302351558260f54ae37c7b4c193dfc95 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. Also seen in: * https://errors.ubuntu.com/problem/936bb1c75c4efe018f968a5773b820bcf52c298a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1806076/+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 1806076] Re: unattended-upgrade --help raises UnicodeEncodeError when stdout encoding is ascii
** Description changed: + [Impact] + + * unattended-upgrades --help crashes in apt.systemd.daily script when + locale is not in UTF-8. + [Test Case] + + In the fixed case no crash is observed. rbalint@yogi:~$ lxc launch ubuntu:18.04 bb-lp-1806076 Creating bb-lp-1806076 Starting bb-lp-1806076 rbalint@yogi:~$ lxc shell bb-lp-1806076 mesg: ttyname failed: No such device root@bb-lp-1806076:~# apt install -yqq language-pack-ru-base The following package was automatically installed and is no longer required: libfreetype6 Use 'apt autoremove' to remove it. The following additional packages will be installed: language-pack-ru The following NEW packages will be installed: language-pack-ru language-pack-ru-base 0 upgraded, 2 newly installed, 0 to remove and 7 not upgraded. Need to get 2310 kB of archives. After this operation, 11.8 MB of additional disk space will be used. Selecting previously unselected package language-pack-ru-base. (Reading database ... 28536 files and directories currently installed.) Preparing to unpack .../language-pack-ru-base_1%3a18.04+20180712_all.deb ... Unpacking language-pack-ru-base (1:18.04+20180712) ... Selecting previously unselected package language-pack-ru. Preparing to unpack .../language-pack-ru_1%3a18.04+20180712_all.deb ... Unpacking language-pack-ru (1:18.04+20180712) ... Setting up language-pack-ru (1:18.04+20180712) ... Setting up language-pack-ru-base (1:18.04+20180712) ... Generating locales (this might take a while)... ru_RU.UTF-8... done ru_UA.UTF-8... done Generation complete. - root@bb-lp-1806076:~# env LANG=ru_RU unattended-upgrade --help | cat + + root@bb-lp-1806076:~# echo LANG=ru_RU | tee /etc/default/locale + LANG=ru_RU + root@bb-lp-1806076:~# + /usr/lib/apt/apt.systemd.daily update Traceback (most recent call last): - File "/usr/bin/unattended-upgrade", line 1983, in - (options, args) = parser.parse_args() # type: ignore - File "/usr/lib/python3.6/optparse.py", line 1387, in parse_args - stop = self._process_args(largs, rargs, values) - File "/usr/lib/python3.6/optparse.py", line 1427, in _process_args - self._process_long_opt(rargs, values) - File "/usr/lib/python3.6/optparse.py", line 1501, in _process_long_opt - option.process(opt, value, values, self) - File "/usr/lib/python3.6/optparse.py", line 785, in process - self.action, self.dest, opt, value, values, parser) - File "/usr/lib/python3.6/optparse.py", line 807, in take_action - parser.print_help() - File "/usr/lib/python3.6/optparse.py", line 1647, in print_help - file.write(self.format_help()) + File "/usr/bin/unattended-upgrade", line 2171, in + (options, args) = parser.parse_args() # type: ignore + File "/usr/lib/python3.6/optparse.py", line 1387, in parse_args + stop = self._process_args(largs, rargs, values) + File "/usr/lib/python3.6/optparse.py", line 1427, in _process_args + self._process_long_opt(rargs, values) + File "/usr/lib/python3.6/optparse.py", line 1501, in _process_long_opt + option.process(opt, value, values, self) + File "/usr/lib/python3.6/optparse.py", line 785, in process + self.action, self.dest, opt, value, values, parser) + File "/usr/lib/python3.6/optparse.py", line 807, in take_action + parser.print_help() + File "/usr/lib/python3.6/optparse.py", line 1647, in print_help + file.write(self.format_help()) UnicodeEncodeError: 'ascii' codec can't encode characters in position 126-133: ordinal not in range(128) - root@bb-lp-1806076:~# env LANG=ru_RU.UTF-8 unattended-upgrade --help | cat - Usage: unattended-upgrade [options] + root@bb-lp-1806076:~# echo LANG=ru_RU.UTF-8 | tee /etc/default/locale + LANG=ru_RU.UTF-8 + root@bb-lp-1806076:~# /usr/lib/apt/apt.systemd.daily update + root@bb-lp-1806076:~# - Options: - -h, --helpshow this help message and exit - -d, --debug print debug messages - --apt-debug make apt/libapt print verbose debug messages - -v, --verbose print info messages - --dry-run Simulation, download but do not install - --download-only Only download, do not even try to install. - --minimal-upgrade-steps - Upgrade in minimal steps (and allow interrupting with - SIGTERM + [Where problems could occur] + + * Nowhere, really. The fix is setting LC_ALL=C.UFT-8 for u-u --help and + it is processed by grep then. + [Original Bug Text] The Ubuntu Error Tracker has been receiving reports about a problem regarding unattended-upgrades. This problem was most recently seen with package version 1.1ubuntu1.18.04.6, the problem page at https://errors.ubuntu.com/problem/b3e3265e302351558260f54ae37c7b4c193dfc95 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tra
[Touch-packages] [Bug 1907472] Re: glibc x32 autopkgtest fails in hirsute with binutils and audit in -proposed
I've observed the failure in the i386 build of glibc_2.33-0ubuntu4: Linux lcy01-amd64-014 4.15.0-136-generic #140-Ubuntu SMP Thu Jan 28 05:20:47 UTC 2021 i686 athlon i686 GNU/Linux ... if [ -f /proc/cpuinfo ] ; then cat /proc/cpuinfo ; fi processor : 0 vendor_id : AuthenticAMD cpu family : 16 model : 2 model name : AMD Opteron 23xx (Gen 3 Class Opteron) stepping: 3 microcode : 0x165 cpu MHz : 2500.048 cache size : 512 KB physical id : 0 siblings: 1 core id : 0 cpu cores : 1 apicid : 0 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 5 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 syscall nx mmxext fxsr_opt pdpe1gb lm 3dnowext 3dnow rep_good nopl cpuid extd_apicid tsc_known_freq pni cx16 x2apic popcnt hypervisor lahf_lm cmp_legacy svm cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw vmmcall bugs: tlb_mmatch fxsave_leak sysret_ss_attrs null_seg spectre_v1 spectre_v2 bogomips: 5000.09 TLB size: 1024 4K pages clflush size: 64 cache_alignment : 64 address sizes : 40 bits physical, 48 bits virtual power management: ... +-+ | Encountered regressions that don't match expected failures. | +-+ FAIL: math/test-double-libmvec-sincos FAIL: math/test-double-vlen2-sincos FAIL: math/test-float-libmvec-sincosf FAIL: math/test-float-vlen4-sincos touch /<>/stamp-dir/check_x32 CHECK SUMMARY check for check_libc passed check for check_amd64 passed check for check_x32 failed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to audit in Ubuntu. https://bugs.launchpad.net/bugs/1907472 Title: glibc x32 autopkgtest fails in hirsute with binutils and audit in -proposed Status in audit package in Ubuntu: New Status in binutils package in Ubuntu: New Status in glibc package in Ubuntu: New Bug description: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest- hirsute/hirsute/amd64/g/glibc/20201208_160143_17354@/log.gz -- FAIL: math/test-double-libmvec-sincos original exit status 1 Didn't expect signal from child: got `Illegal instruction' -- -- FAIL: math/test-double-vlen2-sincos original exit status 132 -- -- FAIL: math/test-float-libmvec-sincosf original exit status 1 Didn't expect signal from child: got `Illegal instruction' -- -- FAIL: math/test-float-vlen4-sincos original exit status 132 -- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/audit/+bug/1907472/+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 1916485] Re: test -x fails inside shell scripts in containers
** Also affects: glibc (Ubuntu) Importance: Undecided Status: New ** Changed in: glibc (Ubuntu) Status: New => Opinion -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1916485 Title: test -x fails inside shell scripts in containers Status in docker.io package in Ubuntu: New Status in glibc package in Ubuntu: Opinion Status in libseccomp package in Ubuntu: Fix Committed Status in runc package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in docker.io source package in Xenial: New Status in libseccomp source package in Xenial: New Status in runc source package in Xenial: New Status in systemd source package in Xenial: New Status in docker.io source package in Bionic: New Status in libseccomp source package in Bionic: New Status in runc source package in Bionic: Fix Committed Status in systemd source package in Bionic: New Status in docker.io source package in Focal: New Status in libseccomp source package in Focal: New Status in runc source package in Focal: Fix Committed Status in systemd source package in Focal: New Status in docker.io source package in Groovy: New Status in libseccomp source package in Groovy: New Status in runc source package in Groovy: Fix Committed Status in systemd source package in Groovy: Fix Released Status in docker.io source package in Hirsute: New Status in libseccomp source package in Hirsute: Fix Committed Status in runc source package in Hirsute: Fix Released Status in systemd source package in Hirsute: Fix Released Bug description: (SRU template for systemd) [impact] bash (and some other shells) builtin test command -x operation fails [test case] on any affected host system, start nspawn container, e.g.: $ sudo apt install systemd-container $ wget https://cloud-images.ubuntu.com/hirsute/current/hirsute-server-cloudimg-amd64-root.tar.xz $ mkdir h $ cd h $ tar xvf ../hirsute-server-cloudimg-amd64-root.tar.xz $ sudo systemd-nspawn Then from a bash shell, verify if test -x works: root@h:~# ls -l /usr/bin/gpg -rwxr-xr-x 1 1000 1000 1083472 Jan 16 09:53 /usr/bin/gpg root@h:~# test -x /usr/bin/gpg || echo "fail" fail [regression potential] any regression would likely occur during a syscall, most likely faccessat2(), or during other syscalls. [scope] this is needed for b/f this is fixed upstream by commit bcf08acbffdee0d6360d3c31d268e73d0623e5dc which is in 247 and later, so this is fixed in h this was pulled into Debian at version 246.2 in commit e80c5e5371ab77792bae94e0f8c5e85a4237e6eb, so this is fixed in g in x, the entire systemd seccomp code is completely different and the patch doesn't apply, nor does it appear to be needed, as the problem doesn't reproduce in a h container under x. [other info] this needs fixing in libseccomp as well [original description] glibc regression causes test -x to fail inside scripts inside docker/podman, dash and bash are broken, mksh and zsh are fine: root@0df2ce5d7a46:/# test -x /usr/bin/gpg || echo Fail root@0df2ce5d7a46:/# dash -c "test -x /usr/bin/gpg || echo Fail" Fail root@0df2ce5d7a46:/# bash -c "test -x /usr/bin/gpg || echo Fail" Fail root@0df2ce5d7a46:/# mksh -c "test -x /usr/bin/gpg || echo Fail" root@0df2ce5d7a46:/# zsh -c "test -x /usr/bin/gpg || echo Fail" root@0df2ce5d7a46:/# root@0df2ce5d7a46:/# zsh -c "[ -x /usr/bin/gpg ] || echo Fail" root@0df2ce5d7a46:/# mksh -c "[ -x /usr/bin/gpg ] || echo Fail" root@0df2ce5d7a46:/# dash -c "[ -x /usr/bin/gpg ] || echo Fail" Fail root@0df2ce5d7a46:/# bash -c "[ -x /usr/bin/gpg ] || echo Fail" Fail The -f flag works, as does /usr/bin/test: # bash -c "test -f /usr/bin/gpg || echo Fail" # bash -c "/usr/bin/test -x /usr/bin/gpg || echo Fail" # [Original bug report] root@84b750e443f8:/# lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 root@84b750e443f8:/# dpkg -l gnupg apt Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==-===--== ii apt2.1.20 amd64commandline package manager ii gnupg 2.2.20-1ubuntu2 all GNU privacy guard - a free PGP replacement Hi, for 3 days our CI pipelines to recreate Docker images fails for the Hirsute images. From comparison this seems to be caused by apt 2.1.20. The build fails with: 0E: gnupg, gnupg2 and unupg1 do not seem to be installed, but one of them is required for this operation The simple Dockerfile to reproduce t
[Touch-packages] [Bug 1920601] Re: Frequent test failures caused by networking issues on armhf runners
@laney IMO 'Confirmed' would be the accurate state since the root cause is not known. I used to be a proponent of adding more retry strings but they also cause retry lool of test failures. I think APT should retry on timeouts instead, thus adding APT as affected package. ** Also affects: 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 apt in Ubuntu. https://bugs.launchpad.net/bugs/1920601 Title: Frequent test failures caused by networking issues on armhf runners Status in Auto Package Testing: Triaged Status in apt package in Ubuntu: New Bug description: Armhf runners have been known to have networking issues for years. A test of Focal's glibc SRU in Bileto shows that those issues did not go away. The glibc package itself is not expected to cause regression, this was just a run to confirm that. The test resuts are shown here: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_39a8dbb93caf4ec889f8a1b7f69885db/bileto-4017-excuses/2021-03-20_09:25:01/4017_focal_excuses.html Out of the 114 failed tests 58 containst the 'Connection timed out' string and only test logs from armhf contain that string: $ zgrep -l 'Connection timed out' ~/.cache/ubuntu-archive-tools/focal_*.gz /home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_atk1.0_20210318_182825_daefa.gz /home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_axe-demultiplexer_20210318_183430_6b008.gz /home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_bacula_20210318_190411_e3ad7.gz /home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_dialign-t_20210318_204503_b4d94.gz /home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_elisa-player_20210318_211129_9537d.gz /home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_fyba_20210318_181755_7731e.gz /home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_gcc-7_20210318_02_4d95c.gz /home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_gcc-8_20210318_221659_0e69f.gz /home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_golang-github-mailru-easyjson_20210318_231917_67888.gz /home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_gphoto2_20210318_200015_eb767.gz /home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_gtk+3.0_20210318_235412_db3e5.gz /home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_ipmitool_20210319_003215_d03da.gz /home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_kbibtex_20210319_004639_0ac1a.gz /home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_kcptun_20210318_193309_6dcd9.gz /home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libcache-memcached-getparserxs-perl_20210319_024051_33029.gz /home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libclass-load-xs-perl_20210319_025846_01419.gz /home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libconvert-uulib-perl_20210319_034852_21cd1.gz /home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libhat-trie_20210319_060826_fd334.gz /home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libhtml-tidy5-perl_20210319_070723_05fa8.gz /home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libimager-perl_20210319_063314_b19a2.gz /home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libipc-sharelite-perl_20210319_072246_0217e.gz /home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_liblexical-var-perl_20210319_070235_4c450.gz /home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libmarpa-r2-perl_20210319_073731_f7554.gz /home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libmemcached-libmemcached-perl_20210319_011004_dbca1.gz /home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libnet-ldns-perl_20210319_081224_49912.gz /home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libnet-pcap-perl_20210319_081606_4d772.gz /home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libparams-util-perl_20210319_084831_74d13.gz /home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libperlio-eol-perl_20210319_085645_97c6c.gz /home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libperlio-layers-perl_20210319_085937_8bd70.gz /home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libsass_20210319_092518_4db37.gz /home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libsdl-perl_20210319_095502_00c8c.gz /home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libtext-bibtex-perl_20210319_105027_abf4a.gz /home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libtext-hunspell-perl_20210319_103326_4a603.gz /home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libunix-syslog-perl_20210319_111403_f4374.gz /home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libwx-scintilla-perl_20210319_114818_a6aab.gz /home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libzstd_20210319_114737_0c4d9.gz /home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_mod-gearman_20210319_132205_d41ca.gz /home/rbalint/.cache/ubuntu-a
[Touch-packages] [Bug 1404003] Re: glibc vulnerability CVE-2014-9402
** Also affects: glibc (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: eglibc (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: glibc (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: eglibc (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: glibc (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: eglibc (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: glibc (Ubuntu Xenial) Status: New => Fix Released ** Changed in: glibc (Ubuntu Bionic) Status: New => Fix Released ** Changed in: glibc (Ubuntu Focal) Status: New => Fix Released ** Changed in: glibc (Ubuntu) Status: Triaged => Fix Released ** Changed in: eglibc (Ubuntu Xenial) Status: New => Invalid ** Changed in: eglibc (Ubuntu Bionic) Status: New => Invalid ** Changed in: eglibc (Ubuntu Focal) Status: New => Invalid ** Changed in: eglibc (Ubuntu) Status: Triaged => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to eglibc in Ubuntu. https://bugs.launchpad.net/bugs/1404003 Title: glibc vulnerability CVE-2014-9402 Status in eglibc package in Ubuntu: Invalid Status in glibc package in Ubuntu: Fix Released Status in eglibc source package in Xenial: Invalid Status in glibc source package in Xenial: Fix Released Status in eglibc source package in Bionic: Invalid Status in glibc source package in Bionic: Fix Released Status in eglibc source package in Focal: Invalid Status in glibc source package in Focal: Fix Released Bug description: https://sourceware.org/bugzilla/show_bug.cgi?id=17630 https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=11e3417af6e354f1942c68a271ae51e892b2814d To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1404003/+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 1916485] Re: test -x fails inside shell scripts in containers
** Bug watch added: Debian Bug tracker #984573 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984573 ** Also affects: docker.io (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984573 Importance: Unknown Status: Unknown ** No longer affects: docker.io (Debian) ** Also affects: systemd (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984573 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1916485 Title: test -x fails inside shell scripts in containers Status in docker.io package in Ubuntu: New Status in glibc package in Ubuntu: Opinion Status in libseccomp package in Ubuntu: Fix Committed Status in runc package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in docker.io source package in Xenial: New Status in libseccomp source package in Xenial: New Status in runc source package in Xenial: New Status in systemd source package in Xenial: New Status in docker.io source package in Bionic: New Status in libseccomp source package in Bionic: New Status in runc source package in Bionic: Fix Committed Status in systemd source package in Bionic: Fix Committed Status in docker.io source package in Focal: New Status in libseccomp source package in Focal: New Status in runc source package in Focal: Fix Committed Status in systemd source package in Focal: Fix Committed Status in docker.io source package in Groovy: New Status in libseccomp source package in Groovy: New Status in runc source package in Groovy: Fix Committed Status in systemd source package in Groovy: Fix Released Status in docker.io source package in Hirsute: New Status in libseccomp source package in Hirsute: Fix Committed Status in runc source package in Hirsute: Fix Released Status in systemd source package in Hirsute: Fix Released Status in systemd package in Debian: Unknown Bug description: (SRU template for systemd) [impact] bash (and some other shells) builtin test command -x operation fails [test case] on any affected host system, start nspawn container, e.g.: $ sudo apt install systemd-container $ wget https://cloud-images.ubuntu.com/hirsute/current/hirsute-server-cloudimg-amd64-root.tar.xz $ mkdir h $ cd h $ tar xvf ../hirsute-server-cloudimg-amd64-root.tar.xz $ sudo systemd-nspawn Then from a bash shell, verify if test -x works: root@h:~# ls -l /usr/bin/gpg -rwxr-xr-x 1 1000 1000 1083472 Jan 16 09:53 /usr/bin/gpg root@h:~# test -x /usr/bin/gpg || echo "fail" fail [regression potential] any regression would likely occur during a syscall, most likely faccessat2(), or during other syscalls. [scope] this is needed for b/f this is fixed upstream by commit bcf08acbffdee0d6360d3c31d268e73d0623e5dc which is in 247 and later, so this is fixed in h this was pulled into Debian at version 246.2 in commit e80c5e5371ab77792bae94e0f8c5e85a4237e6eb, so this is fixed in g in x, the entire systemd seccomp code is completely different and the patch doesn't apply, nor does it appear to be needed, as the problem doesn't reproduce in a h container under x. [other info] this needs fixing in libseccomp as well [original description] glibc regression causes test -x to fail inside scripts inside docker/podman, dash and bash are broken, mksh and zsh are fine: root@0df2ce5d7a46:/# test -x /usr/bin/gpg || echo Fail root@0df2ce5d7a46:/# dash -c "test -x /usr/bin/gpg || echo Fail" Fail root@0df2ce5d7a46:/# bash -c "test -x /usr/bin/gpg || echo Fail" Fail root@0df2ce5d7a46:/# mksh -c "test -x /usr/bin/gpg || echo Fail" root@0df2ce5d7a46:/# zsh -c "test -x /usr/bin/gpg || echo Fail" root@0df2ce5d7a46:/# root@0df2ce5d7a46:/# zsh -c "[ -x /usr/bin/gpg ] || echo Fail" root@0df2ce5d7a46:/# mksh -c "[ -x /usr/bin/gpg ] || echo Fail" root@0df2ce5d7a46:/# dash -c "[ -x /usr/bin/gpg ] || echo Fail" Fail root@0df2ce5d7a46:/# bash -c "[ -x /usr/bin/gpg ] || echo Fail" Fail The -f flag works, as does /usr/bin/test: # bash -c "test -f /usr/bin/gpg || echo Fail" # bash -c "/usr/bin/test -x /usr/bin/gpg || echo Fail" # [Original bug report] root@84b750e443f8:/# lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 root@84b750e443f8:/# dpkg -l gnupg apt Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==-===--== ii apt2.1.20 amd64commandline package manager ii gnupg 2.2.20-1ubuntu2 all
[Touch-packages] [Bug 1921636] Re: resolved CNAME redirect issues
** Also affects: systemd (Ubuntu Groovy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1921636 Title: resolved CNAME redirect issues Status in systemd package in Ubuntu: New Status in systemd source package in Groovy: New Bug description: I am having issues loading certain websites such as linkedin.com and portions of google sites including images.google.com, hotmail.com login, etc. After looking through some logs and such I've determined that resolved is not properly following CNAMEs to an IP address. Querying the DNS server on my network directly for the info works fine. Loading the sites from other computers on the network works fine. In the #systemd IRC channel I was directed to the following two issues: https://github.com/systemd/systemd/pull/18892 https://github.com/systemd/systemd/pull/19009 System info: Ubuntu 20.10 ii systemd246.6-1ubuntu1.2 amd64system and service manager ii linux-generic 5.8.0.48.53 amd64Complete Generic Linux kernel and headers Example: [11:06:00] host static-exp1.licdn.com Host static-exp1.licdn.com not found: 2(SERVFAIL) [11:06:17] resolvectl status Global LLMNR setting: no MulticastDNS setting: no DNSOverTLS setting: no DNSSEC setting: no DNSSEC supported: no DNS Domain: rhos.bigfiber.net bigfiber.net Link 2 (enp6s0) Current Scopes: none DefaultRoute setting: no LLMNR setting: yes MulticastDNS setting: no DNSOverTLS setting: no DNSSEC setting: no DNSSEC supported: no Link 3 (enp4s0f0) Current Scopes: DNS DefaultRoute setting: yes LLMNR setting: yes MulticastDNS setting: no DNSOverTLS setting: no DNSSEC setting: no DNSSEC supported: no Current DNS Server: 10.18.1.1 DNS Servers: 10.18.1.1 DNS Domain: ~. rhos.bigfiber.net bigfiber.net Link 4 (enp4s0f1) Current Scopes: none DefaultRoute setting: no LLMNR setting: yes MulticastDNS setting: no DNSOverTLS setting: no DNSSEC setting: no DNSSEC supported: no [11:06:26] host static-exp1.licdn.com 10.18.1.1 Using domain server: Name: 10.18.1.1 Address: 10.18.1.1#53 Aliases: static-exp1.licdn.com is an alias for 2-01-2c3e-003d.cdx.cedexis.net. 2-01-2c3e-003d.cdx.cedexis.net is an alias for li-prod-static.azureedge.net. li-prod-static.azureedge.net is an alias for li-prod-static.afd.azureedge.net. li-prod-static.afd.azureedge.net is an alias for star-azureedge-prod.trafficmanager.net. star-azureedge-prod.trafficmanager.net is an alias for dual.t-0009.t-msedge.net. dual.t-0009.t-msedge.net is an alias for t-0009.t-msedge.net. t-0009.t-msedge.net is an alias for Edge-Prod-WSTr3.ctrl.t-0009.t-msedge.net. Edge-Prod-WSTr3.ctrl.t-0009.t-msedge.net is an alias for edge-prod-wstr3.ctrl.t-0001.trafficmanager.net. edge-prod-wstr3.ctrl.t-0001.trafficmanager.net is an alias for standard.t-0009.t-msedge.net. standard.t-0009.t-msedge.net has address 13.107.213.19 standard.t-0009.t-msedge.net has address 13.107.246.19 standard.t-0009.t-msedge.net has IPv6 address 2620:1ec:46::19 standard.t-0009.t-msedge.net has IPv6 address 2620:1ec:bdf::19 resolved debugging log is attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1921636/+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 1920781] Re: Mobile phone hotspot unusable due to systemd-resolved not liking the DNS
** Also affects: systemd (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Groovy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1920781 Title: Mobile phone hotspot unusable due to systemd-resolved not liking the DNS Status in systemd package in Ubuntu: New Status in systemd source package in Focal: New Status in systemd source package in Groovy: New Bug description: Seen in 20.04. Trying to connect to the internet using the mobile phone hotspot is impossible due to systemd-resolved not resolving and reporting things like: resolve call failed: DNSSEC validation failed: incompatible-server and systemd-resolved[81699]: DNSSEC validation failed for question d.3.1.b.d.e.1.e.1.6.9.e.7.8.4.5.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa IN PTR: no-signature DNSSEC validation failed for question b.d.e.1.e.1.6.9.e.7.8.4.5.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa IN DS: no-signature etc etc. Name resolution works just fine from the mobile phone. Funny thing is that the issue persists if DNSSEC is disabled via resolvectl for the interface: Link 3 (wlan0) Current Scopes: DNS DefaultRoute setting: yes LLMNR setting: yes MulticastDNS setting: no DNSOverTLS setting: opportunistic DNSSEC setting: no DNSSEC supported: no Current DNS Server: 192.168.43.1 DNS Servers: 192.168.43.1 Systemd-resolved won't accept the issue to be reported upstream saying that a too old version of systemd is being used. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.5 ProcVersionSignature: Ubuntu 5.8.0-45.51~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Mon Mar 22 15:39:23 2021 EcryptfsInUse: Yes InstallationDate: Installed on 2020-02-16 (400 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: SCHENKER SCHENKER_SLIM14_SSL14L19 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-45-generic root=/dev/mapper/VG_NVMe-root ro quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: Upgraded to focal on 2020-05-23 (303 days ago) dmi.bios.date: 10/02/2019 dmi.bios.release: 7.4 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.04RTR1 dmi.board.asset.tag: Tag 12345 dmi.board.name: N141CU dmi.board.vendor: SCHENKER dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.2 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.04RTR1:bd10/02/2019:br7.4:efr7.2:svnSCHENKER:pnSCHENKER_SLIM14_SSL14L19:pvrNotApplicable:rvnSCHENKER:rnN141CU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: SCHENKER_SLIM14_SSL14L19 dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: SCHENKER modified.conffile..etc.systemd.resolved.conf: [modified] mtime.conffile..etc.systemd.resolved.conf: 2021-02-10T11:20:21.512139 mtime.conffile..etc.systemd.sleep.conf: 2020-08-13T07:55:23.365733 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1920781/+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 1921574] Re: package libpam-systemd:amd64 246.6-1ubuntu1.2 failed to install/upgrade: installed libpam-systemd:amd64 package post-installation script subprocess returned error ex
*** This bug is a duplicate of bug 1699360 *** https://bugs.launchpad.net/bugs/1699360 Use of uninitialized value $ret in string eq at /usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 134. dpkg: error processing package libpam-systemd:amd64 (--configure): installed libpam-systemd:amd64 package post-installation script subprocess returned error exit status 128 libpam-systemd.postinst is very short: --- #!/bin/sh set -e pam-auth-update --package #DEBHELPER# --- , and debhelper does not inject any script. I think the most likely cause is debconf connection with the graphical front end going away. ** This bug has been marked a duplicate of bug 1699360 package libpam-systemd:amd64 232-21ubuntu4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1921574 Title: package libpam-systemd:amd64 246.6-1ubuntu1.2 failed to install/upgrade: installed libpam-systemd:amd64 package post- installation script subprocess returned error exit status 128 Status in systemd package in Ubuntu: New Bug description: I have no extra information. ProblemType: Package DistroRelease: Ubuntu 20.10 Package: libpam-systemd:amd64 246.6-1ubuntu1.2 ProcVersionSignature: Ubuntu 5.8.0-44.50-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Mar 23 18:28:20 2021 ErrorMessage: installed libpam-systemd:amd64 package post-installation script subprocess returned error exit status 128 InstallationDate: Installed on 2020-12-07 (110 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 3.8.6-0ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.20.5ubuntu2 apt 2.1.10ubuntu0.2 SourcePackage: systemd Title: package libpam-systemd:amd64 246.6-1ubuntu1.2 failed to install/upgrade: installed libpam-systemd:amd64 package post-installation script subprocess returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1921574/+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 1915887] Re: systemd spams the syslog about lack of native systemd unit file
Fixed in Hirsute in 247.3-2ubuntu1 . ** Changed in: systemd (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1915887 Title: systemd spams the syslog about lack of native systemd unit file Status in apport package in Ubuntu: Invalid Status in fam package in Ubuntu: Invalid Status in freeradius package in Ubuntu: Invalid Status in ipfm package in Ubuntu: Invalid Status in n2n package in Ubuntu: Invalid Status in pfm package in Ubuntu: Invalid Status in shadowsocks package in Ubuntu: Invalid Status in sysfsutils package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in virtualbox package in Ubuntu: Invalid Status in xl2tpd package in Ubuntu: Invalid Status in systemd source package in Focal: Fix Committed Status in systemd source package in Groovy: Fix Committed Status in systemd package in Debian: Fix Released Bug description: [impact] systemd spams journal with log messages [test case] see journalctl output and search for msgs similar to those listed in original description below [regression potential] any regession would likely result in logs incorrectly not logged when detecting a problem such as lack of native unit file, or using /var/run. [scope] this is needed in f/g this is fixed upstream with commit https://salsa.debian.org/systemd- team/systemd/-/commit/0c6d90f783093fc255e529f8a33b2ed2a8e6c2d6 from debian, which is included in 247.3-2 and later so this is fixed in hirsute already (in -proposed package). these log messages aren't present in b or earlier so aren't needed in x/b [original description] systemd in hirsute spams the syslog file several times per second about services lacking native systemd unit files. Two things should happen. 1) a systemd unit file ought to be created 2) systemd should be slowed down with regards to these messages Feb 17 02:02:48 ubuntu-devel kernel: [ 289.794825] systemd-sysv-generator[7105]: SysV service '/etc/init.d/n2n' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:02:49 ubuntu-devel kernel: [ 290.165351] systemd-sysv-generator[7126]: SysV service '/etc/init.d/n2n' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:02:49 ubuntu-devel kernel: [ 291.111278] systemd-sysv-generator[7170]: SysV service '/etc/init.d/n2n' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:02:50 ubuntu-devel kernel: [ 291.507164] systemd-sysv-generator[7199]: SysV service '/etc/init.d/n2n' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:05:57 ubuntu-devel kernel: [ 478.386062] systemd-sysv-generator[9909]: SysV service '/etc/init.d/fam' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:05:57 ubuntu-devel kernel: [ 478.386321] systemd-sysv-generator[9909]: SysV service '/etc/init.d/xl2tpd' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:05:57 ubuntu-devel kernel: [ 478.386742] systemd-sysv-generator[9909]: SysV service '/etc/init.d/ipfm' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:05:57 ubuntu-devel kernel: [ 478.386767] systemd-sysv-generator[9909]: SysV service '/etc/init.d/shadowsocks' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:05:57 ubuntu-devel kernel: [ 478.387281] systemd-sysv-generator[9909]: SysV service '/etc/init.d/virtualbox' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:05:57 ubuntu-devel kernel: [ 478.388931] systemd-sysv-generator[9909]: SysV s
[Touch-packages] [Bug 1806076] Re: unattended-upgrade --help raises UnicodeEncodeError when stdout encoding is ascii
** Description changed: [Impact] - * unattended-upgrades --help crashes in apt.systemd.daily script when + * unattended-upgrades --help crashes in apt.systemd.daily script when locale is not in UTF-8. [Test Case] In the fixed case no crash is observed. rbalint@yogi:~$ lxc launch ubuntu:18.04 bb-lp-1806076 Creating bb-lp-1806076 Starting bb-lp-1806076 rbalint@yogi:~$ lxc shell bb-lp-1806076 mesg: ttyname failed: No such device root@bb-lp-1806076:~# apt install -yqq language-pack-ru-base The following package was automatically installed and is no longer required: libfreetype6 Use 'apt autoremove' to remove it. The following additional packages will be installed: language-pack-ru The following NEW packages will be installed: language-pack-ru language-pack-ru-base 0 upgraded, 2 newly installed, 0 to remove and 7 not upgraded. Need to get 2310 kB of archives. After this operation, 11.8 MB of additional disk space will be used. Selecting previously unselected package language-pack-ru-base. (Reading database ... 28536 files and directories currently installed.) Preparing to unpack .../language-pack-ru-base_1%3a18.04+20180712_all.deb ... Unpacking language-pack-ru-base (1:18.04+20180712) ... Selecting previously unselected package language-pack-ru. Preparing to unpack .../language-pack-ru_1%3a18.04+20180712_all.deb ... Unpacking language-pack-ru (1:18.04+20180712) ... Setting up language-pack-ru (1:18.04+20180712) ... Setting up language-pack-ru-base (1:18.04+20180712) ... Generating locales (this might take a while)... ru_RU.UTF-8... done ru_UA.UTF-8... done Generation complete. - root@bb-lp-1806076:~# echo LANG=ru_RU | tee /etc/default/locale + root@bb-lp-1806076:~# echo LANG=ru_RU | tee /etc/default/locale LANG=ru_RU root@bb-lp-1806076:~# /usr/lib/apt/apt.systemd.daily update Traceback (most recent call last): - File "/usr/bin/unattended-upgrade", line 2171, in - (options, args) = parser.parse_args() # type: ignore - File "/usr/lib/python3.6/optparse.py", line 1387, in parse_args - stop = self._process_args(largs, rargs, values) - File "/usr/lib/python3.6/optparse.py", line 1427, in _process_args - self._process_long_opt(rargs, values) - File "/usr/lib/python3.6/optparse.py", line 1501, in _process_long_opt - option.process(opt, value, values, self) - File "/usr/lib/python3.6/optparse.py", line 785, in process - self.action, self.dest, opt, value, values, parser) - File "/usr/lib/python3.6/optparse.py", line 807, in take_action - parser.print_help() - File "/usr/lib/python3.6/optparse.py", line 1647, in print_help - file.write(self.format_help()) + File "/usr/bin/unattended-upgrade", line 2171, in + (options, args) = parser.parse_args() # type: ignore + File "/usr/lib/python3.6/optparse.py", line 1387, in parse_args + stop = self._process_args(largs, rargs, values) + File "/usr/lib/python3.6/optparse.py", line 1427, in _process_args + self._process_long_opt(rargs, values) + File "/usr/lib/python3.6/optparse.py", line 1501, in _process_long_opt + option.process(opt, value, values, self) + File "/usr/lib/python3.6/optparse.py", line 785, in process + self.action, self.dest, opt, value, values, parser) + File "/usr/lib/python3.6/optparse.py", line 807, in take_action + parser.print_help() + File "/usr/lib/python3.6/optparse.py", line 1647, in print_help + file.write(self.format_help()) UnicodeEncodeError: 'ascii' codec can't encode characters in position 126-133: ordinal not in range(128) - root@bb-lp-1806076:~# echo LANG=ru_RU.UTF-8 | tee /etc/default/locale + root@bb-lp-1806076:~# echo LANG=ru_RU.UTF-8 | tee /etc/default/locale LANG=ru_RU.UTF-8 root@bb-lp-1806076:~# /usr/lib/apt/apt.systemd.daily update root@bb-lp-1806076:~# [Where problems could occur] - * Nowhere, really. The fix is setting LC_ALL=C.UFT-8 for u-u --help and + * Nowhere, really. The fix is setting LC_ALL=C.UTF-8 for u-u --help and it is processed by grep then. - [Original Bug Text] The Ubuntu Error Tracker has been receiving reports about a problem regarding unattended-upgrades. This problem was most recently seen with package version 1.1ubuntu1.18.04.6, the problem page at https://errors.ubuntu.com/problem/b3e3265e302351558260f54ae37c7b4c193dfc95 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. Also seen in: * https://errors.ubuntu.com/problem/936bb1c75c4efe018f968a5773b820bcf52c298a -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1806076 Title: unattended-upgrade --help raise
[Touch-packages] [Bug 1908241] Re: README.sysctl refers to "service procps reload", which no longer works
BTW the reload was added to fix this bug: LP: #1719159.
** Changed in: procps (Ubuntu)
Importance: Undecided => Low
** Changed in: procps (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to procps in Ubuntu.
https://bugs.launchpad.net/bugs/1908241
Title:
README.sysctl refers to "service procps reload", which no longer works
Status in procps package in Ubuntu:
Confirmed
Bug description:
/etc/sysctl.d/README.sysctl states:
After making any changes, please run "service procps reload" (or, from
a Debian package maintainer script "deb-systemd-invoke restart
procps.service").
However, "service procps reload" no longer works:
$ sudo service procps reload
Usage: /etc/init.d/procps {start|stop|status|restart|try-restart|force-reload}
It looks like the correct command should be "service procps force-
reload"?
Local versions:
Ubuntu 20.04.1 LTS
procps 2:3.3.16-1ubuntu2
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1908241/+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 1908241] Re: README.sysctl refers to "service procps reload", which no longer works
Forwarded the fix to Debian:
https://salsa.debian.org/debian/procps/-/merge_requests/2
It is not a good time to apply it in 21.04, because we are close to the
release.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to procps in Ubuntu.
https://bugs.launchpad.net/bugs/1908241
Title:
README.sysctl refers to "service procps reload", which no longer works
Status in procps package in Ubuntu:
Confirmed
Bug description:
/etc/sysctl.d/README.sysctl states:
After making any changes, please run "service procps reload" (or, from
a Debian package maintainer script "deb-systemd-invoke restart
procps.service").
However, "service procps reload" no longer works:
$ sudo service procps reload
Usage: /etc/init.d/procps {start|stop|status|restart|try-restart|force-reload}
It looks like the correct command should be "service procps force-
reload"?
Local versions:
Ubuntu 20.04.1 LTS
procps 2:3.3.16-1ubuntu2
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1908241/+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 1874824] Re: pgrep reports error "cannot allocate" when run without stack limit
I've sponsored the SRUs. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/1874824 Title: pgrep reports error "cannot allocate" when run without stack limit Status in procps package in Ubuntu: Fix Released Status in procps source package in Focal: In Progress Status in procps source package in Groovy: In Progress Status in procps source package in Hirsute: Fix Released Status in procps package in Debian: New Bug description: [Impact] - Users who have ulimit set high would see either slow or failed pgrep and pkill commands - Users who have ulimit set to unlimited would see failed pgrep and pkill commands - This bug occurs because the behavior of sysconf(_SC_ARG_MAX) changed with a newer version of the kernel. [Test Case] - set the ulimit to unlimited by running `ulimit -S -s unlimited` - run `pgrep bash` to see that the "cannot allocate" error is printed and the command has failed. [Where Problems Could Occur] - We have set upper and lower limits on the size of the malloc, but if further kernel versions break the call to sysconf in unexpected ways we could still see problems. [Original Description] If you have no stack limit (ulimit -S -s unlimited), any pgrep call will fail with an error: > pgrep vim pgrep: cannot allocate 4611686018427387903 bytes If you have a high stack limit (e.g. ulimit -S -s 50), pgrep is very slow: > time pgrep vim 2196 real 8.48s user 8.40s syst 0.07s busy 99% rmem 253444 The relevant upstream bug report could be: https://gitlab.com/procps-ng/procps/-/issues/152 Archlinux bug report: https://bugs.archlinux.org/task/66093 procps: Installed: 2:3.3.16-1ubuntu2 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1874824/+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 1922485] Re: systemd: slice: Failed to migrate controller cgroups
The switch of the default did not happen yet in Ubuntu because snapd is not ready: LP: #1850667. The plan is switching to cgroupv2 as default in the 21.10 development cycle. ** Changed in: systemd (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1922485 Title: systemd: slice: Failed to migrate controller cgroups Status in systemd: Fix Released Status in systemd package in Ubuntu: Triaged Status in systemd package in Debian: Fix Released Bug description: Hi, during boot those error messages appear in the logs: # journalctl | grep controller [...] Apr 02 20:16:23 vougeot systemd[3155]: -.slice: Failed to migrate controller cgroups from /user.slice/user-108.slice/user@108.service, ignoring: Permission denied Apr 02 20:16:31 vougeot systemd[3512]: -.slice: Failed to migrate controller cgroups from /user.slice/user-1000.slice/user@1000.service, ignoring: Permission denied ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: systemd 247.3-3ubuntu2 Uname: Linux 5.11.11-05-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sun Apr 4 13:29:25 2021 MachineType: TUXEDO TUXEDO InfinityBook S 15 Gen6 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.11-05-lowlatency root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/07/2020 dmi.bios.release: 7.3 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.03RTR dmi.board.name: NS50MU dmi.board.vendor: TUXEDO dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.2 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.03RTR:bd09/07/2020:br7.3:efr7.2:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50MU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: TUXEDO InfinityBook S 15 Gen6 dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: TUXEDO modified.conffile..etc.systemd.resolved.conf: [modified] mtime.conffile..etc.systemd.resolved.conf: 2021-04-02T13:37:46.839143 To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1922485/+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 1921696] Re: Failed to start Load/Save RF Kill Switch Status
** Changed in: systemd (Ubuntu) Status: Confirmed => In Progress ** Changed in: systemd (Ubuntu) Assignee: (unassigned) => Balint Reczey (rbalint) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1921696 Title: Failed to start Load/Save RF Kill Switch Status Status in systemd package in Ubuntu: In Progress Bug description: When I boot the system I get these lög messages - Failed to start Load/Save RF Kill Switch Statu - A start job for unit systemd-rfkill.service has failed and with sender systemd-rfkil Read event structure of invalid size Also happens on an Ubuntu system on the same computer. System details p-i@pi-tuf-b550m-wifi:~$ inxi -Fz System:Kernel: 5.11.0-11-generic x86_64 bits: 64 Desktop: Cinnamon 4.8.6 Distro: Ubuntu 21.04 (Hirsute Hippo) Machine: Type: Desktop System: ASUS product: N/A v: N/A serial: Mobo: ASUSTeK model: TUF GAMING B550M-PLUS (WI-FI) v: Rev X.0x serial: UEFI: American Megatrends v: 1804 date: 02/02/2021 CPU: Info: 6-Core model: AMD Ryzen 5 5600X bits: 64 type: MT MCP L2 cache: 3 MiB Speed: 2509 MHz min/max: 2200/4791 MHz Core speeds (MHz): 1: 2509 2: 2237 3: 2858 4: 2236 5: 2235 6: 2238 7: 2798 8: 2239 9: 2238 10: 2233 11: 2236 12: 2234 Graphics: Device-1: Advanced Micro Devices [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] driver: amdgpu v: kernel Display: x11 server: X.Org 1.20.10 driver: loaded: amdgpu,ati unloaded: fbdev,modesetting,radeon,vesa resolution: 2560x1440~60Hz OpenGL: renderer: AMD Radeon RX 5700 (NAVI10 DRM 3.40.0 5.11.0-11-generic LLVM 11.0.1) v: 4.6 Mesa 21.0.1 Audio: Device-1: Advanced Micro Devices [AMD/ATI] Navi 10 HDMI Audio driver: snd_hda_intel Device-2: Advanced Micro Devices [AMD] Starship/Matisse HD Audio driver: snd_hda_intel Device-3: Logitech Webcam C250 type: USB driver: snd-usb-audio,uvcvideo Sound Server: ALSA v: k5.11.0-11-generic Network: Device-1: Intel Wi-Fi 6 AX200 driver: iwlwifi IF: wlp6s0 state: down mac: Device-2: Realtek RTL8125 2.5GbE driver: r8169 IF: enp7s0 state: up speed: 1000 Mbps duplex: full mac: IF-ID-1: vmnet1 state: unknown speed: N/A duplex: N/A mac: IF-ID-2: vmnet8 state: unknown speed: N/A duplex: N/A mac: Bluetooth: Device-1: Intel AX200 Bluetooth type: USB driver: btusb Report: ID: hci0 state: up running pscan bt-v: 3.0 address: Drives:Local Storage: total: 1.36 TiB used: 97.88 GiB (7.0%) ID-1: /dev/nvme0n1 vendor: Corsair model: Force MP600 size: 465.76 GiB ID-2: /dev/nvme1n1 vendor: Kingston model: SA2000M8500G size: 465.76 GiB ID-3: /dev/sda vendor: Samsung model: SSD 860 EVO 500GB size: 465.76 GiB Partition: ID-1: / size: 456.96 GiB used: 97.84 GiB (21.4%) fs: ext4 dev: /dev/nvme0n1p2 ID-2: /boot/efi size: 511 MiB used: 33.3 MiB (6.5%) fs: vfat dev: /dev/nvme0n1p1 Swap: ID-1: swap-1 type: file size: 2 GiB used: 0 KiB (0.0%) file: /swapfile Sensors: System Temperatures: cpu: 35.9 C mobo: 39.0 C gpu: amdgpu temp: 40.0 C Fan Speeds (RPM): fan-1: 698 fan-2: 937 fan-3: 711 fan-7: 931 gpu: amdgpu fan: 0 Info: Processes: 372 Uptime: 13m Memory: 15.54 GiB used: 1.88 GiB (12.1%) Shell: Bash inxi: 3.3.01 p-i@pi-tuf-b550m-wifi:~$ ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: systemd 247.3-3ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: X-Cinnamon Date: Mon Mar 29 10:12:21 2021 InstallationDate: Installed on 2021-02-05 (51 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210203) MachineType: ASUS System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-11-generic root=UUID=d37b6e75-43a0-4e56-85c1-4a6ef8e1ffc9 ro acpi_enforce_resources=lax quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/systemd-localed.service → /usr/lib/systemd/system/systemd-localed.service.d/locale-gen.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 3 overridden configuration files found. SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f
[Touch-packages] [Bug 1918328] Re: kernel emits error "Bad value for 'hidepid'" with new systemd on old kernel
** Changed in: systemd (Ubuntu) Status: New => Confirmed ** Changed in: systemd (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1918328 Title: kernel emits error "Bad value for 'hidepid'" with new systemd on old kernel Status in systemd: Fix Released Status in systemd package in Ubuntu: Triaged Bug description: When using a newer systemd (>=247) and older kernel (<5.8), systemd attempts to mount /proc using a value for the 'hidepid' parameter that the older kernel doesn't understand, which causes the kernel to emit a warning message like: [4083297.870684] proc: Bad value for 'hidepid' This is harmless, as systemd falls back to the 'old' mount method, however the logged error message can be confusing. Since there is no ubuntu release where the newer systemd might be directly used with a kernel older than 5.8, this can only reasonably happen in a container on a older ubuntu release. For example, on a focal release with the 5.4 kernel, a hirsute container can be created, and when it starts up the host dmesg will log the kernel error messages shown above. Note that if using a lxd container, as there is a bug where lxd prevents mounting any fs (which mostly breaks systemd), you must set the 'security.nesting' parameter for the lxd container, e.g.: $ lxc launch ubuntu-daily:hirsute test-h $ lxc set config test-h security.nesting true Note that this hasn't been fixed upstream, and as it's purely cosmetic, it's possible it won't get fixed upstream. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1918328/+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 1915936] Re: systemd-coredump user is created by something other than its derived systemd packages
** Changed in: systemd (Ubuntu Hirsute) Importance: Undecided => Wishlist ** Changed in: systemd (Ubuntu Groovy) Importance: Undecided => Wishlist ** Changed in: systemd (Ubuntu Focal) Importance: Undecided => Wishlist ** Changed in: systemd (Ubuntu Bionic) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1915936 Title: systemd-coredump user is created by something other than its derived systemd packages Status in systemd package in Ubuntu: New Status in systemd source package in Bionic: New Status in systemd source package in Focal: New Status in systemd source package in Groovy: New Status in systemd source package in Hirsute: New Status in systemd package in Debian: New Bug description: systemd-coredump binary package is instructed as follows: #debian/systemd-coredump.postinst: adduser --quiet --system --group --no-create-home --home /run/systemd \ --gecos "systemd Core Dumper" systemd-coredump But one doesn't need this package to be installed to have the systemd- coredump user created. This was taken from a focal 20.04.2 fresh installation (Right after a vanilla installation): # cat /etc/passwd: ... systemd-coredump:x:999:999:systemd Core Dumper:/:/usr/sbin/nologin ... # dpkg -l | grep -i systemd ii dbus-user-session1.12.16-2ubuntu2.1 amd64simple interprocess messaging system (systemd --user integration) ii libnss-systemd:amd64 245.4-4ubuntu3.4 amd64nss module providing dynamic user and group name resolution ii libpam-systemd:amd64 245.4-4ubuntu3.4 amd64system and service manager - PAM module ii libsystemd0:amd64245.4-4ubuntu3.4 amd64systemd utility library ii networkd-dispatcher 2.0.1-1 all Dispatcher service for systemd-networkd connection status changes ii python3-systemd 234-3build2 amd64Python 3 bindings for systemd ii systemd 245.4-4ubuntu3.4 amd64system and service manager ii systemd-sysv 245.4-4ubuntu3.4 amd64system and service manager - SysV links ii systemd-timesyncd245.4-4ubuntu3.4 amd64minimalistic service to synchronize local time with NTP servers # /var/log/syslog syslog:Feb 17 15:31:56 test systemd-sysusers[402]: Creating group systemd-coredump with gid 999. syslog:Feb 17 15:31:56 test systemd-sysusers[402]: Creating user systemd-coredump (systemd Core Dumper) with uid 999 and gid 999. Additionnally, you may notice the home directory during the user creation at installation sets it to "/" as opposed to "/run/systemd" directive in the appropriate postint. It is contradictory. * Why systemd-coredump user is created at installation time and/or without 'systemd-coredump' package installed ? * Why this early creation set the home directory to "/" ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1915936/+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 1915502] Re: "systemd --user" fails to start for non-local users
** Also affects: systemd (Ubuntu Focal)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1915502
Title:
"systemd --user" fails to start for non-local users
Status in systemd package in Ubuntu:
Incomplete
Status in systemd source package in Focal:
New
Bug description:
systemd-logind fails to start the systemd --user process for non-local
users on Ubuntu 20.04. This is a reproducible problem; all our
systems are displaying the same symptoms.
The systems are using Kerberos (Active Directory) for authentication,
and NIS for account meta-data and authorisation (groups)
A base installation is performed using the server 20.04 ISO image. No
additional packages are selected. Post-install, I run:
apt-get install tcsh nis krb5-user libpam-krb5 libnss-systemd
I set up the NIS client (supply the default domain name, check ypbind
is running and ypcat passwd is working)
I then set up /etc/krb5.conf for kerberos authentication to a domain
controller, confirm that kinit works and a kerberos ticket is issued.
I modify /etc/passwd, /etc/group and /etc/shadow, appending a "+" to
the end of each.
/etc/nsswitch.conf is modified to support compat mode, as well as
systemd:
passwd: compat systemd
group: compat systemd
shadow: compat
I can log in remotely via ssh using my NIS account and Kerberos
credentials. MY NIS meta-data looks like:
amcvey:KRB5:::Andy McVey:/home/amcvey:/bin/tcsh
(where UID and GID are replaced with values unique to the
organisation)
On login, the following occurs:
hostname:~> systemctl --user
Failed to connect to bus: No such file or directory
I put pam-systemd and systemd-logind into debug mode to get more
information:
Feb 12 09:51:32 myhostname sshd[1210]: Accepted publickey for amcvey from
[redact] port 58849 ssh2: RSA SHA256:[redact]
Feb 12 09:51:32 myhostname sshd[1210]: pam_unix(sshd:session): session opened
for user amcvey by (uid=0)
Feb 12 09:51:32 myhostname systemd-logind[903]: Got message type=method_call
sender=:1.13 destination=org.freedesktop.login1 path=/org/freedesktop/login1
interface=org.freedesktop.login1.Manager member=CreateSession cookie=2
reply_cookie=0 signature=uusussbssa(sv) error-name=n/a error-message=n/a
Feb 12 09:51:32 myhostname sshd[1210]: pam_systemd(sshd:session): pam-systemd
initializing
Feb 12 09:51:32 myhostname systemd-logind[903]: Sent message type=method_call
sender=n/a destination=org.freedesktop.DBus path=/org/freedesktop/DBus
interface=org.freedesktop.DBus member=GetConnectionUnixUser cookie=40
reply_cookie=0 signature=s error-name=n/a error-message=n/a
Feb 12 09:51:32 myhostname sshd[1210]: pam_systemd(sshd:session): Asking
logind to create session: uid=198083 pid=1210 service=sshd type=tty class=user
desktop= seat= vtnr=0 tty= display= remote=yes remote_user=
remote_host=10.105.121.110
Feb 12 09:51:32 myhostname systemd-logind[903]: Got message
type=method_return sender=org.freedesktop.DBus destination=:1.6 path=n/a
interface=n/a member=n/a cookie=13 reply_cookie=40 signature=u error-name=n/a
error-message=n/a
Feb 12 09:51:32 myhostname sshd[1210]: pam_systemd(sshd:session): Session
limits: memory_max=n/a tasks_max=n/a cpu_weight=n/a io_weight=n/a
runtime_max_sec=n/a
Feb 12 09:51:32 myhostname systemd-logind[903]: Sent message type=method_call
sender=n/a destination=org.freedesktop.DBus path=/org/freedesktop/DBus
interface=org.freedesktop.DBus member=GetConnectionUnixProcessID cookie=41
reply_cookie=0 signature=s error-name=n/a error-message=n/a
Feb 12 09:51:32 myhostname sshd[1210]: pam_systemd(sshd:session): Failed to
create session: No such process
Feb 12 09:51:32 myhostname systemd-logind[903]: Got message
type=method_return sender=org.freedesktop.DBus destination=:1.6 path=n/a
interface=n/a member=n/a cookie=14 reply_cookie=41 signature=u error-name=n/a
error-message=n/a
Feb 12 09:51:32 myhostname systemd-logind[903]: Unable to connect to
/run/systemd/userdb/io.systemd.Multiplexer: No such file or directory
Feb 12 09:51:32 myhostname systemd-logind[903]: n/a: varlink: setting state
idle-client
Feb 12 09:51:32 myhostname systemd-logind[903]:
/run/systemd/userdb/io.systemd.DynamicUser: Sending message:
{"method":"io.systemd.UserDatabase.GetUserRecord","parameters":{"uid":198083,"service":"io.systemd.DynamicUser"}}
Feb 12 09:51:32 myhostname systemd-logind[903]:
/run/systemd/userdb/io.systemd.DynamicUser: varlink: changing state idle-client
→ awaiting-reply
Feb 12 09:51:32 myhostname systemd-logind[903]:
/run/systemd/userdb/io.systemd.DynamicUser: New incoming message:
{"error":"io.systemd.UserDatabase.NoRecordFound","parameters":{}}
Feb 12 09:51:32 myhostname systemd-logind[903]:
/run/systemd/userdb/io.systemd.DynamicUs
[Touch-packages] [Bug 1923406] Re: sslh 1.18-1 high CPU load -> Fix available
** Package changed: systemd (Ubuntu) => sslh (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1923406 Title: sslh 1.18-1 high CPU load -> Fix available Status in sslh package in Ubuntu: New Bug description: System: Ubuntu 18.04 LTS Software: sslh v1.18-1 The Problem is that the sslh-daemon causes 100% load after a while. The bug seems to be reported and fixed in december 2020 at the the ssl-project. Should be fixed in v1.21b or newer. So please backport/update the package accordingly to fix the problem for everyone. See: https://github.com/yrutschle/sslh/issues/284 And for the fix in code: https://github.com/yrutschle/sslh/commit/1e33455fe76078d97ea4ce1c8b856df2dea64c71 Workaround: We put a cronjob that kills/restarts sslhd every 3hours and after that we tried to update the binaries from source ourselves. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sslh/+bug/1923406/+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 1923472] Re: xdm fails to start on Sundays
** Package changed: systemd (Ubuntu) => xdm (Ubuntu) ** Bug watch added: Debian Bug tracker #948346 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948346 ** Also affects: xdm (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948346 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1923472 Title: xdm fails to start on Sundays Status in xdm package in Ubuntu: New Status in xdm package in Debian: Unknown Bug description: On the first login of the week, xdm (1.1.11-3ubuntu2) fails to start on Ubuntu 20.04. More correctly, it does start, but exits almost immediately on signal 12. It leaves /var/run/xdm.pid behind, and also a running X server with no clients. This makes it hard to restart, for one needs to kill the X server and remove the pid file first. The cause is logrotate running during startup and killing xdm before xdm installs a handler for SIGUSR2. The issue is more fully described upstream at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948346 In passing I would comment that running logrotate so early during startup seems strange to me. Startup would surely be faster if these sort of "cron" jobs were left until it had finished? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdm/+bug/1923472/+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 1923618] Re: upgrading systemd on groovy terminates sessions
** Also affects: systemd (Ubuntu Groovy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1923618 Title: upgrading systemd on groovy terminates sessions Status in systemd package in Ubuntu: New Status in systemd source package in Groovy: New Bug description: Whenever I upgrade systemd on my groovy system, my gnome session is terminated. This is very annoying, as everything that was running on that session is terminated. NetworkManager also stops running. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1923618/+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 1923485] Re: unable to reconize Asgard NVME with short serial
@mwhudson also reported this issue upstream https://github.com/systemd/systemd/issues/19309 (thanks!) ** Bug watch added: github.com/systemd/systemd/issues #19309 https://github.com/systemd/systemd/issues/19309 ** Also affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1923485 Title: unable to reconize Asgard NVME with short serial Status in curtin: New Status in systemd package in Ubuntu: New Bug description: check this: https://discourse.maas.io/t/unable-to-deploy-valueerror-failed-to-find-storage-volume-id-nvme0n1/4442/4 Maybe the line os.listdir should be changed with os.walk to discover all child directories? Or maybe this is just a BUG of MAAS? To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1923485/+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
