[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] 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 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 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 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 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 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 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 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 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 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 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] [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 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 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 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 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 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 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
** 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 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 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
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] [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 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 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 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 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
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] [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
