[Touch-packages] [Bug 2052535] [NEW] Blocked by pycountry autopkgtest
Public bug reported: https://bugs.launchpad.net/ubuntu/+source/pycountry/+bug/2052318 currently prevents iso-codes to migrate from 4.15.0-1 to 4.16.0-1 ** Affects: iso-codes (Ubuntu) Importance: Undecided Status: New ** Tags: update-excuse -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iso-codes in Ubuntu. https://bugs.launchpad.net/bugs/2052535 Title: Blocked by pycountry autopkgtest Status in iso-codes package in Ubuntu: New Bug description: https://bugs.launchpad.net/ubuntu/+source/pycountry/+bug/2052318 currently prevents iso-codes to migrate from 4.15.0-1 to 4.16.0-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iso-codes/+bug/2052535/+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 2052318] Re: pycountry: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.12 3.11" returned exit code 13
https://bugs.launchpad.net/ubuntu/+source/iso-codes/+bug/2052535
** Also affects: iso-codes (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iso-codes in Ubuntu.
https://bugs.launchpad.net/bugs/2052318
Title:
pycountry: FTBFS: dh_auto_test: error: pybuild --test -i
python{version} -p "3.12 3.11" returned exit code 13
Status in iso-codes package in Ubuntu:
New
Status in pycountry package in Ubuntu:
New
Status in pycountry package in Debian:
New
Bug description:
Imported from Debian bug http://bugs.debian.org/1060934:
Source: pycountry
Version: 23.12.11+ds1-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240115 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> # The data provided by the iso-codes package is not within this
> # source package; reassemble the sources
> # poetry insists on real files not strange out-of-module symlinks when
> # building, but we want to end up with symlinks back to iso-codes
> # in the package
> echo "# AUTOGENERATED FROM d/rules" >> debian/links
> # json databases
> mkdir -p src/pycountry/databases
> for f in /usr/share/iso-codes/json/iso*; do \
> src="$f"; \
> part=`echo "$f" | sed s@/usr/share/iso-codes/json/@@ | tr -d _`; \
> srcdest=src/pycountry/databases/"$part"; \
> debdest=usr/lib/python3/dist-packages/pycountry/databases/"$part"; \
> cp "$src" "$srcdest"; \
> echo "$src" "$debdest" >> debian/links; \
> done
> # locales data
> mkdir -p src/pycountry/locales
> dpkg -L iso-codes | \
> grep /usr/share/locale/ | \
> xargs dirname | \
> uniq | \
> sed "s@/usr/share/locale/@@" | \
> xargs -I{} -n1 mkdir -p src/pycountry/locales/{}
> for f in `dpkg -L iso-codes | grep /usr/share/locale/`; do \
> if [ -f "$f" ]; then \
> src="$f"; \
> part=`echo "$f" | sed "s@/usr/share/locale/@@;s@iso_@iso@"`; \
> srcdest=src/pycountry/locales/"$part"; \
> debdest=/usr/lib/python3/dist-packages/pycountry/locales/"$part"; \
> cp "$src" "$srcdest"; \
> echo "$src" "$debdest" >> debian/links; \
> fi; \
> done
> echo "RECONSTRUCTED PACKAGE:"
> RECONSTRUCTED PACKAGE:
> find src/pycountry
> src/pycountry
> src/pycountry/db.py
> src/pycountry/__init__.py
> src/pycountry/tests
> src/pycountry/tests/test_general.py
> src/pycountry/databases
> src/pycountry/databases/iso3166-2.json
> src/pycountry/databases/iso15924.json
> src/pycountry/databases/iso3166-1.json
> src/pycountry/databases/iso639-5.json
> src/pycountry/databases/iso639-3.json
> src/pycountry/databases/iso3166-3.json
> src/pycountry/databases/iso639-2.json
> src/pycountry/databases/iso4217.json
> src/pycountry/py.typed
> src/pycountry/locales
> src/pycountry/locales/wa
> src/pycountry/locales/wa/LC_MESSAGES
> src/pycountry/locales/wa/LC_MESSAGES/iso3166-1.mo
> src/pycountry/locales/wa/LC_MESSAGES/iso3166.mo
> src/pycountry/locales/wa/LC_MESSAGES/iso639-2.mo
> src/pycountry/locales/wa/LC_MESSAGES/iso3166-2.mo
> src/pycountry/locales/wa/LC_MESSAGES/iso639-3.mo
> src/pycountry/locales/wa/LC_MESSAGES/iso639.mo
> src/pycountry/locales/wa/LC_MESSAGES/iso3166-3.mo
> src/pycountry/locales/wa/LC_MESSAGES/iso639_3.mo
> src/pycountry/locales/wa/LC_MESSAGES/iso3166_2.mo
> src/pycountry/locales/chr
> src/pycountry/locales/chr/LC_MESSAGES
> src/pycountry/locales/chr/LC_MESSAGES/iso3166-1.mo
> src/pycountry/locales/chr/LC_MESSAGES/iso3166.mo
> src/pycountry/locales/gv
> src/pycountry/locales/gv/LC_MESSAGES
> src/pycountry/locales/gv/LC_MESSAGES/iso3166-1.mo
> src/pycountry/locales/gv/LC_MESSAGES/iso3166.mo
> src/pycountry/locales/en
> src/pycountry/locales/en/LC_MESSAGES
> src/pycountry/locales/en/LC_MESSAGES/iso3166-2.mo
> src/pycountry/locales/en/LC_MESSAGES/iso3166_2.mo
> src/pycountry/locales/ka
> src/pycountry/locales/ka/LC_MESSAGES
> src/pycountry/locales/ka/LC_MESSAGES/iso3166-1.mo
> src/pycountry/locales/ka/LC_MESSAGES/iso4217.mo
> src/pycountry/locales/ka/LC_MESSAGES/iso639-5.mo
> src/pycountry/locales/ka/LC_MESSAGES/iso3166.mo
> src/pycountry/locales/ka/LC_MESSAGES/iso639-2.mo
> src/pycountry/locales/ka/LC_MESSAGES/iso3166-2.mo
> src/pycountry/locales/ka/LC_MESSAGES/iso639-3.mo
> src/pycountry/locales/ka/LC_MESSAGES/iso639.mo
> src/pycountry/locales/ka/LC_MESSAGES/iso639_5.mo
> src/pycountry/locales/ka/LC_MESSAGES/iso15924.mo
> src/pycountry/locales/ka/LC_MESSAGES/iso3166-3.mo
> src/pycountry/locales/ka/LC_MESSAGES/iso639_3.mo
> src/pycountry/locales/ka/LC_MESSAGES/iso3166_2.mo
> src/pycountry/locales/tt@iqtelif
> src/pycountry/locales/tt@iqtelif/LC_MESSAGES
> src/pycountry/loca
[Touch-packages] [Bug 2052535] Re: Blocked by pycountry autopkgtest
This bug isn't necessary, if an admin sees it, please delete :-) ** Changed in: iso-codes (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iso-codes in Ubuntu. https://bugs.launchpad.net/bugs/2052535 Title: Blocked by pycountry autopkgtest Status in iso-codes package in Ubuntu: Invalid Bug description: https://bugs.launchpad.net/ubuntu/+source/pycountry/+bug/2052318 currently prevents iso-codes to migrate from 4.15.0-1 to 4.16.0-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iso-codes/+bug/2052535/+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 2052318] Re: pycountry: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.12 3.11" returned exit code 13
Bug fixed and released with pycountry/23.12.11+ds1-2
Patch:
https://salsa.debian.org/debian/pycountry/-/commit/d1177df330b616ddcf3cabc365a0dafd5e5c2925
** Changed in: pycountry (Ubuntu)
Status: New => Fix Released
** Changed in: iso-codes (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iso-codes in Ubuntu.
https://bugs.launchpad.net/bugs/2052318
Title:
pycountry: FTBFS: dh_auto_test: error: pybuild --test -i
python{version} -p "3.12 3.11" returned exit code 13
Status in iso-codes package in Ubuntu:
Fix Released
Status in pycountry package in Ubuntu:
Fix Released
Status in pycountry package in Debian:
New
Bug description:
Imported from Debian bug http://bugs.debian.org/1060934:
Source: pycountry
Version: 23.12.11+ds1-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240115 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> # The data provided by the iso-codes package is not within this
> # source package; reassemble the sources
> # poetry insists on real files not strange out-of-module symlinks when
> # building, but we want to end up with symlinks back to iso-codes
> # in the package
> echo "# AUTOGENERATED FROM d/rules" >> debian/links
> # json databases
> mkdir -p src/pycountry/databases
> for f in /usr/share/iso-codes/json/iso*; do \
> src="$f"; \
> part=`echo "$f" | sed s@/usr/share/iso-codes/json/@@ | tr -d _`; \
> srcdest=src/pycountry/databases/"$part"; \
> debdest=usr/lib/python3/dist-packages/pycountry/databases/"$part"; \
> cp "$src" "$srcdest"; \
> echo "$src" "$debdest" >> debian/links; \
> done
> # locales data
> mkdir -p src/pycountry/locales
> dpkg -L iso-codes | \
> grep /usr/share/locale/ | \
> xargs dirname | \
> uniq | \
> sed "s@/usr/share/locale/@@" | \
> xargs -I{} -n1 mkdir -p src/pycountry/locales/{}
> for f in `dpkg -L iso-codes | grep /usr/share/locale/`; do \
> if [ -f "$f" ]; then \
> src="$f"; \
> part=`echo "$f" | sed "s@/usr/share/locale/@@;s@iso_@iso@"`; \
> srcdest=src/pycountry/locales/"$part"; \
> debdest=/usr/lib/python3/dist-packages/pycountry/locales/"$part"; \
> cp "$src" "$srcdest"; \
> echo "$src" "$debdest" >> debian/links; \
> fi; \
> done
> echo "RECONSTRUCTED PACKAGE:"
> RECONSTRUCTED PACKAGE:
> find src/pycountry
> src/pycountry
> src/pycountry/db.py
> src/pycountry/__init__.py
> src/pycountry/tests
> src/pycountry/tests/test_general.py
> src/pycountry/databases
> src/pycountry/databases/iso3166-2.json
> src/pycountry/databases/iso15924.json
> src/pycountry/databases/iso3166-1.json
> src/pycountry/databases/iso639-5.json
> src/pycountry/databases/iso639-3.json
> src/pycountry/databases/iso3166-3.json
> src/pycountry/databases/iso639-2.json
> src/pycountry/databases/iso4217.json
> src/pycountry/py.typed
> src/pycountry/locales
> src/pycountry/locales/wa
> src/pycountry/locales/wa/LC_MESSAGES
> src/pycountry/locales/wa/LC_MESSAGES/iso3166-1.mo
> src/pycountry/locales/wa/LC_MESSAGES/iso3166.mo
> src/pycountry/locales/wa/LC_MESSAGES/iso639-2.mo
> src/pycountry/locales/wa/LC_MESSAGES/iso3166-2.mo
> src/pycountry/locales/wa/LC_MESSAGES/iso639-3.mo
> src/pycountry/locales/wa/LC_MESSAGES/iso639.mo
> src/pycountry/locales/wa/LC_MESSAGES/iso3166-3.mo
> src/pycountry/locales/wa/LC_MESSAGES/iso639_3.mo
> src/pycountry/locales/wa/LC_MESSAGES/iso3166_2.mo
> src/pycountry/locales/chr
> src/pycountry/locales/chr/LC_MESSAGES
> src/pycountry/locales/chr/LC_MESSAGES/iso3166-1.mo
> src/pycountry/locales/chr/LC_MESSAGES/iso3166.mo
> src/pycountry/locales/gv
> src/pycountry/locales/gv/LC_MESSAGES
> src/pycountry/locales/gv/LC_MESSAGES/iso3166-1.mo
> src/pycountry/locales/gv/LC_MESSAGES/iso3166.mo
> src/pycountry/locales/en
> src/pycountry/locales/en/LC_MESSAGES
> src/pycountry/locales/en/LC_MESSAGES/iso3166-2.mo
> src/pycountry/locales/en/LC_MESSAGES/iso3166_2.mo
> src/pycountry/locales/ka
> src/pycountry/locales/ka/LC_MESSAGES
> src/pycountry/locales/ka/LC_MESSAGES/iso3166-1.mo
> src/pycountry/locales/ka/LC_MESSAGES/iso4217.mo
> src/pycountry/locales/ka/LC_MESSAGES/iso639-5.mo
> src/pycountry/locales/ka/LC_MESSAGES/iso3166.mo
> src/pycountry/locales/ka/LC_MESSAGES/iso639-2.mo
> src/pycountry/locales/ka/LC_MESSAGES/iso3166-2.mo
> src/pycountry/locales/ka/LC_MESSAGES/iso639-3.mo
> src/pycountry/locales/ka/LC_MESSAGES/iso639.mo
> src/pycountry/locales/ka/LC_MESSAGES/iso639_5.mo
> src/pycountry/locales/ka/LC_MESSAGES/iso15924.mo
> src/pycountry/locales/ka/LC_MESSAGES/iso3166-3.mo
> src/pycountry/locales/ka/LC_MESSAGES/iso639_3.
[Touch-packages] [Bug 2054319] Re: System installed from jammy point release iso cannot upgrade to noble
** Also affects: policykit-1 (Ubuntu) Importance: Undecided Status: New ** Also affects: tracker-miners (Ubuntu) Importance: Undecided Status: New ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/2054319 Title: System installed from jammy point release iso cannot upgrade to noble Status in gnome-shell package in Ubuntu: New Status in policykit-1 package in Ubuntu: New Status in tracker-miners package in Ubuntu: New Status in ubuntu-release-upgrader package in Ubuntu: New Bug description: We have different crashes being encountered. In our auto-upgrade- testing, we see gnome-shell crash, however, when testing locally, I didn't experience this. @hyask did experience the gnome-shell crash though. When running an upgrade from jammy to noble in a virsh vm, about halfway through the upgrade process my gui dies. I then ran the upgrade from a console, to which it revealed that just the gui dies - the upgrade process, for me, continues and then laterally fails. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: ubuntu-release-upgrader-core 1:24.04.7 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 ApportVersion: 2.27.0-0ubuntu7 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CrashReports: 640:1000:124:1592041:2024-02-19 14:26:22.564354912 +:2024-02-19 14:51:56.318947066 +:/var/crash/_usr_libexec_tracker-extract-3.1000.crash 600:0:124:833806:2024-02-19 14:34:18.370597600 +:2024-02-19 14:34:19.370597600 +:/var/crash/polkitd.0.crash Date: Mon Feb 19 14:53:39 2024 InstallationDate: Installed on 2024-02-19 (0 days ago) InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240216.1) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to noble on 2024-02-19 (0 days ago) VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', '/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 127: pkexec must be setuid root VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting mtime.conffile..etc.init.d.apport: 2024-02-14T15:51:44 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2054319/+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 2054319] Re: System installed from jammy point release iso cannot upgrade to noble
** Tags added: rls-nn-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/2054319 Title: System installed from jammy point release iso cannot upgrade to noble Status in gnome-shell package in Ubuntu: New Status in policykit-1 package in Ubuntu: New Status in tracker-miners package in Ubuntu: New Status in ubuntu-release-upgrader package in Ubuntu: New Bug description: We have different crashes being encountered. In our auto-upgrade- testing, we see gnome-shell crash, however, when testing locally, I didn't experience this. @hyask did experience the gnome-shell crash though. When running an upgrade from jammy to noble in a virsh vm, about halfway through the upgrade process my gui dies. I then ran the upgrade from a console, to which it revealed that just the gui dies - the upgrade process, for me, continues and then laterally fails. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: ubuntu-release-upgrader-core 1:24.04.7 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 ApportVersion: 2.27.0-0ubuntu7 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CrashReports: 640:1000:124:1592041:2024-02-19 14:26:22.564354912 +:2024-02-19 14:51:56.318947066 +:/var/crash/_usr_libexec_tracker-extract-3.1000.crash 600:0:124:833806:2024-02-19 14:34:18.370597600 +:2024-02-19 14:34:19.370597600 +:/var/crash/polkitd.0.crash Date: Mon Feb 19 14:53:39 2024 InstallationDate: Installed on 2024-02-19 (0 days ago) InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240216.1) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to noble on 2024-02-19 (0 days ago) VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', '/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 127: pkexec must be setuid root VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting mtime.conffile..etc.init.d.apport: 2024-02-14T15:51:44 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2054319/+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 2054319] Re: System installed from jammy point release iso cannot upgrade to noble
Yeah, sorry, I forgot to mention. The crashes that happen in our Jenkins are already pushed to the error tracker. Here are links to the latest oopses: gnome-shell: https://errors.ubuntu.com/oops/af2e99fc-d101-11ee-8a58-fa163ec8ca8c tracker-extract: https://errors.ubuntu.com/oops/7c05a805-d101-11ee-8a58-fa163ec8ca8c Maybe Tim will have a link for the polkit crash, but I couldn't find one. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/2054319 Title: System installed from jammy point release iso cannot upgrade to noble Status in gnome-shell package in Ubuntu: New Status in policykit-1 package in Ubuntu: New Status in tracker-miners package in Ubuntu: New Status in ubuntu-release-upgrader package in Ubuntu: New Bug description: We have different crashes being encountered. In our auto-upgrade- testing, we see gnome-shell crash, however, when testing locally, I didn't experience this. @hyask did experience the gnome-shell crash though. When running an upgrade from jammy to noble in a virsh vm, about halfway through the upgrade process my gui dies. I then ran the upgrade from a console, to which it revealed that just the gui dies - the upgrade process, for me, continues and then laterally fails. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: ubuntu-release-upgrader-core 1:24.04.7 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 ApportVersion: 2.27.0-0ubuntu7 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CrashReports: 640:1000:124:1592041:2024-02-19 14:26:22.564354912 +:2024-02-19 14:51:56.318947066 +:/var/crash/_usr_libexec_tracker-extract-3.1000.crash 600:0:124:833806:2024-02-19 14:34:18.370597600 +:2024-02-19 14:34:19.370597600 +:/var/crash/polkitd.0.crash Date: Mon Feb 19 14:53:39 2024 InstallationDate: Installed on 2024-02-19 (0 days ago) InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240216.1) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to noble on 2024-02-19 (0 days ago) VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', '/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 127: pkexec must be setuid root VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting mtime.conffile..etc.init.d.apport: 2024-02-14T15:51:44 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2054319/+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 2054823] [NEW] Sync klibc 2.0.13-4 (main) from Debian unstable (main)
Public bug reported: Please sync klibc 2.0.13-4 (main) from Debian unstable (main) Explanation of the Ubuntu delta and why it can be dropped: [ Klaus Frank ] * d/i/h/klibc-utils: Fix compatibility issue with busybox and improve verbose debug output. (Closes: #1055694) (LP: #2046336) This patch provided one way to fix the `cp -n` incompatibility. The changelog below mentions another change with the same purpose. I've also checked the code, and that new version from Debian correctly doesn't use `cp -n`, which means it will be safe to use with any version of coreutils, older or newer than the change of semantic in `cp -n`. Changelog entries since current noble version 2.0.13-2ubuntu1: klibc (2.0.13-4) unstable; urgency=medium [ Sven Joachim ] * debian/initramfs-tools/hooks/klibc-utils: Avoid the use of "cp -n" (Closes: #1055694). [ Salvatore Bonaccorso ] * debian/control: Add myself to Uploaders -- Salvatore Bonaccorso Wed, 21 Feb 2024 13:08:58 +0100 klibc (2.0.13-3) experimental; urgency=medium * Install klibc shared library in /usr/lib -- Ben Hutchings Sat, 25 Nov 2023 00:49:35 + ** Affects: klibc (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to klibc in Ubuntu. https://bugs.launchpad.net/bugs/2054823 Title: Sync klibc 2.0.13-4 (main) from Debian unstable (main) Status in klibc package in Ubuntu: New Bug description: Please sync klibc 2.0.13-4 (main) from Debian unstable (main) Explanation of the Ubuntu delta and why it can be dropped: [ Klaus Frank ] * d/i/h/klibc-utils: Fix compatibility issue with busybox and improve verbose debug output. (Closes: #1055694) (LP: #2046336) This patch provided one way to fix the `cp -n` incompatibility. The changelog below mentions another change with the same purpose. I've also checked the code, and that new version from Debian correctly doesn't use `cp -n`, which means it will be safe to use with any version of coreutils, older or newer than the change of semantic in `cp -n`. Changelog entries since current noble version 2.0.13-2ubuntu1: klibc (2.0.13-4) unstable; urgency=medium [ Sven Joachim ] * debian/initramfs-tools/hooks/klibc-utils: Avoid the use of "cp -n" (Closes: #1055694). [ Salvatore Bonaccorso ] * debian/control: Add myself to Uploaders -- Salvatore Bonaccorso Wed, 21 Feb 2024 13:08:58 +0100 klibc (2.0.13-3) experimental; urgency=medium * Install klibc shared library in /usr/lib -- Ben Hutchings Sat, 25 Nov 2023 00:49:35 + To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/2054823/+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 2055146] [NEW] Upgrade from Jammy to Noble breaks
Public bug reported: Hello there! Upgrading `dash` from Jammy to Noble is broken. Here is a quick reproducer: ``` podman pull ubuntu:jammy podman run -it --rm ubuntu:jammy sed -i 's/jammy/noble/' /etc/apt/sources.list apt update apt full-upgrade ``` This should end up with this error: ``` Setting up dash (0.5.12-6ubuntu3) ... Removing 'diversion of /usr/share/man/man1/sh.1.gz to /usr/share/man/man1/sh.distrib.1.gz by dash' Removing 'diversion of /bin/sh to /bin/sh.distrib by dash' This should never be reached dpkg: error processing package dash (--configure): installed dash package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: dash E: Sub-process /usr/bin/dpkg returned an error code (1) ``` As `dash` is pre-installed on almost every kind of Ubuntu, this breaks any upgrade from Jammy to Noble in practice. ** Affects: dash (Ubuntu) Importance: Undecided Status: New ** Tags: rls-nn-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dash in Ubuntu. https://bugs.launchpad.net/bugs/2055146 Title: Upgrade from Jammy to Noble breaks Status in dash package in Ubuntu: New Bug description: Hello there! Upgrading `dash` from Jammy to Noble is broken. Here is a quick reproducer: ``` podman pull ubuntu:jammy podman run -it --rm ubuntu:jammy sed -i 's/jammy/noble/' /etc/apt/sources.list apt update apt full-upgrade ``` This should end up with this error: ``` Setting up dash (0.5.12-6ubuntu3) ... Removing 'diversion of /usr/share/man/man1/sh.1.gz to /usr/share/man/man1/sh.distrib.1.gz by dash' Removing 'diversion of /bin/sh to /bin/sh.distrib by dash' This should never be reached dpkg: error processing package dash (--configure): installed dash package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: dash E: Sub-process /usr/bin/dpkg returned an error code (1) ``` As `dash` is pre-installed on almost every kind of Ubuntu, this breaks any upgrade from Jammy to Noble in practice. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dash/+bug/2055146/+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 2055146] Re: Upgrade from Jammy to Noble breaks
** Tags removed: rls-nn-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dash in Ubuntu. https://bugs.launchpad.net/bugs/2055146 Title: Upgrade from Jammy to Noble breaks Status in dash package in Ubuntu: Fix Committed Bug description: Hello there! Upgrading `dash` from Jammy to Noble is broken. Here is a quick reproducer: ``` podman pull ubuntu:jammy podman run -it --rm ubuntu:jammy sed -i 's/jammy/noble/' /etc/apt/sources.list apt update apt full-upgrade ``` This should end up with this error: ``` Setting up dash (0.5.12-6ubuntu3) ... Removing 'diversion of /usr/share/man/man1/sh.1.gz to /usr/share/man/man1/sh.distrib.1.gz by dash' Removing 'diversion of /bin/sh to /bin/sh.distrib by dash' This should never be reached dpkg: error processing package dash (--configure): installed dash package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: dash E: Sub-process /usr/bin/dpkg returned an error code (1) ``` As `dash` is pre-installed on almost every kind of Ubuntu, this breaks any upgrade from Jammy to Noble in practice. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dash/+bug/2055146/+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 2055200] [NEW] tests-in-lxd is broken on Jammy with latest autopkgtest version
Public bug reported: With autopkgtest 5.32 being SRU'd to Jammy[1], `tests-in-lxd` breaks because it can't patch `autopkgtest-build-lxd` anymore. Please find a debdiff attached to fix that issue. [1]: https://bugs.launchpad.net/ubuntu/+source/autopkgtest/+bug/2051939 ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Attachment added: "tests-in-lxd.debdiff" https://bugs.launchpad.net/bugs/2055200/+attachment/5749847/+files/tests-in-lxd.debdiff ** Description changed: - With autopkgtest 5.32 being SRU'd to Jammy, `tests-in-lxd` breaks + With autopkgtest 5.32 being SRU'd to Jammy[1], `tests-in-lxd` breaks because it can't patch `autopkgtest-build-lxd` anymore. Please find a debdiff attached to fix that issue. + + [1]: https://bugs.launchpad.net/ubuntu/+source/autopkgtest/+bug/2051939 -- 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/2055200 Title: tests-in-lxd is broken on Jammy with latest autopkgtest version Status in systemd package in Ubuntu: New Bug description: With autopkgtest 5.32 being SRU'd to Jammy[1], `tests-in-lxd` breaks because it can't patch `autopkgtest-build-lxd` anymore. Please find a debdiff attached to fix that issue. [1]: https://bugs.launchpad.net/ubuntu/+source/autopkgtest/+bug/2051939 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2055200/+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 2057490] [NEW] Crash during upgrade from Jammy/Mantic to Noble
Public bug reported: Our automatic upgrade testing reports crashes happening regularly, but not 100% time, during upgrades from Mantic to Noble. Here is the corresponding error tracker problem: https://errors.ubuntu.com/problem/0e53cd613cee458a7332d45bfb11c6daef4edeb3 Please also find attached an archive of Jenkins artifacts containing a lot of various additional logs from this morning's occurrence. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Attachment added: "mantic-noble-ubuntu-mate_network-manager_crash.zip" https://bugs.launchpad.net/bugs/2057490/+attachment/5755245/+files/mantic-noble-ubuntu-mate_network-manager_crash.zip ** Summary changed: - Crash during upgrade from Mantic to Noble + Crash during upgrade from Jammy/Mantic to Noble -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2057490 Title: Crash during upgrade from Jammy/Mantic to Noble Status in network-manager package in Ubuntu: New Bug description: Our automatic upgrade testing reports crashes happening regularly, but not 100% time, during upgrades from Mantic to Noble. Here is the corresponding error tracker problem: https://errors.ubuntu.com/problem/0e53cd613cee458a7332d45bfb11c6daef4edeb3 Please also find attached an archive of Jenkins artifacts containing a lot of various additional logs from this morning's occurrence. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2057490/+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 2057490] Re: Crash during upgrade from Jammy/Mantic to Noble
I'll see for reproducing that locally and provide you with a crash report. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2057490 Title: Crash during upgrade from Jammy/Mantic to Noble Status in network-manager package in Ubuntu: New Bug description: Our automatic upgrade testing reports crashes happening regularly, but not 100% time, during upgrades from Mantic to Noble. Here is the corresponding error tracker problem: https://errors.ubuntu.com/problem/0e53cd613cee458a7332d45bfb11c6daef4edeb3 Please also find attached an archive of Jenkins artifacts containing a lot of various additional logs from this morning's occurrence. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2057490/+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 2057490] Re: Crash during upgrade from Jammy/Mantic to Noble
There, I finally got an apport crash file. Is that enough for you to have a first look? ** Attachment added: "_usr_sbin_NetworkManager.0.crash" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2057490/+attachment/5756023/+files/_usr_sbin_NetworkManager.0.crash -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2057490 Title: Crash during upgrade from Jammy/Mantic to Noble Status in network-manager package in Ubuntu: New Bug description: Our automatic upgrade testing reports crashes happening regularly, but not 100% time, during upgrades from Mantic to Noble. Here is the corresponding error tracker problem: https://errors.ubuntu.com/problem/0e53cd613cee458a7332d45bfb11c6daef4edeb3 Please also find attached an archive of Jenkins artifacts containing a lot of various additional logs from this morning's occurrence. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2057490/+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 2058930] Re: Missing in i386 Packages index
Apparently this was linked to the extra `setup-commands` issue that made us loose the `proposed` pocket, and got "fixed" by updating the database with the `no-proposed` tag. TL;DR: fixed, and we didn't loose any cowboy specific to that issue, everything is fine. ** Changed in: libvpx (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 libvpx in Ubuntu. https://bugs.launchpad.net/bugs/2058930 Title: Missing in i386 Packages index Status in libvpx package in Ubuntu: Fix Released Bug description: The new version of libvpx 1.14 seems not to be published to http://ftpmaster.internal on i386 only. This leads to the autopkgtest trigger "libvpx/1.14.0-1ubuntu1", not having any effect on i386: https://autopkgtest.ubuntu.com/packages/libvpx/noble/i386 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvpx/+bug/2058930/+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 2063128] [NEW] Upgrade from mantic to noble shows a debconf prompt
Public bug reported: Reproducer: * Run Ubuntu Studio Mantic in a VM * Run `do-release-upgrade -d` to upgrade it to Noble * After the package download phase, the packages upgrade starts, and you quickly get prompted by jackd2 asking `Enable realtime process priority?` This can be avoided with `export DEBIAN_FRONTEND=noninteractive`, that's why it didn't show up in the CI, but we can't expect users to rely on this. I've attached a screenshot of the prompt, that contains more details on what exactly is asked. ** Affects: jackd2 (Ubuntu) Importance: Undecided Status: New ** Attachment added: "2024-04-22-16_31_14.png" https://bugs.launchpad.net/bugs/2063128/+attachment/5769449/+files/2024-04-22-16_31_14.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to jackd2 in Ubuntu. https://bugs.launchpad.net/bugs/2063128 Title: Upgrade from mantic to noble shows a debconf prompt Status in jackd2 package in Ubuntu: New Bug description: Reproducer: * Run Ubuntu Studio Mantic in a VM * Run `do-release-upgrade -d` to upgrade it to Noble * After the package download phase, the packages upgrade starts, and you quickly get prompted by jackd2 asking `Enable realtime process priority?` This can be avoided with `export DEBIAN_FRONTEND=noninteractive`, that's why it didn't show up in the CI, but we can't expect users to rely on this. I've attached a screenshot of the prompt, that contains more details on what exactly is asked. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/2063128/+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 2063194] [NEW] Sync capnproto 1.0.1-4 (universe) from Debian unstable (main)
Public bug reported: Please sync capnproto 1.0.1-4 (universe) from Debian unstable (main) Changelog entries since current noble version 1.0.1-3build4: capnproto (1.0.1-4) unstable; urgency=medium * Add patch for FTBFS on 32-bit ARM after the time_t 64 transition. Thank you to Arnd Bergmann, Wookey, Tom Lee, and Andrey Rakhmatullin for their for help resolving this bug. (Closes: #1067916) -- tony mancill Mon, 15 Apr 2024 22:09:51 -0700 ** Affects: capnproto (Ubuntu) Importance: Undecided Assignee: Graham Inggs (ginggs) Status: In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to capnproto in Ubuntu. https://bugs.launchpad.net/bugs/2063194 Title: Sync capnproto 1.0.1-4 (universe) from Debian unstable (main) Status in capnproto package in Ubuntu: In Progress Bug description: Please sync capnproto 1.0.1-4 (universe) from Debian unstable (main) Changelog entries since current noble version 1.0.1-3build4: capnproto (1.0.1-4) unstable; urgency=medium * Add patch for FTBFS on 32-bit ARM after the time_t 64 transition. Thank you to Arnd Bergmann, Wookey, Tom Lee, and Andrey Rakhmatullin for their for help resolving this bug. (Closes: #1067916) -- tony mancill Mon, 15 Apr 2024 22:09:51 -0700 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/capnproto/+bug/2063194/+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 1880839] Re: Clock skew on testbeds
** Changed in: auto-package-testing Status: New => Won't Fix -- 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/1880839 Title: Clock skew on testbeds Status in Auto Package Testing: Won't Fix Status in systemd package in Ubuntu: Won't Fix Bug description: Clock stepped backward on a testbed: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest- groovy/groovy/amd64/b/boost1.71/20200501_151103_1e387@/log.gz ... context FAIL stderr: make[2]: Warning: File '/tmp/tmp.qPfGPM84a1/src/demo2.cpp' has modification time 0.52 s in the future autopkgtest [13:55:37]: test context: - - - - - - - - - - stderr - - - - - - - - - - make[2]: Warning: File '/tmp/tmp.qPfGPM84a1/src/demo2.cpp' has modification time 0.52 s in the future make[2]: warning: Clock skew detected. Your build may be incomplete. .. To manage notifications about this bug go to: https://bugs.launchpad.net/auto-package-testing/+bug/1880839/+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 2080972] [NEW] /tmp as non-tmpfs doesn't get cleaned upon reboot
Public bug reported: On Oracular, it seems `/tmp` doesn't get cleaned on reboot, when the `/etc/systemd/system/tmp.mount` file is present. Reproducer: $ wget https://cloud-images.ubuntu.com/minimal/daily/oracular/20240913/oracular-minimal-cloudimg-amd64.img $ qemu-img resize oracular-minimal-cloudimg-amd64.img +20G $ cat >user-data user-data
[Touch-packages] [Bug 2080972] Re: /tmp as non-tmpfs doesn't get cleaned upon reboot
** Tags added: rls-oo-incoming -- 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/2080972 Title: /tmp as non-tmpfs doesn't get cleaned upon reboot Status in systemd package in Ubuntu: New Bug description: On Oracular, it seems `/tmp` doesn't get cleaned on reboot, when the `/etc/systemd/system/tmp.mount` file is present. Reproducer: $ wget https://cloud-images.ubuntu.com/minimal/daily/oracular/20240913/oracular-minimal-cloudimg-amd64.img $ qemu-img resize oracular-minimal-cloudimg-amd64.img +20G $ cat >user-data
[Touch-packages] [Bug 2046336] [NEW] initramfs-tools: After updating coreutils cp: not replacing in console when running update-initramfs
Public bug reported: Imported from Debian bug http://bugs.debian.org/1055694: Package: initramfs-tools Version: 0.142 Severity: normal X-Debbugs-Cc: konomikit...@gmail.com Dear Maintainer, After updating coreutils from 9.1-1 to 9.4-1+b1 the following lines appear when running update-initramfs -u: cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/cat' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/cpio' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/dd' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/dmesg' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/false' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/gunzip' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/kill' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/ln' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/ls' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/mkdir' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/mkfifo' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/mknod' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/mount' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/mv' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/nuke' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/readlink' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/resume' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/sh' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/sleep' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/sync' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/true' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/umount' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/uname' The lines seem to be a cosmetic issue only, but I cannot be entirely sure. -- Package-specific info: -- initramfs sizes -rw-r--r-- 1 root root 78M Nov 10 19:13 /boot/initrd.img-6.5.0-3-amd64 -rw-r--r-- 1 root root 78M Nov 10 19:13 /boot/initrd.img-6.5.0-4-amd64 -- /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-6.5.0-4-amd64 root=UUID=e7b71052-3dff-454b-9730-7b146ebdf115 ro preempt=full quiet -- /proc/filesystems btrfs fuseblk vfat -- lsmod Module Size Used by tcp_diag 12288 0 inet_diag 28672 1 tcp_diag vboxnetadp 28672 0 vboxnetflt 40960 0 vboxdrv 716800 2 vboxnetadp,vboxnetflt nvme_fabrics 32768 0 ccm20480 9 rfcomm102400 16 snd_seq_dummy 12288 0 snd_hrtimer12288 1 snd_seq 114688 7 snd_seq_dummy qrtr 57344 4 cmac 12288 3 algif_hash 12288 1 algif_skcipher 12288 1 af_alg 36864 6 algif_hash,algif_skcipher bnep 36864 2 zstd 12288 12 zram 40960 2 zsmalloc 36864 1 zram btusb 81920 0 btrtl 28672 1 btusb btbcm 24576 1 btusb intel_rapl_msr 20480 0 btintel57344 1 btusb intel_rapl_common 36864 1 intel_rapl_msr btmtk 12288 1 btusb binfmt_misc28672 1 bluetooth1126400 44 btrtl,btmtk,btintel,btbcm,bnep,btusb,rfcomm edac_mce_amd 40960 0 kvm_amd 184320 0 iwlmvm589824 0 kvm 1359872 1 kvm_amd mac80211 1392640 1 iwlmvm sha3_generic 16384 1 jitterentropy_rng 20480 1 snd_hda_codec_realtek 192512 1 irqbypass 12288 1 kvm snd_hda_codec_generic 114688 1 snd_hda_codec_realtek ledtrig_audio 12288 1 snd_hda_codec_generic snd_hda_codec_hdmi 90112 1 libarc412288 1 mac80211 ghash_clmulni_intel16384 0 sha512_ssse3 53248 1 snd_hda_intel 61440 4 sha512_generic 16384 1 sha512_ssse3 snd_usb_audio 417792 3 ctr12288 3 snd_intel_dspcfg 32768 1 snd_hda_intel snd_usbmidi_lib49152 1 snd_usb_audio snd_intel_sdw_acpi 16384 1 snd_intel_dspcfg drbg 49152 1 snd_rawmidi53248 1 snd_usbmidi_lib aesni_intel 360448 10 ansi_cprng 12288 0 iwlwifi 544768 1 iwlmvm snd_hda_codec 225280 4 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec_realtek crypto_simd16384 1 aesni_intel cryptd 28672 3 crypto_simd,ghash_clmulni_intel ecdh_generic 16384 2 bluetooth rapl 20480 0 ecc45056 1 ecdh_generic snd_seq_device 16384 2 snd_seq,snd_rawmidi crc16 12288 1 bluetooth snd_hda_core 147456 5 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_hda_codec_realtek mc 94208 1 snd_usb_audio wmi_bmof 12288 0 snd_hwdep 20480 2 snd_usb_audio,snd_hda_codec gigabyte_wmi 12288 0 sg 45056 0 cfg8
[Touch-packages] [Bug 2046336] Re: initramfs-tools: After updating coreutils cp: not replacing in console when running update-initramfs
Here is a Merge Request with a possible patch: https://salsa.debian.org/kernel-team/klibc/-/merge_requests/12 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to klibc in Ubuntu. https://bugs.launchpad.net/bugs/2046336 Title: initramfs-tools: After updating coreutils cp: not replacing in console when running update-initramfs Status in klibc package in Ubuntu: New Status in klibc package in Debian: New Bug description: Imported from Debian bug http://bugs.debian.org/1055694: Package: initramfs-tools Version: 0.142 Severity: normal X-Debbugs-Cc: konomikit...@gmail.com Dear Maintainer, After updating coreutils from 9.1-1 to 9.4-1+b1 the following lines appear when running update-initramfs -u: cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/cat' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/cpio' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/dd' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/dmesg' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/false' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/gunzip' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/kill' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/ln' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/ls' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/mkdir' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/mkfifo' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/mknod' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/mount' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/mv' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/nuke' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/readlink' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/resume' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/sh' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/sleep' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/sync' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/true' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/umount' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/uname' The lines seem to be a cosmetic issue only, but I cannot be entirely sure. -- Package-specific info: -- initramfs sizes -rw-r--r-- 1 root root 78M Nov 10 19:13 /boot/initrd.img-6.5.0-3-amd64 -rw-r--r-- 1 root root 78M Nov 10 19:13 /boot/initrd.img-6.5.0-4-amd64 -- /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-6.5.0-4-amd64 root=UUID=e7b71052-3dff-454b-9730-7b146ebdf115 ro preempt=full quiet -- /proc/filesystems btrfs fuseblk vfat -- lsmod Module Size Used by tcp_diag 12288 0 inet_diag 28672 1 tcp_diag vboxnetadp 28672 0 vboxnetflt 40960 0 vboxdrv 716800 2 vboxnetadp,vboxnetflt nvme_fabrics 32768 0 ccm20480 9 rfcomm102400 16 snd_seq_dummy 12288 0 snd_hrtimer12288 1 snd_seq 114688 7 snd_seq_dummy qrtr 57344 4 cmac 12288 3 algif_hash 12288 1 algif_skcipher 12288 1 af_alg 36864 6 algif_hash,algif_skcipher bnep 36864 2 zstd 12288 12 zram 40960 2 zsmalloc 36864 1 zram btusb 81920 0 btrtl 28672 1 btusb btbcm 24576 1 btusb intel_rapl_msr 20480 0 btintel57344 1 btusb intel_rapl_common 36864 1 intel_rapl_msr btmtk 12288 1 btusb binfmt_misc28672 1 bluetooth1126400 44 btrtl,btmtk,btintel,btbcm,bnep,btusb,rfcomm edac_mce_amd 40960 0 kvm_amd 184320 0 iwlmvm589824 0 kvm 1359872 1 kvm_amd mac80211 1392640 1 iwlmvm sha3_generic 16384 1 jitterentropy_rng 20480 1 snd_hda_codec_realtek 192512 1 irqbypass 12288 1 kvm snd_hda_codec_generic 114688 1 snd_hda_codec_realtek ledtrig_audio 12288 1 snd_hda_codec_generic snd_hda_codec_hdmi 90112 1 libarc412288 1 mac80211 ghash_clmulni_intel16384 0 sha512_ssse3 53248 1 snd_hda_intel 61440 4 sha512_generic 16384 1 sha512_ssse3 snd_usb_audio 417792 3 ctr12288 3 snd_intel_dspcfg 32768 1 snd_hda_intel snd_usbmidi_lib49152 1 snd_usb_audio snd_intel_sdw_acpi 16384 1 snd_intel_dspcfg drbg 49152 1 snd_rawmidi53248 1 snd_usbmidi_lib aesni_intel 360448 10 ansi_cprng 12288 0 iwlwifi 544768 1 iwlmvm snd_hda_codec 225280 4 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hd
[Touch-packages] [Bug 2046336] Re: initramfs-tools: After updating coreutils cp: not replacing in console when running update-initramfs
Test is passing [1] with `klibc` 2.0.13-2ubuntu1~ppa2 from this PPA: https://launchpad.net/~hyask/+archive/ubuntu/klibc-2046336 [1]: https://autopkgtest.ubuntu.com/results/autopkgtest-noble-hyask-klibc-2046336/noble/amd64/i/initramfs-tools/20231214_120611_9a9f6@/log.gz -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to klibc in Ubuntu. https://bugs.launchpad.net/bugs/2046336 Title: initramfs-tools: After updating coreutils cp: not replacing in console when running update-initramfs Status in klibc package in Ubuntu: New Status in klibc package in Debian: New Bug description: Imported from Debian bug http://bugs.debian.org/1055694: Package: initramfs-tools Version: 0.142 Severity: normal X-Debbugs-Cc: konomikit...@gmail.com Dear Maintainer, After updating coreutils from 9.1-1 to 9.4-1+b1 the following lines appear when running update-initramfs -u: cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/cat' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/cpio' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/dd' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/dmesg' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/false' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/gunzip' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/kill' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/ln' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/ls' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/mkdir' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/mkfifo' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/mknod' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/mount' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/mv' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/nuke' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/readlink' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/resume' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/sh' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/sleep' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/sync' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/true' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/umount' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/uname' The lines seem to be a cosmetic issue only, but I cannot be entirely sure. -- Package-specific info: -- initramfs sizes -rw-r--r-- 1 root root 78M Nov 10 19:13 /boot/initrd.img-6.5.0-3-amd64 -rw-r--r-- 1 root root 78M Nov 10 19:13 /boot/initrd.img-6.5.0-4-amd64 -- /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-6.5.0-4-amd64 root=UUID=e7b71052-3dff-454b-9730-7b146ebdf115 ro preempt=full quiet -- /proc/filesystems btrfs fuseblk vfat -- lsmod Module Size Used by tcp_diag 12288 0 inet_diag 28672 1 tcp_diag vboxnetadp 28672 0 vboxnetflt 40960 0 vboxdrv 716800 2 vboxnetadp,vboxnetflt nvme_fabrics 32768 0 ccm20480 9 rfcomm102400 16 snd_seq_dummy 12288 0 snd_hrtimer12288 1 snd_seq 114688 7 snd_seq_dummy qrtr 57344 4 cmac 12288 3 algif_hash 12288 1 algif_skcipher 12288 1 af_alg 36864 6 algif_hash,algif_skcipher bnep 36864 2 zstd 12288 12 zram 40960 2 zsmalloc 36864 1 zram btusb 81920 0 btrtl 28672 1 btusb btbcm 24576 1 btusb intel_rapl_msr 20480 0 btintel57344 1 btusb intel_rapl_common 36864 1 intel_rapl_msr btmtk 12288 1 btusb binfmt_misc28672 1 bluetooth1126400 44 btrtl,btmtk,btintel,btbcm,bnep,btusb,rfcomm edac_mce_amd 40960 0 kvm_amd 184320 0 iwlmvm589824 0 kvm 1359872 1 kvm_amd mac80211 1392640 1 iwlmvm sha3_generic 16384 1 jitterentropy_rng 20480 1 snd_hda_codec_realtek 192512 1 irqbypass 12288 1 kvm snd_hda_codec_generic 114688 1 snd_hda_codec_realtek ledtrig_audio 12288 1 snd_hda_codec_generic snd_hda_codec_hdmi 90112 1 libarc412288 1 mac80211 ghash_clmulni_intel16384 0 sha512_ssse3 53248 1 snd_hda_intel 61440 4 sha512_generic 16384 1 sha512_ssse3 snd_usb_audio 417792 3 ctr12288 3 snd_intel_dspcfg 32768 1 snd_hda_intel snd_usbmidi_lib49152 1 snd_usb_audio snd_intel_sdw_acpi 16384 1 snd_intel_dspcfg drbg 49152 1 snd_rawmidi53248 1 snd_usbmidi_lib aesni_intel 36044
[Touch-packages] [Bug 2046336] Re: initramfs-tools: After updating coreutils cp: not replacing in console when running update-initramfs
** Changed in: klibc (Ubuntu) Assignee: (unassigned) => Skia (hyask) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to klibc in Ubuntu. https://bugs.launchpad.net/bugs/2046336 Title: initramfs-tools: After updating coreutils cp: not replacing in console when running update-initramfs Status in klibc package in Ubuntu: New Status in klibc package in Debian: New Bug description: Imported from Debian bug http://bugs.debian.org/1055694: Package: initramfs-tools Version: 0.142 Severity: normal X-Debbugs-Cc: konomikit...@gmail.com Dear Maintainer, After updating coreutils from 9.1-1 to 9.4-1+b1 the following lines appear when running update-initramfs -u: cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/cat' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/cpio' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/dd' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/dmesg' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/false' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/gunzip' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/kill' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/ln' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/ls' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/mkdir' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/mkfifo' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/mknod' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/mount' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/mv' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/nuke' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/readlink' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/resume' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/sh' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/sleep' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/sync' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/true' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/umount' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/uname' The lines seem to be a cosmetic issue only, but I cannot be entirely sure. -- Package-specific info: -- initramfs sizes -rw-r--r-- 1 root root 78M Nov 10 19:13 /boot/initrd.img-6.5.0-3-amd64 -rw-r--r-- 1 root root 78M Nov 10 19:13 /boot/initrd.img-6.5.0-4-amd64 -- /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-6.5.0-4-amd64 root=UUID=e7b71052-3dff-454b-9730-7b146ebdf115 ro preempt=full quiet -- /proc/filesystems btrfs fuseblk vfat -- lsmod Module Size Used by tcp_diag 12288 0 inet_diag 28672 1 tcp_diag vboxnetadp 28672 0 vboxnetflt 40960 0 vboxdrv 716800 2 vboxnetadp,vboxnetflt nvme_fabrics 32768 0 ccm20480 9 rfcomm102400 16 snd_seq_dummy 12288 0 snd_hrtimer12288 1 snd_seq 114688 7 snd_seq_dummy qrtr 57344 4 cmac 12288 3 algif_hash 12288 1 algif_skcipher 12288 1 af_alg 36864 6 algif_hash,algif_skcipher bnep 36864 2 zstd 12288 12 zram 40960 2 zsmalloc 36864 1 zram btusb 81920 0 btrtl 28672 1 btusb btbcm 24576 1 btusb intel_rapl_msr 20480 0 btintel57344 1 btusb intel_rapl_common 36864 1 intel_rapl_msr btmtk 12288 1 btusb binfmt_misc28672 1 bluetooth1126400 44 btrtl,btmtk,btintel,btbcm,bnep,btusb,rfcomm edac_mce_amd 40960 0 kvm_amd 184320 0 iwlmvm589824 0 kvm 1359872 1 kvm_amd mac80211 1392640 1 iwlmvm sha3_generic 16384 1 jitterentropy_rng 20480 1 snd_hda_codec_realtek 192512 1 irqbypass 12288 1 kvm snd_hda_codec_generic 114688 1 snd_hda_codec_realtek ledtrig_audio 12288 1 snd_hda_codec_generic snd_hda_codec_hdmi 90112 1 libarc412288 1 mac80211 ghash_clmulni_intel16384 0 sha512_ssse3 53248 1 snd_hda_intel 61440 4 sha512_generic 16384 1 sha512_ssse3 snd_usb_audio 417792 3 ctr12288 3 snd_intel_dspcfg 32768 1 snd_hda_intel snd_usbmidi_lib49152 1 snd_usb_audio snd_intel_sdw_acpi 16384 1 snd_intel_dspcfg drbg 49152 1 snd_rawmidi53248 1 snd_
[Touch-packages] [Bug 2049529] [NEW] Extra ZFS-related log line with `useradd -m -R /path`
Public bug reported: Hi, I was digging into fixing `autopkgtest`'s `unshare` testsuite, and the rabbit hole led me here. Here is a very quick reproducer, first: Start a fresh Ubuntu VM. Here is a quick path, but other ways should do fine: ``` $ cd /tmp $ autopkgtest-buildvm-ubuntu-cloud -a amd64 -r noble $ kvm -m 1G -snapshot -hda autopkgtest-noble-amd64.img ``` Now in the VM: ``` $ sudo apt install -y mmdebstrap $ mmdebstrap noble /tmp/rootfs [...] $ sudo useradd --create-home --root /tmp/rootfs user1 can't open /dev/null: No such file or directory ``` The line `can't open /dev/null: No such file or directory` is printed on `stderr`, and that's unexpected by the part of the code I was debugging in the first place. Digging a bit led me to that line that does the printing: https://git.launchpad.net/ubuntu/+source/shadow/tree/debian/patches/1015_add_zsys_support.patch#n69 There seem to me that there are multiple issues with that patch: * Why try to call `zsysctl` in every case without first checking that it would be relevant: ZFS is not even installed on the VM we just created, less alone it has any ZFS volume/pool/whatever. * Obviously, when creating a user in a `chroot`, `/dev/null` won't exist unless mapped, and `useradd` is perfectly aware of that, because it even does the `chroot` call itself! But why even try to mess with ZFS in the `chroot` case in the first place? >From what history @brian-murray told me, this patch was part of some ZFS experimentation in the past. Maybe that experimentation is now finished, and that patch could be dropped? At the very least it needs improvements, imho. ** Affects: shadow (Ubuntu) Importance: Undecided Status: New ** Tags: rls-nn-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shadow in Ubuntu. https://bugs.launchpad.net/bugs/2049529 Title: Extra ZFS-related log line with `useradd -m -R /path` Status in shadow package in Ubuntu: New Bug description: Hi, I was digging into fixing `autopkgtest`'s `unshare` testsuite, and the rabbit hole led me here. Here is a very quick reproducer, first: Start a fresh Ubuntu VM. Here is a quick path, but other ways should do fine: ``` $ cd /tmp $ autopkgtest-buildvm-ubuntu-cloud -a amd64 -r noble $ kvm -m 1G -snapshot -hda autopkgtest-noble-amd64.img ``` Now in the VM: ``` $ sudo apt install -y mmdebstrap $ mmdebstrap noble /tmp/rootfs [...] $ sudo useradd --create-home --root /tmp/rootfs user1 can't open /dev/null: No such file or directory ``` The line `can't open /dev/null: No such file or directory` is printed on `stderr`, and that's unexpected by the part of the code I was debugging in the first place. Digging a bit led me to that line that does the printing: https://git.launchpad.net/ubuntu/+source/shadow/tree/debian/patches/1015_add_zsys_support.patch#n69 There seem to me that there are multiple issues with that patch: * Why try to call `zsysctl` in every case without first checking that it would be relevant: ZFS is not even installed on the VM we just created, less alone it has any ZFS volume/pool/whatever. * Obviously, when creating a user in a `chroot`, `/dev/null` won't exist unless mapped, and `useradd` is perfectly aware of that, because it even does the `chroot` call itself! But why even try to mess with ZFS in the `chroot` case in the first place? From what history @brian-murray told me, this patch was part of some ZFS experimentation in the past. Maybe that experimentation is now finished, and that patch could be dropped? At the very least it needs improvements, imho. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/2049529/+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 2049529] Re: Extra ZFS-related log line with `useradd -m -R /path`
** Description changed: Hi, I was digging into fixing `autopkgtest`'s `unshare` testsuite, and the rabbit hole led me here. Here is a very quick reproducer, first: Start a fresh Ubuntu VM. Here is a quick path, but other ways should do fine: ``` $ cd /tmp $ autopkgtest-buildvm-ubuntu-cloud -a amd64 -r noble $ kvm -m 1G -snapshot -hda autopkgtest-noble-amd64.img ``` Now in the VM: ``` $ sudo apt install -y mmdebstrap $ mmdebstrap noble /tmp/rootfs [...] $ sudo useradd --create-home --root /tmp/rootfs user1 can't open /dev/null: No such file or directory ``` The line `can't open /dev/null: No such file or directory` is printed on `stderr`, and that's unexpected by the part of the code I was debugging in the first place. Digging a bit led me to that line that does the printing: https://git.launchpad.net/ubuntu/+source/shadow/tree/debian/patches/1015_add_zsys_support.patch#n69 There seem to me that there are multiple issues with that patch: * Why try to call `zsysctl` in every case without first checking that it would be relevant: ZFS is not even installed on the VM we just created, less alone it has any ZFS volume/pool/whatever. * Obviously, when creating a user in a `chroot`, `/dev/null` won't exist unless mapped, and `useradd` is perfectly aware of that, because it even does the `chroot` call itself! But why even try to mess with ZFS in the `chroot` case in the first place? From what history @brian-murray told me, this patch was part of some ZFS experimentation in the past. Maybe that experimentation is now finished, and that patch could be dropped? At the very least it needs improvements, imho. + + EDIT: Just for context on why this issue appears only now: I was trying + to fix the `unshare` testsuite in `autopkgtest`, which is pretty recent + (2022) (https://salsa.debian.org/ci- + team/autopkgtest/-/commit/d1671f94f68bce9a0c6793310a9f8b79b4e919a5) even + upstream on Debian, and has never worked yet on Ubuntu. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shadow in Ubuntu. https://bugs.launchpad.net/bugs/2049529 Title: Extra ZFS-related log line with `useradd -m -R /path` Status in shadow package in Ubuntu: New Bug description: Hi, I was digging into fixing `autopkgtest`'s `unshare` testsuite, and the rabbit hole led me here. Here is a very quick reproducer, first: Start a fresh Ubuntu VM. Here is a quick path, but other ways should do fine: ``` $ cd /tmp $ autopkgtest-buildvm-ubuntu-cloud -a amd64 -r noble $ kvm -m 1G -snapshot -hda autopkgtest-noble-amd64.img ``` Now in the VM: ``` $ sudo apt install -y mmdebstrap $ mmdebstrap noble /tmp/rootfs [...] $ sudo useradd --create-home --root /tmp/rootfs user1 can't open /dev/null: No such file or directory ``` The line `can't open /dev/null: No such file or directory` is printed on `stderr`, and that's unexpected by the part of the code I was debugging in the first place. Digging a bit led me to that line that does the printing: https://git.launchpad.net/ubuntu/+source/shadow/tree/debian/patches/1015_add_zsys_support.patch#n69 There seem to me that there are multiple issues with that patch: * Why try to call `zsysctl` in every case without first checking that it would be relevant: ZFS is not even installed on the VM we just created, less alone it has any ZFS volume/pool/whatever. * Obviously, when creating a user in a `chroot`, `/dev/null` won't exist unless mapped, and `useradd` is perfectly aware of that, because it even does the `chroot` call itself! But why even try to mess with ZFS in the `chroot` case in the first place? From what history @brian-murray told me, this patch was part of some ZFS experimentation in the past. Maybe that experimentation is now finished, and that patch could be dropped? At the very least it needs improvements, imho. EDIT: Just for context on why this issue appears only now: I was trying to fix the `unshare` testsuite in `autopkgtest`, which is pretty recent (2022) (https://salsa.debian.org/ci- team/autopkgtest/-/commit/d1671f94f68bce9a0c6793310a9f8b79b4e919a5) even upstream on Debian, and has never worked yet on Ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/2049529/+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 1980587] Re: text white not readable after selecting
Running `snap refresh --channel=24.10/stable subiquity` on a Jammy ISO shows an up-to-date Subiquity with the right colors. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kbd in Ubuntu. https://bugs.launchpad.net/bugs/1980587 Title: text white not readable after selecting Status in subiquity: New Status in kbd package in Ubuntu: New Bug description: Hello, I ran the subiquity installer with 22.04 Server on a Dell Optiplex 945 with Intel 945G. Some text fields and option fields like "Close" have the same color as their background when I select them. It only affect the blue/yellow subiquity version for legacy graphics, it does not affect the normal version in dark red that is run when I boot the same ISO in VBox. Either the text color or the background should be changed to make it readable. kind regards To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1980587/+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 1980587] Re: text white not readable after selecting
This seems to be still the case on Oracular, on a Thinkpad x201 (bug 2083857), though I can't reproduce it on Jammy .5. Here is a screenshot of colortest-8. The blue background seems to appear during the boot, when the setvtrgb unit is started, so I'm flagging this as also affecting `kbd`. That might even end-up being a kernel driver issue with some particular hardware. ** Attachment added: "IMG_20241008_101603.jpg" https://bugs.launchpad.net/subiquity/+bug/1980587/+attachment/5825869/+files/IMG_20241008_101603.jpg ** Also affects: kbd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kbd in Ubuntu. https://bugs.launchpad.net/bugs/1980587 Title: text white not readable after selecting Status in subiquity: New Status in kbd package in Ubuntu: New Bug description: Hello, I ran the subiquity installer with 22.04 Server on a Dell Optiplex 945 with Intel 945G. Some text fields and option fields like "Close" have the same color as their background when I select them. It only affect the blue/yellow subiquity version for legacy graphics, it does not affect the normal version in dark red that is run when I boot the same ISO in VBox. Either the text color or the background should be changed to make it readable. kind regards To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1980587/+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 2083825] [NEW] Release base-files for Oracular
Public bug reported: Get base-files released for Oracular. ** Affects: base-files (Ubuntu) Importance: Undecided Status: New -- 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/2083825 Title: Release base-files for Oracular Status in base-files package in Ubuntu: New Bug description: Get base-files released for Oracular. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/2083825/+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 2083825] Re: Release base-files for Oracular
Here comes a higher quality contribution after the review failed :-) ** Patch added: "oracular_v2.debdiff" https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/2083825/+attachment/5825631/+files/oracular_v2.debdiff -- 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/2083825 Title: Release base-files for Oracular Status in base-files package in Ubuntu: In Progress Bug description: Get base-files released for Oracular. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/2083825/+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 2083825] Re: Release base-files for Oracular
** Patch added: "oracular.debdiff" https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/2083825/+attachment/5825594/+files/oracular.debdiff -- 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/2083825 Title: Release base-files for Oracular Status in base-files package in Ubuntu: New Bug description: Get base-files released for Oracular. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/2083825/+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 2084923] [NEW] Upload for Plucky has wrong strings
Public bug reported: Just blocking the migration: https://launchpad.net/ubuntu/+source/base-files/13.5ubuntu1 os-release, issue, etc should say something like "Ubuntu Plucky Puffin (development branch)", not directly the version number. Looking at the diff for the Oracular release gives a hint: http://launchpadlibrarian.net/753020717/base-files_13.3ubuntu5_13.3ubuntu6.diff.gz ** Affects: base-files (Ubuntu) Importance: Undecided Status: New ** Tags: block-proposed ** Summary changed: - Upload for Plucky is wrong + Upload for Plucky has wrong strings -- 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/2084923 Title: Upload for Plucky has wrong strings Status in base-files package in Ubuntu: New Bug description: Just blocking the migration: https://launchpad.net/ubuntu/+source/base-files/13.5ubuntu1 os-release, issue, etc should say something like "Ubuntu Plucky Puffin (development branch)", not directly the version number. Looking at the diff for the Oracular release gives a hint: http://launchpadlibrarian.net/753020717/base-files_13.3ubuntu5_13.3ubuntu6.diff.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/2084923/+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 2085147] [NEW] Wrong timezone detection (always UTC)
Public bug reported:
With tzdata 2024b-1ubuntu1 (plucky-proposed), the timezone is wrongly
detected to be UTC, no matter what I do.
This is working fine with 2024a-4ubuntu1, which is what was released in
Oracular.
Simple reproducer:
```cpp
#include
#include
int main() {
const std::chrono::zoned_time cur_time{ std::chrono::current_zone(),
std::chrono::system_clock::now() };
std::cout << cur_time << '\n';
}
```
Compiled with `g++ -std=c++20 main.cpp`
```
$ ./a.out
2024-10-21 16:14:17.489489001 UTC
$ dpkg-query -W tzdata
tzdata 2024b-1ubuntu1
$ sudo apt install tzdata/oracular
[...]
$ dpkg-query -W tzdata
tzdata 2024a-4ubuntu1
$ ./a.out
2024-10-21 18:16:25.554620585 CEST
```
ProblemType: Bug
DistroRelease: Ubuntu 25.04
Package: tzdata 2024b-1ubuntu1
ProcVersionSignature: Ubuntu 6.8.0-45.45-generic 6.8.12
Uname: Linux 6.8.0-45-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.30.0-0ubuntu4
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: sway
Date: Mon Oct 21 14:11:36 2024
InstallationDate: Installed on 2023-08-02 (446 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
PackageArchitecture: all
ProcEnviron:
LANG=fr_FR.UTF-8
PATH=(custom, no user)
SHELL=/bin/zsh
TERM=alacritty
XDG_RUNTIME_DIR=
SourcePackage: tzdata
UpgradeStatus: Upgraded to plucky on 2024-06-12 (131 days ago)
** Affects: tzdata (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug block-proposed package-from-proposed plucky
wayland-session
** Tags added: block-proposed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tzdata in Ubuntu.
https://bugs.launchpad.net/bugs/2085147
Title:
Wrong timezone detection (always UTC)
Status in tzdata package in Ubuntu:
New
Bug description:
With tzdata 2024b-1ubuntu1 (plucky-proposed), the timezone is wrongly
detected to be UTC, no matter what I do.
This is working fine with 2024a-4ubuntu1, which is what was released
in Oracular.
Simple reproducer:
```cpp
#include
#include
int main() {
const std::chrono::zoned_time cur_time{ std::chrono::current_zone(),
std::chrono::system_clock::now()
};
std::cout << cur_time << '\n';
}
```
Compiled with `g++ -std=c++20 main.cpp`
```
$ ./a.out
2024-10-21 16:14:17.489489001 UTC
$ dpkg-query -W tzdata
tzdata2024b-1ubuntu1
$ sudo apt install tzdata/oracular
[...]
$ dpkg-query -W tzdata
tzdata2024a-4ubuntu1
$ ./a.out
2024-10-21 18:16:25.554620585 CEST
```
ProblemType: Bug
DistroRelease: Ubuntu 25.04
Package: tzdata 2024b-1ubuntu1
ProcVersionSignature: Ubuntu 6.8.0-45.45-generic 6.8.12
Uname: Linux 6.8.0-45-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.30.0-0ubuntu4
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: sway
Date: Mon Oct 21 14:11:36 2024
InstallationDate: Installed on 2023-08-02 (446 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
PackageArchitecture: all
ProcEnviron:
LANG=fr_FR.UTF-8
PATH=(custom, no user)
SHELL=/bin/zsh
TERM=alacritty
XDG_RUNTIME_DIR=
SourcePackage: tzdata
UpgradeStatus: Upgraded to plucky on 2024-06-12 (131 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2085147/+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 2085147] Re: Wrong timezone detection (always UTC)
Funny `UpgradeStatus: Upgraded to plucky on 2024-06-12 (131 days ago)`,
btw, but this is unrelated. :-)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tzdata in Ubuntu.
https://bugs.launchpad.net/bugs/2085147
Title:
Wrong timezone detection (always UTC)
Status in tzdata package in Ubuntu:
New
Bug description:
With tzdata 2024b-1ubuntu1 (plucky-proposed), the timezone is wrongly
detected to be UTC, no matter what I do.
This is working fine with 2024a-4ubuntu1, which is what was released
in Oracular.
Simple reproducer:
```cpp
#include
#include
int main() {
const std::chrono::zoned_time cur_time{ std::chrono::current_zone(),
std::chrono::system_clock::now()
};
std::cout << cur_time << '\n';
}
```
Compiled with `g++ -std=c++20 main.cpp`
```
$ ./a.out
2024-10-21 16:14:17.489489001 UTC
$ dpkg-query -W tzdata
tzdata2024b-1ubuntu1
$ sudo apt install tzdata/oracular
[...]
$ dpkg-query -W tzdata
tzdata2024a-4ubuntu1
$ ./a.out
2024-10-21 18:16:25.554620585 CEST
```
ProblemType: Bug
DistroRelease: Ubuntu 25.04
Package: tzdata 2024b-1ubuntu1
ProcVersionSignature: Ubuntu 6.8.0-45.45-generic 6.8.12
Uname: Linux 6.8.0-45-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.30.0-0ubuntu4
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: sway
Date: Mon Oct 21 14:11:36 2024
InstallationDate: Installed on 2023-08-02 (446 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
PackageArchitecture: all
ProcEnviron:
LANG=fr_FR.UTF-8
PATH=(custom, no user)
SHELL=/bin/zsh
TERM=alacritty
XDG_RUNTIME_DIR=
SourcePackage: tzdata
UpgradeStatus: Upgraded to plucky on 2024-06-12 (131 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2085147/+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 2079966] Re: tzdata 2024b release
I'm not running Oracular anymore, so can't really confirm, but Plucky is still pretty close (like almost identical), so this SRU might be hitting bug 2085147. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/2079966 Title: tzdata 2024b release Status in tzdata package in Ubuntu: Fix Committed Status in tzdata source package in Focal: New Status in tzdata source package in Jammy: New Status in tzdata source package in Noble: New Status in tzdata source package in Oracular: Fix Committed Bug description: [ Impact ] The 2024b release contains the following changes: * Improve historical data for Mexico, Mongolia, and Portugal. * System V names are now obsolescent. * The main data form now uses %z. [ Test Plan ] Test cases were added to the autopkgtest to cover the testing: * python: test_2024b * python-icu: test_2024b (only for focal and newer) So the test plan is to check that the autopkgtest succeeds. [ Other Info ] The autopkgtest for chrony is flaky on jammy and newer (see bug #2002910). There are backward-incompatible changes included: Names present only for compatibility with UNIX System V (last released in the 1990s) have been moved to 'backward'. These names, which for post-1970 timestamps mostly just duplicate data of geographical names, were confusing downstream uses. Names moved to 'backward' are now Links to geographical names if there is an exact match since 1970, and remain Zones otherwise. Those needing the previous TZDB behavior, which does not match any real-world clocks, can find the old entries in 'backzone'. (Problem reported by Justin Grant.) We need to exclude this change for the SRU since it can/will break user setup (e. g. the user from bug #2055718) and it will break a handful of tests (including dateparser, pandas, posrtesql-16). See https://bugs.debian.org/1084190 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2079966/+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 2085147] Re: Wrong timezone detection (always UTC)
Indeed, it works on my machine too :-)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tzdata in Ubuntu.
https://bugs.launchpad.net/bugs/2085147
Title:
Wrong timezone detection (always UTC)
Status in tzdata package in Ubuntu:
Fix Committed
Bug description:
With tzdata 2024b-1ubuntu1 (plucky-proposed), the timezone is wrongly
detected to be UTC, no matter what I do.
This is working fine with 2024a-4ubuntu1, which is what was released
in Oracular.
Simple reproducer:
```cpp
#include
#include
int main() {
const std::chrono::zoned_time cur_time{ std::chrono::current_zone(),
std::chrono::system_clock::now()
};
std::cout << cur_time << '\n';
}
```
Compiled with `g++ -std=c++20 main.cpp`
```
$ ./a.out
2024-10-21 16:14:17.489489001 UTC
$ dpkg-query -W tzdata
tzdata2024b-1ubuntu1
$ sudo apt install tzdata/oracular
[...]
$ dpkg-query -W tzdata
tzdata2024a-4ubuntu1
$ ./a.out
2024-10-21 18:16:25.554620585 CEST
```
ProblemType: Bug
DistroRelease: Ubuntu 25.04
Package: tzdata 2024b-1ubuntu1
ProcVersionSignature: Ubuntu 6.8.0-45.45-generic 6.8.12
Uname: Linux 6.8.0-45-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.30.0-0ubuntu4
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: sway
Date: Mon Oct 21 14:11:36 2024
InstallationDate: Installed on 2023-08-02 (446 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
PackageArchitecture: all
ProcEnviron:
LANG=fr_FR.UTF-8
PATH=(custom, no user)
SHELL=/bin/zsh
TERM=alacritty
XDG_RUNTIME_DIR=
SourcePackage: tzdata
UpgradeStatus: Upgraded to plucky on 2024-06-12 (131 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2085147/+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 2081271] Re: FTBFS on Oracular after test rebuild
** Changed in: whoopsie Status: In Progress => Fix Released ** Changed in: whoopsie Assignee: (unassigned) => Skia (hyask) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/2081271 Title: FTBFS on Oracular after test rebuild Status in Whoopsie: Fix Released Status in whoopsie package in Ubuntu: Fix Released Bug description: Following the Oracular test rebuild on 20240912, it appears Whoopsie FTBFS due to some helper binary that went away in libgcrypt-dev (`libgcrypt-config` shall be replaced by standard `pkg-config` calls). report: https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20240912-oracular-oracular.html#foundations-bugs-team build log: https://launchpadlibrarian.net/749245565/buildlog_ubuntu-oracular-amd64.whoopsie_0.2.77build3_BUILDING.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/whoopsie/+bug/2081271/+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 2089923] [NEW] Please merge 1:4.16.0-5 into plucky
Public bug reported: tracking bug Ubuntu plucky: 1:4.15.3-3ubuntu2 Debian unstable: 1:4.16.0-5 I'll see about tackling bug 2049529 along the way. ** Affects: shadow (Ubuntu) Importance: Undecided Assignee: Skia (hyask) Status: In Progress ** Tags: needs-merge ** Changed in: shadow (Ubuntu) Assignee: (unassigned) => Skia (hyask) ** Changed in: shadow (Ubuntu) Status: New => In Progress ** Description changed: tracking bug + + Ubuntu plucky: 1:4.15.3-3ubuntu2 + Debian unstable: 1:4.16.0-5 + + I'll see about tackling bug 2049529 along the way. ** Tags added: needs-merge -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shadow in Ubuntu. https://bugs.launchpad.net/bugs/2089923 Title: Please merge 1:4.16.0-5 into plucky Status in shadow package in Ubuntu: In Progress Bug description: tracking bug Ubuntu plucky: 1:4.15.3-3ubuntu2 Debian unstable: 1:4.16.0-5 I'll see about tackling bug 2049529 along the way. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/2089923/+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 2089923] Re: Please merge 1:4.16.0-5 into plucky
** Description changed:
tracking bug
Ubuntu plucky: 1:4.15.3-3ubuntu2
Debian unstable: 1:4.16.0-5
+ ### New Debian Changes ###
+
+ shadow (1:4.16.0-5) unstable; urgency=medium
+
+ [ Chris Hofstaedtler ]
+ * Always build with btrfs support on linux-any (Closes: #856557)
+ * debputy.manifest: merge path-metadata entries
+ * login.defs: remove info about write(1)
+ Which is not part of Debian trixie. (Closes: #1087519)
+
+ [ Pino Toscano ]
+ * Include , fixing the build on GNU/Hurd
+
+ -- Chris Hofstaedtler Fri, 15 Nov 2024 20:30:32
+ +0100
+
+ shadow (1:4.16.0-4) unstable; urgency=medium
+
+ * Drop Debian-only cppw, cpgr tools (Closes: #750752)
+ * Stop patching login, not installed anymore
+ * Define LOGIN_NAME_MAX on HURD
+ * Remove libsystemd-dev Build-Depends.
+ Only necessary for login(1).
+ * Stop building programs we do not install
+
+ -- Chris Hofstaedtler Tue, 06 Aug 2024 00:29:18
+ +0200
+
+ shadow (1:4.16.0-3) unstable; urgency=medium
+
+ * Upload to unstable.
+ * Fix FTBFS on hurd.
+ DEB_HOST_ARCH_OS was unset.
+
+ -- Chris Hofstaedtler Mon, 05 Aug 2024 17:21:27
+ +0200
+
+ shadow (1:4.16.0-2) experimental; urgency=medium
+
+ * passwd: switch Depends from login to login.defs
+ login will again be installed on fewer systems, but existing installs
+ will retain it (it is Protected: yes).
+ * Drop login package, to allow takeover by util-linux.
+ Move shadow.mo to Package: passwd, have passwd Replaces: older login.
+ * login.defs: ship manpage
+ * Re-add workarounds for tests in tests/tests directory.
+ 4.15.3 fixed this, but 4.16.0 happened earlier.
+
+ -- Chris Hofstaedtler Mon, 05 Aug 2024 02:36:29
+ +0200
+
+ shadow (1:4.16.0-1) experimental; urgency=medium
+
+ * New upstream version 4.16.0
+ * Rebase patches
+ * Split /etc/login.defs into its own binary package (Closes: #1074394)
+ * Rename libsubid4 to libsubid5 (soname bump)
+ * d/watch: add versionmangle for -rc
+
+ -- Chris Hofstaedtler Fri, 02 Aug 2024 17:35:29
+ +0200
+
+
+ ### Old Ubuntu Delta ###
+
+ shadow (1:4.15.3-3ubuntu2) oracular; urgency=medium
+
+ * d/p : disallow pure numeric user and group names (LP: #2076898)
+
+ -- Hector Cao Tue, 13 Aug 2024 12:15:06
+ +0200
+
+ shadow (1:4.15.3-3ubuntu1) oracular; urgency=medium
+
+ * Merge with Debian unstable. Remaining changes (LP: #2073338):
+ - d/p/* : Enable private home directories by default
+ - debian/{source_shadow.py,login.install}: Add apport hook
+ - debian/patches/1010_extrausers.patch:
+ + Add support to passwd for libnss-extrausers
+ + Add automatic detection of "extrausers" for usermod -G
+ - d/p/1011_extrausers_toggle.patch: extrausers support for
useradd/groupadd
+ - d/p/1012_extrausers_chfn.patch: --extrausers support for chfn tool
+ This patch has been refreshed to remove "implicit function declaration"
+ warning
+ - d/p/1013_extrausers_deluser.patch: --extrausers support for userdel
+ - d/p/1014_extrausers_delgroup.patch: --extrausers support for groupdel
+ This patch has been refreshed to remove "implicit function declaration"
+ warning
+ - d/p/1015_add_zsys_support.patch: zsys to handle home dir if available
+ - d/p/1016_extrausers_gpasswd.patch: extrausers support for gpasswd
+ - d/p/506_relaxed_usernames.patch, d/t/{control,numeric-username}:
+ + disallow purely numeric usernames
+ The patch has been integrated in debian but we still have to
+ keep the tests
+ - d/t/smoke: Extend for extrausers support
+ - Add some cursory tests for the extrausers features
+ - d/p/lp2063200: fix useradd group validation with extrausers (LP 2063200)
+
+ Dropped changes:
+ - debian/login.defs: Update documentation of USERGROUPS_ENAB/UMASK
+ Reason: Integrated upstream
+ - Fix ftbfs with -Werror=implicit-function-declaration
+ Reason: Integrated upstream
+
+ -- Hector Cao Mon, 29 Jul 2024 11:30:50
+ +0200
+
+
+
+
I'll see about tackling bug 2049529 along the way.
** Tags added: upgrade-software-version
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to shadow in Ubuntu.
https://bugs.launchpad.net/bugs/2089923
Title:
Please merge 1:4.16.0-5 into plucky
Status in shadow package in Ubuntu:
In Progress
Bug description:
tracking bug
Ubuntu plucky: 1:4.15.3-3ubuntu2
Debian unstable: 1:4.16.0-5
### New Debian Changes ###
shadow (1:4.16.0-5) unstable; urgency=medium
[ Chris Hofstaedtler ]
* Always build with btrfs support on linux-any (Closes: #856557)
* debputy.manifest: merge path-metadata entries
* login.defs: remove info about write(1)
Which is not part of Debian trixie. (Closes: #1087519)
[ Pino Toscano ]
* Include , fixing the build on GNU/Hurd
-- Chris Hofstaedtler Fri, 15 Nov 2024
[Touch-packages] [Bug 2089923] Re: Please merge 1:4.16.0-5 into plucky
Merge work is here:
* git-ubuntu branch:
https://git.launchpad.net/~hyask/ubuntu/+source/shadow/log/?h=skia/merge_lp2089923_plucky
* PPA: https://launchpad.net/~hyask/+archive/ubuntu/shadow-merge-lp2089923
Everything should be mostly done, but I'll run some more tests before
submitting the MP.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to shadow in Ubuntu.
https://bugs.launchpad.net/bugs/2089923
Title:
Please merge 1:4.16.0-5 into plucky
Status in shadow package in Ubuntu:
In Progress
Bug description:
tracking bug
Ubuntu plucky: 1:4.15.3-3ubuntu2
Debian unstable: 1:4.16.0-5
### New Debian Changes ###
shadow (1:4.16.0-5) unstable; urgency=medium
[ Chris Hofstaedtler ]
* Always build with btrfs support on linux-any (Closes: #856557)
* debputy.manifest: merge path-metadata entries
* login.defs: remove info about write(1)
Which is not part of Debian trixie. (Closes: #1087519)
[ Pino Toscano ]
* Include , fixing the build on GNU/Hurd
-- Chris Hofstaedtler Fri, 15 Nov 2024 20:30:32
+0100
shadow (1:4.16.0-4) unstable; urgency=medium
* Drop Debian-only cppw, cpgr tools (Closes: #750752)
* Stop patching login, not installed anymore
* Define LOGIN_NAME_MAX on HURD
* Remove libsystemd-dev Build-Depends.
Only necessary for login(1).
* Stop building programs we do not install
-- Chris Hofstaedtler Tue, 06 Aug 2024 00:29:18
+0200
shadow (1:4.16.0-3) unstable; urgency=medium
* Upload to unstable.
* Fix FTBFS on hurd.
DEB_HOST_ARCH_OS was unset.
-- Chris Hofstaedtler Mon, 05 Aug 2024 17:21:27
+0200
shadow (1:4.16.0-2) experimental; urgency=medium
* passwd: switch Depends from login to login.defs
login will again be installed on fewer systems, but existing installs
will retain it (it is Protected: yes).
* Drop login package, to allow takeover by util-linux.
Move shadow.mo to Package: passwd, have passwd Replaces: older login.
* login.defs: ship manpage
* Re-add workarounds for tests in tests/tests directory.
4.15.3 fixed this, but 4.16.0 happened earlier.
-- Chris Hofstaedtler Mon, 05 Aug 2024 02:36:29
+0200
shadow (1:4.16.0-1) experimental; urgency=medium
* New upstream version 4.16.0
* Rebase patches
* Split /etc/login.defs into its own binary package (Closes: #1074394)
* Rename libsubid4 to libsubid5 (soname bump)
* d/watch: add versionmangle for -rc
-- Chris Hofstaedtler Fri, 02 Aug 2024 17:35:29
+0200
### Old Ubuntu Delta ###
shadow (1:4.15.3-3ubuntu2) oracular; urgency=medium
* d/p : disallow pure numeric user and group names (LP: #2076898)
-- Hector Cao Tue, 13 Aug 2024 12:15:06
+0200
shadow (1:4.15.3-3ubuntu1) oracular; urgency=medium
* Merge with Debian unstable. Remaining changes (LP: #2073338):
- d/p/* : Enable private home directories by default
- debian/{source_shadow.py,login.install}: Add apport hook
- debian/patches/1010_extrausers.patch:
+ Add support to passwd for libnss-extrausers
+ Add automatic detection of "extrausers" for usermod -G
- d/p/1011_extrausers_toggle.patch: extrausers support for
useradd/groupadd
- d/p/1012_extrausers_chfn.patch: --extrausers support for chfn tool
This patch has been refreshed to remove "implicit function declaration"
warning
- d/p/1013_extrausers_deluser.patch: --extrausers support for userdel
- d/p/1014_extrausers_delgroup.patch: --extrausers support for groupdel
This patch has been refreshed to remove "implicit function declaration"
warning
- d/p/1015_add_zsys_support.patch: zsys to handle home dir if available
- d/p/1016_extrausers_gpasswd.patch: extrausers support for gpasswd
- d/p/506_relaxed_usernames.patch, d/t/{control,numeric-username}:
+ disallow purely numeric usernames
The patch has been integrated in debian but we still have to
keep the tests
- d/t/smoke: Extend for extrausers support
- Add some cursory tests for the extrausers features
- d/p/lp2063200: fix useradd group validation with extrausers (LP 2063200)
Dropped changes:
- debian/login.defs: Update documentation of USERGROUPS_ENAB/UMASK
Reason: Integrated upstream
- Fix ftbfs with -Werror=implicit-function-declaration
Reason: Integrated upstream
-- Hector Cao Mon, 29 Jul 2024 11:30:50
+0200
I'll see about tackling bug 2049529 along the way.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/2089923/+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 2049529] Re: Ubuntu delta causes `can't open /dev/null: No such file or directory` errors in minimal environments (chroot/unshare)
@didrocks you were one of the original authors of the `zsys` patch [1] that is now causing the bug, and iirc we discussed in the Hague that this patch could probably be dropped. Do you still support that decision, and validate that I can drop the patch in the upcoming merge of `shadow? [1]: https://git.launchpad.net/ubuntu/+source/shadow/tree/debian/patches/1015_add_zsys_support.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to adduser in Ubuntu. https://bugs.launchpad.net/bugs/2049529 Title: Ubuntu delta causes `can't open /dev/null: No such file or directory` errors in minimal environments (chroot/unshare) Status in adduser package in Ubuntu: Confirmed Status in shadow package in Ubuntu: Confirmed Status in adduser source package in Noble: Confirmed Status in shadow source package in Noble: Confirmed Bug description: Hi, I was digging into fixing `autopkgtest`'s `unshare` testsuite, and the rabbit hole led me here. Here is a very quick reproducer, first: Start a fresh Ubuntu VM. Here is a quick path, but other ways should do fine: ``` $ cd /tmp $ autopkgtest-buildvm-ubuntu-cloud -a amd64 -r noble $ kvm -m 1G -snapshot -hda autopkgtest-noble-amd64.img ``` Now in the VM: ``` $ sudo apt install -y mmdebstrap $ mmdebstrap noble /tmp/rootfs [...] $ sudo useradd --create-home --root /tmp/rootfs user1 can't open /dev/null: No such file or directory ``` The line `can't open /dev/null: No such file or directory` is printed on `stderr`, and that's unexpected by the part of the code I was debugging in the first place. Digging a bit led me to that line that does the printing: https://git.launchpad.net/ubuntu/+source/shadow/tree/debian/patches/1015_add_zsys_support.patch#n69 There seem to me that there are multiple issues with that patch: * Why try to call `zsysctl` in every case without first checking that it would be relevant: ZFS is not even installed on the VM we just created, less alone it has any ZFS volume/pool/whatever. * Obviously, when creating a user in a `chroot`, `/dev/null` won't exist unless mapped, and `useradd` is perfectly aware of that, because it even does the `chroot` call itself! But why even try to mess with ZFS in the `chroot` case in the first place? From what history @brian-murray told me, this patch was part of some ZFS experimentation in the past. Maybe that experimentation is now finished, and that patch could be dropped? At the very least it needs improvements, imho. EDIT: Just for context on why this issue appears only now: I was trying to fix the `unshare` testsuite in `autopkgtest`, which is pretty recent (2022) (https://salsa.debian.org/ci- team/autopkgtest/-/commit/d1671f94f68bce9a0c6793310a9f8b79b4e919a5) even upstream on Debian, and has never worked yet on Ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adduser/+bug/2049529/+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 2089923] Re: Please merge 1:4.16.0-5 into plucky
** Merge proposal linked:
https://code.launchpad.net/~hyask/ubuntu/+source/shadow/+git/shadow/+merge/477650
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to shadow in Ubuntu.
https://bugs.launchpad.net/bugs/2089923
Title:
Please merge 1:4.16.0-5 into plucky
Status in shadow package in Ubuntu:
In Progress
Bug description:
tracking bug
Ubuntu plucky: 1:4.15.3-3ubuntu2
Debian unstable: 1:4.16.0-5
### New Debian Changes ###
shadow (1:4.16.0-5) unstable; urgency=medium
[ Chris Hofstaedtler ]
* Always build with btrfs support on linux-any (Closes: #856557)
* debputy.manifest: merge path-metadata entries
* login.defs: remove info about write(1)
Which is not part of Debian trixie. (Closes: #1087519)
[ Pino Toscano ]
* Include , fixing the build on GNU/Hurd
-- Chris Hofstaedtler Fri, 15 Nov 2024 20:30:32
+0100
shadow (1:4.16.0-4) unstable; urgency=medium
* Drop Debian-only cppw, cpgr tools (Closes: #750752)
* Stop patching login, not installed anymore
* Define LOGIN_NAME_MAX on HURD
* Remove libsystemd-dev Build-Depends.
Only necessary for login(1).
* Stop building programs we do not install
-- Chris Hofstaedtler Tue, 06 Aug 2024 00:29:18
+0200
shadow (1:4.16.0-3) unstable; urgency=medium
* Upload to unstable.
* Fix FTBFS on hurd.
DEB_HOST_ARCH_OS was unset.
-- Chris Hofstaedtler Mon, 05 Aug 2024 17:21:27
+0200
shadow (1:4.16.0-2) experimental; urgency=medium
* passwd: switch Depends from login to login.defs
login will again be installed on fewer systems, but existing installs
will retain it (it is Protected: yes).
* Drop login package, to allow takeover by util-linux.
Move shadow.mo to Package: passwd, have passwd Replaces: older login.
* login.defs: ship manpage
* Re-add workarounds for tests in tests/tests directory.
4.15.3 fixed this, but 4.16.0 happened earlier.
-- Chris Hofstaedtler Mon, 05 Aug 2024 02:36:29
+0200
shadow (1:4.16.0-1) experimental; urgency=medium
* New upstream version 4.16.0
* Rebase patches
* Split /etc/login.defs into its own binary package (Closes: #1074394)
* Rename libsubid4 to libsubid5 (soname bump)
* d/watch: add versionmangle for -rc
-- Chris Hofstaedtler Fri, 02 Aug 2024 17:35:29
+0200
### Old Ubuntu Delta ###
shadow (1:4.15.3-3ubuntu2) oracular; urgency=medium
* d/p : disallow pure numeric user and group names (LP: #2076898)
-- Hector Cao Tue, 13 Aug 2024 12:15:06
+0200
shadow (1:4.15.3-3ubuntu1) oracular; urgency=medium
* Merge with Debian unstable. Remaining changes (LP: #2073338):
- d/p/* : Enable private home directories by default
- debian/{source_shadow.py,login.install}: Add apport hook
- debian/patches/1010_extrausers.patch:
+ Add support to passwd for libnss-extrausers
+ Add automatic detection of "extrausers" for usermod -G
- d/p/1011_extrausers_toggle.patch: extrausers support for
useradd/groupadd
- d/p/1012_extrausers_chfn.patch: --extrausers support for chfn tool
This patch has been refreshed to remove "implicit function declaration"
warning
- d/p/1013_extrausers_deluser.patch: --extrausers support for userdel
- d/p/1014_extrausers_delgroup.patch: --extrausers support for groupdel
This patch has been refreshed to remove "implicit function declaration"
warning
- d/p/1015_add_zsys_support.patch: zsys to handle home dir if available
- d/p/1016_extrausers_gpasswd.patch: extrausers support for gpasswd
- d/p/506_relaxed_usernames.patch, d/t/{control,numeric-username}:
+ disallow purely numeric usernames
The patch has been integrated in debian but we still have to
keep the tests
- d/t/smoke: Extend for extrausers support
- Add some cursory tests for the extrausers features
- d/p/lp2063200: fix useradd group validation with extrausers (LP 2063200)
Dropped changes:
- debian/login.defs: Update documentation of USERGROUPS_ENAB/UMASK
Reason: Integrated upstream
- Fix ftbfs with -Werror=implicit-function-declaration
Reason: Integrated upstream
-- Hector Cao Mon, 29 Jul 2024 11:30:50
+0200
I'll see about tackling bug 2049529 along the way.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/2089923/+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 2089923] Re: Please merge 1:4.16.0-5 into plucky
Autopkgtest is green on my local PPA (except for i386, but baseline is red
since at least focal here):
```
$ ppa tests hyask/shadow-merge-lp2089923
[...]
- shadow/1:4.16.0-5ubuntu1~skiappa4
+ ✅ shadow on plucky for amd64 @ 04.12.24 08:40:34 Log️ 🗒️
+ ✅ shadow on plucky for arm64 @ 04.12.24 10:02:33 Log️ 🗒️
+ ✅ shadow on plucky for armhf @ 04.12.24 08:41:14 Log️ 🗒️
+ ⛔ shadow on plucky for i386@ 04.12.24 08:34:09 Log️ 🗒️
• testbed BAD⛔
+ ✅ shadow on plucky for ppc64el @ 04.12.24 08:44:56 Log️ 🗒️
+ ✅ shadow on plucky for s390x @ 04.12.24 11:14:52 Log️ 🗒️
```
Reproducer for bug 2049529 also fails to reproduce with this new version on my
machine.
All in all, ready for review here:
https://code.launchpad.net/~hyask/ubuntu/+source/shadow/+git/shadow/+merge/477650
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to shadow in Ubuntu.
https://bugs.launchpad.net/bugs/2089923
Title:
Please merge 1:4.16.0-5 into plucky
Status in shadow package in Ubuntu:
In Progress
Bug description:
tracking bug
Ubuntu plucky: 1:4.15.3-3ubuntu2
Debian unstable: 1:4.16.0-5
### New Debian Changes ###
shadow (1:4.16.0-5) unstable; urgency=medium
[ Chris Hofstaedtler ]
* Always build with btrfs support on linux-any (Closes: #856557)
* debputy.manifest: merge path-metadata entries
* login.defs: remove info about write(1)
Which is not part of Debian trixie. (Closes: #1087519)
[ Pino Toscano ]
* Include , fixing the build on GNU/Hurd
-- Chris Hofstaedtler Fri, 15 Nov 2024 20:30:32
+0100
shadow (1:4.16.0-4) unstable; urgency=medium
* Drop Debian-only cppw, cpgr tools (Closes: #750752)
* Stop patching login, not installed anymore
* Define LOGIN_NAME_MAX on HURD
* Remove libsystemd-dev Build-Depends.
Only necessary for login(1).
* Stop building programs we do not install
-- Chris Hofstaedtler Tue, 06 Aug 2024 00:29:18
+0200
shadow (1:4.16.0-3) unstable; urgency=medium
* Upload to unstable.
* Fix FTBFS on hurd.
DEB_HOST_ARCH_OS was unset.
-- Chris Hofstaedtler Mon, 05 Aug 2024 17:21:27
+0200
shadow (1:4.16.0-2) experimental; urgency=medium
* passwd: switch Depends from login to login.defs
login will again be installed on fewer systems, but existing installs
will retain it (it is Protected: yes).
* Drop login package, to allow takeover by util-linux.
Move shadow.mo to Package: passwd, have passwd Replaces: older login.
* login.defs: ship manpage
* Re-add workarounds for tests in tests/tests directory.
4.15.3 fixed this, but 4.16.0 happened earlier.
-- Chris Hofstaedtler Mon, 05 Aug 2024 02:36:29
+0200
shadow (1:4.16.0-1) experimental; urgency=medium
* New upstream version 4.16.0
* Rebase patches
* Split /etc/login.defs into its own binary package (Closes: #1074394)
* Rename libsubid4 to libsubid5 (soname bump)
* d/watch: add versionmangle for -rc
-- Chris Hofstaedtler Fri, 02 Aug 2024 17:35:29
+0200
### Old Ubuntu Delta ###
shadow (1:4.15.3-3ubuntu2) oracular; urgency=medium
* d/p : disallow pure numeric user and group names (LP: #2076898)
-- Hector Cao Tue, 13 Aug 2024 12:15:06
+0200
shadow (1:4.15.3-3ubuntu1) oracular; urgency=medium
* Merge with Debian unstable. Remaining changes (LP: #2073338):
- d/p/* : Enable private home directories by default
- debian/{source_shadow.py,login.install}: Add apport hook
- debian/patches/1010_extrausers.patch:
+ Add support to passwd for libnss-extrausers
+ Add automatic detection of "extrausers" for usermod -G
- d/p/1011_extrausers_toggle.patch: extrausers support for
useradd/groupadd
- d/p/1012_extrausers_chfn.patch: --extrausers support for chfn tool
This patch has been refreshed to remove "implicit function declaration"
warning
- d/p/1013_extrausers_deluser.patch: --extrausers support for userdel
- d/p/1014_extrausers_delgroup.patch: --extrausers support for groupdel
This patch has been refreshed to remove "implicit function declaration"
warning
- d/p/1015_add_zsys_support.patch: zsys to handle home dir if available
- d/p/1016_extrausers_gpasswd.patch: extrausers support for gpasswd
- d/p/506_relaxed_usernames.patch, d/t/{control,numeric-username}:
+ disallow purely numeric usernames
The patch has been integrated in debian but we still have to
keep the tests
- d/t/smoke: Extend for extrausers support
- Add some cursory tests for the extrausers features
- d/p/lp2063200: fix useradd group validation with extrausers (LP 2063200)
Dropped changes:
- debian/login.defs: Update documentation of USERGROUPS_ENAB/UMASK
Reason: Integrated upstream
- Fix ftbfs wi
[Touch-packages] [Bug 2091862] Re: Please merge 2.40.2-13 into plucky
** Summary changed: - Please merge 2.40.2-12 into plucky + Please merge 2.40.2-13 into plucky ** Description changed: tracking bug Ubuntu plucky: 2.40.2-1ubuntu2 - Debian unstable: 2.40.2-12 + Debian unstable: 2.40.2-13 ### New Debian Changes ### + util-linux (2.40.2-13) unstable; urgency=medium + + * Add patches from upstream master branch fixing various bugs, + incl. fixes for cachestat on alpha. + + -- Chris Hofstaedtler Thu, 26 Dec 2024 13:52:42 + +0100 + util-linux (2.40.2-12) unstable; urgency=medium - * Stop building utmpdump, should not be necessary on wtmpdb systems - * Stop marking mkfds-socketpair test as failing - * Skip tmpfs-sensitive tests if fstype cannot be determined - * Amend NEWS entry to hint updating /root/.profile (Closes: #1088009) + * Stop building utmpdump, should not be necessary on wtmpdb systems + * Stop marking mkfds-socketpair test as failing + * Skip tmpfs-sensitive tests if fstype cannot be determined + * Amend NEWS entry to hint updating /root/.profile (Closes: #1088009) - -- Chris Hofstaedtler Fri, 06 Dec 2024 13:35:11 + -- Chris Hofstaedtler Fri, 06 Dec 2024 13:35:11 +0100 util-linux (2.40.2-11) unstable; urgency=medium - * tests: Temporarily mark fincore as failing in unshare - * Stop installing mesg, write + * tests: Temporarily mark fincore as failing in unshare + * Stop installing mesg, write - -- Chris Hofstaedtler Wed, 13 Nov 2024 13:03:57 + -- Chris Hofstaedtler Wed, 13 Nov 2024 13:03:57 +0100 util-linux (2.40.2-10) unstable; urgency=medium - * d/gbp.conf: set debian-branch to debian/unstable + * d/gbp.conf: set debian-branch to debian/unstable - -- Chris Hofstaedtler Sat, 02 Nov 2024 23:01:29 + -- Chris Hofstaedtler Sat, 02 Nov 2024 23:01:29 +0100 util-linux (2.40.2-9) unstable; urgency=medium - [ Pino Toscano ] - * Fix newgrp permissions only on Linux + [ Pino Toscano ] + * Fix newgrp permissions only on Linux - [ Chris Hofstaedtler ] - * Add upstream patch to fix tv_usec formatting (Closes: #1083006) + [ Chris Hofstaedtler ] + * Add upstream patch to fix tv_usec formatting (Closes: #1083006) - -- Chris Hofstaedtler Tue, 01 Oct 2024 20:13:03 + -- Chris Hofstaedtler Tue, 01 Oct 2024 20:13:03 +0200 util-linux (2.40.2-8) unstable; urgency=medium - * Mark nologin, newgrp binaries and man pages linux-any - * Install manpages using dh_install - * Import patches from upstream master - * newgrp: Optionally execute a program after group change - * Treat out of memory as error - * agetty: add "systemd" to --version output - * lscpu: optimize query virt pci device - * more: make sure we have data on stderr - Thanks to Gábor Németh (Closes: #1078122) - * Revert "Remove sg symlink to newgrp" - * Install sg symlink only on Linux - * Install write(1) manpage - * salsa-ci: add nodoc profile + * Mark nologin, newgrp binaries and man pages linux-any + * Install manpages using dh_install + * Import patches from upstream master + * newgrp: Optionally execute a program after group change + * Treat out of memory as error + * agetty: add "systemd" to --version output + * lscpu: optimize query virt pci device + * more: make sure we have data on stderr + Thanks to Gábor Németh (Closes: #1078122) + * Revert "Remove sg symlink to newgrp" + * Install sg symlink only on Linux + * Install write(1) manpage + * salsa-ci: add nodoc profile - -- Chris Hofstaedtler Mon, 09 Sep 2024 23:20:25 + -- Chris Hofstaedtler Mon, 09 Sep 2024 23:20:25 +0200 util-linux (2.40.2-7) unstable; urgency=medium - * login: update Section to admin (like in src:shadow) - Thanks to Johannes Schauer Marin Rodrigues - * Stop installing getopt-example.tcsh. - Per lintian tag csh-considered-harmful and policy section 10.4. + * login: update Section to admin (like in src:shadow) + Thanks to Johannes Schauer Marin Rodrigues + * Stop installing getopt-example.tcsh. + Per lintian tag csh-considered-harmful and policy section 10.4. - -- Chris Hofstaedtler Wed, 14 Aug 2024 12:29:34 + -- Chris Hofstaedtler Wed, 14 Aug 2024 12:29:34 +0200 util-linux (2.40.2-6) unstable; urgency=medium - * Remove sg symlink to newgrp. - Our newgrp does not take a command to execute, so stop pretending - it works like sg. At least for now, we will not have sg. - Addresses #1078122. + * Remove sg symlink to newgrp. + Our newgrp does not take a command to execute, so stop pretending + it works like sg. At least for now, we will not have sg. + Addresses #1078122. - -- Chris Hofstaedtler Wed, 07 Aug 2024 18:35:53 + -- Chris Hofstaedtler Wed, 07 Aug 2024 18:35:53 +0200 util-linux (2.40.2-5) unstable; urgency=medium - [ Chris Hofstaedtler ] - * Do not build login package for stage1 (Closes: #1078027) + [ Chris
[Touch-packages] [Bug 2089923] Re: Please merge 1:4.16.0-7 into plucky
** Summary changed:
- Please merge 1:4.16.0-5 into plucky
+ Please merge 1:4.16.0-7 into plucky
** Description changed:
tracking bug
Ubuntu plucky: 1:4.15.3-3ubuntu2
- Debian unstable: 1:4.16.0-5
+ Debian unstable: 1:4.16.0-7
### New Debian Changes ###
+ shadow (1:4.16.0-7) unstable; urgency=medium
+
+ [ Florent 'Skia' Jacquet ]
+ * d/patches: fix 'upstream' test suite
+
+ -- Chris Hofstaedtler Fri, 06 Dec 2024 13:51:40
+ +0100
+
+ shadow (1:4.16.0-6) unstable; urgency=medium
+
+ * Add NEWS entry about faillog (Closes: #1074320)
+
+ -- Chris Hofstaedtler Fri, 06 Dec 2024 13:29:54
+ +0100
+
shadow (1:4.16.0-5) unstable; urgency=medium
- [ Chris Hofstaedtler ]
- * Always build with btrfs support on linux-any (Closes: #856557)
- * debputy.manifest: merge path-metadata entries
- * login.defs: remove info about write(1)
- Which is not part of Debian trixie. (Closes: #1087519)
+ [ Chris Hofstaedtler ]
+ * Always build with btrfs support on linux-any (Closes: #856557)
+ * debputy.manifest: merge path-metadata entries
+ * login.defs: remove info about write(1)
+ Which is not part of Debian trixie. (Closes: #1087519)
- [ Pino Toscano ]
- * Include , fixing the build on GNU/Hurd
+ [ Pino Toscano ]
+ * Include , fixing the build on GNU/Hurd
- -- Chris Hofstaedtler Fri, 15 Nov 2024 20:30:32
+ -- Chris Hofstaedtler Fri, 15 Nov 2024 20:30:32
+0100
shadow (1:4.16.0-4) unstable; urgency=medium
- * Drop Debian-only cppw, cpgr tools (Closes: #750752)
- * Stop patching login, not installed anymore
- * Define LOGIN_NAME_MAX on HURD
- * Remove libsystemd-dev Build-Depends.
- Only necessary for login(1).
- * Stop building programs we do not install
+ * Drop Debian-only cppw, cpgr tools (Closes: #750752)
+ * Stop patching login, not installed anymore
+ * Define LOGIN_NAME_MAX on HURD
+ * Remove libsystemd-dev Build-Depends.
+ Only necessary for login(1).
+ * Stop building programs we do not install
- -- Chris Hofstaedtler Tue, 06 Aug 2024 00:29:18
+ -- Chris Hofstaedtler Tue, 06 Aug 2024 00:29:18
+0200
shadow (1:4.16.0-3) unstable; urgency=medium
- * Upload to unstable.
- * Fix FTBFS on hurd.
- DEB_HOST_ARCH_OS was unset.
+ * Upload to unstable.
+ * Fix FTBFS on hurd.
+ DEB_HOST_ARCH_OS was unset.
- -- Chris Hofstaedtler Mon, 05 Aug 2024 17:21:27
+ -- Chris Hofstaedtler Mon, 05 Aug 2024 17:21:27
+0200
shadow (1:4.16.0-2) experimental; urgency=medium
- * passwd: switch Depends from login to login.defs
- login will again be installed on fewer systems, but existing installs
- will retain it (it is Protected: yes).
- * Drop login package, to allow takeover by util-linux.
- Move shadow.mo to Package: passwd, have passwd Replaces: older login.
- * login.defs: ship manpage
- * Re-add workarounds for tests in tests/tests directory.
- 4.15.3 fixed this, but 4.16.0 happened earlier.
+ * passwd: switch Depends from login to login.defs
+ login will again be installed on fewer systems, but existing installs
+ will retain it (it is Protected: yes).
+ * Drop login package, to allow takeover by util-linux.
+ Move shadow.mo to Package: passwd, have passwd Replaces: older login.
+ * login.defs: ship manpage
+ * Re-add workarounds for tests in tests/tests directory.
+ 4.15.3 fixed this, but 4.16.0 happened earlier.
- -- Chris Hofstaedtler Mon, 05 Aug 2024 02:36:29
+ -- Chris Hofstaedtler Mon, 05 Aug 2024 02:36:29
+0200
shadow (1:4.16.0-1) experimental; urgency=medium
- * New upstream version 4.16.0
- * Rebase patches
- * Split /etc/login.defs into its own binary package (Closes: #1074394)
- * Rename libsubid4 to libsubid5 (soname bump)
- * d/watch: add versionmangle for -rc
+ * New upstream version 4.16.0
+ * Rebase patches
+ * Split /etc/login.defs into its own binary package (Closes: #1074394)
+ * Rename libsubid4 to libsubid5 (soname bump)
+ * d/watch: add versionmangle for -rc
- -- Chris Hofstaedtler Fri, 02 Aug 2024 17:35:29
+ -- Chris Hofstaedtler Fri, 02 Aug 2024 17:35:29
+0200
-
### Old Ubuntu Delta ###
shadow (1:4.15.3-3ubuntu2) oracular; urgency=medium
- * d/p : disallow pure numeric user and group names (LP: #2076898)
+ * d/p : disallow pure numeric user and group names (LP: #2076898)
- -- Hector Cao Tue, 13 Aug 2024 12:15:06
+ -- Hector Cao Tue, 13 Aug 2024 12:15:06
+0200
shadow (1:4.15.3-3ubuntu1) oracular; urgency=medium
- * Merge with Debian unstable. Remaining changes (LP: #2073338):
- - d/p/* : Enable private home directories by default
- - debian/{source_shadow.py,login.install}: Add apport hook
- - debian/patches/1010_extrausers.patch:
- + Add support to passwd for libnss-extrausers
- + Add automatic detection of "extrausers" for usermod -G
- - d/p/1011_extra
[Touch-packages] [Bug 2097469] Re: Prepare base-files update for .2 release
root@noble:/# cat /etc/{lsb,os}-release /etc/issue*
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=24.04
DISTRIB_CODENAME=noble
DISTRIB_DESCRIPTION="Ubuntu 24.04.1 LTS"
PRETTY_NAME="Ubuntu 24.04.1 LTS"
NAME="Ubuntu"
VERSION_ID="24.04"
VERSION="24.04.1 LTS (Noble Numbat)"
VERSION_CODENAME=noble
ID=ubuntu
ID_LIKE=debian
HOME_URL="https://www.ubuntu.com/";
SUPPORT_URL="https://help.ubuntu.com/";
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/";
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy";
UBUNTU_CODENAME=noble
LOGO=ubuntu-logo
Ubuntu 24.04.1 LTS \n \l
Ubuntu 24.04.1 LTS
root@noble:/# sed -i 's/noble-updates/noble-updates noble-proposed/'
/etc/apt/sources.list.d/ubuntu.sources
root@noble:/# apt update
Get:1 http://archive.ubuntu.com/ubuntu noble InRelease [256 kB]
Get:2 http://archive.ubuntu.com/ubuntu noble-updates InRelease [126 kB]
Get:3 http://archive.ubuntu.com/ubuntu noble-proposed InRelease [265 kB]
Get:4 http://archive.ubuntu.com/ubuntu noble-backports InRelease [126 kB]
Get:5 http://security.ubuntu.com/ubuntu noble-security InRelease [126 kB]
Get:6 http://archive.ubuntu.com/ubuntu noble/universe amd64 Packages [19.3 MB]
Get:7 http://archive.ubuntu.com/ubuntu noble/main amd64 Packages [1808 kB]
Get:8 http://archive.ubuntu.com/ubuntu noble/restricted amd64 Packages [117 kB]
Get:9 http://archive.ubuntu.com/ubuntu noble/multiverse amd64 Packages [331 kB]
Get:10 http://archive.ubuntu.com/ubuntu noble-updates/main amd64 Packages [1065
kB]
Get:11 http://archive.ubuntu.com/ubuntu noble-updates/restricted amd64 Packages
[799 kB]
Get:12 http://archive.ubuntu.com/ubuntu noble-updates/universe amd64 Packages
[1313 kB]
Get:13 http://archive.ubuntu.com/ubuntu noble-updates/multiverse amd64 Packages
[20.1 kB]
Get:14 http://archive.ubuntu.com/ubuntu noble-proposed/restricted amd64
Packages [214 kB]
Get:15 http://archive.ubuntu.com/ubuntu noble-proposed/main amd64 Packages [298
kB]
Get:16 http://archive.ubuntu.com/ubuntu noble-proposed/universe amd64 Packages
[600 kB]
Get:17 http://archive.ubuntu.com/ubuntu noble-proposed/multiverse amd64
Packages [8796 B]
Get:18 http://archive.ubuntu.com/ubuntu noble-backports/universe amd64 Packages
[15.1 kB]
Get:19 http://security.ubuntu.com/ubuntu noble-security/multiverse amd64
Packages [15.5 kB]
Get:20 http://security.ubuntu.com/ubuntu noble-security/main amd64 Packages
[775 kB]
Get:21 http://security.ubuntu.com/ubuntu noble-security/universe amd64 Packages
[1039 kB]
Get:22 http://security.ubuntu.com/ubuntu noble-security/restricted amd64
Packages [784 kB]
Fetched 29.4 MB in 3s (10.2 MB/s)
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
12 packages can be upgraded. Run 'apt list --upgradable' to see them.
root@noble:/# apt install base-files/noble-proposed
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Selected version '13ubuntu10.2' (Ubuntu:24.04/noble-proposed [amd64]) for
'base-files'
The following packages will be upgraded:
base-files
1 upgraded, 0 newly installed, 0 to remove and 12 not upgraded.
Need to get 73.2 kB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 http://archive.ubuntu.com/ubuntu noble-proposed/main amd64 base-files
amd64 13ubuntu10.2 [73.2 kB]
Fetched 73.2 kB in 0s (566 kB/s)
debconf: delaying package configuration, since apt-utils is not installed
(Reading database ... 4383 files and directories currently installed.)
Preparing to unpack .../base-files_13ubuntu10.2_amd64.deb ...
Unpacking base-files (13ubuntu10.2) over (13ubuntu10.1) ...
Setting up base-files (13ubuntu10.2) ...
Installing new version of config file /etc/issue ...
Installing new version of config file /etc/issue.net ...
Installing new version of config file /etc/lsb-release ...
root@noble:/# cat /etc/{lsb,os}-release /etc/issue*
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=24.04
DISTRIB_CODENAME=noble
DISTRIB_DESCRIPTION="Ubuntu 24.04.2 LTS"
PRETTY_NAME="Ubuntu 24.04.2 LTS"
NAME="Ubuntu"
VERSION_ID="24.04"
VERSION="24.04.2 LTS (Noble Numbat)"
VERSION_CODENAME=noble
ID=ubuntu
ID_LIKE=debian
HOME_URL="https://www.ubuntu.com/";
SUPPORT_URL="https://help.ubuntu.com/";
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/";
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy";
UBUNTU_CODENAME=noble
LOGO=ubuntu-logo
Ubuntu 24.04.2 LTS \n \l
Ubuntu 24.04.2 LTS
root@noble:/#
All good!
** Tags removed: verification-needed verification-needed-noble
** Tags added: verification-done verification-done-noble
--
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/2097469
Title:
Prepare base-files update for .2 release
Status in base-files package in Ubuntu:
Invalid
Status in base-files source package in Noble:
Fix Committed
Bug description:
Prepare base-files update for /etc/is
[Touch-packages] [Bug 2096327] Re: apport cannot upload blobs to launchpad - X-Launchpad-Blob-Token missing from http response -> "assert ticket"
** Changed in: apport (Ubuntu Noble) Importance: Undecided => Critical -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/2096327 Title: apport cannot upload blobs to launchpad - X-Launchpad-Blob-Token missing from http response -> "assert ticket" Status in Apport: Fix Committed Status in Launchpad itself: Fix Released Status in apport package in Ubuntu: Fix Released Status in apport source package in Focal: New Status in apport source package in Jammy: New Status in apport source package in Noble: New Status in apport source package in Oracular: New Bug description: [ Impact ] The apport code, through the use of Python's `email` package, isn't HTTP 1.1 compliant when crafting the payload to the LP +storeblob endpoint, using LF as a line separator rather than CRLF. A recent update to the `multipart` dependency of LP made it stricter when parsing this kind of payload, making any attempt to file a bug through Apport (e.g. `ubuntu-bug foo`) fail miserably. The issue was worked around by rolling back that update, but it's not a longterm solution, as it's probably better for everyone if LP stays up-to-date on its dependencies. This impacts 24.04.2 as the workaround needs to stay in place as long as our "default" ISOs ship a buggy apport. [ Test plan ] The newer version of `multipart` is still deployed on the qastaging LP instance, which makes testing the fix fairly simple. We're using the chaos-marmosets package since it's maintained by members of the Apport team so nobody should be too annoyed by the noise. ``` # File a bug in qastaging, and manually inspect the contents of the attached files APPORT_LAUNCHPAD_INSTANCE=qastaging ubuntu-bug chaos-marmosets # Do the same on the prod instance as a control experiment. # Don't forget to close the bug afterwards ;) ubuntu-bug chaos-marmosets ``` [ Where problems could occur ] Fixing the problem with the new dependency could regress against the workaround, which is why the test plan tests against both prod and qastaging. Messing with the way the payload is crafted could potentially corrupt the attached files, which is why the tester must actually *look* at the attached data. [ Original report ] The tale is slightly convoluted. After doing an "apt upgrade" yesterday, xsane and simple-scan started failing: scanner detected, but could not scan. Trying to report it with ubuntu-bug then crashed with the following error: $ sudo ubuntu-bug simple-scan Traceback (most recent call last): File "/usr/share/apport/apport-gtk", line 650, in app.run_argv() File "/usr/lib/python3/dist-packages/apport/ui.py", line 917, in run_argv return self.run_report_bug() ^ File "/usr/lib/python3/dist-packages/apport/ui.py", line 740, in run_report_bug self.file_report() File "/usr/lib/python3/dist-packages/apport/ui.py", line 1788, in file_report upthread.exc_raise() File "/usr/lib/python3/dist-packages/apport/REThread.py", line 67, in exc_raise raise self._exception[1].with_traceback(self._exception[2]) File "/usr/lib/python3/dist-packages/apport/REThread.py", line 42, in run self._retval = self.__target(*self.__args, **self.__kwargs) File "/usr/lib/python3/dist-packages/apport/crashdb_impl/launchpad.py", line 222, in upload ticket = upload_blob(blob_file, progress_callback, hostname=self.get_hostname()) ^^^ File "/usr/lib/python3/dist-packages/apport/crashdb_impl/launchpad.py", line 1246, in upload_blob assert ticket ^^ AssertionError This is a blocker for me. To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/2096327/+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 2069834] Re: systemd defaulting to tmpfs for /tmp causes enospc errors
** Changed in: autopkgtest (Ubuntu Noble) 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/2069834 Title: systemd defaulting to tmpfs for /tmp causes enospc errors Status in Auto Package Testing: Incomplete Status in autopkgtest package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Won't Fix Status in autopkgtest source package in Jammy: Fix Released Status in autopkgtest source package in Noble: Fix Released Bug description: [Impact] systemd 256 changes behavior and makes /tmp a tmpfs by default. This causes some problems with packages for which the sources weight more than the tmpfs size, and this case often happen on the testbed because they usually don't have a lot of RAM by default (see test case below for a concrete example). [Test case] autopkgtest-buildvm-ubuntu-cloud -a amd64 -r oracular autopkgtest --shell gzip -- qemu ./autopkgtest-oracular-amd64.img Jump to the shell when prompted and verify the following: mount -t tmpfs | grep /tmp # this returns nothing, /tmp is not a tmpfs anymore stat /etc/systemd/system/tmp.mount # this file has correctly been created, which explains the previous result Since the default RAM given to the QEMU VM is 2GB and the libreoffice source take more than 4GB, this should have no trouble running in a "No space left on device" error. [Fix] https://salsa.debian.org/ci-team/autopkgtest/-/merge_requests/362 This was release in autopkgtest 5.36, currently in the process of being SRU'd to Jammy and Noble in bug #2071609. [Regression potential] The current SRU has a lot of unrelated changes. While this increases the chances of regression, this also come with a broader test suite, increasing test coverage, and so regressions should only happen in corner-cases, hopefully less important as the current lack of this /tmp bug fix. [Original bug report] Debian systemd now mounts a tmpfs on /tmp by default; relevant d/changelog entry: systemd (256~rc3-3) unstable; urgency=medium * Make /tmp/ a tmpfs by default. Restore the upstream default and make /tmp/ a tmpfs. Can be overridden with: touch /etc/systemd/system/tmp.mount or: systemctl mask tmp.mount Ubuntu is aligning to this, however this means that available space under /tmp is limited to the half of the available ram. That is sometimes not enough to unpack source trees in /tmp, see for example [1]. We need to to decide how to deal with this. Possibilities I can think about: 1. Disable the tmpfs tmp.mount, as suggested in the d/changelog entry. To be done in setup-testbed. Good: easy. Bad: deviates from the Ubuntu defaults, requires rebuilding the images. 2. Make autopkgtest use /var/tmp. Good: we stick to the defaults: Bad: requires non trivial changes in src:autopkgtest, which makes assumptions on stuff being in /tmp, on /tmp being cleared on reboots, ... This under the assumption that the switch to a tmpfs has been discussed, and we want it in Ubuntu. [1] https://autopkgtest.ubuntu.com/results/autopkgtest- oracular/oracular/ppc64el/c/ceph/20240618_194813_d6efc@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/auto-package-testing/+bug/2069834/+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 2089923] Re: Please merge 1:4.16.0-5 into plucky
During review, we saw with @schopin that this requires uploading `util-
linux` at the same time, because of the `login` binary package moving
from `shadow` to `util-linux`. This is handled in bug 2091862.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to shadow in Ubuntu.
https://bugs.launchpad.net/bugs/2089923
Title:
Please merge 1:4.16.0-5 into plucky
Status in shadow package in Ubuntu:
In Progress
Bug description:
tracking bug
Ubuntu plucky: 1:4.15.3-3ubuntu2
Debian unstable: 1:4.16.0-5
### New Debian Changes ###
shadow (1:4.16.0-5) unstable; urgency=medium
[ Chris Hofstaedtler ]
* Always build with btrfs support on linux-any (Closes: #856557)
* debputy.manifest: merge path-metadata entries
* login.defs: remove info about write(1)
Which is not part of Debian trixie. (Closes: #1087519)
[ Pino Toscano ]
* Include , fixing the build on GNU/Hurd
-- Chris Hofstaedtler Fri, 15 Nov 2024 20:30:32
+0100
shadow (1:4.16.0-4) unstable; urgency=medium
* Drop Debian-only cppw, cpgr tools (Closes: #750752)
* Stop patching login, not installed anymore
* Define LOGIN_NAME_MAX on HURD
* Remove libsystemd-dev Build-Depends.
Only necessary for login(1).
* Stop building programs we do not install
-- Chris Hofstaedtler Tue, 06 Aug 2024 00:29:18
+0200
shadow (1:4.16.0-3) unstable; urgency=medium
* Upload to unstable.
* Fix FTBFS on hurd.
DEB_HOST_ARCH_OS was unset.
-- Chris Hofstaedtler Mon, 05 Aug 2024 17:21:27
+0200
shadow (1:4.16.0-2) experimental; urgency=medium
* passwd: switch Depends from login to login.defs
login will again be installed on fewer systems, but existing installs
will retain it (it is Protected: yes).
* Drop login package, to allow takeover by util-linux.
Move shadow.mo to Package: passwd, have passwd Replaces: older login.
* login.defs: ship manpage
* Re-add workarounds for tests in tests/tests directory.
4.15.3 fixed this, but 4.16.0 happened earlier.
-- Chris Hofstaedtler Mon, 05 Aug 2024 02:36:29
+0200
shadow (1:4.16.0-1) experimental; urgency=medium
* New upstream version 4.16.0
* Rebase patches
* Split /etc/login.defs into its own binary package (Closes: #1074394)
* Rename libsubid4 to libsubid5 (soname bump)
* d/watch: add versionmangle for -rc
-- Chris Hofstaedtler Fri, 02 Aug 2024 17:35:29
+0200
### Old Ubuntu Delta ###
shadow (1:4.15.3-3ubuntu2) oracular; urgency=medium
* d/p : disallow pure numeric user and group names (LP: #2076898)
-- Hector Cao Tue, 13 Aug 2024 12:15:06
+0200
shadow (1:4.15.3-3ubuntu1) oracular; urgency=medium
* Merge with Debian unstable. Remaining changes (LP: #2073338):
- d/p/* : Enable private home directories by default
- debian/{source_shadow.py,login.install}: Add apport hook
- debian/patches/1010_extrausers.patch:
+ Add support to passwd for libnss-extrausers
+ Add automatic detection of "extrausers" for usermod -G
- d/p/1011_extrausers_toggle.patch: extrausers support for
useradd/groupadd
- d/p/1012_extrausers_chfn.patch: --extrausers support for chfn tool
This patch has been refreshed to remove "implicit function declaration"
warning
- d/p/1013_extrausers_deluser.patch: --extrausers support for userdel
- d/p/1014_extrausers_delgroup.patch: --extrausers support for groupdel
This patch has been refreshed to remove "implicit function declaration"
warning
- d/p/1015_add_zsys_support.patch: zsys to handle home dir if available
- d/p/1016_extrausers_gpasswd.patch: extrausers support for gpasswd
- d/p/506_relaxed_usernames.patch, d/t/{control,numeric-username}:
+ disallow purely numeric usernames
The patch has been integrated in debian but we still have to
keep the tests
- d/t/smoke: Extend for extrausers support
- Add some cursory tests for the extrausers features
- d/p/lp2063200: fix useradd group validation with extrausers (LP 2063200)
Dropped changes:
- debian/login.defs: Update documentation of USERGROUPS_ENAB/UMASK
Reason: Integrated upstream
- Fix ftbfs with -Werror=implicit-function-declaration
Reason: Integrated upstream
-- Hector Cao Mon, 29 Jul 2024 11:30:50
+0200
I'll see about tackling bug 2049529 along the way.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/2089923/+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 2091862] Re: Please merge 2.40.2-12 into plucky
** Merge proposal linked: https://code.launchpad.net/~hyask/ubuntu/+source/util-linux/+git/util-linux/+merge/478455 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/2091862 Title: Please merge 2.40.2-12 into plucky Status in util-linux package in Ubuntu: In Progress Bug description: tracking bug Ubuntu plucky: 2.40.2-1ubuntu2 Debian unstable: 2.40.2-12 ### New Debian Changes ### util-linux (2.40.2-12) unstable; urgency=medium * Stop building utmpdump, should not be necessary on wtmpdb systems * Stop marking mkfds-socketpair test as failing * Skip tmpfs-sensitive tests if fstype cannot be determined * Amend NEWS entry to hint updating /root/.profile (Closes: #1088009) -- Chris Hofstaedtler Fri, 06 Dec 2024 13:35:11 +0100 util-linux (2.40.2-11) unstable; urgency=medium * tests: Temporarily mark fincore as failing in unshare * Stop installing mesg, write -- Chris Hofstaedtler Wed, 13 Nov 2024 13:03:57 +0100 util-linux (2.40.2-10) unstable; urgency=medium * d/gbp.conf: set debian-branch to debian/unstable -- Chris Hofstaedtler Sat, 02 Nov 2024 23:01:29 +0100 util-linux (2.40.2-9) unstable; urgency=medium [ Pino Toscano ] * Fix newgrp permissions only on Linux [ Chris Hofstaedtler ] * Add upstream patch to fix tv_usec formatting (Closes: #1083006) -- Chris Hofstaedtler Tue, 01 Oct 2024 20:13:03 +0200 util-linux (2.40.2-8) unstable; urgency=medium * Mark nologin, newgrp binaries and man pages linux-any * Install manpages using dh_install * Import patches from upstream master * newgrp: Optionally execute a program after group change * Treat out of memory as error * agetty: add "systemd" to --version output * lscpu: optimize query virt pci device * more: make sure we have data on stderr Thanks to Gábor Németh (Closes: #1078122) * Revert "Remove sg symlink to newgrp" * Install sg symlink only on Linux * Install write(1) manpage * salsa-ci: add nodoc profile -- Chris Hofstaedtler Mon, 09 Sep 2024 23:20:25 +0200 util-linux (2.40.2-7) unstable; urgency=medium * login: update Section to admin (like in src:shadow) Thanks to Johannes Schauer Marin Rodrigues * Stop installing getopt-example.tcsh. Per lintian tag csh-considered-harmful and policy section 10.4. -- Chris Hofstaedtler Wed, 14 Aug 2024 12:29:34 +0200 util-linux (2.40.2-6) unstable; urgency=medium * Remove sg symlink to newgrp. Our newgrp does not take a command to execute, so stop pretending it works like sg. At least for now, we will not have sg. Addresses #1078122. -- Chris Hofstaedtler Wed, 07 Aug 2024 18:35:53 +0200 util-linux (2.40.2-5) unstable; urgency=medium [ Chris Hofstaedtler ] * Do not build login package for stage1 (Closes: #1078027) [ Sven Joachim ] * login: fix installing of /etc/pam.d/login (Closes: #1078036) -- Chris Hofstaedtler Tue, 06 Aug 2024 21:19:26 +0200 util-linux (2.40.2-4) unstable; urgency=medium * Upload to unstable. [ Chris Hofstaedtler ] * Bump Standards-Version to 4.7.0 * Patch login to support our PAM setup [ Helmut Grohne ] * Drop lastlog2 and libpam-lastlog2 from stage1 build (Closes: #1077967) -- Chris Hofstaedtler Mon, 05 Aug 2024 17:20:49 +0200 util-linux (2.40.2-3) experimental; urgency=medium * Take over login package from src:shadow (Closes: #833256) -- Chris Hofstaedtler Mon, 05 Aug 2024 02:54:35 +0200 util-linux (2.40.2-2) unstable; urgency=medium [ Pino Toscano ] * d/lastlog2.install: install systemd files only on Linux. -- Chris Hofstaedtler Mon, 05 Aug 2024 00:31:55 +0200 ### Old Ubuntu Delta ### util-linux (2.40.2-1ubuntu2) plucky; urgency=medium * Read the ext4 superblock with O_DIRECT if the first read produces a checksum failure. This fixes a race where the underlying superblock can be changed in memory but not on disk, resulting in checksum failures which in turn causes systemd-udevd to remove by-uuid and by-label symlinks. (LP: #2090972) - d/p/ubuntu/lp2090972-libblkid-fix-spurious-ext-superblock-checksum-mismat.patch -- Matthew Ruffell Thu, 05 Dec 2024 13:02:57 +1300 util-linux (2.40.2-1ubuntu1) oracular; urgency=medium * Merge with Debian unstable (LP: #2072813). Remaining changes: - Disable brand new feature with --disable-libmount-mountfd-support that causes inability to deploy MAAS LP #2037417 - Add sulogin-fallback-static-sh.patch: Add support for /bin/static-sh as fallback if the regular shell fails to execute. Patch ported from sysvinit. (see LP #505887) - Add sulogin-lockedpwd.patch: Make sure file systems can be fixed on
[Touch-packages] [Bug 2091862] [NEW] Please merge 2.40.2-12 into plucky
id bit from both wall and write. [Fixed in 2.39.3-11] - move more to /usr/bin [Fixed in 2.40.1-8.1] -- Chris Peterson Fri, 09 Aug 2024 15:48:13 -0700 ** Affects: util-linux (Ubuntu) Importance: Undecided Assignee: Skia (hyask) Status: In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/2091862 Title: Please merge 2.40.2-12 into plucky Status in util-linux package in Ubuntu: In Progress Bug description: tracking bug Ubuntu plucky: 2.40.2-1ubuntu2 Debian unstable: 2.40.2-12 ### New Debian Changes ### util-linux (2.40.2-12) unstable; urgency=medium * Stop building utmpdump, should not be necessary on wtmpdb systems * Stop marking mkfds-socketpair test as failing * Skip tmpfs-sensitive tests if fstype cannot be determined * Amend NEWS entry to hint updating /root/.profile (Closes: #1088009) -- Chris Hofstaedtler Fri, 06 Dec 2024 13:35:11 +0100 util-linux (2.40.2-11) unstable; urgency=medium * tests: Temporarily mark fincore as failing in unshare * Stop installing mesg, write -- Chris Hofstaedtler Wed, 13 Nov 2024 13:03:57 +0100 util-linux (2.40.2-10) unstable; urgency=medium * d/gbp.conf: set debian-branch to debian/unstable -- Chris Hofstaedtler Sat, 02 Nov 2024 23:01:29 +0100 util-linux (2.40.2-9) unstable; urgency=medium [ Pino Toscano ] * Fix newgrp permissions only on Linux [ Chris Hofstaedtler ] * Add upstream patch to fix tv_usec formatting (Closes: #1083006) -- Chris Hofstaedtler Tue, 01 Oct 2024 20:13:03 +0200 util-linux (2.40.2-8) unstable; urgency=medium * Mark nologin, newgrp binaries and man pages linux-any * Install manpages using dh_install * Import patches from upstream master * newgrp: Optionally execute a program after group change * Treat out of memory as error * agetty: add "systemd" to --version output * lscpu: optimize query virt pci device * more: make sure we have data on stderr Thanks to Gábor Németh (Closes: #1078122) * Revert "Remove sg symlink to newgrp" * Install sg symlink only on Linux * Install write(1) manpage * salsa-ci: add nodoc profile -- Chris Hofstaedtler Mon, 09 Sep 2024 23:20:25 +0200 util-linux (2.40.2-7) unstable; urgency=medium * login: update Section to admin (like in src:shadow) Thanks to Johannes Schauer Marin Rodrigues * Stop installing getopt-example.tcsh. Per lintian tag csh-considered-harmful and policy section 10.4. -- Chris Hofstaedtler Wed, 14 Aug 2024 12:29:34 +0200 util-linux (2.40.2-6) unstable; urgency=medium * Remove sg symlink to newgrp. Our newgrp does not take a command to execute, so stop pretending it works like sg. At least for now, we will not have sg. Addresses #1078122. -- Chris Hofstaedtler Wed, 07 Aug 2024 18:35:53 +0200 util-linux (2.40.2-5) unstable; urgency=medium [ Chris Hofstaedtler ] * Do not build login package for stage1 (Closes: #1078027) [ Sven Joachim ] * login: fix installing of /etc/pam.d/login (Closes: #1078036) -- Chris Hofstaedtler Tue, 06 Aug 2024 21:19:26 +0200 util-linux (2.40.2-4) unstable; urgency=medium * Upload to unstable. [ Chris Hofstaedtler ] * Bump Standards-Version to 4.7.0 * Patch login to support our PAM setup [ Helmut Grohne ] * Drop lastlog2 and libpam-lastlog2 from stage1 build (Closes: #1077967) -- Chris Hofstaedtler Mon, 05 Aug 2024 17:20:49 +0200 util-linux (2.40.2-3) experimental; urgency=medium * Take over login package from src:shadow (Closes: #833256) -- Chris Hofstaedtler Mon, 05 Aug 2024 02:54:35 +0200 util-linux (2.40.2-2) unstable; urgency=medium [ Pino Toscano ] * d/lastlog2.install: install systemd files only on Linux. -- Chris Hofstaedtler Mon, 05 Aug 2024 00:31:55 +0200 ### Old Ubuntu Delta ### util-linux (2.40.2-1ubuntu2) plucky; urgency=medium * Read the ext4 superblock with O_DIRECT if the first read produces a checksum failure. This fixes a race where the underlying superblock can be changed in memory but not on disk, resulting in checksum failures which in turn causes systemd-udevd to remove by-uuid and by-label symlinks. (LP: #2090972) - d/p/ubuntu/lp2090972-libblkid-fix-spurious-ext-superblock-checksum-mismat.patch -- Matthew Ruffell Thu, 05 Dec 2024 13:02:57 +1300 util-linux (2.40.2-1ubuntu1) oracular; urgency=medium * Merge with Debian unstable (LP: #2072813). Remaining changes: - Disable brand new feature with --disable-libmount-mountfd-support that causes inability to deploy MAAS LP #2037417 - Add sulogin-fallback-static-sh.patch: Add support for /bin/static-sh as
[Touch-packages] [Bug 2091862] Re: Please merge 2.40.2-12 into plucky
$ ppa tests hyask/shadow-merge-lp2089923 [...] - util-linux/2.40.2-12ubuntu1~skiappa2 + ✅ util-linux on plucky for amd64 @ 17.12.24 14:31:25 Log️ 🗒️ + ✅ util-linux on plucky for arm64 @ 17.12.24 15:25:00 Log️ 🗒️ + ✅ util-linux on plucky for s390x @ 17.12.24 14:30:45 Log️ 🗒️ [...] Still waiting for some other tests, that don't want to come out of the infra, but overall works fine. https://autopkgtest.ubuntu.com/results/autopkgtest-plucky-hyask-shadow- merge-lp2089923//plucky/amd64/u/util-linux/20241217_143125_cb0cf@/log.gz We can see in the log file that the dependencies correctly pulled `login.defs` from the `shadow` version in the same PPA, so everything seems fine on that front. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/2091862 Title: Please merge 2.40.2-12 into plucky Status in util-linux package in Ubuntu: In Progress Bug description: tracking bug Ubuntu plucky: 2.40.2-1ubuntu2 Debian unstable: 2.40.2-12 ### New Debian Changes ### util-linux (2.40.2-12) unstable; urgency=medium * Stop building utmpdump, should not be necessary on wtmpdb systems * Stop marking mkfds-socketpair test as failing * Skip tmpfs-sensitive tests if fstype cannot be determined * Amend NEWS entry to hint updating /root/.profile (Closes: #1088009) -- Chris Hofstaedtler Fri, 06 Dec 2024 13:35:11 +0100 util-linux (2.40.2-11) unstable; urgency=medium * tests: Temporarily mark fincore as failing in unshare * Stop installing mesg, write -- Chris Hofstaedtler Wed, 13 Nov 2024 13:03:57 +0100 util-linux (2.40.2-10) unstable; urgency=medium * d/gbp.conf: set debian-branch to debian/unstable -- Chris Hofstaedtler Sat, 02 Nov 2024 23:01:29 +0100 util-linux (2.40.2-9) unstable; urgency=medium [ Pino Toscano ] * Fix newgrp permissions only on Linux [ Chris Hofstaedtler ] * Add upstream patch to fix tv_usec formatting (Closes: #1083006) -- Chris Hofstaedtler Tue, 01 Oct 2024 20:13:03 +0200 util-linux (2.40.2-8) unstable; urgency=medium * Mark nologin, newgrp binaries and man pages linux-any * Install manpages using dh_install * Import patches from upstream master * newgrp: Optionally execute a program after group change * Treat out of memory as error * agetty: add "systemd" to --version output * lscpu: optimize query virt pci device * more: make sure we have data on stderr Thanks to Gábor Németh (Closes: #1078122) * Revert "Remove sg symlink to newgrp" * Install sg symlink only on Linux * Install write(1) manpage * salsa-ci: add nodoc profile -- Chris Hofstaedtler Mon, 09 Sep 2024 23:20:25 +0200 util-linux (2.40.2-7) unstable; urgency=medium * login: update Section to admin (like in src:shadow) Thanks to Johannes Schauer Marin Rodrigues * Stop installing getopt-example.tcsh. Per lintian tag csh-considered-harmful and policy section 10.4. -- Chris Hofstaedtler Wed, 14 Aug 2024 12:29:34 +0200 util-linux (2.40.2-6) unstable; urgency=medium * Remove sg symlink to newgrp. Our newgrp does not take a command to execute, so stop pretending it works like sg. At least for now, we will not have sg. Addresses #1078122. -- Chris Hofstaedtler Wed, 07 Aug 2024 18:35:53 +0200 util-linux (2.40.2-5) unstable; urgency=medium [ Chris Hofstaedtler ] * Do not build login package for stage1 (Closes: #1078027) [ Sven Joachim ] * login: fix installing of /etc/pam.d/login (Closes: #1078036) -- Chris Hofstaedtler Tue, 06 Aug 2024 21:19:26 +0200 util-linux (2.40.2-4) unstable; urgency=medium * Upload to unstable. [ Chris Hofstaedtler ] * Bump Standards-Version to 4.7.0 * Patch login to support our PAM setup [ Helmut Grohne ] * Drop lastlog2 and libpam-lastlog2 from stage1 build (Closes: #1077967) -- Chris Hofstaedtler Mon, 05 Aug 2024 17:20:49 +0200 util-linux (2.40.2-3) experimental; urgency=medium * Take over login package from src:shadow (Closes: #833256) -- Chris Hofstaedtler Mon, 05 Aug 2024 02:54:35 +0200 util-linux (2.40.2-2) unstable; urgency=medium [ Pino Toscano ] * d/lastlog2.install: install systemd files only on Linux. -- Chris Hofstaedtler Mon, 05 Aug 2024 00:31:55 +0200 ### Old Ubuntu Delta ### util-linux (2.40.2-1ubuntu2) plucky; urgency=medium * Read the ext4 superblock with O_DIRECT if the first read produces a checksum failure. This fixes a race where the underlying superblock can be changed in memory but not on disk, resulting in checksum failures which in turn causes systemd-udevd to remove by-uuid and by-label symlinks. (LP: #2090972) - d/p/ubuntu/lp2090972-libblkid-fix-spurious-ext-superblock-checks
[Touch-packages] [Bug 2091862] Re: Please merge 2.40.2-12 into plucky
As part of that merge, I've added a new `login` dep8 test. As soon as it's been reviewed here in Ubuntu, I'll propose it in Debian. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/2091862 Title: Please merge 2.40.2-12 into plucky Status in util-linux package in Ubuntu: In Progress Bug description: tracking bug Ubuntu plucky: 2.40.2-1ubuntu2 Debian unstable: 2.40.2-12 ### New Debian Changes ### util-linux (2.40.2-12) unstable; urgency=medium * Stop building utmpdump, should not be necessary on wtmpdb systems * Stop marking mkfds-socketpair test as failing * Skip tmpfs-sensitive tests if fstype cannot be determined * Amend NEWS entry to hint updating /root/.profile (Closes: #1088009) -- Chris Hofstaedtler Fri, 06 Dec 2024 13:35:11 +0100 util-linux (2.40.2-11) unstable; urgency=medium * tests: Temporarily mark fincore as failing in unshare * Stop installing mesg, write -- Chris Hofstaedtler Wed, 13 Nov 2024 13:03:57 +0100 util-linux (2.40.2-10) unstable; urgency=medium * d/gbp.conf: set debian-branch to debian/unstable -- Chris Hofstaedtler Sat, 02 Nov 2024 23:01:29 +0100 util-linux (2.40.2-9) unstable; urgency=medium [ Pino Toscano ] * Fix newgrp permissions only on Linux [ Chris Hofstaedtler ] * Add upstream patch to fix tv_usec formatting (Closes: #1083006) -- Chris Hofstaedtler Tue, 01 Oct 2024 20:13:03 +0200 util-linux (2.40.2-8) unstable; urgency=medium * Mark nologin, newgrp binaries and man pages linux-any * Install manpages using dh_install * Import patches from upstream master * newgrp: Optionally execute a program after group change * Treat out of memory as error * agetty: add "systemd" to --version output * lscpu: optimize query virt pci device * more: make sure we have data on stderr Thanks to Gábor Németh (Closes: #1078122) * Revert "Remove sg symlink to newgrp" * Install sg symlink only on Linux * Install write(1) manpage * salsa-ci: add nodoc profile -- Chris Hofstaedtler Mon, 09 Sep 2024 23:20:25 +0200 util-linux (2.40.2-7) unstable; urgency=medium * login: update Section to admin (like in src:shadow) Thanks to Johannes Schauer Marin Rodrigues * Stop installing getopt-example.tcsh. Per lintian tag csh-considered-harmful and policy section 10.4. -- Chris Hofstaedtler Wed, 14 Aug 2024 12:29:34 +0200 util-linux (2.40.2-6) unstable; urgency=medium * Remove sg symlink to newgrp. Our newgrp does not take a command to execute, so stop pretending it works like sg. At least for now, we will not have sg. Addresses #1078122. -- Chris Hofstaedtler Wed, 07 Aug 2024 18:35:53 +0200 util-linux (2.40.2-5) unstable; urgency=medium [ Chris Hofstaedtler ] * Do not build login package for stage1 (Closes: #1078027) [ Sven Joachim ] * login: fix installing of /etc/pam.d/login (Closes: #1078036) -- Chris Hofstaedtler Tue, 06 Aug 2024 21:19:26 +0200 util-linux (2.40.2-4) unstable; urgency=medium * Upload to unstable. [ Chris Hofstaedtler ] * Bump Standards-Version to 4.7.0 * Patch login to support our PAM setup [ Helmut Grohne ] * Drop lastlog2 and libpam-lastlog2 from stage1 build (Closes: #1077967) -- Chris Hofstaedtler Mon, 05 Aug 2024 17:20:49 +0200 util-linux (2.40.2-3) experimental; urgency=medium * Take over login package from src:shadow (Closes: #833256) -- Chris Hofstaedtler Mon, 05 Aug 2024 02:54:35 +0200 util-linux (2.40.2-2) unstable; urgency=medium [ Pino Toscano ] * d/lastlog2.install: install systemd files only on Linux. -- Chris Hofstaedtler Mon, 05 Aug 2024 00:31:55 +0200 ### Old Ubuntu Delta ### util-linux (2.40.2-1ubuntu2) plucky; urgency=medium * Read the ext4 superblock with O_DIRECT if the first read produces a checksum failure. This fixes a race where the underlying superblock can be changed in memory but not on disk, resulting in checksum failures which in turn causes systemd-udevd to remove by-uuid and by-label symlinks. (LP: #2090972) - d/p/ubuntu/lp2090972-libblkid-fix-spurious-ext-superblock-checksum-mismat.patch -- Matthew Ruffell Thu, 05 Dec 2024 13:02:57 +1300 util-linux (2.40.2-1ubuntu1) oracular; urgency=medium * Merge with Debian unstable (LP: #2072813). Remaining changes: - Disable brand new feature with --disable-libmount-mountfd-support that causes inability to deploy MAAS LP #2037417 - Add sulogin-fallback-static-sh.patch: Add support for /bin/static-sh as fallback if the regular shell fails to execute. Patch ported from sysvinit. (see LP #505887) - Add sulogin-lockedpwd.patch: Make sure file systems can
[Touch-packages] [Bug 2091228] Re: apport-gtk crashed with SIGTRAP in g_log_writer_default()
** Tags added: rls-pp-incoming
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/2091228
Title:
apport-gtk crashed with SIGTRAP in g_log_writer_default()
Status in apport package in Ubuntu:
Confirmed
Bug description:
Unknown error after installing Unity 25.04 Daily Build.
ProblemType: Crash
DistroRelease: Ubuntu 25.04
Package: apport-gtk 2.30.0-0ubuntu5
ProcVersionSignature: Ubuntu 6.11.0-8.8-generic 6.11.0
Uname: Linux 6.11.0-8-generic x86_64
ApportVersion: 2.30.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: unknown
CrashReports:
664:0:111:0:2024-12-07 22:47:15.566220174 -0600:2024-12-07
22:47:15.566220174 -0600:/var/crash/_usr_bin_add-apt-repository.0.upload
640:0:111:9374885:2024-12-07 21:12:48.279499292 -0600:2024-12-07
21:12:49.279499292 -0600:/var/crash/_usr_share_apport_apport-gtk.0.crash
640:0:111:30796:2024-12-07 22:47:11.070472717 -0600:2024-12-07
22:47:15.758316193 -0600:/var/crash/_usr_bin_add-apt-repository.0.crash
600:107:111:37:2024-12-07 22:47:16.893883811 -0600:2024-12-07
22:47:16.893883811 -0600:/var/crash/_usr_bin_add-apt-repository.0.uploaded
Date: Sat Dec 7 21:12:40 2024
ExecutablePath: /usr/share/apport/apport-gtk
InstallationDate: Installed on 2024-12-08 (0 days ago)
InstallationMedia: Ubuntu-Unity 25.04 "Plucky Puffin" - Daily amd64 (20241206)
InterpreterPath: /usr/bin/python3.12
JournalErrors:
Dec 07 21:12:40 hostname pkexec[7961]: _gtk_css_lookup_resolve: assertion
'(((__extension__ ({ GTypeInstance *__inst = (GTypeInstance*) ((provider));
GType __t = ((_gtk_style_provider_private_get_type ())); gboolean __r; if
(!__inst) __r = (0); else if (__inst->g_class && __inst->g_class->g_type ==
__t) __r = (!(0)); else __r = g_type_check_instance_is_a (__inst, __t); __r;
}' failed
Dec 07 21:12:40 hostname pkexec[7961]: Can't create a GtkStyleContext
without a display connection
Dec 07 21:12:43 hostname kernel: block sda: the capability attribute has
been deprecated.
PackageArchitecture: all
ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk
Python3Details: /usr/bin/python3.12, Python 3.12.7, python3-minimal,
3.12.6-0ubuntu1
PythonDetails: N/A
Signal: 5
SignalName: SIGTRAP
SourcePackage: apport
StacktraceTop:
g_log_writer_default () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
g_log_structured_array () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
g_log_structured_standard () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
??? () at /lib/x86_64-linux-gnu/libgtk-3.so.0
g_type_create_instance () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: apport-gtk crashed with SIGTRAP in g_log_writer_default()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
separator:
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2091228/+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 2096775] [NEW] [SRU Exception] refresh mirrors list
Public bug reported: Here is a link to the exception: https://wiki.ubuntu.com/StableReleaseUpdates#ubuntu-release- upgrader_and_python-apt ** Affects: python-apt (Ubuntu) Importance: Undecided Assignee: Skia (hyask) Status: New ** Affects: python-apt (Ubuntu Noble) Importance: Undecided Assignee: Skia (hyask) Status: New ** Merge proposal linked: https://code.launchpad.net/~hyask/ubuntu/+source/python-apt/+git/python-apt/+merge/480150 ** Changed in: python-apt (Ubuntu) Assignee: (unassigned) => Skia (hyask) ** Also affects: python-apt (Ubuntu Noble) Importance: Undecided Status: New ** Changed in: python-apt (Ubuntu Noble) Assignee: (unassigned) => Skia (hyask) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/2096775 Title: [SRU Exception] refresh mirrors list Status in python-apt package in Ubuntu: New Status in python-apt source package in Noble: New Bug description: Here is a link to the exception: https://wiki.ubuntu.com/StableReleaseUpdates#ubuntu-release- upgrader_and_python-apt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/2096775/+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 2096775] Re: [SRU Exception] refresh mirrors list
** Changed in: python-apt (Ubuntu) Status: New => Invalid ** Changed in: python-apt (Ubuntu Noble) Milestone: None => ubuntu-24.04.2 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/2096775 Title: [SRU Exception] refresh mirrors list Status in python-apt package in Ubuntu: Invalid Status in python-apt source package in Noble: Fix Committed Bug description: Here is a link to the exception: https://wiki.ubuntu.com/StableReleaseUpdates#ubuntu-release- upgrader_and_python-apt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/2096775/+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 2083020] Re: Backport packages for 24.04.2 HWE stack
** Changed in: mesa (Ubuntu Noble) Milestone: None => ubuntu-24.04.2 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/2083020 Title: Backport packages for 24.04.2 HWE stack Status in OEM Priority Project: New Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-19 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in meson-1.5 package in Ubuntu: New Status in spirv-llvm-translator-19 package in Ubuntu: Invalid Status in libdrm source package in Noble: Fix Released Status in llvm-toolchain-19 source package in Noble: Fix Released Status in mesa source package in Noble: Fix Committed Status in meson-1.5 source package in Noble: Fix Released Status in spirv-llvm-translator-19 source package in Noble: Fix Released Bug description: [Impact] The graphics HWE stack from oracular needs to be backported for 24.04.2 libdrm - build-dep of mesa spirv-llvm-translator - build-dep of llvm - note that some symbols changed/added/dropped on certain archs due to older gcc/toolchain, so dh_makeshlibs was overridden to not care about those llvm-toolchain-19 - new source in noble - build-dep of mesa - required for new AMD platforms - needs two uploads: * 1st stage bootstrap build * 2nd stage after spirv-llvm-translator has built against 1st stage mesa - new major release, last of the series (24.2.8) so it has accumulated all the fixes upstream considered worthy for it - new HW support, Lunar Lake, Battlemage.. meson-1.5 - needed by mesa - Conflicts/Replaces meson, because otherwise all of the python lib should be renamed, along with the includes etc so it's not a trivial amount of work - tests disabled because four irrelevant ones fail for some reason, doesn't affect the mesa backport [Test case] We want to cover at least 2-3 different, widely used and already previously supported GPU generations from both AMD and Intel which are supported by this release, as those are the ones that cover most bases; nouveau users tend to switch to the NVIDIA driver after installation. No need to test ancient GPU's supported by mesa-amber. And best to focus on the newer generations (~5y and newer) as the older ones are less likely to break at this point. - AMD: Vega, Navi1x (RX5000*), Navi2x (RX6000*), Navi3x (RX7000*) - Intel: gen9 (SKL/APL/KBL/CFL/WHL/CML), gen11 (ICL), gen12 (TGL/ADL/RKL/RPL/DG2) Install the new packages and run some tests: - check that the desktop is still using hw acceleration and hasn't fallen back to swrast/llvmpipe - run freely available benchmarks that torture the GPU (Unigine Heaven/Valley/Superposition) - run some games from Steam if possible and in each case check that there is no gfx corruption happening or worse. Note that upstream releases have already been tested for OpenGL and Vulkan conformance by their CI. [Where things could go wrong] This is a major update of Mesa, there could be regressions but we'll try to catch any with testing. And since it shares bugs with oracular, we'd already know if there are serious issues. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2083020/+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 2096775] Re: [SRU Exception] refresh mirrors list
root@noble:/# dpkg-query -W python-apt-common
python-apt-common 2.7.7ubuntu3
root@noble:/# grep kumi.systems /usr/share/python-apt/templates/Ubuntu.mirrors
root@noble:/# apt install -y python-apt-common/noble-proposed
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Selected version '2.7.7ubuntu4' (Ubuntu:24.04/noble-proposed [all]) for
'python-apt-common'
The following packages will be upgraded:
python-apt-common
1 upgraded, 0 newly installed, 0 to remove and 15 not upgraded.
Need to get 20.4 kB of archives.
After this operation, 383 kB disk space will be freed.
Get:1 http://archive.ubuntu.com/ubuntu noble-proposed/main amd64
python-apt-common all 2.7.7ubuntu4 [20.4 kB]
Fetched 20.4 kB in 0s (61.5 kB/s)
debconf: delaying package configuration, since apt-utils is not installed
(Reading database ... 9623 files and directories currently installed.)
Preparing to unpack .../python-apt-common_2.7.7ubuntu4_all.deb ...
Unpacking python-apt-common (2.7.7ubuntu4) over (2.7.7ubuntu3) ...
Setting up python-apt-common (2.7.7ubuntu4) ...
root@noble:/# grep kumi.systems /usr/share/python-apt/templates/Ubuntu.mirrors
https://mirror.kumi.systems/ubuntu-ports/
https://mirror.kumi.systems/ubuntu/
root@noble:/# apt install -y python3-apt/noble-proposed
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Selected version '2.7.7ubuntu4' (Ubuntu:24.04/noble-proposed [amd64]) for
'python3-apt'
Suggested packages:
python-apt-doc
The following packages will be upgraded:
python3-apt
1 upgraded, 0 newly installed, 0 to remove and 15 not upgraded.
Need to get 169 kB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 http://archive.ubuntu.com/ubuntu noble-proposed/main amd64 python3-apt
amd64 2.7.7ubuntu4 [169 kB]
Fetched 169 kB in 1s (283 kB/s)
debconf: delaying package configuration, since apt-utils is not installed
(Reading database ... 9568 files and directories currently installed.)
Preparing to unpack .../python3-apt_2.7.7ubuntu4_amd64.deb ...
Unpacking python3-apt (2.7.7ubuntu4) over (2.7.7ubuntu3) ...
Setting up python3-apt (2.7.7ubuntu4) ...
root@noble:/# python3
Python 3.12.3 (main, Jan 17 2025, 18:03:48) [GCC 13.3.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import apt
>>> apt.__dict__
{'__name__': 'apt', '__doc__': 'High-Level Interface for working with apt.',
'__package__': 'apt', '__loader__':
<_frozen_importlib_external.SourceFileLoader object at 0x7d28a0c8a630>,
'__spec__': ModuleSpec(name='apt',
loader=<_frozen_importlib_external.SourceFileLoader object at 0x7d28a0c8a630>,
origin='/usr/lib/python3/dist-packages/apt/__init__.py',
submodule_search_locations=['/usr/lib/python3/dist-packages/apt']), '__path__':
['/usr/lib/python3/dist-packages/apt'], '__file__':
'/usr/lib/python3/dist-packages/apt/__init__.py', '__cached__':
'/usr/lib/python3/dist-packages/apt/__pycache__/__init__.cpython-312.pyc',
'__builtins__': {'__name__': 'builtins', '__doc__': "Built-in functions, types,
exceptions, and other objects.\n\nThis module provides direct access to all
'built-in'\nidentifiers of Python; for example, builtins.len is\nthe full name
for the built-in function len().\n\nThis module is not normally accessed
explicitly by most\napplications, but can be useful in modules
that provide\nobjects with the same name as a built-in value, but in\nwhich
the built-in of that name is also needed.", '__package__': '', '__loader__':
, '__spec__':
ModuleSpec(name='builtins', loader=,
origin='built-in'), '__build_class__': ,
'__import__': , 'abs': ,
'all': , 'any': , 'ascii':
, 'bin': , 'breakpoint':
, 'callable': ,
'chr': , 'compile': ,
'delattr': , 'dir': ,
'divmod': , 'eval': , 'exec':
, 'format': , 'getattr':
, 'glob
als': , 'hasattr': ,
'hash': , 'hex': , 'id':
, 'input': , 'isinstance':
, 'issubclass': ,
'iter': , 'aiter': , 'len':
, 'locals': , 'max': , 'min': , 'next': , 'anext': , 'oct': ,
'ord': , 'pow': , 'print':
, 'repr': , 'round': , 'setattr': , 'sorted': , 'sum': , 'vars': , 'None': None, 'Ellipsis': Ellipsis, 'NotImplemented': NotImplemented,
'False':
False, 'True': True, 'bool': , 'memoryview': , 'bytearray': , 'bytes': ,
'classmethod': , 'complex': , 'dict':
, 'enumerate': , 'filter': ,
'float': , 'frozenset': , 'property': , 'int': , 'list': , 'map': , 'object': , 'range': , 'reversed':
, 'set': , 'slice': ,
'staticmethod': , 'str': , 'super': , 'tuple': , 'type': , 'zip': , '__debug__': True, 'BaseException': ,
'BaseExceptionGroup': , 'Exception': , 'GeneratorExit': , 'KeyboardInterrupt':
, 'SystemE
xit': , 'ArithmeticError': ,
'AssertionError': , 'AttributeError': , 'BufferError': , 'EOFError': , 'ImportError': , 'LookupError': , 'MemoryError': , 'NameError': , 'OSError': , 'ReferenceError': , 'RuntimeError': ,
'StopAsyncIteration': , 'StopIteration': , 'SyntaxError': , 'SystemError': , 'TypeE
[Touch-packages] [Bug 2055054] Re: package udev 249.11-0ubuntu3.12 failed to install/upgrade: installed udev package post-installation script subprocess returned error exit status 1
Hi, Could you please provide the exact steps that you took to reproduce the issue? For example, spin up a new Ubuntu VM and come with a scenario of precisely what you did, then if it reproduces the issue correctly, post it here. Without a reproducer, it's very hard to work on bugs. Thanks ** 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/2055054 Title: package udev 249.11-0ubuntu3.12 failed to install/upgrade: installed udev package post-installation script subprocess returned error exit status 1 Status in systemd package in Ubuntu: Incomplete Bug description: Following this problem, the computer can still be used. However, after the lock screen goes into effect due to inactivity, the following attempt to login fails. After entering the system password, the screen just sits there and no login occurs. The only way to get out of this situation is to powerdown the computer which creates other problems with files that had remained opened. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: udev 249.11-0ubuntu3.12 ProcVersionSignature: Ubuntu 5.15.0-97.107-generic 5.15.136 Uname: Linux 5.15.0-97-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CustomUdevRuleFiles: 70-snap.snapd-desktop-integration.rules 70-snap.quadrapassel.rules 70-snap.tetris.rules 70-snap.gimp.rules 70-snap.gnome-calculator.rules 70-snap.firefox.rules 70-snap.snap-store.rules 70-snap.core.rules 70-snap.freecell-solitaire.rules 70-snap.warble.rules Date: Sun Feb 25 17:49:07 2024 ErrorMessage: installed udev package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2019-12-01 (1548 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-97-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.11 SourcePackage: systemd Title: package udev 249.11-0ubuntu3.12 failed to install/upgrade: installed udev package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to jammy on 2022-08-22 (552 days ago) dmi.bios.date: 10/03/2013 dmi.bios.release: 15.41 dmi.bios.vendor: Insyde dmi.bios.version: F.29 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 181D dmi.board.vendor: Hewlett-Packard dmi.board.version: 52.24 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 52.24 dmi.modalias: dmi:bvnInsyde:bvrF.29:bd10/03/2013:br15.41:efr52.24:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvr078F1020572620100:rvnHewlett-Packard:rn181D:rvr52.24:cvnHewlett-Packard:ct10:cvrChassisVersion:skuA3F79AV: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP Pavilion dv7 Notebook PC dmi.product.sku: A3F79AV dmi.product.version: 078F1020572620100 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2055054/+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 2080718] Re: package bash 5.2.21-2ubuntu4 failed to install/upgrade: installed bash package post-installation script subprocess returned error exit status 1
It appears from the `Dependencies.txt` file that you have a custom libc installed, and that matches the errors `apt` is showing during the installation. Please install a working glibc, and the issue should be solved. ** Changed in: bash (Ubuntu) Status: Confirmed => Invalid ** Changed in: bash (Ubuntu) Status: Invalid => Incomplete ** Changed in: bash (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/2080718 Title: package bash 5.2.21-2ubuntu4 failed to install/upgrade: installed bash package post-installation script subprocess returned error exit status 1 Status in bash package in Ubuntu: Invalid Bug description: Unpacking base-files (13ubuntu10.1) over (12ubuntu4.7) ... Setting up base-files (13ubuntu10.1) ... Installing new version of config file /etc/debian_version ... Installing new version of config file /etc/issue ... Installing new version of config file /etc/issue.net ... Installing new version of config file /etc/lsb-release ... /usr/bin/perl: /lib/aarch64-linux-gnu/libc.so.6: version `GLIBC_2.36' not found (required by /lib/aarch64-linux-gnu/libcrypt.so.1) /usr/bin/perl: /lib/aarch64-linux-gnu/libc.so.6: version `GLIBC_2.38' not found (required by /lib/aarch64-linux-gnu/libcrypt.so.1) /usr/bin/perl: /lib/aarch64-linux-gnu/libc.so.6: version `GLIBC_2.36' not found (required by /lib/aarch64-linux-gnu/libcrypt.so.1) /usr/bin/perl: /lib/aarch64-linux-gnu/libc.so.6: version `GLIBC_2.38' not found (required by /lib/aarch64-linux-gnu/libcrypt.so.1) /usr/bin/perl: /lib/aarch64-linux-gnu/libc.so.6: version `GLIBC_2.36' not found (required by /lib/aarch64-linux-gnu/libcrypt.so.1) /usr/bin/perl: /lib/aarch64-linux-gnu/libc.so.6: version `GLIBC_2.38' not found (required by /lib/aarch64-linux-gnu/libcrypt.so.1) /usr/bin/perl: /lib/aarch64-linux-gnu/libc.so.6: version `GLIBC_2.36' not found (required by /lib/aarch64-linux-gnu/libcrypt.so.1) /usr/bin/perl: /lib/aarch64-linux-gnu/libc.so.6: version `GLIBC_2.38' not found (required by /lib/aarch64-linux-gnu/libcrypt.so.1) /usr/bin/perl: /lib/aarch64-linux-gnu/libc.so.6: version `GLIBC_2.36' not found (required by /lib/aarch64-linux-gnu/libcrypt.so.1) /usr/bin/perl: /lib/aarch64-linux-gnu/libc.so.6: version `GLIBC_2.38' not found (required by /lib/aarch64-linux-gnu/libcrypt.so.1) (Reading database ... 71144 files and directories currently installed.) Preparing to unpack .../debianutils_5.17build1_arm64.deb ... Unpacking debianutils (5.17build1) over (5.5-1ubuntu2) ... Setting up debianutils (5.17build1) ... (Reading database ... 71142 files and directories currently installed.) Preparing to unpack .../bash_5.2.21-2ubuntu4_arm64.deb ... Unpacking bash (5.2.21-2ubuntu4) over (5.1-6ubuntu1.1) ... Setting up bash (5.2.21-2ubuntu4) ... /bin/bash: /lib/aarch64-linux-gnu/libc.so.6: version `GLIBC_2.38' not found (required by /bin/bash) /bin/bash: /lib/aarch64-linux-gnu/libc.so.6: version `GLIBC_2.36' not found (required by /bin/bash) dpkg: error processing package bash (--configure): installed bash package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: bash ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/bash.0.crash' Exception during pm.DoInstall(): E:Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 24.04 Package: bash 5.2.21-2ubuntu4 Uname: Linux 5.10.160-rockchip aarch64 ApportVersion: 2.20.11-0ubuntu82.6 Architecture: arm64 CasperMD5CheckResult: unknown CloudArchitecture: aarch64 CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSubPlatform: config-disk (/dev/sda1) Date: Sat Sep 14 15:03:08 2024 ErrorMessage: installed bash package post-installation script subprocess returned error exit status 1 Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04.1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.3 apt 2.4.13 SourcePackage: bash Title: package bash 5.2.21-2ubuntu4 failed to install/upgrade: installed bash package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to noble on 2024-09-14 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/2080718/+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 2091862] Re: Please merge 2.40.2-14 into plucky
** Summary changed: - Please merge 2.40.2-13 into plucky + Please merge 2.40.2-14 into plucky ** Description changed: tracking bug Ubuntu plucky: 2.40.2-1ubuntu2 - Debian unstable: 2.40.2-13 + Debian unstable: 2.40.2-14 ### New Debian Changes ### util-linux (2.40.2-13) unstable; urgency=medium - * Add patches from upstream master branch fixing various bugs, - incl. fixes for cachestat on alpha. + * Add patches from upstream master branch fixing various bugs, + incl. fixes for cachestat on alpha. - -- Chris Hofstaedtler Thu, 26 Dec 2024 13:52:42 + -- Chris Hofstaedtler Thu, 26 Dec 2024 13:52:42 +0100 util-linux (2.40.2-12) unstable; urgency=medium * Stop building utmpdump, should not be necessary on wtmpdb systems * Stop marking mkfds-socketpair test as failing * Skip tmpfs-sensitive tests if fstype cannot be determined * Amend NEWS entry to hint updating /root/.profile (Closes: #1088009) -- Chris Hofstaedtler Fri, 06 Dec 2024 13:35:11 +0100 util-linux (2.40.2-11) unstable; urgency=medium * tests: Temporarily mark fincore as failing in unshare * Stop installing mesg, write -- Chris Hofstaedtler Wed, 13 Nov 2024 13:03:57 +0100 util-linux (2.40.2-10) unstable; urgency=medium * d/gbp.conf: set debian-branch to debian/unstable -- Chris Hofstaedtler Sat, 02 Nov 2024 23:01:29 +0100 util-linux (2.40.2-9) unstable; urgency=medium [ Pino Toscano ] * Fix newgrp permissions only on Linux [ Chris Hofstaedtler ] * Add upstream patch to fix tv_usec formatting (Closes: #1083006) -- Chris Hofstaedtler Tue, 01 Oct 2024 20:13:03 +0200 util-linux (2.40.2-8) unstable; urgency=medium * Mark nologin, newgrp binaries and man pages linux-any * Install manpages using dh_install * Import patches from upstream master * newgrp: Optionally execute a program after group change * Treat out of memory as error * agetty: add "systemd" to --version output * lscpu: optimize query virt pci device * more: make sure we have data on stderr Thanks to Gábor Németh (Closes: #1078122) * Revert "Remove sg symlink to newgrp" * Install sg symlink only on Linux * Install write(1) manpage * salsa-ci: add nodoc profile -- Chris Hofstaedtler Mon, 09 Sep 2024 23:20:25 +0200 util-linux (2.40.2-7) unstable; urgency=medium * login: update Section to admin (like in src:shadow) Thanks to Johannes Schauer Marin Rodrigues * Stop installing getopt-example.tcsh. Per lintian tag csh-considered-harmful and policy section 10.4. -- Chris Hofstaedtler Wed, 14 Aug 2024 12:29:34 +0200 util-linux (2.40.2-6) unstable; urgency=medium * Remove sg symlink to newgrp. Our newgrp does not take a command to execute, so stop pretending it works like sg. At least for now, we will not have sg. Addresses #1078122. -- Chris Hofstaedtler Wed, 07 Aug 2024 18:35:53 +0200 util-linux (2.40.2-5) unstable; urgency=medium [ Chris Hofstaedtler ] * Do not build login package for stage1 (Closes: #1078027) [ Sven Joachim ] * login: fix installing of /etc/pam.d/login (Closes: #1078036) -- Chris Hofstaedtler Tue, 06 Aug 2024 21:19:26 +0200 util-linux (2.40.2-4) unstable; urgency=medium * Upload to unstable. [ Chris Hofstaedtler ] * Bump Standards-Version to 4.7.0 * Patch login to support our PAM setup [ Helmut Grohne ] * Drop lastlog2 and libpam-lastlog2 from stage1 build (Closes: #1077967) -- Chris Hofstaedtler Mon, 05 Aug 2024 17:20:49 +0200 util-linux (2.40.2-3) experimental; urgency=medium * Take over login package from src:shadow (Closes: #833256) -- Chris Hofstaedtler Mon, 05 Aug 2024 02:54:35 +0200 util-linux (2.40.2-2) unstable; urgency=medium [ Pino Toscano ] * d/lastlog2.install: install systemd files only on Linux. -- Chris Hofstaedtler Mon, 05 Aug 2024 00:31:55 +0200 ### Old Ubuntu Delta ### util-linux (2.40.2-1ubuntu2) plucky; urgency=medium * Read the ext4 superblock with O_DIRECT if the first read produces a checksum failure. This fixes a race where the underlying superblock can be changed in memory but not on disk, resulting in checksum failures which in turn causes systemd-udevd to remove by-uuid and by-label symlinks. (LP: #2090972) - d/p/ubuntu/lp2090972-libblkid-fix-spurious-ext-superblock-checksum-mismat.patch -- Matthew Ruffell Thu, 05 Dec 2024 13:02:57 +1300 util-linux (2.40.2-1ubuntu1) oracular; urgency=medium * Merge with Debian unstable (LP: #2072813). Remaining changes: - Disable brand new feature with --disable-libmount-mountfd-support that causes inability to deploy MAAS LP #2037417 - Add sulogin-fallback-static-sh.patch: Add support
[Touch-packages] [Bug 2096914] Re: rsync 3.3.0-1ubuntu0.1 patch breaks IPv6 over SSH: "ssh: Could not resolve hostname x: Name or service not known"
** Tags added: rls-oo-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/2096914 Title: rsync 3.3.0-1ubuntu0.1 patch breaks IPv6 over SSH: "ssh: Could not resolve hostname x: Name or service not known" Status in rsync package in Ubuntu: Confirmed Bug description: The security upgrade of rsync from 3.3.0-1 (oracular) to 3.3.0-1ubuntu0.1 (oracular-updates) breaks my current rsync over SSH backup for an IPv6-only target host!: rsync -a --delete -s --rsh="ssh -" -p 22 /tmp/emptydir/ ad...@ipv6only.reachable.nas:/share/CACHEDEV3_DATA/targetdir 3.3.0-1ubuntu0.1 outputs here: OpenSSH_9.7p1 Ubuntu-7ubuntu4.1, OpenSSL 3.3.1 4 Jun 2024 debug1: Reading configuration data /etc/ssh/ssh_config [...] debug3: resolve_host: lookup ipv6only.reachable.nas:22 ssh: Could not resolve hostname ipv6only.reachable.nas: Name or service not known rsync: connection unexpectedly closed (0 bytes received so far) [sender] rsync error: unexplained error (code 255) at io.c(232) [sender=3.3.0] while 3.3.0-1 outputs here: OpenSSH_9.7p1 Ubuntu-7ubuntu4.1, OpenSSL 3.3.1 4 Jun 2024 debug1: Reading configuration data /etc/ssh/ssh_config [...] debug3: resolve_host: lookup ipv6only.reachable.nas:22 debug3: channel_clear_timeouts: clearing debug3: ssh_connect_direct: entering debug1: Connecting to ipv6only.reachable.nas [2001:9e8:…] port 22. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/2096914/+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 2098852] Re: Merge 2.7.1-2 into plucky
** Merge proposal linked: https://code.launchpad.net/~hyask/ubuntu/+source/kbd/+git/kbd/+merge/481532 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kbd in Ubuntu. https://bugs.launchpad.net/bugs/2098852 Title: Merge 2.7.1-2 into plucky Status in kbd package in Ubuntu: In Progress Bug description: tracking bug Ubuntu plucky: 2.6.4-2ubuntu3 Debian unstable: 2.7.1-2 ### New Debian Changes ### kbd (2.7.1-2) unstable; urgency=medium * Team upload. * Add debian/patches/ppc-keycode0-test.patch -- Andreas Henriksson Fri, 20 Dec 2024 20:11:27 +0100 kbd (2.7.1-1) unstable; urgency=medium * Team upload. * New upstream release. * Upload to unstable. -- Andreas Henriksson Fri, 20 Dec 2024 11:40:06 +0100 kbd (2.7~rc1-1) experimental; urgency=medium * Team upload. * debian/watch: Mangle rc versions to ~rc * debian/gbp: Rename branches to /latest according to DEP14 * New upstream release candidate. * Upload to experimental. * Update Misc...patch to apply * Revert "Cherry-pick patches from upstream fixing gcc14 FTBFS" * debian/kbd.docs: Drop outdated docs removed upstream * debian/copyright: Update renamed files -- Andreas Henriksson Mon, 18 Nov 2024 20:08:52 +0100 kbd (2.6.4-3) unstable; urgency=medium * Team upload. * Cherry-pick patches from upstream fixing gcc14 FTBFS (Closes: #1075109) * Build-dep on pkgconf instead of pkg-config -- Andreas Henriksson Tue, 24 Sep 2024 03:12:26 +0200 ### Old Ubuntu Delta ### kbd (2.6.4-2ubuntu3) oracular; urgency=medium * d/p/Add-missing-headers.patch: add a patch to fix FTBFS with GCC 14 (LP: #2081329). -- Zixing Liu Thu, 19 Sep 2024 11:27:01 -0600 kbd (2.6.4-2ubuntu2) noble; urgency=medium * No-change rebuild for CVE-2024-3094 -- Steve Langasek Sun, 31 Mar 2024 09:02:08 + kbd (2.6.4-2ubuntu1) noble; urgency=medium * Merge with Debian unstable (LP: #2055065). Remaining changes: - Add setfont, kbd_mode, and loadkeys to initramfs for console-setup. - Use ckbcomp to get the keyboard layout if other data files are not available. - Change loadkeys to find any console not in raw mode when invoked without an explicit console parameter, in case the foreground console is in raw mode. - debian/control: Depend on console-setup | console-setup-mini, since console-setup-mini also Depends on kbd now through console-setup-linux. - Add setvtrgb to kbd-udeb (LP #730672). * Dropped unnecessary changelog entries - Added initramfs hook to have setfont/loadkeys available in initramfs. + This is basically a duplicate of: Add setfont, kbd_mode, and loadkeys to initramfs for console-setup. - debian/patches/loadkeys_find_usable_console.diff: fix wrong type argument to ioctl(..., KDGKBMODE), which causes consoles to not be correctly detected on 64-bit archs. LP #1621824. + This was a bug in an Ubuntu-specific patch so irrelevant to our delta with Debian. - Fix incorrect keymap sanity check in loadkeys_ckbcomp.diff. + This was a bug in an Ubuntu-specific patch so irrelevant to our delta with Debian. -- Olivier Gayot Tue, 27 Feb 2024 10:52:03 +0100 Nothing big expected, just a merge. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kbd/+bug/2098852/+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 2098852] [NEW] Merge 2.7.1-2 into plucky
Public bug reported: tracking bug Ubuntu plucky: 2.6.4-2ubuntu3 Debian unstable: 2.7.1-2 ### New Debian Changes ### kbd (2.7.1-2) unstable; urgency=medium * Team upload. * Add debian/patches/ppc-keycode0-test.patch -- Andreas Henriksson Fri, 20 Dec 2024 20:11:27 +0100 kbd (2.7.1-1) unstable; urgency=medium * Team upload. * New upstream release. * Upload to unstable. -- Andreas Henriksson Fri, 20 Dec 2024 11:40:06 +0100 kbd (2.7~rc1-1) experimental; urgency=medium * Team upload. * debian/watch: Mangle rc versions to ~rc * debian/gbp: Rename branches to /latest according to DEP14 * New upstream release candidate. * Upload to experimental. * Update Misc...patch to apply * Revert "Cherry-pick patches from upstream fixing gcc14 FTBFS" * debian/kbd.docs: Drop outdated docs removed upstream * debian/copyright: Update renamed files -- Andreas Henriksson Mon, 18 Nov 2024 20:08:52 +0100 kbd (2.6.4-3) unstable; urgency=medium * Team upload. * Cherry-pick patches from upstream fixing gcc14 FTBFS (Closes: #1075109) * Build-dep on pkgconf instead of pkg-config -- Andreas Henriksson Tue, 24 Sep 2024 03:12:26 +0200 ### Old Ubuntu Delta ### kbd (2.6.4-2ubuntu3) oracular; urgency=medium * d/p/Add-missing-headers.patch: add a patch to fix FTBFS with GCC 14 (LP: #2081329). -- Zixing Liu Thu, 19 Sep 2024 11:27:01 -0600 kbd (2.6.4-2ubuntu2) noble; urgency=medium * No-change rebuild for CVE-2024-3094 -- Steve Langasek Sun, 31 Mar 2024 09:02:08 + kbd (2.6.4-2ubuntu1) noble; urgency=medium * Merge with Debian unstable (LP: #2055065). Remaining changes: - Add setfont, kbd_mode, and loadkeys to initramfs for console-setup. - Use ckbcomp to get the keyboard layout if other data files are not available. - Change loadkeys to find any console not in raw mode when invoked without an explicit console parameter, in case the foreground console is in raw mode. - debian/control: Depend on console-setup | console-setup-mini, since console-setup-mini also Depends on kbd now through console-setup-linux. - Add setvtrgb to kbd-udeb (LP #730672). * Dropped unnecessary changelog entries - Added initramfs hook to have setfont/loadkeys available in initramfs. + This is basically a duplicate of: Add setfont, kbd_mode, and loadkeys to initramfs for console-setup. - debian/patches/loadkeys_find_usable_console.diff: fix wrong type argument to ioctl(..., KDGKBMODE), which causes consoles to not be correctly detected on 64-bit archs. LP #1621824. + This was a bug in an Ubuntu-specific patch so irrelevant to our delta with Debian. - Fix incorrect keymap sanity check in loadkeys_ckbcomp.diff. + This was a bug in an Ubuntu-specific patch so irrelevant to our delta with Debian. -- Olivier Gayot Tue, 27 Feb 2024 10:52:03 +0100 Nothing big expected, just a merge. ** Affects: kbd (Ubuntu) Importance: Medium Assignee: Skia (hyask) Status: In Progress ** Changed in: kbd (Ubuntu) Importance: Undecided => Medium ** Changed in: kbd (Ubuntu) Assignee: (unassigned) => Skia (hyask) ** Changed in: kbd (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kbd in Ubuntu. https://bugs.launchpad.net/bugs/2098852 Title: Merge 2.7.1-2 into plucky Status in kbd package in Ubuntu: In Progress Bug description: tracking bug Ubuntu plucky: 2.6.4-2ubuntu3 Debian unstable: 2.7.1-2 ### New Debian Changes ### kbd (2.7.1-2) unstable; urgency=medium * Team upload. * Add debian/patches/ppc-keycode0-test.patch -- Andreas Henriksson Fri, 20 Dec 2024 20:11:27 +0100 kbd (2.7.1-1) unstable; urgency=medium * Team upload. * New upstream release. * Upload to unstable. -- Andreas Henriksson Fri, 20 Dec 2024 11:40:06 +0100 kbd (2.7~rc1-1) experimental; urgency=medium * Team upload. * debian/watch: Mangle rc versions to ~rc * debian/gbp: Rename branches to /latest according to DEP14 * New upstream release candidate. * Upload to experimental. * Update Misc...patch to apply * Revert "Cherry-pick patches from upstream fixing gcc14 FTBFS" * debian/kbd.docs: Drop outdated docs removed upstream * debian/copyright: Update renamed files -- Andreas Henriksson Mon, 18 Nov 2024 20:08:52 +0100 kbd (2.6.4-3) unstable; urgency=medium * Team upload. * Cherry-pick patches from upstream fixing gcc14 FTBFS (Closes: #1075109) * Build-dep on pkgconf instead of pkg-config -- Andreas Henriksson Tue, 24 Sep 2024 03:12:26 +0200 ### Old Ubuntu Delta ### kbd (2.6.4-2ubuntu3) oracular; urgency=medium * d/p/Add-missing-headers.patch: add a patch to fix FTBFS with GCC 14 (LP: #2081329). -- Zix
[Touch-packages] [Bug 2098865] [NEW] Please merge shadow 1:4.17.2-5 into plucky
Public bug reported:
tracking bug
Ubuntu plucky: 1:4.16.0-7ubuntu1
Debian Sid: 1:4.17.2-5
### New Debian Changes ###
shadow (1:4.17.2-5) unstable; urgency=medium
* Warn about future --badname removal.
Upstream PR 1158 plans to remove this flag, probably in the forky
timeframe. Warn users now.
* Import upstream patch to fix chfn (#1096187)
* Add regression test for #1096187
* Add regression test for #1095430
* Remove "shadowconfig off"
If needed please run pwunconv, grpunconv manually, but please understand
you are on your own.
-- Chris Hofstaedtler Mon, 17 Feb 2025 19:54:09
+0100
shadow (1:4.17.2-4) unstable; urgency=medium
* Revert upstreams chfn.c strsep change (Closes: #1096187)
-- Chris Hofstaedtler Mon, 17 Feb 2025 12:28:56
+0100
shadow (1:4.17.2-3) unstable; urgency=medium
* Revert upstreams strtoday calculation "fix" (Closes: #1095430)
-- Chris Hofstaedtler Sun, 16 Feb 2025 20:24:35
+0100
shadow (1:4.17.2-2) unstable; urgency=medium
* Upload to unstable.
* Apply upstream revert of "Use local time for human-readable dates"
(Closes: #1095430)
-- Chris Hofstaedtler Sat, 15 Feb 2025 17:21:17
+0100
shadow (1:4.17.2-1) experimental; urgency=medium
* New upstream version 4.17.2
* Apply upstream patch from Marc Haber to document E_BAD_NAME
* Refresh patches
-- Chris Hofstaedtler Sun, 09 Feb 2025 18:14:51
+0100
shadow (1:4.17.1-2) experimental; urgency=medium
* Rewrite shadowconfig(8) manpage.
Thanks to Alejandro Colomar
* Remove unnecessary Build-Depends: quilt.
Thanks to Bastian Germann (Closes: #1092461)
-- Chris Hofstaedtler Wed, 08 Jan 2025 12:40:10
+0100
shadow (1:4.17.1-1) experimental; urgency=medium
* New upstream version 4.17.1
-- Chris Hofstaedtler Sat, 04 Jan 2025 12:41:51
+0100
shadow (1:4.17.0-1) experimental; urgency=medium
* New upstream version 4.17.0
* Refresh patches.
-- Chris Hofstaedtler Sat, 28 Dec 2024 13:14:16
+0100
shadow (1:4.17.0~rc1-2) experimental; urgency=medium
* Remove Debian patch to relax username checks.
Per discussion on d-devel, with upstream, and with the
adduser maintainer.
Thanks: Marc Haber
-- Chris Hofstaedtler Sun, 22 Dec 2024 20:15:16
+0100
shadow (1:4.17.0~rc1-1) experimental; urgency=medium
* New upstream version 4.17.0~rc1
* Add upstream patch for new return-code for bad usernames
* Refresh patches
* d/copyright: update
* Forbid purely numeric user/group names, and "." and ".."
-- Chris Hofstaedtler Fri, 06 Dec 2024 19:55:32
+0100
### Old Ubuntu Delta ###
shadow (1:4.16.0-7ubuntu1) plucky; urgency=medium
* Merge with Debian unstable. Remaining changes (LP: #2089923):
- d/p/* : Enable private home directories by default
- debian/{source_shadow.py,login.defs.install}: Add apport hook
- debian/patches/1010_extrausers.patch:
+ Add support to passwd for libnss-extrausers
+ Add automatic detection of "extrausers" for usermod -G
- d/p/1011_extrausers_toggle.patch: extrausers support for useradd/groupadd
- d/p/1012_extrausers_chfn.patch: --extrausers support for chfn tool
- d/p/1013_extrausers_deluser.patch: --extrausers support for userdel
- d/p/1014_extrausers_delgroup.patch: --extrausers support for groupdel
- d/p/1016_extrausers_gpasswd.patch: extrausers support for gpasswd
- d/p/506_relaxed_usernames.patch, d/t/{control,numeric-username}:
- d/t/smoke: Extend for extrausers support
- Add some cursory tests for the extrausers features
- d/p/lp2063200: fix useradd group validation with extrausers (LP 2063200)
* New Changes:
- d/tests: make 'upstream' tests work with current sources layout
* Drop Changes:
- d/p/1015_add_zsys_support.patch: zsys to handle home dir if available
Reason: buggy and unmaintained zsys integration (LP: #2049529)
-- Florent 'Skia' Jacquet Mon, 02 Dec
2024 12:39:54 +0100
** Affects: shadow (Ubuntu)
Importance: Medium
Assignee: Skia (hyask)
Status: In Progress
** Changed in: shadow (Ubuntu)
Status: New => In Progress
** Changed in: shadow (Ubuntu)
Importance: Undecided => Medium
** Changed in: shadow (Ubuntu)
Assignee: (unassigned) => Skia (hyask)
** Changed in: shadow (Ubuntu)
Milestone: None => ubuntu-25.04-feature-freeze
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to shadow in Ubuntu.
https://bugs.launchpad.net/bugs/2098865
Title:
Please merge shadow 1:4.17.2-5 into plucky
Status in shadow package in Ubuntu:
In Progress
Bug description:
tracking bug
Ubuntu plucky: 1:4.16.0-7ubuntu1
Debian Sid: 1:4.17.2-5
### New Debian Changes ###
shadow (1:4.17.2-5) unstable; urgency=medium
* Warn about future --badname removal.
Upstream PR 1158 plans to remove this flag, probably in
[Touch-packages] [Bug 2098852] Re: Merge 2.7.1-2 into plucky
** Merge proposal linked: https://code.launchpad.net/~hyask/ubuntu/+source/kbd/+git/kbd/+merge/481541 ** Changed in: kbd (Ubuntu) Milestone: None => ubuntu-25.04-feature-freeze -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kbd in Ubuntu. https://bugs.launchpad.net/bugs/2098852 Title: Merge 2.7.1-2 into plucky Status in kbd package in Ubuntu: In Progress Bug description: tracking bug Ubuntu plucky: 2.6.4-2ubuntu3 Debian unstable: 2.7.1-2 ### New Debian Changes ### kbd (2.7.1-2) unstable; urgency=medium * Team upload. * Add debian/patches/ppc-keycode0-test.patch -- Andreas Henriksson Fri, 20 Dec 2024 20:11:27 +0100 kbd (2.7.1-1) unstable; urgency=medium * Team upload. * New upstream release. * Upload to unstable. -- Andreas Henriksson Fri, 20 Dec 2024 11:40:06 +0100 kbd (2.7~rc1-1) experimental; urgency=medium * Team upload. * debian/watch: Mangle rc versions to ~rc * debian/gbp: Rename branches to /latest according to DEP14 * New upstream release candidate. * Upload to experimental. * Update Misc...patch to apply * Revert "Cherry-pick patches from upstream fixing gcc14 FTBFS" * debian/kbd.docs: Drop outdated docs removed upstream * debian/copyright: Update renamed files -- Andreas Henriksson Mon, 18 Nov 2024 20:08:52 +0100 kbd (2.6.4-3) unstable; urgency=medium * Team upload. * Cherry-pick patches from upstream fixing gcc14 FTBFS (Closes: #1075109) * Build-dep on pkgconf instead of pkg-config -- Andreas Henriksson Tue, 24 Sep 2024 03:12:26 +0200 ### Old Ubuntu Delta ### kbd (2.6.4-2ubuntu3) oracular; urgency=medium * d/p/Add-missing-headers.patch: add a patch to fix FTBFS with GCC 14 (LP: #2081329). -- Zixing Liu Thu, 19 Sep 2024 11:27:01 -0600 kbd (2.6.4-2ubuntu2) noble; urgency=medium * No-change rebuild for CVE-2024-3094 -- Steve Langasek Sun, 31 Mar 2024 09:02:08 + kbd (2.6.4-2ubuntu1) noble; urgency=medium * Merge with Debian unstable (LP: #2055065). Remaining changes: - Add setfont, kbd_mode, and loadkeys to initramfs for console-setup. - Use ckbcomp to get the keyboard layout if other data files are not available. - Change loadkeys to find any console not in raw mode when invoked without an explicit console parameter, in case the foreground console is in raw mode. - debian/control: Depend on console-setup | console-setup-mini, since console-setup-mini also Depends on kbd now through console-setup-linux. - Add setvtrgb to kbd-udeb (LP #730672). * Dropped unnecessary changelog entries - Added initramfs hook to have setfont/loadkeys available in initramfs. + This is basically a duplicate of: Add setfont, kbd_mode, and loadkeys to initramfs for console-setup. - debian/patches/loadkeys_find_usable_console.diff: fix wrong type argument to ioctl(..., KDGKBMODE), which causes consoles to not be correctly detected on 64-bit archs. LP #1621824. + This was a bug in an Ubuntu-specific patch so irrelevant to our delta with Debian. - Fix incorrect keymap sanity check in loadkeys_ckbcomp.diff. + This was a bug in an Ubuntu-specific patch so irrelevant to our delta with Debian. -- Olivier Gayot Tue, 27 Feb 2024 10:52:03 +0100 Nothing big expected, just a merge. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kbd/+bug/2098852/+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 2098865] Re: Please merge shadow 1:4.17.2-5 into plucky
** Merge proposal linked:
https://code.launchpad.net/~hyask/ubuntu/+source/shadow/+git/shadow/+merge/481573
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to shadow in Ubuntu.
https://bugs.launchpad.net/bugs/2098865
Title:
Please merge shadow 1:4.17.2-5 into plucky
Status in shadow package in Ubuntu:
In Progress
Bug description:
tracking bug
Ubuntu plucky: 1:4.16.0-7ubuntu1
Debian Sid: 1:4.17.2-5
### New Debian Changes ###
shadow (1:4.17.2-5) unstable; urgency=medium
* Warn about future --badname removal.
Upstream PR 1158 plans to remove this flag, probably in the forky
timeframe. Warn users now.
* Import upstream patch to fix chfn (#1096187)
* Add regression test for #1096187
* Add regression test for #1095430
* Remove "shadowconfig off"
If needed please run pwunconv, grpunconv manually, but please understand
you are on your own.
-- Chris Hofstaedtler Mon, 17 Feb 2025 19:54:09
+0100
shadow (1:4.17.2-4) unstable; urgency=medium
* Revert upstreams chfn.c strsep change (Closes: #1096187)
-- Chris Hofstaedtler Mon, 17 Feb 2025 12:28:56
+0100
shadow (1:4.17.2-3) unstable; urgency=medium
* Revert upstreams strtoday calculation "fix" (Closes: #1095430)
-- Chris Hofstaedtler Sun, 16 Feb 2025 20:24:35
+0100
shadow (1:4.17.2-2) unstable; urgency=medium
* Upload to unstable.
* Apply upstream revert of "Use local time for human-readable dates"
(Closes: #1095430)
-- Chris Hofstaedtler Sat, 15 Feb 2025 17:21:17
+0100
shadow (1:4.17.2-1) experimental; urgency=medium
* New upstream version 4.17.2
* Apply upstream patch from Marc Haber to document E_BAD_NAME
* Refresh patches
-- Chris Hofstaedtler Sun, 09 Feb 2025 18:14:51
+0100
shadow (1:4.17.1-2) experimental; urgency=medium
* Rewrite shadowconfig(8) manpage.
Thanks to Alejandro Colomar
* Remove unnecessary Build-Depends: quilt.
Thanks to Bastian Germann (Closes: #1092461)
-- Chris Hofstaedtler Wed, 08 Jan 2025 12:40:10
+0100
shadow (1:4.17.1-1) experimental; urgency=medium
* New upstream version 4.17.1
-- Chris Hofstaedtler Sat, 04 Jan 2025 12:41:51
+0100
shadow (1:4.17.0-1) experimental; urgency=medium
* New upstream version 4.17.0
* Refresh patches.
-- Chris Hofstaedtler Sat, 28 Dec 2024 13:14:16
+0100
shadow (1:4.17.0~rc1-2) experimental; urgency=medium
* Remove Debian patch to relax username checks.
Per discussion on d-devel, with upstream, and with the
adduser maintainer.
Thanks: Marc Haber
-- Chris Hofstaedtler Sun, 22 Dec 2024 20:15:16
+0100
shadow (1:4.17.0~rc1-1) experimental; urgency=medium
* New upstream version 4.17.0~rc1
* Add upstream patch for new return-code for bad usernames
* Refresh patches
* d/copyright: update
* Forbid purely numeric user/group names, and "." and ".."
-- Chris Hofstaedtler Fri, 06 Dec 2024 19:55:32
+0100
### Old Ubuntu Delta ###
shadow (1:4.16.0-7ubuntu1) plucky; urgency=medium
* Merge with Debian unstable. Remaining changes (LP: #2089923):
- d/p/* : Enable private home directories by default
- debian/{source_shadow.py,login.defs.install}: Add apport hook
- debian/patches/1010_extrausers.patch:
+ Add support to passwd for libnss-extrausers
+ Add automatic detection of "extrausers" for usermod -G
- d/p/1011_extrausers_toggle.patch: extrausers support for
useradd/groupadd
- d/p/1012_extrausers_chfn.patch: --extrausers support for chfn tool
- d/p/1013_extrausers_deluser.patch: --extrausers support for userdel
- d/p/1014_extrausers_delgroup.patch: --extrausers support for groupdel
- d/p/1016_extrausers_gpasswd.patch: extrausers support for gpasswd
- d/p/506_relaxed_usernames.patch, d/t/{control,numeric-username}:
- d/t/smoke: Extend for extrausers support
- Add some cursory tests for the extrausers features
- d/p/lp2063200: fix useradd group validation with extrausers (LP 2063200)
* New Changes:
- d/tests: make 'upstream' tests work with current sources layout
* Drop Changes:
- d/p/1015_add_zsys_support.patch: zsys to handle home dir if available
Reason: buggy and unmaintained zsys integration (LP: #2049529)
-- Florent 'Skia' Jacquet Mon, 02
Dec 2024 12:39:54 +0100
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/2098865/+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 2098930] Re: openvpn profile doesn't allow access to files on home dir
I hit this too, and had to adapt the work-around to be slightly more
permissive, since `openvpn` actually needs to load multiple files, making it
look more like this:
sudo bash -c "echo '@{HOME}/Documents/canonical/vpn/* r,' >>
/etc/apparmor.d/local/openvpn"
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/2098930
Title:
openvpn profile doesn't allow access to files on home dir
Status in apparmor package in Ubuntu:
Confirmed
Status in gnome-control-center package in Ubuntu:
Confirmed
Bug description:
my VPN keys & certs are stored in my HOME directory. The current
apparmor update broke that. When I try to activate my VPN through
NetworkManager, the journal says:
Feb 20 07:48:57 paprika NetworkManager[3405]: [1740034137.4372]
vpn[0x58db282782d0,132c9eee-2134-4f7a-8326-58bde38036de,"canonical-uk"]:
starting openvpn
[snipped]
Feb 20 07:48:57 paprika nm-openvpn[10793]: Cannot pre-load keyfile
(/home/tom/Documents/vpn/ta.key)
Feb 20 07:48:57 paprika nm-openvpn[10793]: Exiting due to fatal error
[snipped]
Feb 20 07:48:57 paprika kernel: audit: type=1400 audit(1740034137.454:789):
apparmor="DENIED" operation="open" class="file" profile="openvpn"
name="/home/tom/Documents/vpn/ta.key" pid=10793 comm="openvpn"
requested_mask="r" denied_ma>
So openvpn can no longer access
/home/tom/Documents/canonical/vpn/canonical_ta.key .
ProblemType: Bug
DistroRelease: Ubuntu 25.04
Package: apparmor 4.1.0~beta5-0ubuntu2
ProcVersionSignature: Ubuntu 6.12.0-15.15-generic 6.12.11
Uname: Linux 6.12.0-15-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.31.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Feb 20 08:57:57 2025
InstallationDate: Installed on 2024-07-18 (217 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/usr/bin/zsh
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-6.12.0-15-generic
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
SourcePackage: apparmor
UpgradeStatus: Upgraded to plucky on 2024-12-20 (62 days ago)
modified.conffile..etc.apparmor.d.element-desktop: [modified]
mtime.conffile..etc.apparmor.d.element-desktop: 2025-02-11T18:32:02.077059
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2098930/+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 2098093] Re: Setting primary interface for a bond fails with netplan
Probably for Desktop/Server to figure out who needs to take care of that. ** Tags added: rls-nn-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2098093 Title: Setting primary interface for a bond fails with netplan Status in netplan.io package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: Ubuntu 2404 network-manager 1.46.0-1ubuntu2.2 netplan.io 1.1.1-1~ubuntu24.04.1 When [improving support for primary interfaces of bonds](https://github.com/cockpit-project/cockpit/pull/21533) in Cockpit, we encountered this message in the journal: ``` Feb 10 08:43:17 ubuntu NetworkManager[9361]: /etc/netplan/90-NM-861a710b-9858-48f4-b5e5-a770ab67bd1f.yaml:13:18: Error in network definition: tbond: interface 'cockpit' is not defined Feb 10 08:43:17 ubuntu NetworkManager[9361]: primary: "cockpit" Feb 10 08:43:17 ubuntu NetworkManager[9361]: ^ ``` The message seems to come from "netplan apply": ``` # netplan apply [...] /etc/netplan/90-NM-4883fb46-4315-41f1-b945-bb096768da61.yaml:13:18: Error in network definition: tbond: interface 'cockpit' is not defined primary: "cockpit" ^ # echo $? 78 ``` NetworkManager seems to ignore the failure, and somehow the bond interface is created anyway, but the "bond.options" setting of its connection doesn't include the expected "primary" attribute: ``` # nmcli con show tbond | grep ^bond bond.options: mode=active-backup,downdelay=0,miimon=100,updelay=0 ``` I have no idea what the relationship between netplan and NetworkManager is. I am guessing that NetworkManager is writing the yaml files in /etc/netplan/. The problem seems to be that the definition of the "cockpit" interface uses a generated name: ``` network: version: 2 ethernets: NM-3287d9ea-ffda-49df-9f21-27594d7cc1b8: renderer: NetworkManager match: name: "cockpit" wakeonlan: true networkmanager: uuid: "3287d9ea-ffda-49df-9f21-27594d7cc1b8" name: "cockpit" passthrough: connection.controller: "tbond" connection.master: "tbond" connection.port-type: "bond" connection.slave-type: "bond" ethernet._: "" ``` If I change this to ``` network: version: 2 ethernets: cockpit: renderer: NetworkManager match: name: "cockpit" [...] ``` then the error disappears and `bond.options` shows the expected value: ``` # nmcli con show tbond | grep ^bond bond.options: mode=active-backup,downdelay=0,miimon=100,primary=cockpit,updelay=0 ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2098093/+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 1165536] Re: grep doesn't handle \w correctly
I think the usage of `grep` is a bit mistaken. `\w` is a literal
replacement for `[_[:alnum:]]`, and `\W` is for inverting that, so if
you enclose it again in some brackets, it doesn't work anymore. You
probably want something more like this:
❯ grep -Re '\Wlog\W' /tmp/test2
if ($this->_touchOnly) //log if touchOnly
only log the output of the controller if $silent
if (window.console) console.log(data);
** Changed in: grep (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to grep in Ubuntu.
https://bugs.launchpad.net/bugs/1165536
Title:
grep doesn't handle \w correctly
Status in grep package in Ubuntu:
Invalid
Bug description:
Put the following text into a file called testfile.txt:
---testfile.txt---
if ($this->_touchOnly) //log if touchOnly
only log the output of the controller if $silent
if (window.console) console.log(data);
ERunActions::runAction($logOutput=false,$silent=false)
self::logTrace('Action output: ' . $output,$controller->id,$actionId);
self::logError($msg,$controller->id,$actionId);
---end of testfile.txt
Try this command:
$ grep -Re "[^\w]log[^\w]" testfile.txt
Expected result:
Should find matches only in lines 1,2,3, gighlighting the word "log"
Observed result:
Finds also matches in lines 5,6,7, highlighting the strings "logO", "logT"
and "logE" respectively.
According to the man page:
The symbol \w is a synonym for [_[:alnum:]]
And in turn:
For example, [[:alnum:]] means the character class of numbers and
letters in the current locale. In the C locale and ASCII character set
encoding, this is the same as [0-9A-Za-z].
It looks like, instead, \w is interpreted as only numbers and
LOWERCASE letters, but not uppercase letters.
I know it seems unbelievable to be finding a bug in grep in 2013, but compare
to
http://regexr.com?34e4i
which shows the expected result
ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: grep 2.12-2
ProcVersionSignature: Ubuntu 3.5.0-27.46-generic 3.5.7.7
Uname: Linux 3.5.0-27-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 2.6.1-0ubuntu10
Architecture: i386
Date: Sat Apr 6 22:27:39 2013
InstallationDate: Installed on 2010-06-23 (1018 days ago)
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
MarkForUpload: True
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: grep
UpgradeStatus: Upgraded to quantal on 2013-01-13 (83 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grep/+bug/1165536/+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 2099680] Re: Please document how to enable/disable autoreporting
In addition, in auto-upgrade-testing, we manually trigger the upload of crashes with `sudo systemctl start whoopsie.service --wait` -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/2099680 Title: Please document how to enable/disable autoreporting Status in apport package in Ubuntu: Confirmed Bug description: We got the question: How is apport autoreporting enabled in a headless system? I found https://documentation.ubuntu.com/server/how- to/software/report-a-bug/ but that does not say anything about the autoreporting. I found a lot of very old documentation that did not help. Please document how to enable/disable autoreporting. In case this documentation lives outside the apport code base, the documentation in the apport code should point to that documentation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2099680/+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 2049529] Re: Ubuntu delta causes `can't open /dev/null: No such file or directory` errors in minimal environments (chroot/unshare)
** Also affects: autopkgtest (Ubuntu) Importance: Undecided Status: New ** No longer affects: autopkgtest (Ubuntu Plucky) ** Changed in: autopkgtest (Ubuntu Noble) Status: New => Confirmed ** Changed in: autopkgtest (Ubuntu Oracular) Status: New => Confirmed ** Changed in: autopkgtest (Ubuntu) Status: New => Invalid ** Changed in: autopkgtest (Ubuntu Noble) Importance: Undecided => High ** Changed in: autopkgtest (Ubuntu Oracular) Importance: Undecided => High ** Changed in: autopkgtest (Ubuntu Noble) Assignee: (unassigned) => Ural Tunaboyu (uralt) ** Changed in: autopkgtest (Ubuntu Oracular) Assignee: (unassigned) => Ural Tunaboyu (uralt) ** Changed in: shadow (Ubuntu Noble) Status: Confirmed => Won't Fix ** Changed in: shadow (Ubuntu Oracular) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to adduser in Ubuntu. https://bugs.launchpad.net/bugs/2049529 Title: Ubuntu delta causes `can't open /dev/null: No such file or directory` errors in minimal environments (chroot/unshare) Status in adduser package in Ubuntu: Confirmed Status in autopkgtest package in Ubuntu: Invalid Status in shadow package in Ubuntu: Fix Released Status in adduser source package in Noble: Confirmed Status in autopkgtest source package in Noble: Confirmed Status in shadow source package in Noble: Won't Fix Status in adduser source package in Oracular: New Status in autopkgtest source package in Oracular: Confirmed Status in shadow source package in Oracular: Won't Fix Status in adduser source package in Plucky: Confirmed Status in shadow source package in Plucky: Fix Released Bug description: Hi, I was digging into fixing `autopkgtest`'s `unshare` testsuite, and the rabbit hole led me here. Here is a very quick reproducer, first: Start a fresh Ubuntu VM. Here is a quick path, but other ways should do fine: ``` $ cd /tmp $ autopkgtest-buildvm-ubuntu-cloud -a amd64 -r noble $ kvm -m 1G -snapshot -hda autopkgtest-noble-amd64.img ``` Now in the VM: ``` $ sudo apt install -y mmdebstrap $ mmdebstrap noble /tmp/rootfs [...] $ sudo useradd --create-home --root /tmp/rootfs user1 can't open /dev/null: No such file or directory ``` The line `can't open /dev/null: No such file or directory` is printed on `stderr`, and that's unexpected by the part of the code I was debugging in the first place. Digging a bit led me to that line that does the printing: https://git.launchpad.net/ubuntu/+source/shadow/tree/debian/patches/1015_add_zsys_support.patch#n69 There seem to me that there are multiple issues with that patch: * Why try to call `zsysctl` in every case without first checking that it would be relevant: ZFS is not even installed on the VM we just created, less alone it has any ZFS volume/pool/whatever. * Obviously, when creating a user in a `chroot`, `/dev/null` won't exist unless mapped, and `useradd` is perfectly aware of that, because it even does the `chroot` call itself! But why even try to mess with ZFS in the `chroot` case in the first place? From what history @brian-murray told me, this patch was part of some ZFS experimentation in the past. Maybe that experimentation is now finished, and that patch could be dropped? At the very least it needs improvements, imho. EDIT: Just for context on why this issue appears only now: I was trying to fix the `unshare` testsuite in `autopkgtest`, which is pretty recent (2022) (https://salsa.debian.org/ci- team/autopkgtest/-/commit/d1671f94f68bce9a0c6793310a9f8b79b4e919a5) even upstream on Debian, and has never worked yet on Ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adduser/+bug/2049529/+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 2049529] Re: Ubuntu delta causes `can't open /dev/null: No such file or directory` errors in minimal environments (chroot/unshare)
Okay, lots of status changes: * the root cause of this bug is a delta in shadow, that has already been dropped in Plucky * this delta was candidate for shadow SRU to Noble/Oracular, but: * dropping the delta kinda breaks functionality (zsys integration) in existing releases * even with the delta, the user gets created anyway, so the bug is "just" an extra line printed on stderr, so nothing too serious * autopkgtest's unshare backend is currently broken in some other ways anyway on Noble * autopkgtest has more recent versions that include the workaround, making them to work on Noble * with the above information, the safer fix for this would just be to SRU autopkgtest instead of shadow to Noble/Oracular Since Ural will likely take on the autopkgtest SRU, I'm assigning the autopkgtest tasks to him. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to adduser in Ubuntu. https://bugs.launchpad.net/bugs/2049529 Title: Ubuntu delta causes `can't open /dev/null: No such file or directory` errors in minimal environments (chroot/unshare) Status in adduser package in Ubuntu: Confirmed Status in autopkgtest package in Ubuntu: Invalid Status in shadow package in Ubuntu: Fix Released Status in adduser source package in Noble: Confirmed Status in autopkgtest source package in Noble: Confirmed Status in shadow source package in Noble: Won't Fix Status in adduser source package in Oracular: New Status in autopkgtest source package in Oracular: Confirmed Status in shadow source package in Oracular: Won't Fix Status in adduser source package in Plucky: Confirmed Status in shadow source package in Plucky: Fix Released Bug description: Hi, I was digging into fixing `autopkgtest`'s `unshare` testsuite, and the rabbit hole led me here. Here is a very quick reproducer, first: Start a fresh Ubuntu VM. Here is a quick path, but other ways should do fine: ``` $ cd /tmp $ autopkgtest-buildvm-ubuntu-cloud -a amd64 -r noble $ kvm -m 1G -snapshot -hda autopkgtest-noble-amd64.img ``` Now in the VM: ``` $ sudo apt install -y mmdebstrap $ mmdebstrap noble /tmp/rootfs [...] $ sudo useradd --create-home --root /tmp/rootfs user1 can't open /dev/null: No such file or directory ``` The line `can't open /dev/null: No such file or directory` is printed on `stderr`, and that's unexpected by the part of the code I was debugging in the first place. Digging a bit led me to that line that does the printing: https://git.launchpad.net/ubuntu/+source/shadow/tree/debian/patches/1015_add_zsys_support.patch#n69 There seem to me that there are multiple issues with that patch: * Why try to call `zsysctl` in every case without first checking that it would be relevant: ZFS is not even installed on the VM we just created, less alone it has any ZFS volume/pool/whatever. * Obviously, when creating a user in a `chroot`, `/dev/null` won't exist unless mapped, and `useradd` is perfectly aware of that, because it even does the `chroot` call itself! But why even try to mess with ZFS in the `chroot` case in the first place? From what history @brian-murray told me, this patch was part of some ZFS experimentation in the past. Maybe that experimentation is now finished, and that patch could be dropped? At the very least it needs improvements, imho. EDIT: Just for context on why this issue appears only now: I was trying to fix the `unshare` testsuite in `autopkgtest`, which is pretty recent (2022) (https://salsa.debian.org/ci- team/autopkgtest/-/commit/d1671f94f68bce9a0c6793310a9f8b79b4e919a5) even upstream on Debian, and has never worked yet on Ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adduser/+bug/2049529/+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 2103526] Re: [FFe] Allow 'AptSolverDump' field for apt solver 3 reports
** Description changed: [Context] Apt solver 3 is coming to plucky. Julian, apt's maintainer, would like to collect apt solver issues in the Ubuntu Error Tracker. Everything is already mostly wired, but `whoopsie` currently doesn't allow the `AptSolverDump` field in the produced crashes. [Changes] Since I'm slowly taking over this mostly unmaintained package, I'm also improving some other small things that would be good to be evaluated in the FFe: - * Add some additional logging for more discoverable behavior. - * Fix some lintian errors. - * Raise debhelper-compat to 13. + * Add some additional logging for more discoverable behavior. + * Fix some lintian errors. + * Raise debhelper-compat to 13. + + The exhaustive list of changes can be found on this MP: + https://code.launchpad.net/~hyask/whoopsie/+git/whoopsie/+merge/482986 [Test plan] + + Here is a PPA: https://launchpad.net/~hyask/+archive/ubuntu/whoopsie- + aptsolverdump/+packages I've already installed the package from the PPA, and verified the following: * systemd .service and .path files are correctly installed at the right place. * whoopsie service correctly triggers when something appears in `/var/crash`. - * The new log lines correctly appear in the journal of the whoopsie service. + * The new log lines correctly appear in the journal of the whoopsie service: + ``` + mars 18 17:44:49 kiffex systemd[1]: Started whoopsie.service - Service uploading crash reports to the Ubuntu Error Tracker. + mars 18 17:44:49 kiffex whoopsie[1209860]: [17:44:49] Using lock path: /var/lock/whoopsie/lock + mars 18 17:44:49 kiffex whoopsie[1209860]: [17:44:49] Looking for .upload files in /var/crash + mars 18 17:44:49 kiffex whoopsie[1209860]: [17:44:49] Found .crash corresponding to .upload (/var/crash/_usr_share_apport_apport.0.crash) + mars 18 17:44:49 kiffex whoopsie[1209860]: [17:44:49] Crash already uploaded, skipping + mars 18 17:44:49 kiffex whoopsie[1209860]: [17:44:49] Found .crash corresponding to .upload (/var/crash/_usr_libexec_fwupd_fwupd.0.crash) + mars 18 17:44:49 kiffex whoopsie[1209860]: [17:44:49] Crash already uploaded, skipping + mars 18 17:44:49 kiffex whoopsie[1209860]: [17:44:49] Found .crash corresponding to .upload (/var/crash/_usr_bin_seg-fault.1000.crash) + mars 18 17:44:49 kiffex whoopsie[1209860]: [17:44:49] Parsing /var/crash/_usr_bin_seg-fault.1000.crash. + mars 18 17:44:49 kiffex whoopsie[1209860]: [17:44:49] Uploading /var/crash/_usr_bin_seg-fault.1000.crash. + mars 18 17:44:50 kiffex whoopsie[1209860]: [17:44:50] Sent; server replied with: No error + mars 18 17:44:50 kiffex whoopsie[1209860]: [17:44:50] Response code: 200 + mars 18 17:44:50 kiffex whoopsie[1209860]: [17:44:50] Reported OOPS ID 4e2150de-0418-11f0-999a-fa163e171f02 + mars 18 17:44:50 kiffex systemd[1]: whoopsie.service: Deactivated successfully. + ``` ** Description changed: [Context] Apt solver 3 is coming to plucky. Julian, apt's maintainer, would like to collect apt solver issues in the Ubuntu Error Tracker. Everything is already mostly wired, but `whoopsie` currently doesn't allow the `AptSolverDump` field in the produced crashes. [Changes] + + This is mostly a one-line change to add `AptSolverDump` to the right + allow-list. Since I'm slowly taking over this mostly unmaintained package, I'm also improving some other small things that would be good to be evaluated in the FFe: * Add some additional logging for more discoverable behavior. * Fix some lintian errors. * Raise debhelper-compat to 13. The exhaustive list of changes can be found on this MP: https://code.launchpad.net/~hyask/whoopsie/+git/whoopsie/+merge/482986 [Test plan] Here is a PPA: https://launchpad.net/~hyask/+archive/ubuntu/whoopsie- aptsolverdump/+packages I've already installed the package from the PPA, and verified the following: * systemd .service and .path files are correctly installed at the right place. * whoopsie service correctly triggers when something appears in `/var/crash`. * The new log lines correctly appear in the journal of the whoopsie service: ``` mars 18 17:44:49 kiffex systemd[1]: Started whoopsie.service - Service uploading crash reports to the Ubuntu Error Tracker. mars 18 17:44:49 kiffex whoopsie[1209860]: [17:44:49] Using lock path: /var/lock/whoopsie/lock mars 18 17:44:49 kiffex whoopsie[1209860]: [17:44:49] Looking for .upload files in /var/crash mars 18 17:44:49 kiffex whoopsie[1209860]: [17:44:49] Found .crash corresponding to .upload (/var/crash/_usr_share_apport_apport.0.crash) mars 18 17:44:49 kiffex whoopsie[1209860]: [17:44:49] Crash already uploaded, skipping mars 18 17:44:49 kiffex whoopsie[1209860]: [17:44:49] Found .crash corresponding to .upload (/var/crash/_usr_libexec_fwupd_fwupd.0.crash) mars 18 17:44:49 kiffex whoopsie[1209860]: [17:44:49] Crash already uploaded, skipping mars 18 17:44:
[Touch-packages] [Bug 2103526] [NEW] [FFe] Allow 'AptSolverDump' field for apt solver 3 reports
Public bug reported: [Context] Apt solver 3 is coming to plucky. Julian, apt's maintainer, would like to collect apt solver issues in the Ubuntu Error Tracker. Everything is already mostly wired, but `whoopsie` currently doesn't allow the `AptSolverDump` field in the produced crashes. [Changes] Since I'm slowly taking over this mostly unmaintained package, I'm also improving some other small things that would be good to be evaluated in the FFe: * Add some additional logging for more discoverable behavior. * Fix some lintian errors. * Raise debhelper-compat to 13. [Test plan] I've already installed the package from the PPA, and verified the following: * systemd .service and .path files are correctly installed at the right place. * whoopsie service correctly triggers when something appears in `/var/crash`. * The new log lines correctly appear in the journal of the whoopsie service. ** Affects: whoopsie (Ubuntu) Importance: Undecided Assignee: Skia (hyask) Status: New ** Changed in: whoopsie (Ubuntu) Assignee: (unassigned) => Skia (hyask) ** Changed in: whoopsie (Ubuntu) Milestone: None => ubuntu-25.04-beta -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/2103526 Title: [FFe] Allow 'AptSolverDump' field for apt solver 3 reports Status in whoopsie package in Ubuntu: New Bug description: [Context] Apt solver 3 is coming to plucky. Julian, apt's maintainer, would like to collect apt solver issues in the Ubuntu Error Tracker. Everything is already mostly wired, but `whoopsie` currently doesn't allow the `AptSolverDump` field in the produced crashes. [Changes] Since I'm slowly taking over this mostly unmaintained package, I'm also improving some other small things that would be good to be evaluated in the FFe: * Add some additional logging for more discoverable behavior. * Fix some lintian errors. * Raise debhelper-compat to 13. [Test plan] I've already installed the package from the PPA, and verified the following: * systemd .service and .path files are correctly installed at the right place. * whoopsie service correctly triggers when something appears in `/var/crash`. * The new log lines correctly appear in the journal of the whoopsie service. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/2103526/+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 2105503] Re: Uncontrolled memory usage
** Description changed:
- Here is a simplified snippet, taken from `cnf-extractor`:
-
+ Here is a simplified snippet of the `filelist` function in the
+ `debfile.py` file. I got there while debugging OOM kill triggering on
+ cnf-extractor, that makes use of that function.
```
$ cat apt_file_0ad-data.py
import apt_inst
files = []
debfile = apt_inst.DebFile("0ad-data_0.27.0-1_all.deb")
debfile.data.go(lambda item, data: files.append(item.name))
print(files)
```
To run this, you need the latest `0ad-data` package downloaded next to
the script: `apt download 0ad-data`.
When running this "normally", I can see very high memory usage, sometimes
leading to OOM kill (how I digged into that in the first place):
python3 apt_file_0ad-data.py & ; htop -p $!
Interestingly, when wrapping that with some kind of constraints, the issue
doesn't appear anymore at all, and the memory usage remains low:
prlimit -v536870912 python3 apt_file_0ad-data.py & ; htop -p $!
With that previous command, even the time to finish is divided by two
(~consistently 8s vs 15s without wrapping on my machine), but I didn't take
precise measurements there, so might be noise, but still...
And then one final interesting result:
systemd-run --scope -p MemoryMax=500M --user python3 apt_file_0ad-data.py
Sometimes this works just as with `prlimit`, with slightly higher memory
usage, and sometimes it correctly triggers oom kill, after more than one
minute. Again, the timing benchmark is inaccurate, but still...
ProblemType: Bug
DistroRelease: Ubuntu 25.04
Package: python3-apt 2.9.9build1
ProcVersionSignature: Ubuntu 6.12.0-12.12-generic 6.12.4
Uname: Linux 6.12.0-12-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.32.0-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: sway
Date: Mon Mar 31 15:58:25 2025
InstallationDate: Installed on 2023-08-02 (607 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
ProcEnviron:
- LANG=fr_FR.UTF-8
- PATH=(custom, no user)
- SHELL=/bin/zsh
- TERM=alacritty
- XDG_RUNTIME_DIR=
+ LANG=fr_FR.UTF-8
+ PATH=(custom, no user)
+ SHELL=/bin/zsh
+ TERM=alacritty
+ XDG_RUNTIME_DIR=
SourcePackage: python-apt
UpgradeStatus: Upgraded to plucky on 2024-06-12 (292 days ago)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-apt in Ubuntu.
https://bugs.launchpad.net/bugs/2105503
Title:
Uncontrolled memory usage
Status in python-apt package in Ubuntu:
New
Bug description:
Here is a simplified snippet of the `filelist` function in the
`debfile.py` file. I got there while debugging OOM kill triggering on
cnf-extractor, that makes use of that function.
```
$ cat apt_file_0ad-data.py
import apt_inst
files = []
debfile = apt_inst.DebFile("0ad-data_0.27.0-1_all.deb")
debfile.data.go(lambda item, data: files.append(item.name))
print(files)
```
To run this, you need the latest `0ad-data` package downloaded next to
the script: `apt download 0ad-data`.
When running this "normally", I can see very high memory usage, sometimes
leading to OOM kill (how I digged into that in the first place):
python3 apt_file_0ad-data.py & ; htop -p $!
Interestingly, when wrapping that with some kind of constraints, the issue
doesn't appear anymore at all, and the memory usage remains low:
prlimit -v536870912 python3 apt_file_0ad-data.py & ; htop -p $!
With that previous command, even the time to finish is divided by two
(~consistently 8s vs 15s without wrapping on my machine), but I didn't take
precise measurements there, so might be noise, but still...
And then one final interesting result:
systemd-run --scope -p MemoryMax=500M --user python3 apt_file_0ad-data.py
Sometimes this works just as with `prlimit`, with slightly higher memory
usage, and sometimes it correctly triggers oom kill, after more than one
minute. Again, the timing benchmark is inaccurate, but still...
ProblemType: Bug
DistroRelease: Ubuntu 25.04
Package: python3-apt 2.9.9build1
ProcVersionSignature: Ubuntu 6.12.0-12.12-generic 6.12.4
Uname: Linux 6.12.0-12-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.32.0-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: sway
Date: Mon Mar 31 15:58:25 2025
InstallationDate: Installed on 2023-08-02 (607 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
ProcEnviron:
LANG=fr_FR.UTF-8
PATH=(custom, no user)
SHELL=/bin/zsh
TERM=alacritty
XDG_RUNTIME_DIR=
SourcePackage: python-apt
UpgradeStatus: Upgraded to plucky on 2024-06-12 (292 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/2105503/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch
[Touch-packages] [Bug 2049529] Re: Ubuntu delta causes `can't open /dev/null: No such file or directory` errors in minimal environments (chroot/unshare)
** Also affects: adduser (Ubuntu Oracular) Importance: Undecided Status: New ** Also affects: shadow (Ubuntu Oracular) Importance: Undecided Status: New ** Also affects: adduser (Ubuntu Plucky) Importance: Undecided Status: Confirmed ** Also affects: shadow (Ubuntu Plucky) Importance: High Status: Fix Released ** Changed in: shadow (Ubuntu Oracular) Status: New => Confirmed ** Changed in: shadow (Ubuntu Oracular) Importance: Undecided => High ** Changed in: shadow (Ubuntu Oracular) Assignee: (unassigned) => Skia (hyask) ** Changed in: shadow (Ubuntu Noble) Assignee: (unassigned) => Skia (hyask) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to adduser in Ubuntu. https://bugs.launchpad.net/bugs/2049529 Title: Ubuntu delta causes `can't open /dev/null: No such file or directory` errors in minimal environments (chroot/unshare) Status in adduser package in Ubuntu: Confirmed Status in shadow package in Ubuntu: Fix Released Status in adduser source package in Noble: Confirmed Status in shadow source package in Noble: Confirmed Status in adduser source package in Oracular: New Status in shadow source package in Oracular: Confirmed Status in adduser source package in Plucky: Confirmed Status in shadow source package in Plucky: Fix Released Bug description: Hi, I was digging into fixing `autopkgtest`'s `unshare` testsuite, and the rabbit hole led me here. Here is a very quick reproducer, first: Start a fresh Ubuntu VM. Here is a quick path, but other ways should do fine: ``` $ cd /tmp $ autopkgtest-buildvm-ubuntu-cloud -a amd64 -r noble $ kvm -m 1G -snapshot -hda autopkgtest-noble-amd64.img ``` Now in the VM: ``` $ sudo apt install -y mmdebstrap $ mmdebstrap noble /tmp/rootfs [...] $ sudo useradd --create-home --root /tmp/rootfs user1 can't open /dev/null: No such file or directory ``` The line `can't open /dev/null: No such file or directory` is printed on `stderr`, and that's unexpected by the part of the code I was debugging in the first place. Digging a bit led me to that line that does the printing: https://git.launchpad.net/ubuntu/+source/shadow/tree/debian/patches/1015_add_zsys_support.patch#n69 There seem to me that there are multiple issues with that patch: * Why try to call `zsysctl` in every case without first checking that it would be relevant: ZFS is not even installed on the VM we just created, less alone it has any ZFS volume/pool/whatever. * Obviously, when creating a user in a `chroot`, `/dev/null` won't exist unless mapped, and `useradd` is perfectly aware of that, because it even does the `chroot` call itself! But why even try to mess with ZFS in the `chroot` case in the first place? From what history @brian-murray told me, this patch was part of some ZFS experimentation in the past. Maybe that experimentation is now finished, and that patch could be dropped? At the very least it needs improvements, imho. EDIT: Just for context on why this issue appears only now: I was trying to fix the `unshare` testsuite in `autopkgtest`, which is pretty recent (2022) (https://salsa.debian.org/ci- team/autopkgtest/-/commit/d1671f94f68bce9a0c6793310a9f8b79b4e919a5) even upstream on Debian, and has never worked yet on Ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adduser/+bug/2049529/+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 2105503] [NEW] Uncontrolled memory usage
Public bug reported:
Here is a simplified snippet, taken from `cnf-extractor`:
```
$ cat apt_file_0ad-data.py
import apt_inst
files = []
debfile = apt_inst.DebFile("0ad-data_0.27.0-1_all.deb")
debfile.data.go(lambda item, data: files.append(item.name))
print(files)
```
To run this, you need the latest `0ad-data` package downloaded next to
the script: `apt download 0ad-data`.
When running this "normally", I can see very high memory usage, sometimes
leading to OOM kill (how I digged into that in the first place):
python3 apt_file_0ad-data.py & ; htop -p $!
Interestingly, when wrapping that with some kind of constraints, the issue
doesn't appear anymore at all, and the memory usage remains low:
prlimit -v536870912 python3 apt_file_0ad-data.py & ; htop -p $!
With that previous command, even the time to finish is divided by two
(~consistently 8s vs 15s without wrapping on my machine), but I didn't take
precise measurements there, so might be noise, but still...
And then one final interesting result:
systemd-run --scope -p MemoryMax=500M --user python3 apt_file_0ad-data.py
Sometimes this works just as with `prlimit`, with slightly higher memory usage,
and sometimes it correctly triggers oom kill, after more than one minute.
Again, the timing benchmark is inaccurate, but still...
ProblemType: Bug
DistroRelease: Ubuntu 25.04
Package: python3-apt 2.9.9build1
ProcVersionSignature: Ubuntu 6.12.0-12.12-generic 6.12.4
Uname: Linux 6.12.0-12-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.32.0-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: sway
Date: Mon Mar 31 15:58:25 2025
InstallationDate: Installed on 2023-08-02 (607 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
ProcEnviron:
LANG=fr_FR.UTF-8
PATH=(custom, no user)
SHELL=/bin/zsh
TERM=alacritty
XDG_RUNTIME_DIR=
SourcePackage: python-apt
UpgradeStatus: Upgraded to plucky on 2024-06-12 (292 days ago)
** Affects: python-apt (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug plucky wayland-session
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-apt in Ubuntu.
https://bugs.launchpad.net/bugs/2105503
Title:
Uncontrolled memory usage
Status in python-apt package in Ubuntu:
New
Bug description:
Here is a simplified snippet, taken from `cnf-extractor`:
```
$ cat apt_file_0ad-data.py
import apt_inst
files = []
debfile = apt_inst.DebFile("0ad-data_0.27.0-1_all.deb")
debfile.data.go(lambda item, data: files.append(item.name))
print(files)
```
To run this, you need the latest `0ad-data` package downloaded next to
the script: `apt download 0ad-data`.
When running this "normally", I can see very high memory usage, sometimes
leading to OOM kill (how I digged into that in the first place):
python3 apt_file_0ad-data.py & ; htop -p $!
Interestingly, when wrapping that with some kind of constraints, the issue
doesn't appear anymore at all, and the memory usage remains low:
prlimit -v536870912 python3 apt_file_0ad-data.py & ; htop -p $!
With that previous command, even the time to finish is divided by two
(~consistently 8s vs 15s without wrapping on my machine), but I didn't take
precise measurements there, so might be noise, but still...
And then one final interesting result:
systemd-run --scope -p MemoryMax=500M --user python3 apt_file_0ad-data.py
Sometimes this works just as with `prlimit`, with slightly higher memory
usage, and sometimes it correctly triggers oom kill, after more than one
minute. Again, the timing benchmark is inaccurate, but still...
ProblemType: Bug
DistroRelease: Ubuntu 25.04
Package: python3-apt 2.9.9build1
ProcVersionSignature: Ubuntu 6.12.0-12.12-generic 6.12.4
Uname: Linux 6.12.0-12-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.32.0-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: sway
Date: Mon Mar 31 15:58:25 2025
InstallationDate: Installed on 2023-08-02 (607 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
ProcEnviron:
LANG=fr_FR.UTF-8
PATH=(custom, no user)
SHELL=/bin/zsh
TERM=alacritty
XDG_RUNTIME_DIR=
SourcePackage: python-apt
UpgradeStatus: Upgraded to plucky on 2024-06-12 (292 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/2105503/+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 2060082] Re: Dublin timezone cause systemd cpu high
I'm not sure about the proposed fix, but: * Dublin is probably not the only timezone impacted. * We should probably try to reproduce that and confirm the bug on Jammy, but also check Noble, just to be sure. ** Tags added: rls-jj-incoming ** Also affects: systemd (Ubuntu Jammy) 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/2060082 Title: Dublin timezone cause systemd cpu high Status in systemd package in Ubuntu: Confirmed Status in systemd source package in Jammy: New Bug description: Systemd version(249) in Jammy Jellyfish is too old, When using the Dublin time zone for daylight saving time switching，the CPU usage will suddenly increase to 100% starting from 2024-03-31 00:00:00 and last for 1 hour, but return to normal at 2024-03-31 02:00:00. plz backport the bugfix to v249 or update 255 version in Jammy Jellyfish to fix it. thank you. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2060082/+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 2083017] Re: network-manager changed path to nm-dhcp-helper, apparmor need update
** Also affects: apparmor (Ubuntu)
Importance: Undecided
Status: New
** Changed in: apparmor (Ubuntu)
Status: New => Confirmed
** Changed in: isc-dhcp (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/2083017
Title:
network-manager changed path to nm-dhcp-helper, apparmor need update
Status in apparmor package in Ubuntu:
Confirmed
Status in isc-dhcp package in Ubuntu:
Invalid
Bug description:
From the Debian Bug report logs - #1055067
isc-dhcp-client: network-manager 1.44.2-3 changed path to nm-dhcp-helper,
apparmor need update
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055067
The problem causes the DHCP fail to receive the IP with this error in
the dmesg command:
[ 1037.911083] audit: type=1400 audit(1727430402.572:1355):
apparmor="DENIED" operation="exec" class="file"
profile="/{,usr/}sbin/dhclient" name="/usr/libexec/nm-dhcp-helper"
pid=6763 comm="dhclient" requested_mask="x" denied_mask="x" fsuid=0
ouid=0
The /etc/apparmor.d/sbin.dhclient file needs to be updated to include
the /usr/libexec/nm-dhcp-helper (instead of
/usr/lib/NetworkManager/nm-dhcp-helper). Just in case, to solve it, I
duplicated the definitions for the NetworkManager/nm-dhcp-helper.
FILE: /etc/apparmor.d/sbin.dhclient
# Support the new executable helper from NetworkManager.
/usr/lib/NetworkManager/nm-dhcp-helper Pxrm,
signal (receive) peer=/usr/lib/NetworkManager/nm-dhcp-helper,
/usr/libexec/nm-dhcp-helper Pxrm,
signal (receive) peer=/usr/libexec/nm-dhcp-helper,
/usr/lib/NetworkManager/nm-dhcp-helper {
#include
#include
/usr/lib/NetworkManager/nm-dhcp-helper mr,
/run/NetworkManager/private-dhcp rw,
signal (send) peer=/sbin/dhclient,
/var/lib/NetworkManager/*lease r,
signal (receive) peer=/usr/sbin/NetworkManager,
ptrace (readby) peer=/usr/sbin/NetworkManager,
network inet dgram,
network inet6 dgram,
}
/usr/libexec/nm-dhcp-helper {
#include
#include
/usr/libexec/nm-dhcp-helper mr,
/run/NetworkManager/private-dhcp rw,
signal (send) peer=/sbin/dhclient,
/var/lib/NetworkManager/*lease r,
signal (receive) peer=/usr/sbin/NetworkManager,
ptrace (readby) peer=/usr/sbin/NetworkManager,
network inet dgram,
network inet6 dgram,
}
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2083017/+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 2103595] Re: apparmor policy prevents unshare --user --map-auto
** Changed in: util-linux (Ubuntu) Milestone: None => ubuntu-25.04-beta ** Tags added: rls-pp-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/2103595 Title: apparmor policy prevents unshare --user --map-auto Status in util-linux package in Ubuntu: New Bug description: In plucky: $ unshare --user --map-auto newuidmap: open of uid_map failed: Permission denied The journal shows: audit: type=1400 audit(1742379629.731:1072): apparmor="AUDIT" operation="exec" class="file" info="ix fallback" profile="unshare" name="/usr/bin/newuidmap" pid=9897 comm="unshare" requested_mask="x" fsuid=1000 ouid=0 target="unpriv_unshare//&unshare" audit: type=1400 audit(1742379629.734:1073): apparmor="DENIED" operation="capable" class="cap" profile="unpriv_unshare" pid=9897 comm="newuidmap" capability=1 capname="dac_override" This also prevents the execution of `autopkgtest -- unshare`, although somehow `sbuild --run-autopkgtest` makes it work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/2103595/+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 2102274] Re: Failure occur during installation of Ubuntu 24.04
*** This bug is a duplicate of bug 2102187 *** https://bugs.launchpad.net/bugs/2102187 ** This bug has been marked a duplicate of bug 2102187 Failure occured during installation of Ubuntu 24.04 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2102274 Title: Failure occur during installation of Ubuntu 24.04 Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: The error occurred on booting from the USB drive. This happened before any prompt to start the installation process. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: ubuntu-desktop 1.539.2 ProcVersionSignature: Ubuntu 6.11.0-17.17~24.04.2-generic 6.11.11 Uname: Linux 6.11.0-17-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.1-0ubuntu3.3 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.498 CloudArchitecture: x86_64 CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud) CurrentDesktop: ubuntu:GNOME Date: Fri Mar 14 06:54:18 2025 LiveMediaBuild: Ubuntu 24.04.2 LTS "Noble Numbat" - Release amd64 (20250215) ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color SourcePackage: ubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2102274/+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 2102187] Re: Failure occured during installation of Ubuntu 24.04
Can you please provide detailed steps to reproduce the issue, so that we can investigate? ** Changed in: ubuntu-meta (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2102187 Title: Failure occured during installation of Ubuntu 24.04 Status in ubuntu-meta package in Ubuntu: Incomplete Bug description: Unable to install Ubuntu 24.04 on my laptop. Failure occur during the early stages of the installation steps. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: ubuntu-desktop 1.539.2 ProcVersionSignature: Ubuntu 6.11.0-17.17~24.04.2-generic 6.11.11 Uname: Linux 6.11.0-17-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.1-0ubuntu3.3 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.498 CloudArchitecture: x86_64 CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud) CurrentDesktop: ubuntu:GNOME Date: Thu Mar 13 14:37:04 2025 LiveMediaBuild: Ubuntu 24.04.2 LTS "Noble Numbat" - Release amd64 (20250215) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color SourcePackage: ubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2102187/+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 1876917] Re: libu2f-udev has been rendered unnecessary by systemd v244
@enr0n you might have more info on the systemd part, let's triage that in meeting, and maybe plan for qq cycle? ** Tags added: rls-pp-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1876917 Title: libu2f-udev has been rendered unnecessary by systemd v244 Status in libu2f-host package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: Since systemd v244, specifically this commit (https://github.com/systemd/systemd/issues/11996), systemd detects U2F devices based on their declared usage (page) and automatically generates the relevant udev rules. Manually maintaining device- specific rules is therefore no longer necessary and libu2f-udev can be removed from libu2f-host. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libu2f-host/+bug/1876917/+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 2060082] Re: Dublin timezone cause systemd cpu high
I took a bit of time to try to reproduce, without success. Here were my steps: $ lxc launch ubuntu:jammy --vm jammy Launching jammy $ lxc exec jammy bash root@jammy:~# apt update && apt install -y atop ... root@jammy:~# systemctl stop systemd-timesyncd root@jammy:~# timedatectl set-timezone Europe/Dublin root@jammy:~# timedatectl set-time "2024-03-30 23:59:50" In another terminal before messing with the time: $ lxc exec jammy htop I did not see init eating 100% CPU, the machine remained mostly idle. Could you please provide more details on how to reproduce the bug? ** Changed in: systemd (Ubuntu Jammy) Status: New => Incomplete ** Changed in: systemd (Ubuntu) Status: Confirmed => Invalid ** Tags removed: rls-jj-incoming -- 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/2060082 Title: Dublin timezone cause systemd cpu high Status in systemd package in Ubuntu: Invalid Status in systemd source package in Jammy: Incomplete Bug description: Systemd version(249) in Jammy Jellyfish is too old, When using the Dublin time zone for daylight saving time switching，the CPU usage will suddenly increase to 100% starting from 2024-03-31 00:00:00 and last for 1 hour, but return to normal at 2024-03-31 02:00:00. plz backport the bugfix to v249 or update 255 version in Jammy Jellyfish to fix it. thank you. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2060082/+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 2083017] Re: network-manager changed path to nm-dhcp-helper, apparmor need update
Looking at the Debian, it seems it's all resolved in unstable/testing,
right? If that's not the case, could you please provide more details,
such as the Ubuntu release where you experience the issue?
** Changed in: apparmor (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/2083017
Title:
network-manager changed path to nm-dhcp-helper, apparmor need update
Status in apparmor package in Ubuntu:
Incomplete
Status in isc-dhcp package in Ubuntu:
Invalid
Bug description:
From the Debian Bug report logs - #1055067
isc-dhcp-client: network-manager 1.44.2-3 changed path to nm-dhcp-helper,
apparmor need update
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055067
The problem causes the DHCP fail to receive the IP with this error in
the dmesg command:
[ 1037.911083] audit: type=1400 audit(1727430402.572:1355):
apparmor="DENIED" operation="exec" class="file"
profile="/{,usr/}sbin/dhclient" name="/usr/libexec/nm-dhcp-helper"
pid=6763 comm="dhclient" requested_mask="x" denied_mask="x" fsuid=0
ouid=0
The /etc/apparmor.d/sbin.dhclient file needs to be updated to include
the /usr/libexec/nm-dhcp-helper (instead of
/usr/lib/NetworkManager/nm-dhcp-helper). Just in case, to solve it, I
duplicated the definitions for the NetworkManager/nm-dhcp-helper.
FILE: /etc/apparmor.d/sbin.dhclient
# Support the new executable helper from NetworkManager.
/usr/lib/NetworkManager/nm-dhcp-helper Pxrm,
signal (receive) peer=/usr/lib/NetworkManager/nm-dhcp-helper,
/usr/libexec/nm-dhcp-helper Pxrm,
signal (receive) peer=/usr/libexec/nm-dhcp-helper,
/usr/lib/NetworkManager/nm-dhcp-helper {
#include
#include
/usr/lib/NetworkManager/nm-dhcp-helper mr,
/run/NetworkManager/private-dhcp rw,
signal (send) peer=/sbin/dhclient,
/var/lib/NetworkManager/*lease r,
signal (receive) peer=/usr/sbin/NetworkManager,
ptrace (readby) peer=/usr/sbin/NetworkManager,
network inet dgram,
network inet6 dgram,
}
/usr/libexec/nm-dhcp-helper {
#include
#include
/usr/libexec/nm-dhcp-helper mr,
/run/NetworkManager/private-dhcp rw,
signal (send) peer=/sbin/dhclient,
/var/lib/NetworkManager/*lease r,
signal (receive) peer=/usr/sbin/NetworkManager,
ptrace (readby) peer=/usr/sbin/NetworkManager,
network inet dgram,
network inet6 dgram,
}
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2083017/+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
