[Touch-packages] [Bug 2019856] Re: Add missing ARM-cores to support Grace-based systems
Jammy verification done in comments 31 (with tag flip) and 39. Lunar is now Won't Fix (2024-01-17), thus removing lunar tags. ** Tags removed: block-proposed-lunar verification-done-lunar -- 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/2019856 Title: Add missing ARM-cores to support Grace-based systems Status in util-linux package in Ubuntu: Fix Released Status in util-linux source package in Jammy: Fix Committed Status in util-linux source package in Kinetic: Won't Fix Status in util-linux source package in Lunar: Won't Fix Status in util-linux source package in Mantic: Fix Released Bug description: [Impact] When running "lscpu" on a Grace-based system + Ubuntu 22.04, it doesn't report a model name: Vendor ID: ARM Model: 0 [Fix] Adding the additional arm_part to sys-utils/lscpu-arm.c solves the problem. The commit below adds the specific codes missing from Jammy's version. https://github.com/util-linux/util- linux/commit/6857cccbb4157d5da34ca98f77a0ac9d68e1e740 [Test Steps] * Verify whether output of lscpu is correct on new CPUs; eg: Vendor ID: ARM Model name: Neoverse-V2 * Verify whether output of lscpu doesn't change on old CPUs; eg: Vendor ID: ARM Model name: Neoverse-N1 [What Could Go Wrong] The fix only introduces additional model identifiers to match against and print a model name string, thus regression impact should be contained within lscpu and printing cpus model name on ARM systems. Output doesn't change on systems with non-affected CPU models. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/2019856/+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 2019856] Re: Add missing ARM-cores to support Grace-based systems
PS: the Jammy verification done in comment 31 used version 2.37.2-4ubuntu3.1 (staged in this bug), and that in comment 39 used (newer) version 2.37.2-4ubuntu3.2 (also staged, in bug 2048092) -- both have positive results. BTW, since the newer upload is still planned for staging, not removing the block-proposed-jammy tag, IIUIC. """ In principle the block-proposed- tag should be removed by an SRU team member when accepting a newer upload not planned for further staging. But if they overlook this, it's appropriate for whoever notices it (SRU team, or uploader) to remove the block-proposed- tag with a suitable comment when it no longer applies. """ @ https://wiki.ubuntu.com/StableReleaseUpdates#Staging_an_upload -- 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/2019856 Title: Add missing ARM-cores to support Grace-based systems Status in util-linux package in Ubuntu: Fix Released Status in util-linux source package in Jammy: Fix Committed Status in util-linux source package in Kinetic: Won't Fix Status in util-linux source package in Lunar: Won't Fix Status in util-linux source package in Mantic: Fix Released Bug description: [Impact] When running "lscpu" on a Grace-based system + Ubuntu 22.04, it doesn't report a model name: Vendor ID: ARM Model: 0 [Fix] Adding the additional arm_part to sys-utils/lscpu-arm.c solves the problem. The commit below adds the specific codes missing from Jammy's version. https://github.com/util-linux/util- linux/commit/6857cccbb4157d5da34ca98f77a0ac9d68e1e740 [Test Steps] * Verify whether output of lscpu is correct on new CPUs; eg: Vendor ID: ARM Model name: Neoverse-V2 * Verify whether output of lscpu doesn't change on old CPUs; eg: Vendor ID: ARM Model name: Neoverse-N1 [What Could Go Wrong] The fix only introduces additional model identifiers to match against and print a model name string, thus regression impact should be contained within lscpu and printing cpus model name on ARM systems. Output doesn't change on systems with non-affected CPU models. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/2019856/+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 2054925] Re: Debootstrap fails for Noble with base-files 13ubuntu7
TL;DR: The fix is not needed on Mantic.
This is just to expand a bit on the brief note in '[Where problems could
occur]' ("moved to merging post-extraction"), for clarity.
The code in `scripts/gutsy` (used for noble) is different between Mantic
and Jammy with regards to the order of package extraction and usr-merge
setup, in first_stage_install().
The issue happens in Jammy because usr-merge setup runs _before_
extraction (thus extraction of base-files fails as the
/{bin,lib,lib64,sbin} symlinks already exist):
setup_merged_usr
extract $required
But it doesn't happen in Mantic because usr-merge setup runs _after_
extraction (thus extraction of base-files works as the symlinks don't
yet exist):
extract $required
merge_usr
--
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/2054925
Title:
Debootstrap fails for Noble with base-files 13ubuntu7
Status in base-files package in Ubuntu:
Won't Fix
Status in debootstrap package in Ubuntu:
Fix Released
Status in debootstrap source package in Focal:
In Progress
Status in debootstrap source package in Jammy:
In Progress
Bug description:
[Impact]
The last couple of days, I have been unable to run a successful debootstrap
for Noble Numbat.
Apparently this is caused by the addition of symlinks (/bin, /lib,
/lib64 and /sbin) in base-files 13ubuntu7. According to
debootstrap.log, it fails to extract said symlinks because they
already exist at that point.
This can be reproduced on build hosts running Jammy Jellyfish against
any up-to-date Ubuntu public archive mirror as of today.
# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 22.04.4 LTS
Release: 22.04
Codename: jammy
# apt-cache policy debootstrap
debootstrap:
Installed: 1.0.126+nmu1ubuntu0.5
Candidate: 1.0.126+nmu1ubuntu0.5
Version table:
*** 1.0.126+nmu1ubuntu0.5 500
500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages
500 http://archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages
100 /var/lib/dpkg/status
1.0.126+nmu1 500
500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
500 http://archive.ubuntu.com/ubuntu jammy/main i386 Packages
Attached shell output of two runs of debootstrap. First run uses
mirror archive.ubuntu.com (which as of this report serves base-files
version 13ubuntu7), and second run uses a local custom mirror (which
serves base-files 13ubuntu6). First run fails, second run succeeds.
[Test plan]
Successfully for each of focal, jammy, mantic, noble
- debootstrap
- mksbuild
- pbuilder whatever chroot management tool it has
- ubuntu-image, if we can pull debootstrap from proposed for this
as well as
- debootstrap noble --merged-usr
[Where problems could occur]
We do not anticipate any regressions as we replace the previous *) case for
usrmerge for post-hirsute with a new jammy|kinetic|lunar|mantic one, and the
new solution will only impact noble and onward.
That said, this is a different approach than mantic and newer take,
and a different approach than Debian takes, where they moved to
merging post-extraction, even in stable releases.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/2054925/+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 2054925] Re: Debootstrap fails for Noble with base-files 13ubuntu7
I confirmed that the resulting target dir of debootstrap in Jammy (with patch/MERGED_USR=no) and Mantic is the same, with a comparison of `ls -lR` (normalized for Month/Day/Time fields). ... Test command for Jammy (patched) and Mantic: # debootstrap --arch=amd64 --variant=minbase --keyring /usr/share/keyrings/ubuntu-archive-keyring.gpg noble /tmp/nobletest http://archive.ubuntu.com/ubuntu Dir listing for Jammy (patched) and Mantic: deboostrap-jammy # ls -lR /tmp/nobletest/ > list.jammy deboostrap-mantic # ls -lR /tmp/nobletest/ > list.mantic Normalization and comparison: $ sed -i 's/[A-Z][a-z][a-z] .[0-9] [0-9][0-9]:[0-9][0-9]/DATETIME/' list.jammy list.mantic $ diff -U0 list.jammy list.mantic --- list.jammy 2024-02-26 19:39:49.102864808 -0300 +++ list.mantic 2024-02-26 19:39:49.114864569 -0300 @@ -76 +76 @@ --rw-r--r-- 1 root root 18 DATETIME hostname +-rw-r--r-- 1 root root 19 DATETIME hostname @@ -7093 +7093 @@ --rw-r--r-- 1 root root 60238 DATETIME bootstrap.log +-rw-r--r-- 1 root root 60045 DATETIME bootstrap.log -- 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/2054925 Title: Debootstrap fails for Noble with base-files 13ubuntu7 Status in base-files package in Ubuntu: Won't Fix Status in debootstrap package in Ubuntu: Fix Released Status in debootstrap source package in Focal: In Progress Status in debootstrap source package in Jammy: In Progress Status in base-files source package in Mantic: New Status in debootstrap source package in Mantic: Fix Released Bug description: [Impact] The last couple of days, I have been unable to run a successful debootstrap for Noble Numbat. Apparently this is caused by the addition of symlinks (/bin, /lib, /lib64 and /sbin) in base-files 13ubuntu7. According to debootstrap.log, it fails to extract said symlinks because they already exist at that point. This can be reproduced on build hosts running Jammy Jellyfish against any up-to-date Ubuntu public archive mirror as of today. # lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 22.04.4 LTS Release: 22.04 Codename: jammy # apt-cache policy debootstrap debootstrap: Installed: 1.0.126+nmu1ubuntu0.5 Candidate: 1.0.126+nmu1ubuntu0.5 Version table: *** 1.0.126+nmu1ubuntu0.5 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages 100 /var/lib/dpkg/status 1.0.126+nmu1 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu jammy/main i386 Packages Attached shell output of two runs of debootstrap. First run uses mirror archive.ubuntu.com (which as of this report serves base-files version 13ubuntu7), and second run uses a local custom mirror (which serves base-files 13ubuntu6). First run fails, second run succeeds. [Test plan] Successfully for each of focal, jammy, mantic, noble - debootstrap - mksbuild - pbuilder whatever chroot management tool it has - ubuntu-image, if we can pull debootstrap from proposed for this as well as - debootstrap noble --merged-usr [Where problems could occur] We do not anticipate any regressions as we replace the previous *) case for usrmerge for post-hirsute with a new jammy|kinetic|lunar|mantic one, and the new solution will only impact noble and onward. That said, this is a different approach than mantic and newer take, and a different approach than Debian takes, where they moved to merging post-extraction, even in stable releases. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/2054925/+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 2054925] Re: Debootstrap fails for Noble with base-files 13ubuntu7
Hello Åka, or anyone else affected, Accepted debootstrap into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/debootstrap/1.0.126+nmu1ubuntu0.7 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: debootstrap (Ubuntu Jammy) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- 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/2054925 Title: Debootstrap fails for Noble with base-files 13ubuntu7 Status in base-files package in Ubuntu: Won't Fix Status in debootstrap package in Ubuntu: Fix Released Status in debootstrap source package in Focal: In Progress Status in debootstrap source package in Jammy: Fix Committed Status in base-files source package in Mantic: New Status in debootstrap source package in Mantic: Fix Released Bug description: [Impact] The last couple of days, I have been unable to run a successful debootstrap for Noble Numbat. Apparently this is caused by the addition of symlinks (/bin, /lib, /lib64 and /sbin) in base-files 13ubuntu7. According to debootstrap.log, it fails to extract said symlinks because they already exist at that point. This can be reproduced on build hosts running Jammy Jellyfish against any up-to-date Ubuntu public archive mirror as of today. # lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 22.04.4 LTS Release: 22.04 Codename: jammy # apt-cache policy debootstrap debootstrap: Installed: 1.0.126+nmu1ubuntu0.5 Candidate: 1.0.126+nmu1ubuntu0.5 Version table: *** 1.0.126+nmu1ubuntu0.5 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages 100 /var/lib/dpkg/status 1.0.126+nmu1 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu jammy/main i386 Packages Attached shell output of two runs of debootstrap. First run uses mirror archive.ubuntu.com (which as of this report serves base-files version 13ubuntu7), and second run uses a local custom mirror (which serves base-files 13ubuntu6). First run fails, second run succeeds. [Test plan] Successfully for each of focal, jammy, mantic, noble - debootstrap - mksbuild - pbuilder whatever chroot management tool it has - ubuntu-image, if we can pull debootstrap from proposed for this as well as - debootstrap noble --merged-usr [Where problems could occur] We do not anticipate any regressions as we replace the previous *) case for usrmerge for post-hirsute with a new jammy|kinetic|lunar|mantic one, and the new solution will only impact noble and onward. That said, this is a different approach than mantic and newer take, and a different approach than Debian takes, where they moved to merging post-extraction, even in stable releases. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/2054925/+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 2033892] Re: ls -l triggers mount of autofs shares when --ghost option is present or browse_mode is enabled
** Tags removed: sts-sponsor -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/2033892 Title: ls -l triggers mount of autofs shares when --ghost option is present or browse_mode is enabled Status in coreutils package in Ubuntu: Fix Released Status in coreutils source package in Jammy: In Progress Status in coreutils package in Fedora: Fix Released Bug description: [Impact] Issuing a 'ls -l' or a 'stat' on an autofs share when you have set --ghost in the auto.master file, or browse_mode=yes in autofs.conf will lead to the shares being mounted, when they didn't previously. Disks / shares may not be present and the mounts may fail, leading to errors in your output. This is a behaviour change in autofs 8.32, which occurred in the transition to using statx() instead of stat()/lstat() in previous releases. There doesn't seem to be any workarounds, apart from not running a 'ls -l' in your autofs share directory. [Testcase] Start two Jammy VMs. One will be a NFS server, the other, the client. NFS server: Server VM: $ sudo hostnamectl set-hostname jammy-nfs-server $ sudo apt update && sudo apt upgrade -y $ sudo apt install nfs-kernel-server $ sudo mkdir /export $ sudo mkdir /export/users $ sudo vi /etc/exports # add the following lines: /export 192.168.122.0/24(rw,fsid=0,no_subtree_check,sync) /export/users 192.168.122.0/24(rw,nohide,insecure,no_subtree_check,sync) $ sudo systemctl restart nfs-server.service AutoFS Client: $ sudo apt update $ sudo apt install autofs $ sudo vim /etc/autofs.conf browse_mode = yes $ sudo mkdir /mnt2 $ sudo vim /etc/auto.master /mnt2 /etc/auto.indirect $ sudo vim /etc/auto.indirect export 192.168.122.18:/export export-missing 192.168.122.18:/export-missing $ sudo reboot $ cd /mnt2 $ ls -l ls: cannot access 'export-missing': No such file or directory total 4 drwxr-xr-x 3 root root 4096 Feb 12 21:48 export d? ? ?? ?? export-missing $ mount -l | grep /mnt2 /etc/auto.indirect on /mnt2 type autofs (rw,relatime,fd=6,pgrp=634,timeout=300,minproto=5,maxproto=5,indirect,pipe_ino=21561) 192.168.122.18:/export on /mnt2/export type nfs (rw,relatime,vers=3,rsize=524288,wsize=524288,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=192.168.122.18,mountvers=3,mountport=35786,mountproto=udp,local_lock=none,addr=192.168.122.18) We see the mount for export occurred, and export-missing was attempted, but it was either bogus or the disk was not present, leading to a "No such file or directory" error. There are test packages available in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/sf378489-test If you install them, this is what should occur: $ ls -l total 0 drwxr-xr-x 2 root root 0 Feb 12 22:01 export drwxr-xr-x 2 root root 0 Feb 12 22:01 export-missing $ mount -l | grep /mnt2 /etc/auto.indirect on /mnt2 type autofs (rw,relatime,fd=6,pgrp=636,timeout=300,minproto=5,maxproto=5,indirect,pipe_ino=18346) No mounts happen, and no errors either. [Where problems could occur] We are changing the behaviour of core utilities, ls and stat, such that they no longer attempt to mount autofs shares when --ghost option is present or browse_mode is enabled. This is the intended behaviour in the first place, and has been this way for at least a decade prior, and was changed to return to this behaviour shortly after the release of coreutils that introduced statx() that caused automounts to occur. It is unlikely any system administrators are relying on the behaviour found in jammy in any scripts or day to day operations that would be adversely affected by the change. The worst case scenario is that a user doing an 'ls -l' on an unmounted disk finds the mount doesn't automatically occur, and they have to attach the disk and issue the mount themselves. If a regression were to occur, it would be limited to the ls and stat commands, specifically when listing directories linked to autofs mountpoints. [Other info] The automount behaviour change was introduced upstream in version 8.32, with the introduction of the statx() call. This means only Jammy is affected. It was quickly reverted back to how it was originally in version 9.1, which is already available in Mantic and onward. The commits that solve the issue are: commit 85c975df2c25bd799370b04bb294e568e001102f From: Rohan Sable Date: Mon, 7 Mar 2022 14:14:13 + Subject: ls: avoid triggering automounts Link: https://git.savannah.gnu.org/gitweb/?p=coreutils.git;a=commitdiff;h=v9.0-177-g85c975df2c2 commit 92cb8427c537f37edd43c5cef1909585201372ab From: Pádraig Brady Date: Mon, 7 Mar 2022 23:29:20 + Subject: stat: only automount with --cached=never Link: https://g
[Touch-packages] [Bug 2033892] Re: ls -l triggers mount of autofs shares when --ghost option is present or browse_mode is enabled
Reviewed and sponsored to Jammy; thanks! Notes: - Please add test for `stat` as well (bottom of tests comment). - I just changed the DEP3 Origin tag (commit ID; backport_ed_). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/2033892 Title: ls -l triggers mount of autofs shares when --ghost option is present or browse_mode is enabled Status in coreutils package in Ubuntu: Fix Released Status in coreutils source package in Jammy: In Progress Status in coreutils package in Fedora: Fix Released Bug description: [Impact] Issuing a 'ls -l' or a 'stat' on an autofs share when you have set --ghost in the auto.master file, or browse_mode=yes in autofs.conf will lead to the shares being mounted, when they didn't previously. Disks / shares may not be present and the mounts may fail, leading to errors in your output. This is a behaviour change in autofs 8.32, which occurred in the transition to using statx() instead of stat()/lstat() in previous releases. There doesn't seem to be any workarounds, apart from not running a 'ls -l' in your autofs share directory. [Testcase] Start two Jammy VMs. One will be a NFS server, the other, the client. NFS server: Server VM: $ sudo hostnamectl set-hostname jammy-nfs-server $ sudo apt update && sudo apt upgrade -y $ sudo apt install nfs-kernel-server $ sudo mkdir /export $ sudo mkdir /export/users $ sudo vi /etc/exports # add the following lines: /export 192.168.122.0/24(rw,fsid=0,no_subtree_check,sync) /export/users 192.168.122.0/24(rw,nohide,insecure,no_subtree_check,sync) $ sudo systemctl restart nfs-server.service AutoFS Client: $ sudo apt update $ sudo apt install autofs $ sudo vim /etc/autofs.conf browse_mode = yes $ sudo mkdir /mnt2 $ sudo vim /etc/auto.master /mnt2 /etc/auto.indirect $ sudo vim /etc/auto.indirect export 192.168.122.18:/export export-missing 192.168.122.18:/export-missing $ sudo reboot $ cd /mnt2 $ ls -l ls: cannot access 'export-missing': No such file or directory total 4 drwxr-xr-x 3 root root 4096 Feb 12 21:48 export d? ? ?? ?? export-missing $ mount -l | grep /mnt2 /etc/auto.indirect on /mnt2 type autofs (rw,relatime,fd=6,pgrp=634,timeout=300,minproto=5,maxproto=5,indirect,pipe_ino=21561) 192.168.122.18:/export on /mnt2/export type nfs (rw,relatime,vers=3,rsize=524288,wsize=524288,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=192.168.122.18,mountvers=3,mountport=35786,mountproto=udp,local_lock=none,addr=192.168.122.18) We see the mount for export occurred, and export-missing was attempted, but it was either bogus or the disk was not present, leading to a "No such file or directory" error. There are test packages available in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/sf378489-test If you install them, this is what should occur: $ ls -l total 0 drwxr-xr-x 2 root root 0 Feb 12 22:01 export drwxr-xr-x 2 root root 0 Feb 12 22:01 export-missing $ mount -l | grep /mnt2 /etc/auto.indirect on /mnt2 type autofs (rw,relatime,fd=6,pgrp=636,timeout=300,minproto=5,maxproto=5,indirect,pipe_ino=18346) No mounts happen, and no errors either. [Where problems could occur] We are changing the behaviour of core utilities, ls and stat, such that they no longer attempt to mount autofs shares when --ghost option is present or browse_mode is enabled. This is the intended behaviour in the first place, and has been this way for at least a decade prior, and was changed to return to this behaviour shortly after the release of coreutils that introduced statx() that caused automounts to occur. It is unlikely any system administrators are relying on the behaviour found in jammy in any scripts or day to day operations that would be adversely affected by the change. The worst case scenario is that a user doing an 'ls -l' on an unmounted disk finds the mount doesn't automatically occur, and they have to attach the disk and issue the mount themselves. If a regression were to occur, it would be limited to the ls and stat commands, specifically when listing directories linked to autofs mountpoints. [Other info] The automount behaviour change was introduced upstream in version 8.32, with the introduction of the statx() call. This means only Jammy is affected. It was quickly reverted back to how it was originally in version 9.1, which is already available in Mantic and onward. The commits that solve the issue are: commit 85c975df2c25bd799370b04bb294e568e001102f From: Rohan Sable Date: Mon, 7 Mar 2022 14:14:13 + Subject: ls: avoid triggering automounts Link: https://git.savannah.gnu.org/gitweb/?p=coreutils.git;a=commitdiff;h=v9.0-177-g85c975df2c2 commit 92cb8427c537f37edd43c5cef1
[Touch-packages] [Bug 2033892] Re: ls -l triggers mount of autofs shares when --ghost option is present or browse_mode is enabled
Test Steps: lxc launch --vm ubuntu:$SERIES autofs-$SERIES lxc shell autofs-$SERIES # replace linux-kvm with linux-generic for autofs DEBIAN_FRONTEND=noninteractive apt remove --yes --purge '?and(?installed,?or(?source-package(linux-kvm),?source-package(linux-meta-kvm)))' dpkg -s linux-image-virtual >/dev/null 2>/dev/null || (apt install --yes linux-image-virtual && reboot) apt update && apt install -y autofs sed '/^browse_mode =/ s/=.*/= yes/' -i /etc/autofs.conf echo '/test /etc/auto.test' >/etc/auto.master.d/test.autofs cat >/etc/auto.test
[Touch-packages] [Bug 2033892] Re: ls -l triggers mount of autofs shares when --ghost option is present or browse_mode is enabled
Considerations for the SRU team: I confirmed that the behavior in Jammy is different than Focal and Mantic, the previous / next supported releases. (Steps in the next comment.) So, although this SRU changes behavior in a stable release (generally not OK in SRUs), it is actually Jammy that changed behavior _across_ stable releases (and to a buggy one!). Thus, the SRU is reasonably _restoring_ (arguably, _fixing_) the _expected_ behavior. So, this looks OK for SRU, IMHO. Additionally, I considered two points before sponsoring this. 1) The impact of the code changes to non-autofs/non-automount: And it seems virtually zero, considering the man pages explain the flag now used in statx() is used in other related syscalls (stat, lstat, fstatat), which have it implied since Linux 4.11. And it indeed only affects automount (note the flag name). So, even though this change is "new" in Jammy, it's been tested in older and later releases for a long time (pre-Bionic kernels). stat(2): AT_NO_AUTOMOUNT (since Linux 2.6.38) [...] Since Linux 4.11 this flag is implied. statx(2): AT_NO_AUTOMOUNT [...] All of stat(2), lstat(2), and fstatat(2) act as though AT_NO_AUTOMOUNT was set. 2) Whether users may have started to rely on this behavior I agree this is unlikely, and think so because of 3 points: 2.1) This behavior did not exist in previous releases, which reduces the chances it has been 'learned' before. 2.2) The usage of autofs/automount rely on access to be made _to a particular mountpoint_ in order for it to be _mounted_. This is reflected in different documentation sources online, so it is likely that this is the way that has been 'learned'. 2.3) The safe side is, _even if_ an user started to rely on this behavior to automount the subdirs, the very next thing they will do (if they actually need that subdir mounted) is to _access_ that subdir - which can mount it just as before! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/2033892 Title: ls -l triggers mount of autofs shares when --ghost option is present or browse_mode is enabled Status in coreutils package in Ubuntu: Fix Released Status in coreutils source package in Jammy: In Progress Status in coreutils package in Fedora: Fix Released Bug description: [Impact] Issuing a 'ls -l' or a 'stat' on an autofs share when you have set --ghost in the auto.master file, or browse_mode=yes in autofs.conf will lead to the shares being mounted, when they didn't previously. Disks / shares may not be present and the mounts may fail, leading to errors in your output. This is a behaviour change in autofs 8.32, which occurred in the transition to using statx() instead of stat()/lstat() in previous releases. There doesn't seem to be any workarounds, apart from not running a 'ls -l' in your autofs share directory. [Testcase] Start two Jammy VMs. One will be a NFS server, the other, the client. NFS server: Server VM: $ sudo hostnamectl set-hostname jammy-nfs-server $ sudo apt update && sudo apt upgrade -y $ sudo apt install nfs-kernel-server $ sudo mkdir /export $ sudo mkdir /export/users $ sudo vi /etc/exports # add the following lines: /export 192.168.122.0/24(rw,fsid=0,no_subtree_check,sync) /export/users 192.168.122.0/24(rw,nohide,insecure,no_subtree_check,sync) $ sudo systemctl restart nfs-server.service AutoFS Client: $ sudo apt update $ sudo apt install autofs $ sudo vim /etc/autofs.conf browse_mode = yes $ sudo mkdir /mnt2 $ sudo vim /etc/auto.master /mnt2 /etc/auto.indirect $ sudo vim /etc/auto.indirect export 192.168.122.18:/export export-missing 192.168.122.18:/export-missing $ sudo reboot $ cd /mnt2 $ ls -l ls: cannot access 'export-missing': No such file or directory total 4 drwxr-xr-x 3 root root 4096 Feb 12 21:48 export d? ? ?? ?? export-missing $ mount -l | grep /mnt2 /etc/auto.indirect on /mnt2 type autofs (rw,relatime,fd=6,pgrp=634,timeout=300,minproto=5,maxproto=5,indirect,pipe_ino=21561) 192.168.122.18:/export on /mnt2/export type nfs (rw,relatime,vers=3,rsize=524288,wsize=524288,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=192.168.122.18,mountvers=3,mountport=35786,mountproto=udp,local_lock=none,addr=192.168.122.18) We see the mount for export occurred, and export-missing was attempted, but it was either bogus or the disk was not present, leading to a "No such file or directory" error. There are test packages available in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/sf378489-test If you install them, this is what should occur: $ ls -l total 0 drwxr-xr-x 2 root root 0 Feb 12 22:01 expor
[Touch-packages] [Bug 2054925] Re: Debootstrap fails for Noble with base-files 13ubuntu7
The changes for Focal had a syntax error (double ';;' lines, not present in Jammy) which causes debootstrap to fail early and silently, even for a previously working series. Original: $ sudo debootstrap --variant=minbase focal /tmp/debootstrap.focal http://br.archive.ubuntu.com/ubuntu ... I: Base system installed successfully. $ echo $? 0 Patched: $ sudo debootstrap --variant=minbase focal /tmp/debootstrap.focal http://br.archive.ubuntu.com/ubuntu $ echo $? 2 Addressed this issue; verified the diff only changed in that regard; and re-uploaded. $ diff -U0 debootstrap_1.0.118ubuntu1.12_1.0.118ubuntu1.13.diff debdiff | grep -v '^@@' | sort | uniq -c | sort 1 +++ debdiff 2024-03-04 21:01:43.500570118 + 1 --- debootstrap_1.0.118ubuntu1.12_1.0.118ubuntu1.13.diff 2024-02-26 15:24:26.0 + 32 +@@ -78,7 +78,14 @@ 32 -+ ;; 32 -@@ -78,7 +78,15 @@ -- 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/2054925 Title: Debootstrap fails for Noble with base-files 13ubuntu7 Status in base-files package in Ubuntu: Won't Fix Status in debootstrap package in Ubuntu: Fix Released Status in debootstrap source package in Focal: Fix Committed Status in debootstrap source package in Jammy: Fix Released Status in base-files source package in Mantic: New Status in debootstrap source package in Mantic: Fix Released Bug description: [Impact] The last couple of days, I have been unable to run a successful debootstrap for Noble Numbat. Apparently this is caused by the addition of symlinks (/bin, /lib, /lib64 and /sbin) in base-files 13ubuntu7. According to debootstrap.log, it fails to extract said symlinks because they already exist at that point. This can be reproduced on build hosts running Jammy Jellyfish against any up-to-date Ubuntu public archive mirror as of today. # lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 22.04.4 LTS Release: 22.04 Codename: jammy # apt-cache policy debootstrap debootstrap: Installed: 1.0.126+nmu1ubuntu0.5 Candidate: 1.0.126+nmu1ubuntu0.5 Version table: *** 1.0.126+nmu1ubuntu0.5 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages 100 /var/lib/dpkg/status 1.0.126+nmu1 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu jammy/main i386 Packages Attached shell output of two runs of debootstrap. First run uses mirror archive.ubuntu.com (which as of this report serves base-files version 13ubuntu7), and second run uses a local custom mirror (which serves base-files 13ubuntu6). First run fails, second run succeeds. [Test plan] Successfully for each of focal, jammy, mantic, noble - debootstrap - mk-sbuild - pbuilder-dist $release create - ubuntu-image, if we can pull debootstrap from proposed for this as well as - debootstrap noble --merged-usr [Where problems could occur] We do not anticipate any regressions as we replace the previous *) case for usrmerge for post-hirsute with a new jammy|kinetic|lunar|mantic one, and the new solution will only impact noble and onward. That said, this is a different approach than mantic and newer take, and a different approach than Debian takes, where they moved to merging post-extraction, even in stable releases. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/2054925/+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 2054925] Re: Debootstrap fails for Noble with base-files 13ubuntu7
Testing with the change applied: $ sudo debootstrap --variant=minbase noble /tmp/debootstrap.noble http://br.archive.ubuntu.com/ubuntu ... I: Base system installed successfully. $ echo $? 0 $ ls -l /tmp/debootstrap.noble/ | grep usr/ lrwxrwxrwx 1 root root7 Feb 22 14:39 bin -> usr/bin lrwxrwxrwx 1 root root7 Feb 22 14:39 lib -> usr/lib lrwxrwxrwx 1 root root9 Feb 22 14:39 lib64 -> usr/lib64 lrwxrwxrwx 1 root root8 Feb 22 14:39 sbin -> usr/sbin ** Changed in: debootstrap (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags removed: verification-done ** Tags added: verification-needed verification-needed-focal -- 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/2054925 Title: Debootstrap fails for Noble with base-files 13ubuntu7 Status in base-files package in Ubuntu: Won't Fix Status in debootstrap package in Ubuntu: Fix Released Status in debootstrap source package in Focal: Fix Committed Status in debootstrap source package in Jammy: Fix Released Status in base-files source package in Mantic: New Status in debootstrap source package in Mantic: Fix Released Bug description: [Impact] The last couple of days, I have been unable to run a successful debootstrap for Noble Numbat. Apparently this is caused by the addition of symlinks (/bin, /lib, /lib64 and /sbin) in base-files 13ubuntu7. According to debootstrap.log, it fails to extract said symlinks because they already exist at that point. This can be reproduced on build hosts running Jammy Jellyfish against any up-to-date Ubuntu public archive mirror as of today. # lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 22.04.4 LTS Release: 22.04 Codename: jammy # apt-cache policy debootstrap debootstrap: Installed: 1.0.126+nmu1ubuntu0.5 Candidate: 1.0.126+nmu1ubuntu0.5 Version table: *** 1.0.126+nmu1ubuntu0.5 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages 100 /var/lib/dpkg/status 1.0.126+nmu1 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu jammy/main i386 Packages Attached shell output of two runs of debootstrap. First run uses mirror archive.ubuntu.com (which as of this report serves base-files version 13ubuntu7), and second run uses a local custom mirror (which serves base-files 13ubuntu6). First run fails, second run succeeds. [Test plan] Successfully for each of focal, jammy, mantic, noble - debootstrap - mk-sbuild - pbuilder-dist $release create - ubuntu-image, if we can pull debootstrap from proposed for this as well as - debootstrap noble --merged-usr [Where problems could occur] We do not anticipate any regressions as we replace the previous *) case for usrmerge for post-hirsute with a new jammy|kinetic|lunar|mantic one, and the new solution will only impact noble and onward. That said, this is a different approach than mantic and newer take, and a different approach than Debian takes, where they moved to merging post-extraction, even in stable releases. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/2054925/+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 2054925] Please test proposed package
Hello Åka, or anyone else affected, Accepted debootstrap into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/debootstrap/1.0.118ubuntu1.13 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- 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/2054925 Title: Debootstrap fails for Noble with base-files 13ubuntu7 Status in base-files package in Ubuntu: Won't Fix Status in debootstrap package in Ubuntu: Fix Released Status in debootstrap source package in Focal: Fix Committed Status in debootstrap source package in Jammy: Fix Released Status in base-files source package in Mantic: New Status in debootstrap source package in Mantic: Fix Released Bug description: [Impact] The last couple of days, I have been unable to run a successful debootstrap for Noble Numbat. Apparently this is caused by the addition of symlinks (/bin, /lib, /lib64 and /sbin) in base-files 13ubuntu7. According to debootstrap.log, it fails to extract said symlinks because they already exist at that point. This can be reproduced on build hosts running Jammy Jellyfish against any up-to-date Ubuntu public archive mirror as of today. # lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 22.04.4 LTS Release: 22.04 Codename: jammy # apt-cache policy debootstrap debootstrap: Installed: 1.0.126+nmu1ubuntu0.5 Candidate: 1.0.126+nmu1ubuntu0.5 Version table: *** 1.0.126+nmu1ubuntu0.5 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages 100 /var/lib/dpkg/status 1.0.126+nmu1 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu jammy/main i386 Packages Attached shell output of two runs of debootstrap. First run uses mirror archive.ubuntu.com (which as of this report serves base-files version 13ubuntu7), and second run uses a local custom mirror (which serves base-files 13ubuntu6). First run fails, second run succeeds. [Test plan] Successfully for each of focal, jammy, mantic, noble - debootstrap - mk-sbuild - pbuilder-dist $release create - ubuntu-image, if we can pull debootstrap from proposed for this as well as - debootstrap noble --merged-usr [Where problems could occur] We do not anticipate any regressions as we replace the previous *) case for usrmerge for post-hirsute with a new jammy|kinetic|lunar|mantic one, and the new solution will only impact noble and onward. That said, this is a different approach than mantic and newer take, and a different approach than Debian takes, where they moved to merging post-extraction, even in stable releases. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/2054925/+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 2054925] Re: Debootstrap fails for Noble with base-files 13ubuntu7
> Apologies, I saw the same issue locally fixed it but must have forgotten to build a new .dsc:/ No worries; thanks for mentioning! -- 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/2054925 Title: Debootstrap fails for Noble with base-files 13ubuntu7 Status in base-files package in Ubuntu: Won't Fix Status in debootstrap package in Ubuntu: Fix Released Status in debootstrap source package in Focal: Fix Committed Status in debootstrap source package in Jammy: Fix Released Status in base-files source package in Mantic: New Status in debootstrap source package in Mantic: Fix Released Bug description: [Impact] The last couple of days, I have been unable to run a successful debootstrap for Noble Numbat. Apparently this is caused by the addition of symlinks (/bin, /lib, /lib64 and /sbin) in base-files 13ubuntu7. According to debootstrap.log, it fails to extract said symlinks because they already exist at that point. This can be reproduced on build hosts running Jammy Jellyfish against any up-to-date Ubuntu public archive mirror as of today. # lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 22.04.4 LTS Release: 22.04 Codename: jammy # apt-cache policy debootstrap debootstrap: Installed: 1.0.126+nmu1ubuntu0.5 Candidate: 1.0.126+nmu1ubuntu0.5 Version table: *** 1.0.126+nmu1ubuntu0.5 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages 100 /var/lib/dpkg/status 1.0.126+nmu1 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu jammy/main i386 Packages Attached shell output of two runs of debootstrap. First run uses mirror archive.ubuntu.com (which as of this report serves base-files version 13ubuntu7), and second run uses a local custom mirror (which serves base-files 13ubuntu6). First run fails, second run succeeds. [Test plan] Successfully for each of focal, jammy, mantic, noble - debootstrap - mk-sbuild - pbuilder-dist $release create - ubuntu-image, if we can pull debootstrap from proposed for this as well as - debootstrap noble --merged-usr [Where problems could occur] We do not anticipate any regressions as we replace the previous *) case for usrmerge for post-hirsute with a new jammy|kinetic|lunar|mantic one, and the new solution will only impact noble and onward. That said, this is a different approach than mantic and newer take, and a different approach than Debian takes, where they moved to merging post-extraction, even in stable releases. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/2054925/+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 2002043] Re: Python extension modules get built using wrong compiler flags with python2
Just a few observations before release. 1) The verification for Jammy apparently has a copy-paste error, as the banner about the env var is present (step 5) _before_ the package from -proposed -- which adds it -- is installed (step 6). To be clear, this is not a problem and should not block the release, as the _new_ behavior (with -proposed installed) is what matters, and that looks correct in the output: - env var undefined/no opt-in = old behavior; - env var defined/opted-in = new behavior. The verification for Focal is OK on that regard (does not show the banner in step 5). 2) The autopkgtests for python2.7/focal failed, but this is not due to these changes. I re-run the tests with the trigger migration-reference/0, and they continue to fail. This is expected, since the changes are opt-in / are not enabled by default. The only change which _is_ enabled by default is the new banner during build, but that output is likely not checked for, I'd imagine (ie, it's OK to change). 3) There's been a recent rebuild of the autopkgtest database, and I'd have to verify the status (ie, finished?) and impact (eg, report pages) at the moment to make sure this is OK on that regard. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/2002043 Title: Python extension modules get built using wrong compiler flags with python2 Status in python2.7 package in Ubuntu: Invalid Status in python2.7 source package in Bionic: Won't Fix Status in python2.7 source package in Focal: Fix Committed Status in python2.7 source package in Jammy: Fix Committed Status in python2.7 source package in Kinetic: Invalid Status in python2.7 source package in Lunar: Invalid Status in python2.7 source package in Mantic: Invalid Bug description: [ Impact ] When compiling Python extensions using Python2, CFLAGS optimization flags are dropped. This behavior has been caused by our update in this patch http://archive.ubuntu.com/ubuntu/pool/universe/p/python2.7/python2.7_2.7.18-1~20.04.3.diff.gz which differs from upstream. The fix modifies the portion of code in Lib/distutils/sysconfig.py which gets the cflags from the environments, and includes the dropped OPT flag from get_config_vars(). [ Test Plan ] There will be 2 separate tests for this bug: * Ensuring no-change rebuilds are not changed * Ensuring local builds are not changed unless environment variable is set Test 1) No-change rebuilds To test that no-change rebuilds are not changed, the package python- stdlib-extensions will be built against the new python2.7, and confirm the compiler flags are not altered. This will be a manual test and visual inspection of the build logs. Test 2) Functional test 1. Create test container $ lxc launch ubuntu:jammy jammy-2002043 $ lxc shell jammy-2002043 2. Install required packages For Jammy # apt update -y && apt install -y python2 python-pip For Focal # apt update -y && apt install -y python2 python-setuptools gcc 3. Create test files # mkdir testprog # cd testprog # cat >setup.py
[Touch-packages] [Bug 2002043] Re: Python extension modules get built using wrong compiler flags with python2
Hey Mitchell,
No, the autopkgtests re-run for python2.7/focal are done and OK ('they continue
to fail').
Link: [1] (see the Focal results on diff archs have 'migration-reference/0' and
'mfo').
The autopkgtests point pending is a clarification on the
database/results, ie, whether we can trust the report pages (pending-
sru, update_excuses).
We'll check that. Thanks!
[1] https://autopkgtest.ubuntu.com/packages/python2.7
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python2.7 in Ubuntu.
https://bugs.launchpad.net/bugs/2002043
Title:
Python extension modules get built using wrong compiler flags with
python2
Status in python2.7 package in Ubuntu:
Invalid
Status in python2.7 source package in Bionic:
Won't Fix
Status in python2.7 source package in Focal:
Fix Committed
Status in python2.7 source package in Jammy:
Fix Committed
Status in python2.7 source package in Kinetic:
Invalid
Status in python2.7 source package in Lunar:
Invalid
Status in python2.7 source package in Mantic:
Invalid
Bug description:
[ Impact ]
When compiling Python extensions using Python2, CFLAGS optimization
flags are dropped.
This behavior has been caused by our update in this patch
http://archive.ubuntu.com/ubuntu/pool/universe/p/python2.7/python2.7_2.7.18-1~20.04.3.diff.gz
which differs from upstream.
The fix modifies the portion of code in Lib/distutils/sysconfig.py
which gets the cflags from the environments, and includes the dropped
OPT flag from get_config_vars().
[ Test Plan ]
There will be 2 separate tests for this bug:
* Ensuring no-change rebuilds are not changed
* Ensuring local builds are not changed unless environment variable is set
Test 1) No-change rebuilds
To test that no-change rebuilds are not changed, the package python-
stdlib-extensions will be built against the new python2.7, and confirm
the compiler flags are not altered. This will be a manual test and
visual inspection of the build logs.
Test 2) Functional test
1. Create test container
$ lxc launch ubuntu:jammy jammy-2002043
$ lxc shell jammy-2002043
2. Install required packages
For Jammy
# apt update -y && apt install -y python2 python-pip
For Focal
# apt update -y && apt install -y python2 python-setuptools gcc
3. Create test files
# mkdir testprog
# cd testprog
# cat >setup.py
[Touch-packages] [Bug 2002043] Re: Python extension modules get built using wrong compiler flags with python2
RELEASE=focal
TRIGGER=python2.7/2.7.18-1~20.04.4
sqlite3 autopkgtest.db -column -header \
"SELECT test.release, test.arch, test.package, "\
" result.version, result.exitcode, "\
" result.triggers, result.requester "\
"FROM test, result "\
"WHERE test.id = result.test_id "\
"AND test.release = '${RELEASE}' "\
"AND result.triggers LIKE '%${TRIGGER}%' "\
"ORDER BY test.release, test.package, test.arch"
release arch packageversion exitcode
triggersrequester
--- --- -
-- -
focalamd64dbus-python1.2.16-1build10
python2.7/2.7.18-1~20.04.4
focalarm64dbus-python1.2.16-1build10
python2.7/2.7.18-1~20.04.4
focalarmhfdbus-python1.2.16-1build10
python2.7/2.7.18-1~20.04.4
focali386 dbus-python1.2.16-1build114
python2.7/2.7.18-1~20.04.4
focalppc64el dbus-python1.2.16-1build10
python2.7/2.7.18-1~20.04.4
focals390xdbus-python1.2.16-1build10
python2.7/2.7.18-1~20.04.4
focalamd64kodi 2:18.6+dfsg1-2ubuntu1 0
python2.7/2.7.18-1~20.04.4
focalarm64kodi 2:18.6+dfsg1-2ubuntu1 0
python2.7/2.7.18-1~20.04.4
focalarmhfkodi 2:18.6+dfsg1-2ubuntu1 0
python2.7/2.7.18-1~20.04.4
focalppc64el kodi 2:18.6+dfsg1-2ubuntu1 0
python2.7/2.7.18-1~20.04.4
focalamd64libapache2-mod-python 3.3.1-11ubuntu5 0
python2.7/2.7.18-1~20.04.4
focalarm64libapache2-mod-python 3.3.1-11ubuntu5 0
python2.7/2.7.18-1~20.04.4
focalarmhflibapache2-mod-python 3.3.1-11ubuntu5 0
python2.7/2.7.18-1~20.04.4
focalppc64el libapache2-mod-python 3.3.1-11ubuntu5 0
python2.7/2.7.18-1~20.04.4
focals390xlibapache2-mod-python 3.3.1-11ubuntu5 0
python2.7/2.7.18-1~20.04.4
focalamd64libgnatcoll-bindings 19-2 0
python2.7/2.7.18-1~20.04.4
focalarm64libgnatcoll-bindings 19-2 0
python2.7/2.7.18-1~20.04.4
focalarmhflibgnatcoll-bindings 19-2 0
python2.7/2.7.18-1~20.04.4
focalppc64el libgnatcoll-bindings 19-2 0
python2.7/2.7.18-1~20.04.4
focals390xlibgnatcoll-bindings 19-2 0
python2.7/2.7.18-1~20.04.4
focalamd64libxml22.9.10+dfsg-5ubuntu0.20.04.6 0
python2.7/2.7.18-1~20.04.4
focalarm64libxml22.9.10+dfsg-5ubuntu0.20.04.6 0
python2.7/2.7.18-1~20.04.4
focalarmhflibxml22.9.10+dfsg-5ubuntu0.20.04.6 0
python2.7/2.7.18-1~20.04.4
focali386 libxml22.9.10+dfsg-5ubuntu0.20.04.6 12
python2.7/2.7.18-1~20.04.4
focalppc64el libxml22.9.10+dfsg-5ubuntu0.20.04.6 0
python2.7/2.7.18-1~20.04.4
focals390xlibxml22.9.10+dfsg-5ubuntu0.20.04.6 0
python2.7/2.7.18-1~20.04.4
focalamd64llvm-toolchain-7 1:7.0.1-120
python2.7/2.7.18-1~20.04.4
focalarm64llvm-toolchain-7 1:7.0.1-124
python2.7/2.7.18-1~20.04.4
focalarmhfllvm-toolchain-7 1:7.0.1-124
python2.7/2.7.18-1~20.04.4
focalppc64el llvm-toolchain-7 1:7.0.1-124
python2.7/2.7.18-1~20.04.4
focalamd64mercurial 5.3.1-1ubuntu14
python2.7/2.7.18-1~20.04.4
focalarm64mercurial 5.3.1-1ubuntu14
python2.7/2.7.18-1~20.04.4
focalarmhfmercurial 5.3.1-1ubuntu14
python2.7/2.7.18-1~20.04.4
focali386 mercurial 5.3.1-1ubuntu112
python2.7/2.7.18-1~20.04.4
focalppc64el mercurial 5.3.1-1ubuntu14
python2.7/2.7.18-1~20.04.4
focals390xmercurial 5.3.1-1ubuntu14
python2.7/2.7.18-1~20.04.4
focalamd64mod-wsgi 4.6.8-1ubuntu3.1 0
python2.7/2.7.18-1~20.04.4
focalarm64mod-wsgi 4.6.8-1ubuntu3.1 0
python2.7/2.7.18-1~20.04.4
focalarmhfmod-wsgi 4.6.8-1ubuntu3.1 0
python2.7/2.7.18-1~20.04.4
focalppc64el mod-wsgi 4.6.8-1ubuntu3.1 0
python2.7
[Touch-packages] [Bug 2002043] Re: Python extension modules get built using wrong compiler flags with python2
RELEASE=jammy
TRIGGER=python2.7/2.7.18-13ubuntu1.2
sqlite3 autopkgtest.db -column -header \
"SELECT test.release, test.arch, test.package, "\
" result.version, result.exitcode, "\
" result.triggers, result.requester "\
"FROM test, result "\
"WHERE test.id = result.test_id "\
"AND test.release = '${RELEASE}' "\
"AND result.triggers LIKE '%${TRIGGER}%' "\
"ORDER BY test.release, test.package, test.arch"
release arch package version exitcode triggers
requester
--- --- -- --
-
jammyamd64libgnatcoll-python 21.0.0-20
python2.7/2.7.18-13ubuntu1.2
jammyarm64libgnatcoll-python 21.0.0-20
python2.7/2.7.18-13ubuntu1.2
jammyarmhflibgnatcoll-python 21.0.0-20
python2.7/2.7.18-13ubuntu1.2
jammyppc64el libgnatcoll-python 21.0.0-20
python2.7/2.7.18-13ubuntu1.2
jammys390xlibgnatcoll-python 21.0.0-20
python2.7/2.7.18-13ubuntu1.2
jammyamd64python2.7 2.7.18-13ubuntu1.2 0
python2.7/2.7.18-13ubuntu1.2
jammyarm64python2.7 2.7.18-13ubuntu1.2 0
python2.7/2.7.18-13ubuntu1.2
jammyarmhfpython2.7 2.7.18-13ubuntu1.2 0
python2.7/2.7.18-13ubuntu1.2
jammyi386 python2.7 2.7.18-13ubuntu1.2 12
python2.7/2.7.18-13ubuntu1.2
jammyppc64el python2.7 2.7.18-13ubuntu1.2 0
python2.7/2.7.18-13ubuntu1.2
jammys390xpython2.7 2.7.18-13ubuntu1.2 0
python2.7/2.7.18-13ubuntu1.2
jammy/i386/python2.7: not a regression (unrelated failure)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python2.7 in Ubuntu.
https://bugs.launchpad.net/bugs/2002043
Title:
Python extension modules get built using wrong compiler flags with
python2
Status in python2.7 package in Ubuntu:
Invalid
Status in python2.7 source package in Bionic:
Won't Fix
Status in python2.7 source package in Focal:
Fix Committed
Status in python2.7 source package in Jammy:
Fix Committed
Status in python2.7 source package in Kinetic:
Invalid
Status in python2.7 source package in Lunar:
Invalid
Status in python2.7 source package in Mantic:
Invalid
Bug description:
[ Impact ]
When compiling Python extensions using Python2, CFLAGS optimization
flags are dropped.
This behavior has been caused by our update in this patch
http://archive.ubuntu.com/ubuntu/pool/universe/p/python2.7/python2.7_2.7.18-1~20.04.3.diff.gz
which differs from upstream.
The fix modifies the portion of code in Lib/distutils/sysconfig.py
which gets the cflags from the environments, and includes the dropped
OPT flag from get_config_vars().
[ Test Plan ]
There will be 2 separate tests for this bug:
* Ensuring no-change rebuilds are not changed
* Ensuring local builds are not changed unless environment variable is set
Test 1) No-change rebuilds
To test that no-change rebuilds are not changed, the package python-
stdlib-extensions will be built against the new python2.7, and confirm
the compiler flags are not altered. This will be a manual test and
visual inspection of the build logs.
Test 2) Functional test
1. Create test container
$ lxc launch ubuntu:jammy jammy-2002043
$ lxc shell jammy-2002043
2. Install required packages
For Jammy
# apt update -y && apt install -y python2 python-pip
For Focal
# apt update -y && apt install -y python2 python-setuptools gcc
3. Create test files
# mkdir testprog
# cd testprog
# cat >setup.py
[Touch-packages] [Bug 2002043] Re: Python extension modules get built using wrong compiler flags with python2
Hi Mitchell, Indeed, there are some autopkgtests results/failures that are not reported in pending-sru or update_excuses -- this is the case specially for Focal (Jammy looks good). I downloaded the autopkgtest.db from autopkgtest.ubuntu.com, and locally queried it. The test results with exitcode != 0 need checking. Could you please take a look at those? If you need any tests retried or other assistance, please let us know! (You know, starting from https://autopkgtest.ubuntu.com/packages/$SRCPKG and going from there.) Thanks! Mauricio -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/2002043 Title: Python extension modules get built using wrong compiler flags with python2 Status in python2.7 package in Ubuntu: Invalid Status in python2.7 source package in Bionic: Won't Fix Status in python2.7 source package in Focal: Fix Committed Status in python2.7 source package in Jammy: Fix Committed Status in python2.7 source package in Kinetic: Invalid Status in python2.7 source package in Lunar: Invalid Status in python2.7 source package in Mantic: Invalid Bug description: [ Impact ] When compiling Python extensions using Python2, CFLAGS optimization flags are dropped. This behavior has been caused by our update in this patch http://archive.ubuntu.com/ubuntu/pool/universe/p/python2.7/python2.7_2.7.18-1~20.04.3.diff.gz which differs from upstream. The fix modifies the portion of code in Lib/distutils/sysconfig.py which gets the cflags from the environments, and includes the dropped OPT flag from get_config_vars(). [ Test Plan ] There will be 2 separate tests for this bug: * Ensuring no-change rebuilds are not changed * Ensuring local builds are not changed unless environment variable is set Test 1) No-change rebuilds To test that no-change rebuilds are not changed, the package python- stdlib-extensions will be built against the new python2.7, and confirm the compiler flags are not altered. This will be a manual test and visual inspection of the build logs. Test 2) Functional test 1. Create test container $ lxc launch ubuntu:jammy jammy-2002043 $ lxc shell jammy-2002043 2. Install required packages For Jammy # apt update -y && apt install -y python2 python-pip For Focal # apt update -y && apt install -y python2 python-setuptools gcc 3. Create test files # mkdir testprog # cd testprog # cat >setup.py
[Touch-packages] [Bug 2002043] Re: Python extension modules get built using wrong compiler flags with python2
No problem, Mitchell! Yes, the point pending from comment #44 (.3) is resolved for Jammy per #48 (so Jammy should be OK, AFAICT), and pending for Focal per #49 (being addressed per #50; thanks!). Please note that other SRU vanguards may have a different opinion (or raise other points I may have missed); my shift is on Mondays, so this is to be checked by someone else during this week. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/2002043 Title: Python extension modules get built using wrong compiler flags with python2 Status in python2.7 package in Ubuntu: Invalid Status in python2.7 source package in Bionic: Won't Fix Status in python2.7 source package in Focal: Fix Committed Status in python2.7 source package in Jammy: Fix Committed Status in python2.7 source package in Kinetic: Invalid Status in python2.7 source package in Lunar: Invalid Status in python2.7 source package in Mantic: Invalid Bug description: [ Impact ] When compiling Python extensions using Python2, CFLAGS optimization flags are dropped. This behavior has been caused by our update in this patch http://archive.ubuntu.com/ubuntu/pool/universe/p/python2.7/python2.7_2.7.18-1~20.04.3.diff.gz which differs from upstream. The fix modifies the portion of code in Lib/distutils/sysconfig.py which gets the cflags from the environments, and includes the dropped OPT flag from get_config_vars(). [ Test Plan ] There will be 2 separate tests for this bug: * Ensuring no-change rebuilds are not changed * Ensuring local builds are not changed unless environment variable is set Test 1) No-change rebuilds To test that no-change rebuilds are not changed, the package python- stdlib-extensions will be built against the new python2.7, and confirm the compiler flags are not altered. This will be a manual test and visual inspection of the build logs. Test 2) Functional test 1. Create test container $ lxc launch ubuntu:jammy jammy-2002043 $ lxc shell jammy-2002043 2. Install required packages For Jammy # apt update -y && apt install -y python2 python-pip For Focal # apt update -y && apt install -y python2 python-setuptools gcc 3. Create test files # mkdir testprog # cd testprog # cat >setup.py
[Touch-packages] [Bug 2033892] Re: ls -l triggers mount of autofs shares when --ghost option is present or browse_mode is enabled
Re: comment #15
> autopkgtest for dotnet6/6.0.128-0ubuntu1~22.04.1: amd64: Regression ♻ ,
> arm64: Regression ♻
> autopkgtest for linux-hwe-5.19/5.19.0-50.50: amd64: Pass, arm64: Regression ♻
> , ...
> autopkgtest for linux-hwe-6.5/6.5.0-27.28~22.04.1: arm64: Regression ♻ , ...
dotnet6 amd64
apparently unrelated; rerunning without core-utils as trigger:
- rerun with trigger on dotnet6 (from proposed)
- rerun with trigger on glibc (last passing)
dotnet6 jammy/arm64
likewise
linux-hwe-5.19/arm64
timedout several times
rerun
linux-hwe-6.5/arm64
timeout several times
rerun
linux-gcp-5.19 and -6.2 already cleared due to reruns.
Proposed {linux,linux-*}/{arm64,armhf} to long_tests [1] per [2].
[1]
https://code.launchpad.net/~mfo/autopkgtest-cloud/+git/autopkgtest-cloud/+merge/462861
[2] https://wiki.ubuntu.com/ProposedMigration#autopkgtests
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to coreutils in Ubuntu.
https://bugs.launchpad.net/bugs/2033892
Title:
ls -l triggers mount of autofs shares when --ghost option is present
or browse_mode is enabled
Status in coreutils package in Ubuntu:
Fix Released
Status in coreutils source package in Jammy:
Fix Committed
Status in coreutils package in Fedora:
Fix Released
Bug description:
[Impact]
Issuing a 'ls -l' or a 'stat' on an autofs share when you have set
--ghost in the auto.master file, or browse_mode=yes in autofs.conf
will lead to the shares being mounted, when they didn't previously.
Disks / shares may not be present and the mounts may fail, leading to
errors in your output.
This is a behaviour change in autofs 8.32, which occurred in the
transition to using statx() instead of stat()/lstat() in previous
releases.
There doesn't seem to be any workarounds, apart from not running a 'ls
-l' in your autofs share directory.
[Testcase]
Start two Jammy VMs. One will be a NFS server, the other, the client.
NFS server:
Server VM:
$ sudo hostnamectl set-hostname jammy-nfs-server
$ sudo apt update && sudo apt upgrade -y
$ sudo apt install nfs-kernel-server
$ sudo mkdir /export
$ sudo mkdir /export/users
$ sudo vi /etc/exports # add the following lines:
/export 192.168.122.0/24(rw,fsid=0,no_subtree_check,sync)
/export/users 192.168.122.0/24(rw,nohide,insecure,no_subtree_check,sync)
$ sudo systemctl restart nfs-server.service
AutoFS Client:
$ sudo apt update
$ sudo apt install autofs
$ sudo vim /etc/autofs.conf
browse_mode = yes
$ sudo mkdir /mnt2
$ sudo vim /etc/auto.master
/mnt2 /etc/auto.indirect
$ sudo vim /etc/auto.indirect
export 192.168.122.18:/export
export-missing 192.168.122.18:/export-missing
$ sudo reboot
$ cd /mnt2
$ ls -l
ls: cannot access 'export-missing': No such file or directory
total 4
drwxr-xr-x 3 root root 4096 Feb 12 21:48 export
d? ? ?? ?? export-missing
$ mount -l | grep /mnt2
/etc/auto.indirect on /mnt2 type autofs
(rw,relatime,fd=6,pgrp=634,timeout=300,minproto=5,maxproto=5,indirect,pipe_ino=21561)
192.168.122.18:/export on /mnt2/export type nfs
(rw,relatime,vers=3,rsize=524288,wsize=524288,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=192.168.122.18,mountvers=3,mountport=35786,mountproto=udp,local_lock=none,addr=192.168.122.18)
We see the mount for export occurred, and export-missing was
attempted, but it was either bogus or the disk was not present,
leading to a "No such file or directory" error.
There are test packages available in the following ppa:
https://launchpad.net/~mruffell/+archive/ubuntu/sf378489-test
If you install them, this is what should occur:
$ ls -l
total 0
drwxr-xr-x 2 root root 0 Feb 12 22:01 export
drwxr-xr-x 2 root root 0 Feb 12 22:01 export-missing
$ mount -l | grep /mnt2
/etc/auto.indirect on /mnt2 type autofs
(rw,relatime,fd=6,pgrp=636,timeout=300,minproto=5,maxproto=5,indirect,pipe_ino=18346)
No mounts happen, and no errors either.
[Where problems could occur]
We are changing the behaviour of core utilities, ls and stat, such
that they no longer attempt to mount autofs shares when --ghost option
is present or browse_mode is enabled.
This is the intended behaviour in the first place, and has been this
way for at least a decade prior, and was changed to return to this
behaviour shortly after the release of coreutils that introduced
statx() that caused automounts to occur.
It is unlikely any system administrators are relying on the behaviour
found in jammy in any scripts or day to day operations that would be
adversely affected by the change. The worst case scenario is that a
user doing an 'ls -l' on an unmounted disk finds the mount doesn't
automatically occur, and they have to attach the disk and issue the
mount themselves.
If a r
[Touch-packages] [Bug 2033892] Re: ls -l triggers mount of autofs shares when --ghost option is present or browse_mode is enabled
For dotnet6 on amd64 and arm64, the errors are unrelated to coreutils
(the same test errors happen against dotnet6 itself and even glibc),
thus triggered a migration-reference/0 run.
[0,3] trigger: coreutils/8.32-4.1ubuntu1.2
dotnet-runtime-json-contains-ubuntu-rids FAIL non-zero exit status 253
[1,4] trigger: dotnet6/6.0.128-0ubuntu1~22.04.1
dotnet-runtime-json-contains-ubuntu-rids FAIL non-zero exit status 253
[2,5] trigger: glibc/2.35-0ubuntu3.6
dotnet-runtime-json-contains-ubuntu-rids FAIL non-zero exit status 253
All fail with error messages:
ERROR: RID (Runtime Identifier) 'ubuntu.24.04{,-arm,-arm64,-x64,-x86}'
is missing in
'src/runtime/src/libraries/Microsoft.NETCore.Platforms/src/runtime.json'!
[0]
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/d/dotnet6/20240319_131027_34202@/log.gz
[1]
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/d/dotnet6/20240321_145231_25ae8@/log.gz
[2]
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/d/dotnet6/20240321_154527_e413f@/log.gz
[3]
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/arm64/d/dotnet6/20240319_111747_74352@/log.gz
[4]
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/arm64/d/dotnet6/20240321_135858_e04d0@/log.gz
[5]
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/arm64/d/dotnet6/20240321_141049_ff5d1@/log.gz
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to coreutils in Ubuntu.
https://bugs.launchpad.net/bugs/2033892
Title:
ls -l triggers mount of autofs shares when --ghost option is present
or browse_mode is enabled
Status in coreutils package in Ubuntu:
Fix Released
Status in coreutils source package in Jammy:
Fix Committed
Status in coreutils package in Fedora:
Fix Released
Bug description:
[Impact]
Issuing a 'ls -l' or a 'stat' on an autofs share when you have set
--ghost in the auto.master file, or browse_mode=yes in autofs.conf
will lead to the shares being mounted, when they didn't previously.
Disks / shares may not be present and the mounts may fail, leading to
errors in your output.
This is a behaviour change in autofs 8.32, which occurred in the
transition to using statx() instead of stat()/lstat() in previous
releases.
There doesn't seem to be any workarounds, apart from not running a 'ls
-l' in your autofs share directory.
[Testcase]
Start two Jammy VMs. One will be a NFS server, the other, the client.
NFS server:
Server VM:
$ sudo hostnamectl set-hostname jammy-nfs-server
$ sudo apt update && sudo apt upgrade -y
$ sudo apt install nfs-kernel-server
$ sudo mkdir /export
$ sudo mkdir /export/users
$ sudo vi /etc/exports # add the following lines:
/export 192.168.122.0/24(rw,fsid=0,no_subtree_check,sync)
/export/users 192.168.122.0/24(rw,nohide,insecure,no_subtree_check,sync)
$ sudo systemctl restart nfs-server.service
AutoFS Client:
$ sudo apt update
$ sudo apt install autofs
$ sudo vim /etc/autofs.conf
browse_mode = yes
$ sudo mkdir /mnt2
$ sudo vim /etc/auto.master
/mnt2 /etc/auto.indirect
$ sudo vim /etc/auto.indirect
export 192.168.122.18:/export
export-missing 192.168.122.18:/export-missing
$ sudo reboot
$ cd /mnt2
$ ls -l
ls: cannot access 'export-missing': No such file or directory
total 4
drwxr-xr-x 3 root root 4096 Feb 12 21:48 export
d? ? ?? ?? export-missing
$ mount -l | grep /mnt2
/etc/auto.indirect on /mnt2 type autofs
(rw,relatime,fd=6,pgrp=634,timeout=300,minproto=5,maxproto=5,indirect,pipe_ino=21561)
192.168.122.18:/export on /mnt2/export type nfs
(rw,relatime,vers=3,rsize=524288,wsize=524288,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=192.168.122.18,mountvers=3,mountport=35786,mountproto=udp,local_lock=none,addr=192.168.122.18)
We see the mount for export occurred, and export-missing was
attempted, but it was either bogus or the disk was not present,
leading to a "No such file or directory" error.
There are test packages available in the following ppa:
https://launchpad.net/~mruffell/+archive/ubuntu/sf378489-test
If you install them, this is what should occur:
$ ls -l
total 0
drwxr-xr-x 2 root root 0 Feb 12 22:01 export
drwxr-xr-x 2 root root 0 Feb 12 22:01 export-missing
$ mount -l | grep /mnt2
/etc/auto.indirect on /mnt2 type autofs
(rw,relatime,fd=6,pgrp=636,timeout=300,minproto=5,maxproto=5,indirect,pipe_ino=18346)
No mounts happen, and no errors either.
[Where problems could occur]
We are changing the behaviour of core utilities, ls and stat, such
that they no longer attempt to mount autofs shares when --ghost option
is present or browse_mode is enabled.
This is the intended behaviour in the first place, and has been this
way for at least a decade prior, and was changed to return to this
[Touch-packages] [Bug 2033892] Re: ls -l triggers mount of autofs shares when --ghost option is present or browse_mode is enabled
Autopkgtests are now clear in update_excuses and pending-sru. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/2033892 Title: ls -l triggers mount of autofs shares when --ghost option is present or browse_mode is enabled Status in coreutils package in Ubuntu: Fix Released Status in coreutils source package in Jammy: Fix Committed Status in coreutils package in Fedora: Fix Released Bug description: [Impact] Issuing a 'ls -l' or a 'stat' on an autofs share when you have set --ghost in the auto.master file, or browse_mode=yes in autofs.conf will lead to the shares being mounted, when they didn't previously. Disks / shares may not be present and the mounts may fail, leading to errors in your output. This is a behaviour change in autofs 8.32, which occurred in the transition to using statx() instead of stat()/lstat() in previous releases. There doesn't seem to be any workarounds, apart from not running a 'ls -l' in your autofs share directory. [Testcase] Start two Jammy VMs. One will be a NFS server, the other, the client. NFS server: Server VM: $ sudo hostnamectl set-hostname jammy-nfs-server $ sudo apt update && sudo apt upgrade -y $ sudo apt install nfs-kernel-server $ sudo mkdir /export $ sudo mkdir /export/users $ sudo vi /etc/exports # add the following lines: /export 192.168.122.0/24(rw,fsid=0,no_subtree_check,sync) /export/users 192.168.122.0/24(rw,nohide,insecure,no_subtree_check,sync) $ sudo systemctl restart nfs-server.service AutoFS Client: $ sudo apt update $ sudo apt install autofs $ sudo vim /etc/autofs.conf browse_mode = yes $ sudo mkdir /mnt2 $ sudo vim /etc/auto.master /mnt2 /etc/auto.indirect $ sudo vim /etc/auto.indirect export 192.168.122.18:/export export-missing 192.168.122.18:/export-missing $ sudo reboot $ cd /mnt2 $ ls -l ls: cannot access 'export-missing': No such file or directory total 4 drwxr-xr-x 3 root root 4096 Feb 12 21:48 export d? ? ?? ?? export-missing $ mount -l | grep /mnt2 /etc/auto.indirect on /mnt2 type autofs (rw,relatime,fd=6,pgrp=634,timeout=300,minproto=5,maxproto=5,indirect,pipe_ino=21561) 192.168.122.18:/export on /mnt2/export type nfs (rw,relatime,vers=3,rsize=524288,wsize=524288,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=192.168.122.18,mountvers=3,mountport=35786,mountproto=udp,local_lock=none,addr=192.168.122.18) We see the mount for export occurred, and export-missing was attempted, but it was either bogus or the disk was not present, leading to a "No such file or directory" error. There are test packages available in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/sf378489-test If you install them, this is what should occur: $ ls -l total 0 drwxr-xr-x 2 root root 0 Feb 12 22:01 export drwxr-xr-x 2 root root 0 Feb 12 22:01 export-missing $ mount -l | grep /mnt2 /etc/auto.indirect on /mnt2 type autofs (rw,relatime,fd=6,pgrp=636,timeout=300,minproto=5,maxproto=5,indirect,pipe_ino=18346) No mounts happen, and no errors either. [Where problems could occur] We are changing the behaviour of core utilities, ls and stat, such that they no longer attempt to mount autofs shares when --ghost option is present or browse_mode is enabled. This is the intended behaviour in the first place, and has been this way for at least a decade prior, and was changed to return to this behaviour shortly after the release of coreutils that introduced statx() that caused automounts to occur. It is unlikely any system administrators are relying on the behaviour found in jammy in any scripts or day to day operations that would be adversely affected by the change. The worst case scenario is that a user doing an 'ls -l' on an unmounted disk finds the mount doesn't automatically occur, and they have to attach the disk and issue the mount themselves. If a regression were to occur, it would be limited to the ls and stat commands, specifically when listing directories linked to autofs mountpoints. [Other info] The automount behaviour change was introduced upstream in version 8.32, with the introduction of the statx() call. This means only Jammy is affected. It was quickly reverted back to how it was originally in version 9.1, which is already available in Mantic and onward. The commits that solve the issue are: commit 85c975df2c25bd799370b04bb294e568e001102f From: Rohan Sable Date: Mon, 7 Mar 2022 14:14:13 + Subject: ls: avoid triggering automounts Link: https://git.savannah.gnu.org/gitweb/?p=coreutils.git;a=commitdiff;h=v9.0-177-g85c975df2c2 commit 92cb8427c537f37edd43c5cef1909585201372ab From: Pádraig Brady Date: Mon, 7 Mar 2022 23:29:20 + Subject: stat: only automount wit
[Touch-packages] [Bug 1834250] Re: update-grub complains about non-existent drives (due to cardreader)
** Also affects: lvm2 (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: lvm2 (Ubuntu) Status: Confirmed => Fix Released ** Changed in: lvm2 (Ubuntu) Importance: Low => Undecided ** Changed in: lvm2 (Ubuntu Focal) Status: New => In Progress ** Changed in: lvm2 (Ubuntu Focal) Importance: Undecided => Low ** Changed in: lvm2 (Ubuntu Focal) Assignee: (unassigned) => Mauricio Faria de Oliveira (mfo) ** Tags added: sts-sponsor-mfo -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1834250 Title: update-grub complains about non-existent drives (due to cardreader) Status in lvm2 package in Ubuntu: Fix Released Status in lvm2 source package in Focal: In Progress Bug description: sudo update-grub Sourcing file `/etc/default/grub' Sourcing file `/etc/default/grub.d/init-select.cfg' Generating grub configuration file ... /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found Found linux image: /boot/vmlinuz-5.0.0-17-generic Found initrd image: /boot/initrd.img-5.0.0-17-generic Found linux image: /boot/vmlinuz-5.0.0-16-generic Found initrd image: /boot/initrd.img-5.0.0-16-generic /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found Adding boot menu entry for EFI firmware configuration done -- lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda8:00 3.7T 0 disk ├─sda1 8:10 512M 0 part /boot/efi ├─sda2 8:20 732M 0 part /boot └─sda3 8:30 3.7T 0 part └─sda3_crypt 253:00 3.7T 0 crypt ├─kubuntu--vg-swap_1 253:10 976M 0 lvm [SWAP] └─kubuntu--vg-root 253:20 3.7T 0 lvm / sdb8:16 0 3.7T 0 disk └─sdb1 8:17 0 3.7T 0 part sdg8:96 0 7.3T 0 disk └─sdg1 8:97 0 7.3T 0 part /media/scott/8TB Ext Drive sr0 11:01 15.7G 0 rom -- cat /etc/default/grub GRUB_DEFAULT=0 GRUB_TIMEOUT=10 GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian` GRUB_CMDLINE_LINUX_DEFAULT="intel_iommu=on" GRUB_CMDLINE_LINUX="" ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: grub2-common 2.02+dfsg1-12ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8 Uname: Linux 5.0.0-17-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu3 Architecture: amd64 CurrentDesktop: KDE Date: Tue Jun 25 15:05:29 2019 InstallationDate: Installed on 2019-06-14 (10 days ago) InstallationMedia: Kub
[Touch-packages] [Bug 1834250] Re: update-grub complains about non-existent drives (due to cardreader)
Setup:
--
Add '/dev/sda' from the host to a Focal LXD container:
$ lxc launch ubuntu:focal 'focal-container'
$ lxc config device add 'focal-container' 'lxc-dev-sda' unix-block
source='/dev/sda' path='/dev/sda'
Device:
---
$ grep ^ /sys/block/sda/{removable,device/{vendor,model,rev}}
/sys/block/sda/removable:1
/sys/block/sda/device/vendor:Generic-
/sys/block/sda/device/model:SD/MMC
/sys/block/sda/device/rev:1.00
Original:
---
Error messages:
$ sudo vgs
/dev/sda: open failed: No medium found
/dev/sda: open failed: No medium found
$ echo $?
0
NOTE syscalls/error codes for /dev/sda:
$ sudo strace -f -e openat vgs 2>&1 | grep /dev/sda
openat(AT_FDCWD, "/dev/sda", O_RDONLY|O_DIRECT|O_NOATIME) = -1
ENOMEDIUM (No medium found)
openat(AT_FDCWD, "/dev/sda", O_RDONLY|O_NOATIME) = -1 ENOMEDIUM (No
medium found)
/dev/sda: open failed: No medium found
openat(AT_FDCWD, "/dev/sda", O_RDONLY|O_DIRECT|O_NOATIME) = -1
ENOMEDIUM (No medium found)
openat(AT_FDCWD, "/dev/sda", O_RDONLY|O_NOATIME) = -1 ENOMEDIUM (No
medium found)
/dev/sda: open failed: No medium found
Patched:
---
No messages:
$ sudo vgs
$ echo $?
0
SAME syscalls/error codes for /dev/sda:
$ sudo strace -f -e openat vgs 2>&1 | grep /dev/sda
openat(AT_FDCWD, "/dev/sda", O_RDONLY|O_DIRECT|O_NOATIME) = -1
ENOMEDIUM (No medium found)
openat(AT_FDCWD, "/dev/sda", O_RDONLY|O_NOATIME) = -1 ENOMEDIUM (No
medium found)
openat(AT_FDCWD, "/dev/sda", O_RDONLY|O_DIRECT|O_NOATIME) = -1
ENOMEDIUM (No medium found)
openat(AT_FDCWD, "/dev/sda", O_RDONLY|O_NOATIME) = -1 ENOMEDIUM (No
medium found)
** Description changed:
+ [Impact]
+
+ * `update-grub` (actually `vgs`) complains about
+'No medium found' on systems with card readers
+that have no card in.
+
+ * This may confuse users who aren't sure whether
+it means problems occurred with the bootloader,
+and concern their ability to safely boot again.
+
+ * The workaround is to add a filter to LVM config,
+but this might be hard to find and error prone.
+(And not even seem relate to `update-grub` at
+all, specially on non-LVM storage layouts.)
+
+ [Test Plan]
+
+ * Run `vgs` on a system with a card reader
+and check for 'No medium found' messages.
+
+ [Where problems could occur]
+
+ * The patch changes syscall error reporting on the
+'scan' path, so problems could occur when listing
+LVM resources in block devices (e.g., list volume
+groups with `vgs`).
+
+ * There's little to no changes upstream on this area,
+and the change is present in Jammy; both help with
+a lower chance of regression.
+
+ [Info]
+
+ * This upload is being staged (`block-proposed-focal`)
+as it's just a cosmetic change, but affects `lvm2`,
+which is present in so many systems, triggering a
+lot of upgrades/boot risk (in case something else
+broke and this upgrade could reveal it indirectly).
+
+ * So, it will probably only be released once a more
+serious issue has to be fixed in `lvm2`.
+
+ [Original Bug Description]
+
sudo update-grub
Sourcing file `/etc/default/grub'
Sourcing file `/etc/default/grub.d/init-select.cfg'
Generating grub configuration file ...
- /dev/sdc: open failed: No medium found
- /dev/sdd: open failed: No medium found
- /dev/sde: open failed: No medium found
- /dev/sdf: open failed: No medium found
- /dev/sdc: open failed: No medium found
- /dev/sdd: open failed: No medium found
- /dev/sde: open failed: No medium found
- /dev/sdf: open failed: No medium found
- /dev/sdc: open failed: No medium found
- /dev/sdd: open failed: No medium found
- /dev/sde: open failed: No medium found
- /dev/sdf: open failed: No medium found
- /dev/sdc: open failed: No medium found
- /dev/sdd: open failed: No medium found
- /dev/sde: open failed: No medium found
- /dev/sdf: open failed: No medium found
- /dev/sdc: open failed: No medium found
- /dev/sdd: open failed: No medium found
- /dev/sde: open failed: No medium found
- /dev/sdf: open failed: No medium found
- /dev/sdc: open failed: No medium found
- /dev/sdd: open failed: No medium found
- /dev/sde: open failed: No medium found
- /dev/sdf: open failed: No medium found
- /dev/sdc: open failed: No medium found
- /dev/sdd: open failed: No medium found
- /dev/sde: open failed: No medium found
- /dev/sdf: open failed: No medium found
- /dev/sdc: open failed: No medium found
- /dev/sdd: open failed: No medium found
- /dev/sde: open failed: No medium found
- /dev/sdf: open failed: No medium found
- /dev/sdc: open failed: No medium found
- /dev/sdd: open failed: No medium found
- /dev/sde: open failed: No medium found
- /dev/sdf: open failed: No medium found
- /dev/sdc: o
[Touch-packages] [Bug 1834250] Re: update-grub complains about non-existent drives (due to cardreader)
** Description changed: [Impact] * `update-grub` (actually `vgs`) complains about 'No medium found' on systems with card readers that have no card in. * This may confuse users who aren't sure whether it means problems occurred with the bootloader, and concern their ability to safely boot again. * The workaround is to add a filter to LVM config, but this might be hard to find and error prone. (And not even seem relate to `update-grub` at all, specially on non-LVM storage layouts.) -[See comment #16] + [See comment #16] [Test Plan] * Run `vgs` on a system with a card reader and check for 'No medium found' messages. - * Run `strace -f -e openat vgs` to confirm -system calls/error codes have no changes. + * Run `strace -f -e openat vgs` to confirm + system calls/error codes have no changes. - * [See comment #20] + * [See comment #20] [Where problems could occur] * The patch changes syscall error reporting on the 'scan' path, so problems could occur when listing LVM resources in block devices (e.g., list volume groups with `vgs`). * There's little to no changes upstream on this area, and the change is present in Jammy; both help with a lower chance of regression. - [Info] + [Other Info] - * This upload is being staged (`block-proposed-focal`) + * `block-proposed-focal`: The upload is being staged as it's just a cosmetic change, but affects `lvm2`, which is present in so many systems, triggering a lot of upgrades/boot risk (in case something else broke and this upgrade could reveal it indirectly). * So, it will probably only be released once a more serious issue has to be fixed in `lvm2`. + + * Scope: Jammy has the fix, and Impish will EOL soon. [Original Bug Description] sudo update-grub Sourcing file `/etc/default/grub' Sourcing file `/etc/default/grub.d/init-select.cfg' Generating grub configuration file ... /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found Found linux image: /boot/vmlinuz-5.0.0-17-generic Found initrd image: /boot/initrd.img-5.0.0-17-generic Found linux image: /boot/vmlinuz-5.0.0-16-generic Found initrd image: /boot/initrd.img-5.0.0-16-generic /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found Adding boot menu entry for EFI firmware configuration done -- lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda8:00 3.7T 0 disk ├─sda1 8:10 512M 0 part /boot/efi ├─sda2 8:20 732M 0 part /boot └─sda3 8:30 3.7T 0 part └─sda3_crypt 253:00 3.7T 0 crypt ├─kubuntu--vg-swap_1 253:10 976M 0 lvm [SWAP] └─kubuntu--vg-roo
[Touch-packages] [Bug 1834250] Re: update-grub complains about non-existent drives (due to cardreader)
Uploaded to Focal, and tagged block-proposed-focal. Attaching slightly modified debdiff (local build version), for users who want to build lvm2 before a SRU is released. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1834250 Title: update-grub complains about non-existent drives (due to cardreader) Status in lvm2 package in Ubuntu: Fix Released Status in lvm2 source package in Focal: In Progress Bug description: [Impact] * `update-grub` (actually `vgs`) complains about 'No medium found' on systems with card readers that have no card in. * This may confuse users who aren't sure whether it means problems occurred with the bootloader, and concern their ability to safely boot again. * The workaround is to add a filter to LVM config, but this might be hard to find and error prone. (And not even seem relate to `update-grub` at all, specially on non-LVM storage layouts.) [See comment #16] * The fix replaces calls to `dev_open_readonly()` with `dev_open_readonly_quiet()` in scan path, where such errors are not a problem. [Test Plan] * Run `vgs` on a system with a card reader and check for 'No medium found' messages. * Run `strace -f -e openat vgs` to confirm system calls/error codes have no changes. * [See comment #20] [Where problems could occur] * The patch changes syscall error reporting on the 'scan' path, so problems could occur when listing LVM resources in block devices (e.g., list volume groups with `vgs`). * There's little to no changes upstream on this area, and the change is present in Jammy; both help with a lower chance of regression. [Other Info] * `block-proposed-focal`: The upload is being staged as it's just a cosmetic change, but affects `lvm2`, which is present in so many systems, triggering a lot of upgrades/boot risk (in case something else broke and this upgrade could reveal it indirectly). * So, it will probably only be released once a more serious issue has to be fixed in `lvm2`. * Scope: Jammy has the fix, and Impish will EOL soon. [Original Bug Description] sudo update-grub Sourcing file `/etc/default/grub' Sourcing file `/etc/default/grub.d/init-select.cfg' Generating grub configuration file ... /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found Found linux image: /boot/vmlinuz-5.0.0-17-generic Found initrd image: /boot/initrd.img-5.0.0-17-generic Found linux image: /boot/vmlinuz-5.0.0-16-generic Found initrd image: /boot/initrd.img-5.0.0-16-generic /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found Adding boot menu entry for EFI firmware configuration done -- lsblk
[Touch-packages] [Bug 1834250] Re: update-grub complains about non-existent drives (due to cardreader)
** Patch added: "lp1834250_lvm2_focal.debdiff" https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1834250/+attachment/5593897/+files/lp1834250_lvm2_focal.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1834250 Title: update-grub complains about non-existent drives (due to cardreader) Status in lvm2 package in Ubuntu: Fix Released Status in lvm2 source package in Focal: In Progress Bug description: [Impact] * `update-grub` (actually `vgs`) complains about 'No medium found' on systems with card readers that have no card in. * This may confuse users who aren't sure whether it means problems occurred with the bootloader, and concern their ability to safely boot again. * The workaround is to add a filter to LVM config, but this might be hard to find and error prone. (And not even seem relate to `update-grub` at all, specially on non-LVM storage layouts.) [See comment #16] * The fix replaces calls to `dev_open_readonly()` with `dev_open_readonly_quiet()` in scan path, where such errors are not a problem. [Test Plan] * Run `vgs` on a system with a card reader and check for 'No medium found' messages. * Run `strace -f -e openat vgs` to confirm system calls/error codes have no changes. * [See comment #20] [Where problems could occur] * The patch changes syscall error reporting on the 'scan' path, so problems could occur when listing LVM resources in block devices (e.g., list volume groups with `vgs`). * There's little to no changes upstream on this area, and the change is present in Jammy; both help with a lower chance of regression. [Other Info] * `block-proposed-focal`: The upload is being staged as it's just a cosmetic change, but affects `lvm2`, which is present in so many systems, triggering a lot of upgrades/boot risk (in case something else broke and this upgrade could reveal it indirectly). * So, it will probably only be released once a more serious issue has to be fixed in `lvm2`. * Scope: Jammy has the fix, and Impish will EOL soon. [Original Bug Description] sudo update-grub Sourcing file `/etc/default/grub' Sourcing file `/etc/default/grub.d/init-select.cfg' Generating grub configuration file ... /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found Found linux image: /boot/vmlinuz-5.0.0-17-generic Found initrd image: /boot/initrd.img-5.0.0-17-generic Found linux image: /boot/vmlinuz-5.0.0-16-generic Found initrd image: /boot/initrd.img-5.0.0-16-generic /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found Adding boot menu entry for EFI firmware configuration done -- lsblk NAME
[Touch-packages] [Bug 1834250] Re: update-grub complains about non-existent drives (due to cardreader)
Verification done on focal-proposed; all good. Host: --- $ sudo dd if=/dev/sda of=/dev/null dd: failed to open '/dev/sda': No medium found $ lxc launch ubuntu:focal lp1834250 $ lxc config device add lp1834250 host-sda unix-block source=/dev/sda path=/dev/sda $ lxc shell lp1834250 Container: --- # lsb_release -cs focal focal-updates: error messages # dpkg -s lvm2 | grep Version: Version: 2.03.07-1ubuntu1 # vgs /dev/sda: open failed: No medium found /dev/sda: open failed: No medium found # strace -e openat vgs 2>&1 | grep /dev/sda openat(AT_FDCWD, "/dev/sda", O_RDONLY|O_DIRECT|O_NOATIME) = -1 ENOMEDIUM (No medium found) openat(AT_FDCWD, "/dev/sda", O_RDONLY|O_NOATIME) = -1 ENOMEDIUM (No medium found) /dev/sda: open failed: No medium found openat(AT_FDCWD, "/dev/sda", O_RDONLY|O_DIRECT|O_NOATIME) = -1 ENOMEDIUM (No medium found) openat(AT_FDCWD, "/dev/sda", O_RDONLY|O_NOATIME) = -1 ENOMEDIUM (No medium found) /dev/sda: open failed: No medium found # vgs /dev/sda: open failed: No medium found /dev/sda: open failed: No medium found focal-proposed: no error messages; same syscall behavior # echo 'deb http://archive.ubuntu.com/ubuntu focal-proposed main' >>/etc/apt/sources.list # apt update # apt-cache madison lvm2 | grep focal-proposed lvm2 | 2.03.07-1ubuntu1.1 | http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages # apt install lvm2 # dpkg -s lvm2 | grep Version: Version: 2.03.07-1ubuntu1.1 # vgs # # strace -e openat vgs 2>&1 | grep /dev/sda openat(AT_FDCWD, "/dev/sda", O_RDONLY|O_DIRECT|O_NOATIME) = -1 ENOMEDIUM (No medium found) openat(AT_FDCWD, "/dev/sda", O_RDONLY|O_NOATIME) = -1 ENOMEDIUM (No medium found) openat(AT_FDCWD, "/dev/sda", O_RDONLY|O_DIRECT|O_NOATIME) = -1 ENOMEDIUM (No medium found) openat(AT_FDCWD, "/dev/sda", O_RDONLY|O_NOATIME) = -1 ENOMEDIUM (No medium found) ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1834250 Title: update-grub complains about non-existent drives (due to cardreader) Status in lvm2 package in Ubuntu: Fix Released Status in lvm2 source package in Focal: Fix Committed Bug description: [Impact] * `update-grub` (actually `vgs`) complains about 'No medium found' on systems with card readers that have no card in. * This may confuse users who aren't sure whether it means problems occurred with the bootloader, and concern their ability to safely boot again. * The workaround is to add a filter to LVM config, but this might be hard to find and error prone. (And not even seem relate to `update-grub` at all, specially on non-LVM storage layouts.) [See comment #16] * The fix replaces calls to `dev_open_readonly()` with `dev_open_readonly_quiet()` in scan path, where such errors are not a problem. [Test Plan] * Run `vgs` on a system with a card reader and check for 'No medium found' messages. * Run `strace -f -e openat vgs` to confirm system calls/error codes have no changes. * [See comment #20] [Where problems could occur] * The patch changes syscall error reporting on the 'scan' path, so problems could occur when listing LVM resources in block devices (e.g., list volume groups with `vgs`). * There's little to no changes upstream on this area, and the change is present in Jammy; both help with a lower chance of regression. [Other Info] * `block-proposed-focal`: The upload is being staged as it's just a cosmetic change, but affects `lvm2`, which is present in so many systems, triggering a lot of upgrades/boot risk (in case something else broke and this upgrade could reveal it indirectly). * So, it will probably only be released once a more serious issue has to be fixed in `lvm2`. * Scope: Jammy has the fix, and Impish will EOL soon. [Original Bug Description] sudo update-grub Sourcing file `/etc/default/grub' Sourcing file `/etc/default/grub.d/init-select.cfg' Generating grub configuration file ... /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No mediu
[Touch-packages] [Bug 1947099] Re: ipconfig does not honour user-requested timeouts in some cases
Setting verification-done-bionic per comments 39/40.
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic
--
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/1947099
Title:
ipconfig does not honour user-requested timeouts in some cases
Status in klibc package in Ubuntu:
Won't Fix
Status in klibc source package in Bionic:
Fix Released
Bug description:
[Impact]
In some cases, ipconfig can take a longer time than the user-specified
timeouts, causing unexpected delays.
[Test Plan]
- Check that the ipconfig utility is able to obtain an IP through
dhcp:
# ip l set dev ens9 down
# date; /usr/lib/klibc/bin/ipconfig ens9; date
- Check if it respects the timeout (i.e. 2 seconds in the example
below):
# ip l set dev ens9 down
# date; /usr/lib/klibc/bin/ipconfig -t 2 ens9; date
- The original issue is that timeout is being ignored when not
receiving any reply from a DHCP Server, so for this test you have to
stop your DHCP Server (i.e. dnsmasq) and then test the timeouts:
# ip l set dev ens9 down
# date; /usr/lib/klibc/bin/ipconfig -t 2 ens9; date
# ip l set dev ens9 down
# date; /usr/lib/klibc/bin/ipconfig -t 5 ens9; date
Make sure it times out respectivelly in 2 and 5 seconds.
[racb: pending agreement with the SRU team; please see comment 37]
Any situation where ipconfig encounters an error sending the DHCP
packet, it will automatically set a delay of 10 seconds, which could
be longer than the user-specified timeout. It can be reproduced by
creating a dummy interface and attempting to run ipconfig on it with a
timeout value of less than 10:
# ip link add eth1 type dummy
# date; /usr/lib/klibc/bin/ipconfig -t 2 eth1; date
Thu Nov 18 04:46:13 EST 2021
IP-Config: eth1 hardware address ae:e0:f5:9d:7e:00 mtu 1500 DHCP RARP
IP-Config: no response after 2 secs - giving up
Thu Nov 18 04:46:23 EST 2021
^ Notice above, ipconfig thinks that it waited 2 seconds, but the
timestamps show an actual delay of 10 seconds.
[Where problems could occur]
Please see reproduction steps above. We are seeing this in production too
(see comment #2).
[Other Info]
A patch to fix the issue is being proposed here. It is a safe fix - it only
checks before going into sleep that the timeout never exceeds the
user-requested value.
[Original Description]
In some cases, ipconfig can take longer than the user-specified
timeouts, causing unexpected delays.
in main.c, in function loop(), the process can go into
process_timeout_event() (or process_receive_event() ) and if it
encounters an error situation, will set an attempt to "try again
later" at time equal now + 10 seconds by setting
s->expire = now + 10;
This can happen at any time during the main event loop, which can end
up extending the user-specified timeout if "now + 10" is greater than
"start_time + user-specified-timeout".
I believe a patch like the following is needed to avoid this problem:
--- a/usr/kinit/ipconfig/main.c
+++ b/usr/kinit/ipconfig/main.c
@@ -437,6 +437,13 @@ static int loop(void)
if (timeout > s->expire - now.tv_sec)
timeout = s->expire - now.tv_sec;
+
+ /* Compensate for already-lost time */
+ gettimeofday(&now, NULL);
+ if (now.tv_sec + timeout > start + loop_timeout) {
+ timeout = loop_timeout - (now.tv_sec - start);
+ printf("Lowered timeout to match user request
= (%d s) \n", timeout);
+ }
}
I believe the current behaviour is buggy. This is confirmed when the
following line is executed:
if (loop_timeout >= 0 &&
now.tv_sec - start >= loop_timeout) {
printf("IP-Config: no response after %d "
"secs - giving up\n", loop_timeout);
rc = -1;
goto bail;
}
'loop_timeout' is the user-specified time-out. With a value of 2, in
case of error, this line prints:
IP-Config: no response after 2 secs - giving up
So it thinks that it waited 2 seconds - however, in reality it had
actually waited for 10 seconds.
The suggested code-change ensures that the timeout that is actually
used never exceeds the user-specified timeout.
[ Regression potential ]
This change ensures that user-specified timeouts are never exceeded, which is
a problem that appears to happen only in case of interface errors.
It may be that someone is relying on current behaviour where they receive
DHCP offers after t
[Touch-packages] [Bug 1951279] Re: OpenSSL 1.1.1f raise a segmentation faults on Arm64 builds
Update: this has been fixed in Focal (same fix commit): openssl (1.1.1f-1ubuntu2.11) focal; urgency=medium * Fixup pointer authentication for armv8 systems that support it when using the poly1305 MAC, preventing segmentation faults. (LP: #1960863) - d/p/lp-1960863-crypto-poly1305-asm-fix-armv8-pointer-authenticat.patch -- Matthew Ruffell Tue, 15 Feb 2022 10:10:01 +1300 ** Changed in: openssl (Ubuntu Focal) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1951279 Title: OpenSSL 1.1.1f raise a segmentation faults on Arm64 builds Status in OpenSSL: Fix Released Status in openssl package in Ubuntu: Fix Released Status in openssl source package in Focal: Fix Released Status in openssl package in Debian: Fix Released Bug description: Description --- It seems that current Ubuntu 20.04 (Focal) distribution for Arm64/Aarch64 raise a segmentation fault when certain validates some certificates. This issue affects only to Arm64/Aarch64 all the tools statically or dynamically linked with this version of the library are affected (Libcurl4, Curl, Wget, OpenJDK, Curl-PHP, etc). Environment and platform Linux 5.4.0-89-generic #100-Ubuntu SMP Fri Sep 24 14:29:20 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux Steps to reproduce -- 1. Run: curl -v https://graph.facebook.com/v12.0/act_111/ or wget https://graph.facebook.com/v12.0/act_111/ Result received --- Segmentation fault (core dumped) Notes - This bug was found by the Curl users: See: https://github.com/curl/curl/issues/8024 I believe that this bug is related to https://ubuntu.com/security/CVE-2020-1967 that maybe used as a vector point for code injection. Actually there isn't any replacement for OpenSSL 1.1.1f for Focal (Arm64), so it makes difficult to use Ubuntu 20.04 in a production environment. To manage notifications about this bug go to: https://bugs.launchpad.net/openssl/+bug/1951279/+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 1983100] Re: dotnet build intermittently crashes with segfault on Ubuntu 18.04
Nicolas and I talked about a brief review of the debdiff,
and he kindly agreed to provide an update/v2 to address:
- changelog version and description line
- patches dep3 headers and lpnumber- prefix
... while patches are reviewed for feedback (not yet done).
Thanks, Nicolas!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1983100
Title:
dotnet build intermittently crashes with segfault on Ubuntu 18.04
Status in openssl package in Ubuntu:
New
Status in openssl source package in Bionic:
New
Bug description:
[Impact]
Bionic's OpenSSL 1.1.1 package
(https://launchpad.net/ubuntu/bionic/+source/openssl) is the only
version of openssl 1.1.1 on any distro that we've encountered that
does not have support for the OPENSSL_NO_ATEXIT functionality from
1.1.1b (openssl/openssl@c2b3db2).
The threading model in .NET has the possibility that background
threads are still running when exit() is called, which can cause
SIGSEGV if a background thread interacts with OpenSSL after/while it
has unloaded. For that reason, we always initialize OpenSSL 1.1.1 with
the OPENSSL_NO_ATEXIT flag (which, of all the distros we run on only
has no effect on Bionic).
We feel that the stability of applications on Ubuntu 18.04 would be
improved if the functionality of OPENSSL_NO_ATEXIT was merged into the
bionic openssl 1.1.1 package, even if the constant isn't published
into the header for the dev package.
Context:
https://github.com/dotnet/runtime/issues/48411#issuecomment-1178405101
[Test Plan]
The described behavior can be reproduced by passing the
OPENSSL_NO_ATEXIT to the OPENSSL_init_ssl() call. The application will
terminate with a SEGFAULT. More concretely, a minimal reproducer is:
#include
#include
#include
#ifndef OPENSSL_INIT_NO_ATEXIT
#define OPENSSL_INIT_NO_ATEXIT 0x0008L
#endif
static void print_error_string()
{
printf("print_error_string:\n");
printf("ERR_reason_error_string(0) => %s\n", ERR_reason_error_string(0));
}
int main(int argc, char* argv[])
{
// register this handler first, so it runs last.
atexit(print_error_string);
OPENSSL_init_ssl(
OPENSSL_INIT_ADD_ALL_CIPHERS |
OPENSSL_INIT_ADD_ALL_DIGESTS |
OPENSSL_INIT_LOAD_CONFIG |
OPENSSL_INIT_NO_ATEXIT |
OPENSSL_INIT_LOAD_CRYPTO_STRINGS |
OPENSSL_INIT_LOAD_SSL_STRINGS,
NULL);
print_error_string();
return 0;
}
Building
$ sudo apt install libssl-dev
$ gcc test.c -lssl -lcrypto
$ ./a.out
print_error_string:
ERR_reason_error_string(0) => (null)
print_error_string:
Segmentation fault (core dumped)
[Where problems could occur]
The patches adds an option to the OPENSSL_init_crypto() function to
disable the default behavior of calling of a cleanup function on
application exit. The patch also includes a few bug fixes around
various initializations that were supposed to happen once when running
threaded but were not.
These changes have the potential for regressions and it is conceivable
that they lead to incorrect behavior. However, I have also backported
and included all new testing functions in the hope that the changed
behavior will get appropriate testing.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1983100/+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 1842320] Re: Can't boot: "error: out of memory." immediately after the grub menu
Hi Jeremy,
It seems the PR in rhboot's grub2 hasn't been reviewed yet;
just mentions from other folks who also found it helpful.
Would you consider sending this to the grub-devel list? (i.e., upstream gnu's
grub2)
It looks like it wasn't yet (search results only cover rhboot).
By the way, this type of change had an interesting discussion
about the implementation approach a few years ago [1], but it
seems it ceased as the sender didn't provide further replies.
Your understanding of the tech details seems very deep, so it
might hopefully be a good opportunity to propose that again :)
Thanks!
[1] https://lists.gnu.org/archive/html/grub-devel/2017-03/msg00032.html
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1842320
Title:
Can't boot: "error: out of memory." immediately after the grub menu
Status in grub:
Unknown
Status in OEM Priority Project:
Triaged
Status in grub2-signed package in Ubuntu:
Confirmed
Status in initramfs-tools package in Ubuntu:
Confirmed
Status in linux package in Ubuntu:
Confirmed
Bug description:
[Impact]
* In some cases, if the users’ initramfs grow bigger, then it’ll
likely not be able to be loaded by grub2.
* Some real cases from OEM projects:
In many built-in 4k monitor laptops with nvidia drivers, the u-d-c
puts the nvidia*.ko to initramfs which grows the initramfs to ~120M.
Also the gfxpayload=auto will remain to use 4K resolution since it’s
what EFI POST passed.
In this case, the grub isn't able to load initramfs because the
grub_memalign() won't be able to get suitable memory for the larger
file:
```
#0 grub_memalign (align=1, size=592214020) at ../../../grub-core/kern/mm.c:376
#1 0x7dd7b074 in grub_malloc (size=592214020) at
../../../grub-core/kern/mm.c:408
#2 0x7dd7a2c8 in grub_verifiers_open (io=0x7bc02d80, type=131076)
at ../../../grub-core/kern/verifiers.c:150
#3 0x7dd801d4 in grub_file_open (name=0x7bc02f00
"/boot/initrd.img-5.17.0-1011-oem",
type=131076) at ../../../grub-core/kern/file.c:121
#4 0x7bcd5a30 in ?? ()
#5 0x7fe21247 in ?? ()
#6 0x7bc030c8 in ?? ()
#7 0x00017fe21238 in ?? ()
#8 0x7bcd5320 in ?? ()
#9 0x7fe21250 in ?? ()
#10 0x in ?? ()
```
Based on grub_mm_dump, we can see the memory fragment (some parts seem
likely be used because of 4K resolution?) and doesn’t have available
contiguous memory for larger file as:
```
grub_real_malloc(...)
...
if (cur->size >= n + extra)
```
Based on UEFI Specification Section 7.2[1] and UEFI driver writers’
guide 4.2.3[2], we can ask 32bits+ on AllocatePages().
As most X86_64 platforms should support 64 bits addressing, we should
extend GRUB_EFI_MAX_USABLE_ADDRESS to 64 bits to get more available
memory.
* When users grown the initramfs, then probably will get initramfs
not found which really annoyed and impact the user experience (system
not able to boot).
[Test Plan]
* detailed instructions how to reproduce the bug:
1. Any method to grow the initramfs, such as install nvidia-driver.
2. If developers would like to reproduce, then could dd if=/dev/random
of=... bs=1M count=500, something like:
```
$ cat /usr/share/initramfs-tools/hooks/zzz-touch-a-file
#!/bin/sh
PREREQ=""
prereqs()
{
echo "$PREREQ"
}
case $1 in
# get pre-requisites
prereqs)
prereqs
exit 0
;;
esac
. /usr/share/initramfs-tools/hook-functions
dd if=/dev/random of=${DESTDIR}/test-500M bs=1M count=500
```
And then update-initramfs
* After applying my patches, the issue is gone.
* I did also test my test grubx64.efi in:
1. X86_64 qemu with
1.1. 60M initramfs + 5.15.0-37-generic kernel
1.2. 565M initramfs + 5.17.0-1011-oem kernel
2. Amd64 HP mobile workstation with
2.1. 65M initramfs + 5.15.0-39-generic kernel
2.2. 771M initramfs + 5.17.0-1011-oem kernel
All working well.
[Where problems could occur]
* The changes almost in i386/efi, thus the impact will be in the i386 /
x86_64 EFI system.
The other change is to modify the “grub-core/kern/efi/mm.c” but I use the
original addressing for “arm/arm64/ia64/riscv32/riscv64”.
Thus it should not impact them.
* There is a “#if defined(__x86_64__)” which intent to limit the >
32bits code in i386 system and also
```
#if defined (__code_model_large__)
-#define GRUB_EFI_MAX_USABLE_ADDRESS 0x
+#define GRUB_EFI_MAX_USABLE_ADDRESS __UINTPTR_MAX__
+#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x7fff
#else
#define GRUB_EFI_MAX_USABLE_ADDRESS 0x7fff
+#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x3fff
#endif
```
If everything works as expected, then i386 should working good.
If not lucky, based on “UEFI writers’ guide”[2], th
[Touch-packages] [Bug 1842320] Re: Can't boot: "error: out of memory." immediately after the grub menu
Hey Jeremy,
Understood; thanks for clarifying!
I thought that maybe having upstream input could be helpful
(as Julian mentioned to avoid diverging further), but if it
is so much different nowadays, as you mentioned, it likely
won't be that helpful anyway.
By the way, appreciate that "newbie" statement.. after all
this work/analysis/patches, I couldn't think that of you :)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1842320
Title:
Can't boot: "error: out of memory." immediately after the grub menu
Status in grub:
Unknown
Status in OEM Priority Project:
Triaged
Status in grub2-signed package in Ubuntu:
Confirmed
Status in initramfs-tools package in Ubuntu:
Confirmed
Status in linux package in Ubuntu:
Confirmed
Bug description:
[Impact]
* In some cases, if the users’ initramfs grow bigger, then it’ll
likely not be able to be loaded by grub2.
* Some real cases from OEM projects:
In many built-in 4k monitor laptops with nvidia drivers, the u-d-c
puts the nvidia*.ko to initramfs which grows the initramfs to ~120M.
Also the gfxpayload=auto will remain to use 4K resolution since it’s
what EFI POST passed.
In this case, the grub isn't able to load initramfs because the
grub_memalign() won't be able to get suitable memory for the larger
file:
```
#0 grub_memalign (align=1, size=592214020) at ../../../grub-core/kern/mm.c:376
#1 0x7dd7b074 in grub_malloc (size=592214020) at
../../../grub-core/kern/mm.c:408
#2 0x7dd7a2c8 in grub_verifiers_open (io=0x7bc02d80, type=131076)
at ../../../grub-core/kern/verifiers.c:150
#3 0x7dd801d4 in grub_file_open (name=0x7bc02f00
"/boot/initrd.img-5.17.0-1011-oem",
type=131076) at ../../../grub-core/kern/file.c:121
#4 0x7bcd5a30 in ?? ()
#5 0x7fe21247 in ?? ()
#6 0x7bc030c8 in ?? ()
#7 0x00017fe21238 in ?? ()
#8 0x7bcd5320 in ?? ()
#9 0x7fe21250 in ?? ()
#10 0x in ?? ()
```
Based on grub_mm_dump, we can see the memory fragment (some parts seem
likely be used because of 4K resolution?) and doesn’t have available
contiguous memory for larger file as:
```
grub_real_malloc(...)
...
if (cur->size >= n + extra)
```
Based on UEFI Specification Section 7.2[1] and UEFI driver writers’
guide 4.2.3[2], we can ask 32bits+ on AllocatePages().
As most X86_64 platforms should support 64 bits addressing, we should
extend GRUB_EFI_MAX_USABLE_ADDRESS to 64 bits to get more available
memory.
* When users grown the initramfs, then probably will get initramfs
not found which really annoyed and impact the user experience (system
not able to boot).
[Test Plan]
* detailed instructions how to reproduce the bug:
1. Any method to grow the initramfs, such as install nvidia-driver.
2. If developers would like to reproduce, then could dd if=/dev/random
of=... bs=1M count=500, something like:
```
$ cat /usr/share/initramfs-tools/hooks/zzz-touch-a-file
#!/bin/sh
PREREQ=""
prereqs()
{
echo "$PREREQ"
}
case $1 in
# get pre-requisites
prereqs)
prereqs
exit 0
;;
esac
. /usr/share/initramfs-tools/hook-functions
dd if=/dev/random of=${DESTDIR}/test-500M bs=1M count=500
```
And then update-initramfs
* After applying my patches, the issue is gone.
* I did also test my test grubx64.efi in:
1. X86_64 qemu with
1.1. 60M initramfs + 5.15.0-37-generic kernel
1.2. 565M initramfs + 5.17.0-1011-oem kernel
2. Amd64 HP mobile workstation with
2.1. 65M initramfs + 5.15.0-39-generic kernel
2.2. 771M initramfs + 5.17.0-1011-oem kernel
All working well.
[Where problems could occur]
* The changes almost in i386/efi, thus the impact will be in the i386 /
x86_64 EFI system.
The other change is to modify the “grub-core/kern/efi/mm.c” but I use the
original addressing for “arm/arm64/ia64/riscv32/riscv64”.
Thus it should not impact them.
* There is a “#if defined(__x86_64__)” which intent to limit the >
32bits code in i386 system and also
```
#if defined (__code_model_large__)
-#define GRUB_EFI_MAX_USABLE_ADDRESS 0x
+#define GRUB_EFI_MAX_USABLE_ADDRESS __UINTPTR_MAX__
+#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x7fff
#else
#define GRUB_EFI_MAX_USABLE_ADDRESS 0x7fff
+#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x3fff
#endif
```
If everything works as expected, then i386 should working good.
If not lucky, based on “UEFI writers’ guide”[2], the i386 will get >
4GB memory region and never be able to access.
[Other Info]
* Upstream grub2 bug #61058
https://savannah.gnu.org/bugs/index.php?61058
* Test PPA: https://launchpad.net/~os369510/+archive/ubuntu/lp1842320
* Test grubx64.efi:
https://people.canonical.com/~jerem
[Touch-packages] [Bug 2063221] Re: Drop libglib2.0-0 transitional package
I tested this with a local package build and local repo in a mantic container,
doing an `apt --dry-run dist-upgrade` without/with that repo (w/ noble apt
sources list),
and manually download/run noble's release upgrader without/with that repo.
The behavior is the same (ie, no regressions) as expected;
libglib2.0-0 is removed in favor of libglib2.0-0t64 in all cases.
Test 1)
Just Noble:
$ apt-cache show libglib2.0-bin | grep Version:
Version: 2.80.0-6ubuntu1
Version: 2.78.0-2
$ sudo apt --dry-run dist-upgrade 2>&1 | awk '{ print NR ": " $0 }' |
fgrep libglib2.0
17: libevent-core-2.1-7 libext2fs2 libgdbm-compat4 libgdbm6
libglib2.0-0
30: libgdbm6t64 libglib2.0-0t64 libgnutls30t64 libgpgme11t64
79: libglib2.0-bin libglib2.0-data libgmp10 libgomp1 libgpg-error-l10n
154: Remv libelf1 [0.189-4] [libglib2.0-bin:amd64 libbpf1:amd64
iproute2:amd64 ]
156: Inst libglib2.0-bin [2.78.0-2] (2.80.0-6ubuntu1 Ubuntu:24.04/noble
[amd64]) []
378: Remv libglib2.0-0 [2.78.0-2] [libappstream4:amd64
open-vm-tools:amd64 libc-dev-bin:amd64 libc-bin:amd64 libc6-dev:amd64
libnetplan0:amd64 ]
379: Inst libglib2.0-0t64 (2.80.0-6ubuntu1 Ubuntu:24.04/noble [amd64])
[open-vm-tools:amd64 libc-dev-bin:amd64 libc-bin:amd64 libc6-dev:amd64 ]
611: Inst libglib2.0-data [2.78.0-2] (2.80.0-6ubuntu1
Ubuntu:24.04/noble [all])
927: Conf libglib2.0-bin (2.80.0-6ubuntu1 Ubuntu:24.04/noble [amd64])
1070: Conf libglib2.0-0t64 (2.80.0-6ubuntu1 Ubuntu:24.04/noble [amd64])
1201: Conf libglib2.0-data (2.80.0-6ubuntu1 Ubuntu:24.04/noble [all])
Noble and local build/repo:
$ apt-cache show libglib2.0-bin | grep Version:
Version: 2.80.0-6ubuntu3
Version: 2.80.0-6ubuntu1
Version: 2.78.0-2
$ sudo apt --dry-run dist-upgrade 2>&1 | awk '{ print NR ": " $0 }' |
fgrep libglib2.0
17: libevent-core-2.1-7 libext2fs2 libgdbm-compat4 libgdbm6
libglib2.0-0
30: libgdbm6t64 libglib2.0-0t64 libgnutls30t64 libgpgme11t64
79: libglib2.0-bin libglib2.0-data libgmp10 libgomp1 libgpg-error-l10n
154: Remv libelf1 [0.189-4] [libglib2.0-bin:amd64 libbpf1:amd64
iproute2:amd64 ]
156: Inst libglib2.0-bin [2.78.0-2] (2.80.0-6ubuntu3 localhost [amd64])
[]
378: Remv libglib2.0-0 [2.78.0-2] [libappstream4:amd64
open-vm-tools:amd64 libc-dev-bin:amd64 libc-bin:amd64 libc6-dev:amd64
libnetplan0:amd64 ]
379: Inst libglib2.0-0t64 (2.80.0-6ubuntu3 localhost [amd64])
[open-vm-tools:amd64 libc-dev-bin:amd64 libc-bin:amd64 libc6-dev:amd64 ]
611: Inst libglib2.0-data [2.78.0-2] (2.80.0-6ubuntu3 localhost [all])
927: Conf libglib2.0-bin (2.80.0-6ubuntu3 localhost [amd64])
1070: Conf libglib2.0-0t64 (2.80.0-6ubuntu3 localhost [amd64])
1201: Conf libglib2.0-data (2.80.0-6ubuntu3 localhost [all])
Test 2)
Just Noble:
$ dpkg -l | fgrep libglib2.0
rc libglib2.0-0:amd64 2.78.0-2
amd64GLib library of C routines
ii libglib2.0-0t64:amd64 2.80.0-6ubuntu1
amd64GLib library of C routines
ii libglib2.0-bin 2.80.0-6ubuntu1
amd64Programs for the GLib library
ii libglib2.0-data 2.80.0-6ubuntu1
all Common files for GLib library
$ dpkg -l | grep thunderbird
ii thunderbird 2:1snap1-0ubuntu3
amd64Transitional package - thunderbird -> thunderbird snap
$ snap list thunderbird
Name Version Rev Tracking Publisher Notes
thunderbird 115.10.1-1 470 latest/stable canonical✓ -
Noble and local build/repo:
$ dpkg -l | fgrep libglib2.0
rc libglib2.0-0:amd64 2.78.0-2
amd64GLib library of C routines
ii libglib2.0-0t64:amd64 2.80.0-6ubuntu3
amd64GLib library of C routines
ii libglib2.0-bin 2.80.0-6ubuntu3
amd64Programs for the GLib library
ii libglib2.0-data 2.80.0-6ubuntu3
all Common files for GLib library
$ dpkg -l | grep thunderbird
ii thunderbird 2:1snap1-0ubuntu3
amd64Transitional package - thunderbird -> thunderbird snap
$ snap list thunderbird
Name Version Rev Tracking Publisher Notes
thunderbird 115.10.1-1 470 latest/stable canonical✓ -
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2063221
Title:
Drop libglib2.0
[Touch-packages] [Bug 2063221] Re: Drop libglib2.0-0 transitional package
Hi Jeremy, This looks mostly good, AFAICT. Could you please complete the SRU bug template by adding the section 'Where problems could occur' / 'Regression potential'? [1] And although the 'Test Case' is feasible to understand, based on the 'Impact' section, it would be nice to have a 'functional' test, if at all possible/reasonably doable. For example, I tried to reproduce the thunderbird deb2snap issue, but it didn't. I realize there might be a more complex package setup/install list to trigger it, but maybe there's something simpler that you are aware of. (Or if it's too complex / not worth it, just clarifying that and mentioning what shouldn't change / how to check for no regressions, would be OK too; I tried to convey that in comment #1). Thanks! [1] https://wiki.ubuntu.com/StableReleaseUpdates#SRU_Bug_Template ** Changed in: glib2.0 (Ubuntu Noble) Status: In Progress => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2063221 Title: Drop libglib2.0-0 transitional package Status in glib2.0 package in Ubuntu: In Progress Status in glib2.0 source package in Noble: Incomplete Bug description: Impact -- apt can struggle with ordering when handling the massive Y2028 time_t transition when upgrading to Ubuntu 24.04 LTS. It was identified that dropping the libglib2.0-0 transitional package can help apt do things in the correct order. Test Case - Is libglib2.0-0 built? Where Problems Could Occur -- We have landed the change from this SRU in Debian Unstable and it successfully migrated to Debian Testing on April 27 as one of the first t64 packages to migrate there. This SRU was recommended by Julian Klode, the apt maintainer for Debian and Ubuntu. The original transitional package was added by Simon McVittie in hopes that it would help apt be able to calculate the upgrade easier. At least in the Ubuntu Desktop 22.04 LTS → 24.04 LTS case, it looks like it was the opposite. Hmm, we can't actually drop libglib2.0-0 after release, can we? Other Info -- This is related to LP: #2061918 for the thunderbird deb to snap upgrade There are likely several other Launchpad bugs that can be resolved by this update and some other workarounds in other packages, like in the transitional thunderbird package. https://salsa.debian.org/gnome-team/glib/-/merge_requests/34 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2063221/+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 2063221] Re: Drop libglib2.0-0 transitional package
The updates look good, thanks! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2063221 Title: Drop libglib2.0-0 transitional package Status in glib2.0 package in Ubuntu: In Progress Status in glib2.0 source package in Noble: Confirmed Bug description: Impact -- apt can struggle with ordering when handling the massive Y2028 time_t transition when upgrading to Ubuntu 24.04 LTS. It was identified that dropping the libglib2.0-0 transitional package can help apt do things in the correct order. Technically, Steve Langasek already removed libglib2.0-0 from noble release just before release. This upload is necessary to ensure that we don't accidentally bring it back. Test Case - 1. Is libglib2.0-0 built? 2. Run rmadison libglib2.0-0 There should be 0 results for noble, noble-proposed, or noble-updates 3. Ensure that libglib2.0-0 is removed during the upgrade from Ubuntu 22.04 LTS to 24.04 LTS. Technically, ubuntu-release-upgrader is currently set to disallow upgrades to 24.04 LTS. If this is still the case when it is time to verify this SRU, you can manually substitute jammy → noble in /etc/apt/sources.list for purposes of testing this upgrade, probably in a VM since that's not the supported way to upgrade. Where Problems Could Occur -- Doing an upload to not build a package that already does not exist in Ubuntu 24.04 LTS should have no regression potential. The only other change in this SRU is bumping the Breaks version to ensure that the transitional libglib2.0-0 is also removed for people who were using Ubuntu 24.04 LTS early. That also should not cause problems since the package was an empty transitional package for early Ubuntu 24.04 LTS users. Other Info -- This is related to LP: #2061918 for the thunderbird deb to snap upgrade There are likely several other Launchpad bugs that can be resolved by removing the transitional package and some other workarounds in other packages, like in the transitional thunderbird package. https://salsa.debian.org/gnome-team/glib/-/merge_requests/34 We have landed the removal in Debian Unstable and it successfully migrated to Debian Testing on April 27 as one of the first t64 packages to migrate there. The removal was recommended by Julian Klode, the apt maintainer for Debian and Ubuntu. The original transitional package was added by Simon McVittie in hopes that it would help apt be able to calculate the upgrade easier. At least in the Ubuntu Desktop 22.04 LTS → 24.04 LTS case, it looks like it was the opposite. (Although that particular detail was fixed by the removal that already happened.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2063221/+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 1974483] Re: autoinstall ssh:install-server:false is misleading in 22.04
Just for doc purposes,
ubuntu-meta's server-minimal binary package dependencies no longer list
`ssh-import-id` [1, 2], as expected.
$ wget -q
https://launchpad.net/ubuntu/+archive/primary/+files/ubuntu-server-minimal_1.481.{2,3}_amd64.deb
$ debdiff ubuntu-server-minimal_1.481.{2,3}_amd64.deb
File lists identical (after any substitutions)
Control files: lines which differ (wdiff format)
Depends: apparmor, apport, apt, bcache-tools, btrfs-progs, cloud-init,
cryptsetup, dbus, lvm2, mdadm, multipath-tools, netbase, ntfs-3g, open-iscsi,
pollinate, snapd, [-ssh-import-id,-] sudo, systemd, systemd-sysv,
ubuntu-drivers-common, ubuntu-release-upgrader-core, udev, xfsprogs
Version: [-1.481.2-] {+1.481.3+}
[1] https://launchpad.net/ubuntu/jammy/amd64/ubuntu-server-minimal/1.481.2
[2] https://launchpad.net/ubuntu/jammy/amd64/ubuntu-server-minimal/1.481.3
--
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/1974483
Title:
autoinstall ssh:install-server:false is misleading in 22.04
Status in subiquity:
Fix Released
Status in livecd-rootfs package in Ubuntu:
Fix Released
Status in ubuntu-meta package in Ubuntu:
Fix Released
Status in livecd-rootfs source package in Jammy:
Fix Released
Status in ubuntu-meta source package in Jammy:
Fix Released
Bug description:
[ Impact ]
openssh-server is always installed to the target machine regardless of the
user's explicit choice to not have it installed.
Backporting the fix will allow image builds to pick up it up and
become available for the next point release.
The upload fixes the bug by removing ssh-import-id from the server-
minimal seed and meta-package such that it's not part of the base
layer copied over during install.
[ Test Plan ]
live images -- Test 1:
1. Download the latest server installer image from
https://cdimage.ubuntu.com/ubuntu-server/jammy/daily-live/
2. Perform a regular install using the image and on the "SSH configuration"
screen make sure "Install OpenSSH server" is NOT selected.
3. Finish the install and reboot the machine.
4. Login to the rebooted machine using the credentials provided during
install.
5. Using "apt-cache policy openssh-server" and "apt-cache policy
ssh-import-id" confirm neither are installed.
live images -- Test 2:
- Perform Test 1 but instead opt-in to installing openssh-server and ensure
it is installed in the target system.
live-images -- Test 3:
- Perform Test 2 but in a completely offline fashion.
pre-installed images:
- Download the latest preinstalled image from:
https://cdimage.ubuntu.com/ubuntu-server/jammy/daily-preinstalled/
- Boot the image and, using the same commands as above, confirm
openssh-server and ssh-import-id ARE installed
[ Where problems could occur ]
- openssh-server could be included in the build through other means than
identified by the proposed upload, causing the package to be still installed by
default.
- openssh-server and ssh-import-id could fail to become part of the pool,
prohibiting offline install of the packages.
- Changes to the seeds could cause preinstalled images to lack the package.
- The image build(s) may produce errors if they rely on openssh-server or
ssh-import-id already being available in a layer in which it's now no longer
included. (I can't say it's likely but it is worth mentioning)
[ Other Info ]
* I have built test images for ubuntu-cpc, both minimized and non-minimized,
with my seed changes and verified those images will still correctly contain
ssh-import-id and open-ssh-server
[ Original Description]
With 22.04, openssh-server is baked into the image curtin copies to
the target. The ssh:install-server key no longer controls whether
openssh-server gets installed. It should be easy enough to have the
bit of code that installs openssh-server when the key is true also
remove it when the key is false.
To manage notifications about this bug go to:
https://bugs.launchpad.net/subiquity/+bug/1974483/+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 2055397] Re: netplan/systemd-networkd: route metric not applied to routes to the local subnet
The release of this SRU is blocked in failing autopkgtests [1, 2]. 1) Ignore the `linux-*` "regressions" as these packages are denylisted (shouldn't run autopkgtests; this seems like a parsing/reporting issue). 2) Please look at the `gvfs` regressions. It seems the `integreation` test finishes but does not exit, so it keeps running until a timeout. (previous passing runs finished <5 minutes, currently failing ones time out at 2-3 hours). 3) Please look at the `systemd/armhf` regression. The test case failing is `test_resolved_domain_restricted_dns`, due to a `resolvectl query` failing. This passes in other archs, so this could use test packages with instrumentation and autopkgtest runs against PPAs with them [3] (I'm happy to trigger those if needed) to figure out why the command fails (get its stdout/stderr in all arches and print it). Thanks! [1] https://ubuntu-archive-team.ubuntu.com/pending-sru.html # search for 245.4-4ubuntu3.24 [2] https://ubuntu-archive-team.ubuntu.com/proposed-migration/focal/update_excuses.html#systemd [3] https://wiki.ubuntu.com/ProposedMigration#Testing_against_a_PPA -- 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/2055397 Title: netplan/systemd-networkd: route metric not applied to routes to the local subnet Status in cloud-init package in Ubuntu: Invalid Status in netplan.io package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Fix Committed Bug description: [SRU TEMPLATE] [DESCRIPTION] Cloud-init introduced a feature to configure policy routing on AWS EC2 instances with multiple NICs in https://github.com/canonical/cloud-init/commit/0ca5f31043e2d98eab31a43d9dde9bdaef1435cb targeting v24.1. Cloud-init generates the following netplan config: ``` $ cat /etc/netplan/50-cloud-init.yaml network: ethernets: ens5: dhcp4: true dhcp4-overrides: &id001 route-metric: 100 dhcp6: true dhcp6-overrides: *id001 match: macaddress: 0a:c8:ab:90:c2:fb set-name: ens5 ens6: dhcp4: true dhcp4-overrides: route-metric: 200 use-routes: true dhcp6: false match: macaddress: 0a:c6:55:a1:dc:3b routes: - table: 101 to: 0.0.0.0/0 via: 192.168.0.1 - table: 101 to: 192.168.0.0/20 routing-policy: - from: 192.168.10.212 table: 101 set-name: ens6 version: 2 ``` Which renders the following systemd-networkd config files: ``` $ cat 10-netplan-ens5.link [Match] MACAddress=0a:c8:ab:90:c2:fb [Link] Name=ens5 WakeOnLan=off $ cat 10-netplan-ens5.network [Match] MACAddress=0a:c8:ab:90:c2:fb Name=ens5 [Network] DHCP=yes LinkLocalAddressing=ipv6 [DHCP] RouteMetric=100 UseMTU=true $ cat 10-netplan-ens6.link [Match] MACAddress=0a:c6:55:a1:dc:3b [Link] Name=ens6 WakeOnLan=off $ cat 10-netplan-ens6.network [Match] MACAddress=0a:c6:55:a1:dc:3b Name=ens6 [Network] DHCP=ipv4 LinkLocalAddressing=ipv6 [Route] Destination=0.0.0.0/0 Gateway=192.168.0.1 Table=101 [Route] Destination=192.168.0.0/20 Scope=link Table=101 [RoutingPolicyRule] From=192.168.10.212 Table=101 [DHCP] RouteMetric=200 UseMTU=true ``` Which configures the instance with the following state in Ubuntu Focal: ``` $ ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: ens5: mtu 9001 qdisc mq state UP group default qlen 1000 link/ether 0a:c8:ab:90:c2:fb brd ff:ff:ff:ff:ff:ff inet 192.168.12.94/20 brd 192.168.15.255 scope global dynamic ens5 valid_lft 2087sec preferred_lft 2087sec inet6 2a05:d012:ea0:c500:6d12:2b20:5fef:a502/128 scope global dynamic noprefixroute valid_lft 440sec preferred_lft 130sec inet6 fe80::8c8:abff:fe90:c2fb/64 scope link valid_lft forever preferred_lft forever 3: ens6: mtu 9001 qdisc mq state UP group default qlen 1000 link/ether 0a:c6:55:a1:dc:3b brd ff:ff:ff:ff:ff:ff inet 192.168.10.212/20 brd 192.168.15.255 scope global dynamic ens6 valid_lft 2083sec preferred_lft 2083sec inet6 fe80::8c6:55ff:fea1:dc3b/64 scope link valid_lft forever preferred_lft forever $ ip route show default via 192.168.0.1 dev ens5 proto dhcp src 192.168.12.9
[Touch-packages] [Bug 2066990] Re: high memory consumption in Ubuntu Noble
** Changed in: ca-certificates (Ubuntu) Assignee: (unassigned) => Mauricio Faria de Oliveira (mfo) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/2066990 Title: high memory consumption in Ubuntu Noble Status in ca-certificates package in Ubuntu: Confirmed Bug description: I wanted to try the new Ubuntu 24.04 Noble Numbat based .NET docker image and updated the base docker image in our CI pipeline to mcr.microsoft.com/dotnet/sdk:8.0-noble. However, it results in an out- of-memory exception. Based on my investigation, the exception occurs specifically when the update-ca-certificates command is executed. I can also repro the issue with ubuntu:noble image which means it's not specific to .NET docker images. It works fine with Jammy, by the way. The problem likely lies with the Noble base image rather than the .NET image. I'm not sure what changes were made between Jammy and Noble, but it appears that updating certificates consumes a lot of memory in Noble. I adjusted some memory settings in our GitLab runner, but it didn't resolve the issue. I attached all Gitlab Runner shell logs for .NET 8 Jammy, .NET 8 Noble and Ubuntu Noble images. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/2066990/+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 2076340] Re: SRU: no-change rebuild to pick up changed build flags on ppc64el and s390x
Hi Frank Heimes,
Comment #67:
> A new upload of the s390-tools package always also requires an upload of the
> s390-tools-signed package with the same version as well.
> I've attached the debdiff for it here...
Thanks for that.
The upload contains removals of d/{changelog,control}.orig which aren't
mentioned in d/changelog.
While that seems obvious to understand (apparently, such files aren't
referenced, and this is done also in Oracular in 2.33.1-0ubuntu1), for
SRU process reasons (see Procedure [1], item 4), could you please
clarify that in the changelog?
[1] https://wiki.ubuntu.com/StableReleaseUpdates#Procedure
"The upload must have [...], and no other unrelated changes."
** Changed in: s390-tools-signed (Ubuntu Noble)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bzip2 in Ubuntu.
https://bugs.launchpad.net/bugs/2076340
Title:
SRU: no-change rebuild to pick up changed build flags on ppc64el and
s390x
Status in atlas package in Ubuntu:
New
Status in bzip2 package in Ubuntu:
Fix Released
Status in containerd-app package in Ubuntu:
New
Status in curl package in Ubuntu:
New
Status in cyrus-sasl2 package in Ubuntu:
New
Status in dbus package in Ubuntu:
Fix Released
Status in docker.io-app package in Ubuntu:
New
Status in dotnet8 package in Ubuntu:
New
Status in gnutls28 package in Ubuntu:
New
Status in golang-1.22 package in Ubuntu:
New
Status in icu package in Ubuntu:
Fix Released
Status in lapack package in Ubuntu:
Fix Released
Status in libdeflate package in Ubuntu:
New
Status in libseccomp package in Ubuntu:
Fix Released
Status in libzdnn package in Ubuntu:
Fix Released
Status in libzstd package in Ubuntu:
New
Status in lz4 package in Ubuntu:
New
Status in mysql-8.0 package in Ubuntu:
New
Status in nettle package in Ubuntu:
New
Status in openssh package in Ubuntu:
New
Status in openssl package in Ubuntu:
New
Status in p11-kit package in Ubuntu:
New
Status in postgresql-16 package in Ubuntu:
New
Status in postgresql-common package in Ubuntu:
New
Status in powerpc-utils package in Ubuntu:
Fix Released
Status in python-greenlet package in Ubuntu:
Fix Released
Status in qemu package in Ubuntu:
New
Status in runc-app package in Ubuntu:
Fix Released
Status in rustc package in Ubuntu:
New
Status in s390-tools package in Ubuntu:
New
Status in s390-tools-signed package in Ubuntu:
New
Status in systemd package in Ubuntu:
New
Status in util-linux package in Ubuntu:
New
Status in xz-utils package in Ubuntu:
New
Status in zlib package in Ubuntu:
New
Status in atlas source package in Noble:
Fix Committed
Status in bzip2 source package in Noble:
Fix Committed
Status in containerd-app source package in Noble:
Fix Committed
Status in curl source package in Noble:
Fix Committed
Status in cyrus-sasl2 source package in Noble:
Fix Committed
Status in dbus source package in Noble:
Fix Committed
Status in docker.io-app source package in Noble:
Fix Committed
Status in dotnet8 source package in Noble:
Fix Committed
Status in gnutls28 source package in Noble:
Fix Committed
Status in golang-1.22 source package in Noble:
Fix Committed
Status in icu source package in Noble:
Fix Committed
Status in lapack source package in Noble:
Fix Committed
Status in libdeflate source package in Noble:
Fix Committed
Status in libseccomp source package in Noble:
Fix Committed
Status in libzdnn source package in Noble:
Fix Committed
Status in libzstd source package in Noble:
Fix Committed
Status in lz4 source package in Noble:
Fix Committed
Status in mysql-8.0 source package in Noble:
Fix Committed
Status in nettle source package in Noble:
Fix Committed
Status in openssh source package in Noble:
Fix Committed
Status in openssl source package in Noble:
Fix Committed
Status in p11-kit source package in Noble:
Fix Committed
Status in postgresql-16 source package in Noble:
Fix Committed
Status in postgresql-common source package in Noble:
Fix Committed
Status in powerpc-utils source package in Noble:
Fix Committed
Status in python-greenlet source package in Noble:
Fix Committed
Status in qemu source package in Noble:
Fix Committed
Status in runc-app source package in Noble:
Fix Committed
Status in rustc source package in Noble:
Fix Committed
Status in s390-tools source package in Noble:
Fix Committed
Status in s390-tools-signed source package in Noble:
Incomplete
Status in systemd source package in Noble:
Fix Committed
Status in util-linux source package in Noble:
Fix Committed
Status in xz-utils source package in Noble:
Fix Committed
Status in zlib source package in Noble:
Fix Committed
Bug description:
SRU: no-change rebuild to pick up changed build flags on ppc64el and
s390x
This is batch of packages that we want to rebuild to pick up the
changed build flags on ppc64el (LP: #2064539
[Touch-packages] [Bug 2063200] Re: useradd --extrausers --groups tries to lock /etc/group
The autopkgtests in mysql-8.0/armhf seems to be timeouts (retried), and output mismatch (apparently the shutdown banner is unexpected). The latter might need to be looked at. mysql-8.0/armhf autopkgtests regressions (timeouts and output mismatch) 9086s Completed: Failed 4/1073 tests, 99.63% were successful. 9086s 9086s Failing test(s): main.lock_multi_bug38691 main.multi_update main.mysqlslap main.basedir 1) 6152s [ 77%] main.lock_multi_bug38691 w1 [ fail ] timeout after 900 seconds 6152s Test ended at 2024-08-23 15:07:42 6152s mysqltest: Could not open connection 'default': 2013 Lost connection to MySQL server at 'reading initial communication packet', system error: 104 6152s safe_process[47785]: Child process: 47786, exit: 1 ... 7088s Test main.lock_multi_bug38691 has failed 2 times, no more retries. 2) 3607s [ 49%] main.multi_updatew7 [ fail ] timeout after 900 seconds 4571s [ 59%] main.multi_updatew7 [ retry-fail ] timeout after 900 seconds 3) 6000s [ 75%] main.mysqlslap w7 [ fail ] timeout after 900 seconds 6000s 2024-08-23T15:04:08.636678Z 734 [Note] [MY-010914] [Server] Aborted connection 734 to db: 'bug58090' user: 'root' host: 'localhost' (Got an error reading communication packets). 4) 1832s [ 21%] main.basedir w4 [ fail ] ... 1832s --- /usr/lib/mysql-test/r/basedir.result 2024-07-12 22:15:25.0 +0300 1832s +++ /tmp/tmp.5Zzx61IMMy/var/4/log/basedir.reject 2024-08-23 16:55:42.443786800 +0300 ... 1832s # Supressing output for initialize: 1832s +2024-08-23T13:55:33.808784Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.0.39-0ubuntu0.24.04.2) (Ubuntu). 1832s # Wait for daemon server to start -- 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/2063200 Title: useradd --extrausers --groups tries to lock /etc/group Status in shadow package in Ubuntu: Fix Released Status in shadow source package in Jammy: Invalid Status in shadow source package in Mantic: Won't Fix Status in shadow source package in Noble: Fix Committed Status in shadow source package in Oracular: Fix Released Bug description: [ Impact ] On Ubuntu Core 24 calling the command line useradd --extrausers --groups somegroup somenewuser ... fails with: useradd: cannot lock /etc/group; try again later. It worked on 22.04. /etc is not writable. It also fails if somegroup is a group in extrausers. [ Test Plan ] Part of the upload is adding an autopkgtest script testing useradd and usermod in the extrausers+readonly-etc case. In addition, the following commands should be run as root in a fresh container: ``` # Install prerequisites apt install libnss-extrausers sed -i -r '/^(passwd|group|shadow|gshadow)/ s/$/ extrausers/' /etc/nsswitch.conf # enable extrausers in group, passwd, shadow and gshadow # Sanity checks of "normal" path groupadd etcgroup useradd --groups etcgroup etcuser id etcuser | grep etcgroup groupadd etcgroup2 usermod --groups etcgroup2 etcuser id etcuser | grep etcgroup2 useradd --groups nullgroup etcuser || echo Successfully rejected invalid group ls /var/lib/extrausers/ # should be empty # Sanity checks of "extrausers" path in rw context groupadd --extrausers extragroup useradd --extrausers --groups extragroup extrauser # currently fails id extrauser | grep extragroup useradd --extrausers extrauser2 id extrauser2 # Sanity checks of "extrausers" path in ro context mv /etc /etc-rw mkdir /etc mount -o bind,ro /etc-rw /etc groupadd --extrausers extragroup2 useradd --extrausers --groups etcgroup extrauser3 id extrauser4 | grep etcgroup ``` Furthermore, validation from the Ubuntu Core team that this actually fixes their use case is required. [ Where problems could occur ] Regression potential is in the group validation stage of the `usermod` and `useradd` tools. Besides the usual risks related to C code, the various failure scenarios that come to mind are: * try to add the user to an non-existing local group, which would fail further down with a different error message * actually fail to identify a valid local group * Fail to either add the user to the system, or the user to the group * Update the wrong file (/var/lib/extrausers/* vs /etc/*) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/2063200/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-package
[Touch-packages] [Bug 2075337] Re: [SRU] py3clean fails when using alternate character set
Hello Robie, or anyone else affected, Accepted syncplay into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/syncplay/1.7.0+repack1-2ubuntu0.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-noble. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: syncplay (Ubuntu Noble) Status: Incomplete => Fix Committed ** Changed in: pagure (Ubuntu Noble) Status: Incomplete => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dh-python in Ubuntu. https://bugs.launchpad.net/bugs/2075337 Title: [SRU] py3clean fails when using alternate character set Status in cloud-init package in Ubuntu: New Status in dh-python package in Ubuntu: Invalid Status in logdata-anomaly-miner package in Ubuntu: Invalid Status in lomiri package in Ubuntu: Invalid Status in mailman3 package in Ubuntu: Invalid Status in matrix-sydent package in Ubuntu: Invalid Status in mom package in Ubuntu: Invalid Status in mopidy package in Ubuntu: Invalid Status in mpd-sima package in Ubuntu: Invalid Status in nordugrid-arc package in Ubuntu: Invalid Status in notus-scanner package in Ubuntu: Invalid Status in nrpe-ng package in Ubuntu: Invalid Status in onionprobe package in Ubuntu: Invalid Status in openscap-daemon package in Ubuntu: Invalid Status in ospd-openvas package in Ubuntu: Invalid Status in pagekite package in Ubuntu: Invalid Status in pagure package in Ubuntu: Invalid Status in pglistener package in Ubuntu: Invalid Status in policyd-rate-limit package in Ubuntu: Invalid Status in postfix-mta-sts-resolver package in Ubuntu: Invalid Status in powa-collector package in Ubuntu: Invalid Status in prelude-correlator package in Ubuntu: Invalid Status in prometheus-pgbouncer-exporter package in Ubuntu: Invalid Status in prometheus-xmpp-alerts package in Ubuntu: Invalid Status in pyro5 package in Ubuntu: Invalid Status in pyroman package in Ubuntu: Invalid Status in python3-defaults package in Ubuntu: Fix Released Status in r4d package in Ubuntu: Invalid Status in razercfg package in Ubuntu: Invalid Status in sgt-launcher package in Ubuntu: Fix Released Status in sms4you package in Ubuntu: Invalid Status in supervisor package in Ubuntu: Invalid Status in syncplay package in Ubuntu: Invalid Status in timekpr-next package in Ubuntu: Fix Released Status in twms package in Ubuntu: Invalid Status in ubuntu-advantage-tools package in Ubuntu: New Status in vanguards package in Ubuntu: Incomplete Status in vaultlocker package in Ubuntu: Invalid Status in virtualbox package in Ubuntu: Invalid Status in voctomix-outcasts package in Ubuntu: Invalid Status in weborf package in Ubuntu: Invalid Status in xdiagnose package in Ubuntu: Fix Released Status in cloud-init source package in Jammy: Invalid Status in dh-python source package in Jammy: Invalid Status in logdata-anomaly-miner source package in Jammy: Invalid Status in lomiri source package in Jammy: Invalid Status in mailman3 source package in Jammy: Invalid Status in matrix-sydent source package in Jammy: Invalid Status in mom source package in Jammy: Invalid Status in mopidy source package in Jammy: Invalid Status in mpd-sima source package in Jammy: Invalid Status in nordugrid-arc source package in Jammy: Invalid Status in notus-scanner source package in Jammy: Invalid Status in nrpe-ng source package in Jammy: Invalid Status in onionprobe source package in Jammy: Invalid Status in openscap-daemon source package in Jammy: Invalid Status in ospd-openvas source package in Jammy: Invalid Status in pagekite source package in Jammy: Invalid Status in pagure source package in Jammy: Invalid Status in pglistener source package in Jammy: Invalid Status in policyd-rate-limit source package in Jammy: Invalid Status in postfix-mta-sts-resolver source package in Jammy: Invalid Stat
[Touch-packages] [Bug 2075337] Please test proposed package
Hello Robie, or anyone else affected, Accepted pagure into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/pagure/5.11.3+dfsg-2.1ubuntu0.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-noble. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: prometheus-pgbouncer-exporter (Ubuntu Noble) Status: Incomplete => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dh-python in Ubuntu. https://bugs.launchpad.net/bugs/2075337 Title: [SRU] py3clean fails when using alternate character set Status in cloud-init package in Ubuntu: New Status in dh-python package in Ubuntu: Invalid Status in logdata-anomaly-miner package in Ubuntu: Invalid Status in lomiri package in Ubuntu: Invalid Status in mailman3 package in Ubuntu: Invalid Status in matrix-sydent package in Ubuntu: Invalid Status in mom package in Ubuntu: Invalid Status in mopidy package in Ubuntu: Invalid Status in mpd-sima package in Ubuntu: Invalid Status in nordugrid-arc package in Ubuntu: Invalid Status in notus-scanner package in Ubuntu: Invalid Status in nrpe-ng package in Ubuntu: Invalid Status in onionprobe package in Ubuntu: Invalid Status in openscap-daemon package in Ubuntu: Invalid Status in ospd-openvas package in Ubuntu: Invalid Status in pagekite package in Ubuntu: Invalid Status in pagure package in Ubuntu: Invalid Status in pglistener package in Ubuntu: Invalid Status in policyd-rate-limit package in Ubuntu: Invalid Status in postfix-mta-sts-resolver package in Ubuntu: Invalid Status in powa-collector package in Ubuntu: Invalid Status in prelude-correlator package in Ubuntu: Invalid Status in prometheus-pgbouncer-exporter package in Ubuntu: Invalid Status in prometheus-xmpp-alerts package in Ubuntu: Invalid Status in pyro5 package in Ubuntu: Invalid Status in pyroman package in Ubuntu: Invalid Status in python3-defaults package in Ubuntu: Fix Released Status in r4d package in Ubuntu: Invalid Status in razercfg package in Ubuntu: Invalid Status in sgt-launcher package in Ubuntu: Fix Released Status in sms4you package in Ubuntu: Invalid Status in supervisor package in Ubuntu: Invalid Status in syncplay package in Ubuntu: Invalid Status in timekpr-next package in Ubuntu: Fix Released Status in twms package in Ubuntu: Invalid Status in ubuntu-advantage-tools package in Ubuntu: New Status in vanguards package in Ubuntu: Incomplete Status in vaultlocker package in Ubuntu: Invalid Status in virtualbox package in Ubuntu: Invalid Status in voctomix-outcasts package in Ubuntu: Invalid Status in weborf package in Ubuntu: Invalid Status in xdiagnose package in Ubuntu: Fix Released Status in cloud-init source package in Jammy: Invalid Status in dh-python source package in Jammy: Invalid Status in logdata-anomaly-miner source package in Jammy: Invalid Status in lomiri source package in Jammy: Invalid Status in mailman3 source package in Jammy: Invalid Status in matrix-sydent source package in Jammy: Invalid Status in mom source package in Jammy: Invalid Status in mopidy source package in Jammy: Invalid Status in mpd-sima source package in Jammy: Invalid Status in nordugrid-arc source package in Jammy: Invalid Status in notus-scanner source package in Jammy: Invalid Status in nrpe-ng source package in Jammy: Invalid Status in onionprobe source package in Jammy: Invalid Status in openscap-daemon source package in Jammy: Invalid Status in ospd-openvas source package in Jammy: Invalid Status in pagekite source package in Jammy: Invalid Status in pagure source package in Jammy: Invalid Status in pglistener source package in Jammy: Invalid Status in policyd-rate-limit source package in Jammy: Invalid Status in postfix-mta-sts-resolver source package in Jammy: Invalid Status in powa-collector source package in Jammy: Invalid Status i
[Touch-packages] [Bug 2075337] Please test proposed package
Hello Robie, or anyone else affected, Accepted prometheus-pgbouncer-exporter into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/prometheus-pgbouncer- exporter/1.7-3ubuntu0.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-noble. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: sgt-launcher (Ubuntu Jammy) Status: Invalid => New ** Changed in: sgt-launcher (Ubuntu Noble) Status: Incomplete => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dh-python in Ubuntu. https://bugs.launchpad.net/bugs/2075337 Title: [SRU] py3clean fails when using alternate character set Status in cloud-init package in Ubuntu: New Status in dh-python package in Ubuntu: Invalid Status in logdata-anomaly-miner package in Ubuntu: Invalid Status in lomiri package in Ubuntu: Invalid Status in mailman3 package in Ubuntu: Invalid Status in matrix-sydent package in Ubuntu: Invalid Status in mom package in Ubuntu: Invalid Status in mopidy package in Ubuntu: Invalid Status in mpd-sima package in Ubuntu: Invalid Status in nordugrid-arc package in Ubuntu: Invalid Status in notus-scanner package in Ubuntu: Invalid Status in nrpe-ng package in Ubuntu: Invalid Status in onionprobe package in Ubuntu: Invalid Status in openscap-daemon package in Ubuntu: Invalid Status in ospd-openvas package in Ubuntu: Invalid Status in pagekite package in Ubuntu: Invalid Status in pagure package in Ubuntu: Invalid Status in pglistener package in Ubuntu: Invalid Status in policyd-rate-limit package in Ubuntu: Invalid Status in postfix-mta-sts-resolver package in Ubuntu: Invalid Status in powa-collector package in Ubuntu: Invalid Status in prelude-correlator package in Ubuntu: Invalid Status in prometheus-pgbouncer-exporter package in Ubuntu: Invalid Status in prometheus-xmpp-alerts package in Ubuntu: Invalid Status in pyro5 package in Ubuntu: Invalid Status in pyroman package in Ubuntu: Invalid Status in python3-defaults package in Ubuntu: Fix Released Status in r4d package in Ubuntu: Invalid Status in razercfg package in Ubuntu: Invalid Status in sgt-launcher package in Ubuntu: Fix Released Status in sms4you package in Ubuntu: Invalid Status in supervisor package in Ubuntu: Invalid Status in syncplay package in Ubuntu: Invalid Status in timekpr-next package in Ubuntu: Fix Released Status in twms package in Ubuntu: Invalid Status in ubuntu-advantage-tools package in Ubuntu: New Status in vanguards package in Ubuntu: Incomplete Status in vaultlocker package in Ubuntu: Invalid Status in virtualbox package in Ubuntu: Invalid Status in voctomix-outcasts package in Ubuntu: Invalid Status in weborf package in Ubuntu: Invalid Status in xdiagnose package in Ubuntu: Fix Released Status in cloud-init source package in Jammy: Invalid Status in dh-python source package in Jammy: Invalid Status in logdata-anomaly-miner source package in Jammy: Invalid Status in lomiri source package in Jammy: Invalid Status in mailman3 source package in Jammy: Invalid Status in matrix-sydent source package in Jammy: Invalid Status in mom source package in Jammy: Invalid Status in mopidy source package in Jammy: Invalid Status in mpd-sima source package in Jammy: Invalid Status in nordugrid-arc source package in Jammy: Invalid Status in notus-scanner source package in Jammy: Invalid Status in nrpe-ng source package in Jammy: Invalid Status in onionprobe source package in Jammy: Invalid Status in openscap-daemon source package in Jammy: Invalid Status in ospd-openvas source package in Jammy: Invalid Status in pagekite source package in Jammy: Invalid Status in pagure source package in Jammy: Invalid Status in pglistener source package in Jammy: Invalid Status in policyd-rate-limit source package in Jammy: Invalid Status in postfix-mta-sts-resolver source pa
[Touch-packages] [Bug 2075337] Please test proposed package
Hello Robie, or anyone else affected, Accepted sgt-launcher into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/sgt- launcher/0.2.8-0ubuntu1.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-noble. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dh-python in Ubuntu. https://bugs.launchpad.net/bugs/2075337 Title: [SRU] py3clean fails when using alternate character set Status in cloud-init package in Ubuntu: New Status in dh-python package in Ubuntu: Invalid Status in logdata-anomaly-miner package in Ubuntu: Invalid Status in lomiri package in Ubuntu: Invalid Status in mailman3 package in Ubuntu: Invalid Status in matrix-sydent package in Ubuntu: Invalid Status in mom package in Ubuntu: Invalid Status in mopidy package in Ubuntu: Invalid Status in mpd-sima package in Ubuntu: Invalid Status in nordugrid-arc package in Ubuntu: Invalid Status in notus-scanner package in Ubuntu: Invalid Status in nrpe-ng package in Ubuntu: Invalid Status in onionprobe package in Ubuntu: Invalid Status in openscap-daemon package in Ubuntu: Invalid Status in ospd-openvas package in Ubuntu: Invalid Status in pagekite package in Ubuntu: Invalid Status in pagure package in Ubuntu: Invalid Status in pglistener package in Ubuntu: Invalid Status in policyd-rate-limit package in Ubuntu: Invalid Status in postfix-mta-sts-resolver package in Ubuntu: Invalid Status in powa-collector package in Ubuntu: Invalid Status in prelude-correlator package in Ubuntu: Invalid Status in prometheus-pgbouncer-exporter package in Ubuntu: Invalid Status in prometheus-xmpp-alerts package in Ubuntu: Invalid Status in pyro5 package in Ubuntu: Invalid Status in pyroman package in Ubuntu: Invalid Status in python3-defaults package in Ubuntu: Fix Released Status in r4d package in Ubuntu: Invalid Status in razercfg package in Ubuntu: Invalid Status in sgt-launcher package in Ubuntu: Fix Released Status in sms4you package in Ubuntu: Invalid Status in supervisor package in Ubuntu: Invalid Status in syncplay package in Ubuntu: Invalid Status in timekpr-next package in Ubuntu: Fix Released Status in twms package in Ubuntu: Invalid Status in ubuntu-advantage-tools package in Ubuntu: New Status in vanguards package in Ubuntu: Incomplete Status in vaultlocker package in Ubuntu: Invalid Status in virtualbox package in Ubuntu: Invalid Status in voctomix-outcasts package in Ubuntu: Invalid Status in weborf package in Ubuntu: Invalid Status in xdiagnose package in Ubuntu: Fix Released Status in cloud-init source package in Jammy: Invalid Status in dh-python source package in Jammy: Invalid Status in logdata-anomaly-miner source package in Jammy: Invalid Status in lomiri source package in Jammy: Invalid Status in mailman3 source package in Jammy: Invalid Status in matrix-sydent source package in Jammy: Invalid Status in mom source package in Jammy: Invalid Status in mopidy source package in Jammy: Invalid Status in mpd-sima source package in Jammy: Invalid Status in nordugrid-arc source package in Jammy: Invalid Status in notus-scanner source package in Jammy: Invalid Status in nrpe-ng source package in Jammy: Invalid Status in onionprobe source package in Jammy: Invalid Status in openscap-daemon source package in Jammy: Invalid Status in ospd-openvas source package in Jammy: Invalid Status in pagekite source package in Jammy: Invalid Status in pagure source package in Jammy: Invalid Status in pglistener source package in Jammy: Invalid Status in policyd-rate-limit source package in Jammy: Invalid Status in postfix-mta-sts-resolver source package in Jammy: Invalid Status in powa-collector source package in Jammy: Invalid Status in prelude-correlator source package in Jammy: Invalid Status in prometheus-pgbouncer-exporter sou
[Touch-packages] [Bug 2075337] Re: [SRU] py3clean fails when using alternate character set
Hello Robie, or anyone else affected, Accepted razercfg into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/razercfg/0.42+ds-4ubuntu0.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-noble. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: razercfg (Ubuntu Noble) Status: Incomplete => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dh-python in Ubuntu. https://bugs.launchpad.net/bugs/2075337 Title: [SRU] py3clean fails when using alternate character set Status in cloud-init package in Ubuntu: New Status in dh-python package in Ubuntu: Invalid Status in logdata-anomaly-miner package in Ubuntu: Invalid Status in lomiri package in Ubuntu: Invalid Status in mailman3 package in Ubuntu: Invalid Status in matrix-sydent package in Ubuntu: Invalid Status in mom package in Ubuntu: Invalid Status in mopidy package in Ubuntu: Invalid Status in mpd-sima package in Ubuntu: Invalid Status in nordugrid-arc package in Ubuntu: Invalid Status in notus-scanner package in Ubuntu: Invalid Status in nrpe-ng package in Ubuntu: Invalid Status in onionprobe package in Ubuntu: Invalid Status in openscap-daemon package in Ubuntu: Invalid Status in ospd-openvas package in Ubuntu: Invalid Status in pagekite package in Ubuntu: Invalid Status in pagure package in Ubuntu: Invalid Status in pglistener package in Ubuntu: Invalid Status in policyd-rate-limit package in Ubuntu: Invalid Status in postfix-mta-sts-resolver package in Ubuntu: Invalid Status in powa-collector package in Ubuntu: Invalid Status in prelude-correlator package in Ubuntu: Invalid Status in prometheus-pgbouncer-exporter package in Ubuntu: Invalid Status in prometheus-xmpp-alerts package in Ubuntu: Invalid Status in pyro5 package in Ubuntu: Invalid Status in pyroman package in Ubuntu: Invalid Status in python3-defaults package in Ubuntu: Fix Released Status in r4d package in Ubuntu: Invalid Status in razercfg package in Ubuntu: Invalid Status in sgt-launcher package in Ubuntu: Fix Released Status in sms4you package in Ubuntu: Invalid Status in supervisor package in Ubuntu: Invalid Status in syncplay package in Ubuntu: Invalid Status in timekpr-next package in Ubuntu: Fix Released Status in twms package in Ubuntu: Invalid Status in ubuntu-advantage-tools package in Ubuntu: New Status in vanguards package in Ubuntu: Incomplete Status in vaultlocker package in Ubuntu: Invalid Status in virtualbox package in Ubuntu: Invalid Status in voctomix-outcasts package in Ubuntu: Invalid Status in weborf package in Ubuntu: Invalid Status in xdiagnose package in Ubuntu: Fix Released Status in cloud-init source package in Jammy: Invalid Status in dh-python source package in Jammy: Invalid Status in logdata-anomaly-miner source package in Jammy: Invalid Status in lomiri source package in Jammy: Invalid Status in mailman3 source package in Jammy: Invalid Status in matrix-sydent source package in Jammy: Invalid Status in mom source package in Jammy: Invalid Status in mopidy source package in Jammy: Invalid Status in mpd-sima source package in Jammy: Invalid Status in nordugrid-arc source package in Jammy: Invalid Status in notus-scanner source package in Jammy: Invalid Status in nrpe-ng source package in Jammy: Invalid Status in onionprobe source package in Jammy: Invalid Status in openscap-daemon source package in Jammy: Invalid Status in ospd-openvas source package in Jammy: Invalid Status in pagekite source package in Jammy: Invalid Status in pagure source package in Jammy: Invalid Status in pglistener source package in Jammy: Invalid Status in policyd-rate-limit source package in Jammy: Invalid Status in postfix-mta-sts-resolver source package in Jammy: Invalid Status in powa-collector source package in Jammy: Invalid Status in prelude-correlator so
[Touch-packages] [Bug 2075337] Re: [SRU] py3clean fails when using alternate character set
Hello Robie, or anyone else affected, Accepted pyro5 into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/pyro5/5.14-2ubuntu0.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-noble. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: pyro5 (Ubuntu Noble) Status: Incomplete => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dh-python in Ubuntu. https://bugs.launchpad.net/bugs/2075337 Title: [SRU] py3clean fails when using alternate character set Status in cloud-init package in Ubuntu: New Status in dh-python package in Ubuntu: Invalid Status in logdata-anomaly-miner package in Ubuntu: Invalid Status in lomiri package in Ubuntu: Invalid Status in mailman3 package in Ubuntu: Invalid Status in matrix-sydent package in Ubuntu: Invalid Status in mom package in Ubuntu: Invalid Status in mopidy package in Ubuntu: Invalid Status in mpd-sima package in Ubuntu: Invalid Status in nordugrid-arc package in Ubuntu: Invalid Status in notus-scanner package in Ubuntu: Invalid Status in nrpe-ng package in Ubuntu: Invalid Status in onionprobe package in Ubuntu: Invalid Status in openscap-daemon package in Ubuntu: Invalid Status in ospd-openvas package in Ubuntu: Invalid Status in pagekite package in Ubuntu: Invalid Status in pagure package in Ubuntu: Invalid Status in pglistener package in Ubuntu: Invalid Status in policyd-rate-limit package in Ubuntu: Invalid Status in postfix-mta-sts-resolver package in Ubuntu: Invalid Status in powa-collector package in Ubuntu: Invalid Status in prelude-correlator package in Ubuntu: Invalid Status in prometheus-pgbouncer-exporter package in Ubuntu: Invalid Status in prometheus-xmpp-alerts package in Ubuntu: Invalid Status in pyro5 package in Ubuntu: Incomplete Status in pyroman package in Ubuntu: Invalid Status in python3-defaults package in Ubuntu: Fix Released Status in r4d package in Ubuntu: Invalid Status in razercfg package in Ubuntu: Invalid Status in sgt-launcher package in Ubuntu: Fix Released Status in sms4you package in Ubuntu: Invalid Status in supervisor package in Ubuntu: Invalid Status in syncplay package in Ubuntu: Invalid Status in timekpr-next package in Ubuntu: Fix Released Status in twms package in Ubuntu: Invalid Status in ubuntu-advantage-tools package in Ubuntu: New Status in vanguards package in Ubuntu: Incomplete Status in vaultlocker package in Ubuntu: Invalid Status in virtualbox package in Ubuntu: Invalid Status in voctomix-outcasts package in Ubuntu: Invalid Status in weborf package in Ubuntu: Invalid Status in xdiagnose package in Ubuntu: Fix Released Status in cloud-init source package in Jammy: Invalid Status in dh-python source package in Jammy: Invalid Status in logdata-anomaly-miner source package in Jammy: Invalid Status in lomiri source package in Jammy: Invalid Status in mailman3 source package in Jammy: Invalid Status in matrix-sydent source package in Jammy: Invalid Status in mom source package in Jammy: Invalid Status in mopidy source package in Jammy: Invalid Status in mpd-sima source package in Jammy: Invalid Status in nordugrid-arc source package in Jammy: Invalid Status in notus-scanner source package in Jammy: Invalid Status in nrpe-ng source package in Jammy: Invalid Status in onionprobe source package in Jammy: Invalid Status in openscap-daemon source package in Jammy: Invalid Status in ospd-openvas source package in Jammy: Invalid Status in pagekite source package in Jammy: Invalid Status in pagure source package in Jammy: Invalid Status in pglistener source package in Jammy: Invalid Status in policyd-rate-limit source package in Jammy: Invalid Status in postfix-mta-sts-resolver source package in Jammy: Invalid Status in powa-collector source package in Jammy: Invalid Status in prelude-correlator source pack
[Touch-packages] [Bug 2075337] Re: [SRU] py3clean fails when using alternate character set
Re: comment #91, the new upload fixes the spacing issues, and targets the same stanza; I'll assume the binary package is correct. Thanks for the re-upload! ** Changed in: nordugrid-arc (Ubuntu Noble) Status: Incomplete => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dh-python in Ubuntu. https://bugs.launchpad.net/bugs/2075337 Title: [SRU] py3clean fails when using alternate character set Status in cloud-init package in Ubuntu: New Status in dh-python package in Ubuntu: Invalid Status in logdata-anomaly-miner package in Ubuntu: Invalid Status in lomiri package in Ubuntu: Invalid Status in mailman3 package in Ubuntu: Invalid Status in matrix-sydent package in Ubuntu: Invalid Status in mom package in Ubuntu: Invalid Status in mopidy package in Ubuntu: Invalid Status in mpd-sima package in Ubuntu: Invalid Status in nordugrid-arc package in Ubuntu: Invalid Status in notus-scanner package in Ubuntu: Invalid Status in nrpe-ng package in Ubuntu: Invalid Status in onionprobe package in Ubuntu: Invalid Status in openscap-daemon package in Ubuntu: Invalid Status in ospd-openvas package in Ubuntu: Invalid Status in pagekite package in Ubuntu: Invalid Status in pagure package in Ubuntu: Invalid Status in pglistener package in Ubuntu: Invalid Status in policyd-rate-limit package in Ubuntu: Invalid Status in postfix-mta-sts-resolver package in Ubuntu: Invalid Status in powa-collector package in Ubuntu: Invalid Status in prelude-correlator package in Ubuntu: Invalid Status in prometheus-pgbouncer-exporter package in Ubuntu: Invalid Status in prometheus-xmpp-alerts package in Ubuntu: Invalid Status in pyro5 package in Ubuntu: Incomplete Status in pyroman package in Ubuntu: Invalid Status in python3-defaults package in Ubuntu: Fix Released Status in r4d package in Ubuntu: Invalid Status in razercfg package in Ubuntu: Invalid Status in sgt-launcher package in Ubuntu: Fix Released Status in sms4you package in Ubuntu: Invalid Status in supervisor package in Ubuntu: Invalid Status in syncplay package in Ubuntu: Invalid Status in timekpr-next package in Ubuntu: Fix Released Status in twms package in Ubuntu: Invalid Status in ubuntu-advantage-tools package in Ubuntu: New Status in vanguards package in Ubuntu: Incomplete Status in vaultlocker package in Ubuntu: Invalid Status in virtualbox package in Ubuntu: Invalid Status in voctomix-outcasts package in Ubuntu: Invalid Status in weborf package in Ubuntu: Invalid Status in xdiagnose package in Ubuntu: Fix Released Status in cloud-init source package in Jammy: Invalid Status in dh-python source package in Jammy: Invalid Status in logdata-anomaly-miner source package in Jammy: Invalid Status in lomiri source package in Jammy: Invalid Status in mailman3 source package in Jammy: Invalid Status in matrix-sydent source package in Jammy: Invalid Status in mom source package in Jammy: Invalid Status in mopidy source package in Jammy: Invalid Status in mpd-sima source package in Jammy: Invalid Status in nordugrid-arc source package in Jammy: Invalid Status in notus-scanner source package in Jammy: Invalid Status in nrpe-ng source package in Jammy: Invalid Status in onionprobe source package in Jammy: Invalid Status in openscap-daemon source package in Jammy: Invalid Status in ospd-openvas source package in Jammy: Invalid Status in pagekite source package in Jammy: Invalid Status in pagure source package in Jammy: Invalid Status in pglistener source package in Jammy: Invalid Status in policyd-rate-limit source package in Jammy: Invalid Status in postfix-mta-sts-resolver source package in Jammy: Invalid Status in powa-collector source package in Jammy: Invalid Status in prelude-correlator source package in Jammy: Invalid Status in prometheus-pgbouncer-exporter source package in Jammy: Invalid Status in prometheus-xmpp-alerts source package in Jammy: Invalid Status in pyro5 source package in Jammy: Invalid Status in pyroman source package in Jammy: Invalid Status in python3-defaults source package in Jammy: Fix Released Status in r4d source package in Jammy: Invalid Status in razercfg source package in Jammy: Invalid Status in sgt-launcher source package in Jammy: New Status in sms4you source package in Jammy: Invalid Status in supervisor source package in Jammy: Invalid Status in syncplay source package in Jammy: Invalid Status in timekpr-next source package in Jammy: Invalid Status in twms source package in Jammy: Invalid Status in ubuntu-advantage-tools source package in Jammy: Invalid Status in vanguards source package in Jammy: Invalid Status in vaultlocker source package in Jammy: Invalid Status in virtualbox source package in Jammy: Invalid Status in voctomix-outcasts source package in Jammy: Invalid Status in weborf source
[Touch-packages] [Bug 2075337] Re: [SRU] py3clean fails when using alternate character set
The mpd-sima (re-upload) for Noble has Build-Depends(-Indep) changes not yet in Oracular. Could you please upload it to Oracular too? Thanks! (Sorry, I should have caught earlier.) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dh-python in Ubuntu. https://bugs.launchpad.net/bugs/2075337 Title: [SRU] py3clean fails when using alternate character set Status in cloud-init package in Ubuntu: New Status in dh-python package in Ubuntu: Invalid Status in logdata-anomaly-miner package in Ubuntu: Invalid Status in lomiri package in Ubuntu: Invalid Status in mailman3 package in Ubuntu: Invalid Status in matrix-sydent package in Ubuntu: Invalid Status in mom package in Ubuntu: Invalid Status in mopidy package in Ubuntu: Invalid Status in mpd-sima package in Ubuntu: Invalid Status in nordugrid-arc package in Ubuntu: Invalid Status in notus-scanner package in Ubuntu: Invalid Status in nrpe-ng package in Ubuntu: Invalid Status in onionprobe package in Ubuntu: Invalid Status in openscap-daemon package in Ubuntu: Invalid Status in ospd-openvas package in Ubuntu: Invalid Status in pagekite package in Ubuntu: Invalid Status in pagure package in Ubuntu: Invalid Status in pglistener package in Ubuntu: Invalid Status in policyd-rate-limit package in Ubuntu: Invalid Status in postfix-mta-sts-resolver package in Ubuntu: Invalid Status in powa-collector package in Ubuntu: Invalid Status in prelude-correlator package in Ubuntu: Invalid Status in prometheus-pgbouncer-exporter package in Ubuntu: Invalid Status in prometheus-xmpp-alerts package in Ubuntu: Invalid Status in pyro5 package in Ubuntu: Incomplete Status in pyroman package in Ubuntu: Invalid Status in python3-defaults package in Ubuntu: Fix Released Status in r4d package in Ubuntu: Invalid Status in razercfg package in Ubuntu: Invalid Status in sgt-launcher package in Ubuntu: Fix Released Status in sms4you package in Ubuntu: Invalid Status in supervisor package in Ubuntu: Invalid Status in syncplay package in Ubuntu: Invalid Status in timekpr-next package in Ubuntu: Fix Released Status in twms package in Ubuntu: Invalid Status in ubuntu-advantage-tools package in Ubuntu: New Status in vanguards package in Ubuntu: Incomplete Status in vaultlocker package in Ubuntu: Invalid Status in virtualbox package in Ubuntu: Invalid Status in voctomix-outcasts package in Ubuntu: Invalid Status in weborf package in Ubuntu: Invalid Status in xdiagnose package in Ubuntu: Fix Released Status in cloud-init source package in Jammy: Invalid Status in dh-python source package in Jammy: Invalid Status in logdata-anomaly-miner source package in Jammy: Invalid Status in lomiri source package in Jammy: Invalid Status in mailman3 source package in Jammy: Invalid Status in matrix-sydent source package in Jammy: Invalid Status in mom source package in Jammy: Invalid Status in mopidy source package in Jammy: Invalid Status in mpd-sima source package in Jammy: Invalid Status in nordugrid-arc source package in Jammy: Invalid Status in notus-scanner source package in Jammy: Invalid Status in nrpe-ng source package in Jammy: Invalid Status in onionprobe source package in Jammy: Invalid Status in openscap-daemon source package in Jammy: Invalid Status in ospd-openvas source package in Jammy: Invalid Status in pagekite source package in Jammy: Invalid Status in pagure source package in Jammy: Invalid Status in pglistener source package in Jammy: Invalid Status in policyd-rate-limit source package in Jammy: Invalid Status in postfix-mta-sts-resolver source package in Jammy: Invalid Status in powa-collector source package in Jammy: Invalid Status in prelude-correlator source package in Jammy: Invalid Status in prometheus-pgbouncer-exporter source package in Jammy: Invalid Status in prometheus-xmpp-alerts source package in Jammy: Invalid Status in pyro5 source package in Jammy: Invalid Status in pyroman source package in Jammy: Invalid Status in python3-defaults source package in Jammy: Fix Released Status in r4d source package in Jammy: Invalid Status in razercfg source package in Jammy: Invalid Status in sgt-launcher source package in Jammy: New Status in sms4you source package in Jammy: Invalid Status in supervisor source package in Jammy: Invalid Status in syncplay source package in Jammy: Invalid Status in timekpr-next source package in Jammy: Invalid Status in twms source package in Jammy: Invalid Status in ubuntu-advantage-tools source package in Jammy: Invalid Status in vanguards source package in Jammy: Invalid Status in vaultlocker source package in Jammy: Invalid Status in virtualbox source package in Jammy: Invalid Status in voctomix-outcasts source package in Jammy: Invalid Status in weborf source package in Jammy: Invalid Status in xdiagnose source packag
[Touch-packages] [Bug 2075337] Re: [SRU] py3clean fails when using alternate character set
Apologies, I accepted pyro5 into Noble with the Build-Depends(-Indep) change not yet in Oracular. Could you please upload it to Oracular too? Thanks! ** Changed in: pyro5 (Ubuntu) Status: Invalid => Incomplete ** Changed in: pyro5 (Ubuntu) Assignee: (unassigned) => Dave Jones (waveform) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dh-python in Ubuntu. https://bugs.launchpad.net/bugs/2075337 Title: [SRU] py3clean fails when using alternate character set Status in cloud-init package in Ubuntu: New Status in dh-python package in Ubuntu: Invalid Status in logdata-anomaly-miner package in Ubuntu: Invalid Status in lomiri package in Ubuntu: Invalid Status in mailman3 package in Ubuntu: Invalid Status in matrix-sydent package in Ubuntu: Invalid Status in mom package in Ubuntu: Invalid Status in mopidy package in Ubuntu: Invalid Status in mpd-sima package in Ubuntu: Invalid Status in nordugrid-arc package in Ubuntu: Invalid Status in notus-scanner package in Ubuntu: Invalid Status in nrpe-ng package in Ubuntu: Invalid Status in onionprobe package in Ubuntu: Invalid Status in openscap-daemon package in Ubuntu: Invalid Status in ospd-openvas package in Ubuntu: Invalid Status in pagekite package in Ubuntu: Invalid Status in pagure package in Ubuntu: Invalid Status in pglistener package in Ubuntu: Invalid Status in policyd-rate-limit package in Ubuntu: Invalid Status in postfix-mta-sts-resolver package in Ubuntu: Invalid Status in powa-collector package in Ubuntu: Invalid Status in prelude-correlator package in Ubuntu: Invalid Status in prometheus-pgbouncer-exporter package in Ubuntu: Invalid Status in prometheus-xmpp-alerts package in Ubuntu: Invalid Status in pyro5 package in Ubuntu: Incomplete Status in pyroman package in Ubuntu: Invalid Status in python3-defaults package in Ubuntu: Fix Released Status in r4d package in Ubuntu: Invalid Status in razercfg package in Ubuntu: Invalid Status in sgt-launcher package in Ubuntu: Fix Released Status in sms4you package in Ubuntu: Invalid Status in supervisor package in Ubuntu: Invalid Status in syncplay package in Ubuntu: Invalid Status in timekpr-next package in Ubuntu: Fix Released Status in twms package in Ubuntu: Invalid Status in ubuntu-advantage-tools package in Ubuntu: New Status in vanguards package in Ubuntu: Incomplete Status in vaultlocker package in Ubuntu: Invalid Status in virtualbox package in Ubuntu: Invalid Status in voctomix-outcasts package in Ubuntu: Invalid Status in weborf package in Ubuntu: Invalid Status in xdiagnose package in Ubuntu: Fix Released Status in cloud-init source package in Jammy: Invalid Status in dh-python source package in Jammy: Invalid Status in logdata-anomaly-miner source package in Jammy: Invalid Status in lomiri source package in Jammy: Invalid Status in mailman3 source package in Jammy: Invalid Status in matrix-sydent source package in Jammy: Invalid Status in mom source package in Jammy: Invalid Status in mopidy source package in Jammy: Invalid Status in mpd-sima source package in Jammy: Invalid Status in nordugrid-arc source package in Jammy: Invalid Status in notus-scanner source package in Jammy: Invalid Status in nrpe-ng source package in Jammy: Invalid Status in onionprobe source package in Jammy: Invalid Status in openscap-daemon source package in Jammy: Invalid Status in ospd-openvas source package in Jammy: Invalid Status in pagekite source package in Jammy: Invalid Status in pagure source package in Jammy: Invalid Status in pglistener source package in Jammy: Invalid Status in policyd-rate-limit source package in Jammy: Invalid Status in postfix-mta-sts-resolver source package in Jammy: Invalid Status in powa-collector source package in Jammy: Invalid Status in prelude-correlator source package in Jammy: Invalid Status in prometheus-pgbouncer-exporter source package in Jammy: Invalid Status in prometheus-xmpp-alerts source package in Jammy: Invalid Status in pyro5 source package in Jammy: Invalid Status in pyroman source package in Jammy: Invalid Status in python3-defaults source package in Jammy: Fix Released Status in r4d source package in Jammy: Invalid Status in razercfg source package in Jammy: Invalid Status in sgt-launcher source package in Jammy: New Status in sms4you source package in Jammy: Invalid Status in supervisor source package in Jammy: Invalid Status in syncplay source package in Jammy: Invalid Status in timekpr-next source package in Jammy: Invalid Status in twms source package in Jammy: Invalid Status in ubuntu-advantage-tools source package in Jammy: Invalid Status in vanguards source package in Jammy: Invalid Status in vaultlocker source package in Jammy: Invalid Status in virtualbox source package in Jammy: Invalid Status in voctomix-outcasts
[Touch-packages] [Bug 2075337] Re: [SRU] py3clean fails when using alternate character set
^ The same for pagekite; caught before accepting. (Thanks for fixing up d/changelog, and re-uploading!) ** Changed in: openscap-daemon (Ubuntu Noble) Status: Incomplete => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dh-python in Ubuntu. https://bugs.launchpad.net/bugs/2075337 Title: [SRU] py3clean fails when using alternate character set Status in cloud-init package in Ubuntu: New Status in dh-python package in Ubuntu: Invalid Status in logdata-anomaly-miner package in Ubuntu: Invalid Status in lomiri package in Ubuntu: Invalid Status in mailman3 package in Ubuntu: Invalid Status in matrix-sydent package in Ubuntu: Invalid Status in mom package in Ubuntu: Invalid Status in mopidy package in Ubuntu: Invalid Status in mpd-sima package in Ubuntu: Invalid Status in nordugrid-arc package in Ubuntu: Invalid Status in notus-scanner package in Ubuntu: Invalid Status in nrpe-ng package in Ubuntu: Invalid Status in onionprobe package in Ubuntu: Invalid Status in openscap-daemon package in Ubuntu: Invalid Status in ospd-openvas package in Ubuntu: Invalid Status in pagekite package in Ubuntu: Invalid Status in pagure package in Ubuntu: Invalid Status in pglistener package in Ubuntu: Invalid Status in policyd-rate-limit package in Ubuntu: Invalid Status in postfix-mta-sts-resolver package in Ubuntu: Invalid Status in powa-collector package in Ubuntu: Invalid Status in prelude-correlator package in Ubuntu: Invalid Status in prometheus-pgbouncer-exporter package in Ubuntu: Invalid Status in prometheus-xmpp-alerts package in Ubuntu: Invalid Status in pyro5 package in Ubuntu: Incomplete Status in pyroman package in Ubuntu: Invalid Status in python3-defaults package in Ubuntu: Fix Released Status in r4d package in Ubuntu: Invalid Status in razercfg package in Ubuntu: Invalid Status in sgt-launcher package in Ubuntu: Fix Released Status in sms4you package in Ubuntu: Invalid Status in supervisor package in Ubuntu: Invalid Status in syncplay package in Ubuntu: Invalid Status in timekpr-next package in Ubuntu: Fix Released Status in twms package in Ubuntu: Invalid Status in ubuntu-advantage-tools package in Ubuntu: New Status in vanguards package in Ubuntu: Incomplete Status in vaultlocker package in Ubuntu: Invalid Status in virtualbox package in Ubuntu: Invalid Status in voctomix-outcasts package in Ubuntu: Invalid Status in weborf package in Ubuntu: Invalid Status in xdiagnose package in Ubuntu: Fix Released Status in cloud-init source package in Jammy: Invalid Status in dh-python source package in Jammy: Invalid Status in logdata-anomaly-miner source package in Jammy: Invalid Status in lomiri source package in Jammy: Invalid Status in mailman3 source package in Jammy: Invalid Status in matrix-sydent source package in Jammy: Invalid Status in mom source package in Jammy: Invalid Status in mopidy source package in Jammy: Invalid Status in mpd-sima source package in Jammy: Invalid Status in nordugrid-arc source package in Jammy: Invalid Status in notus-scanner source package in Jammy: Invalid Status in nrpe-ng source package in Jammy: Invalid Status in onionprobe source package in Jammy: Invalid Status in openscap-daemon source package in Jammy: Invalid Status in ospd-openvas source package in Jammy: Invalid Status in pagekite source package in Jammy: Invalid Status in pagure source package in Jammy: Invalid Status in pglistener source package in Jammy: Invalid Status in policyd-rate-limit source package in Jammy: Invalid Status in postfix-mta-sts-resolver source package in Jammy: Invalid Status in powa-collector source package in Jammy: Invalid Status in prelude-correlator source package in Jammy: Invalid Status in prometheus-pgbouncer-exporter source package in Jammy: Invalid Status in prometheus-xmpp-alerts source package in Jammy: Invalid Status in pyro5 source package in Jammy: Invalid Status in pyroman source package in Jammy: Invalid Status in python3-defaults source package in Jammy: Fix Released Status in r4d source package in Jammy: Invalid Status in razercfg source package in Jammy: Invalid Status in sgt-launcher source package in Jammy: New Status in sms4you source package in Jammy: Invalid Status in supervisor source package in Jammy: Invalid Status in syncplay source package in Jammy: Invalid Status in timekpr-next source package in Jammy: Invalid Status in twms source package in Jammy: Invalid Status in ubuntu-advantage-tools source package in Jammy: Invalid Status in vanguards source package in Jammy: Invalid Status in vaultlocker source package in Jammy: Invalid Status in virtualbox source package in Jammy: Invalid Status in voctomix-outcasts source package in Jammy: Invalid Status in weborf source package in Jammy: Invalid Status in xdiagnose so
[Touch-packages] [Bug 2075337] Please test proposed package
Hello Robie, or anyone else affected, Accepted openscap-daemon into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/openscap- daemon/0.1.10-3.1ubuntu3.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-noble. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dh-python in Ubuntu. https://bugs.launchpad.net/bugs/2075337 Title: [SRU] py3clean fails when using alternate character set Status in cloud-init package in Ubuntu: New Status in dh-python package in Ubuntu: Invalid Status in logdata-anomaly-miner package in Ubuntu: Invalid Status in lomiri package in Ubuntu: Invalid Status in mailman3 package in Ubuntu: Invalid Status in matrix-sydent package in Ubuntu: Invalid Status in mom package in Ubuntu: Invalid Status in mopidy package in Ubuntu: Invalid Status in mpd-sima package in Ubuntu: Invalid Status in nordugrid-arc package in Ubuntu: Invalid Status in notus-scanner package in Ubuntu: Invalid Status in nrpe-ng package in Ubuntu: Invalid Status in onionprobe package in Ubuntu: Invalid Status in openscap-daemon package in Ubuntu: Invalid Status in ospd-openvas package in Ubuntu: Invalid Status in pagekite package in Ubuntu: Invalid Status in pagure package in Ubuntu: Invalid Status in pglistener package in Ubuntu: Invalid Status in policyd-rate-limit package in Ubuntu: Invalid Status in postfix-mta-sts-resolver package in Ubuntu: Invalid Status in powa-collector package in Ubuntu: Invalid Status in prelude-correlator package in Ubuntu: Invalid Status in prometheus-pgbouncer-exporter package in Ubuntu: Invalid Status in prometheus-xmpp-alerts package in Ubuntu: Invalid Status in pyro5 package in Ubuntu: Incomplete Status in pyroman package in Ubuntu: Invalid Status in python3-defaults package in Ubuntu: Fix Released Status in r4d package in Ubuntu: Invalid Status in razercfg package in Ubuntu: Invalid Status in sgt-launcher package in Ubuntu: Fix Released Status in sms4you package in Ubuntu: Invalid Status in supervisor package in Ubuntu: Invalid Status in syncplay package in Ubuntu: Invalid Status in timekpr-next package in Ubuntu: Fix Released Status in twms package in Ubuntu: Invalid Status in ubuntu-advantage-tools package in Ubuntu: New Status in vanguards package in Ubuntu: Incomplete Status in vaultlocker package in Ubuntu: Invalid Status in virtualbox package in Ubuntu: Invalid Status in voctomix-outcasts package in Ubuntu: Invalid Status in weborf package in Ubuntu: Invalid Status in xdiagnose package in Ubuntu: Fix Released Status in cloud-init source package in Jammy: Invalid Status in dh-python source package in Jammy: Invalid Status in logdata-anomaly-miner source package in Jammy: Invalid Status in lomiri source package in Jammy: Invalid Status in mailman3 source package in Jammy: Invalid Status in matrix-sydent source package in Jammy: Invalid Status in mom source package in Jammy: Invalid Status in mopidy source package in Jammy: Invalid Status in mpd-sima source package in Jammy: Invalid Status in nordugrid-arc source package in Jammy: Invalid Status in notus-scanner source package in Jammy: Invalid Status in nrpe-ng source package in Jammy: Invalid Status in onionprobe source package in Jammy: Invalid Status in openscap-daemon source package in Jammy: Invalid Status in ospd-openvas source package in Jammy: Invalid Status in pagekite source package in Jammy: Invalid Status in pagure source package in Jammy: Invalid Status in pglistener source package in Jammy: Invalid Status in policyd-rate-limit source package in Jammy: Invalid Status in postfix-mta-sts-resolver source package in Jammy: Invalid Status in powa-collector source package in Jammy: Invalid Status in prelude-correlator source package in Jammy: Invalid Status in prometheus-pgbouncer-
[Touch-packages] [Bug 2075337] Please test proposed package
Hello Robie, or anyone else affected, Accepted nordugrid-arc into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/nordugrid- arc/6.18.0-2.2ubuntu0.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-noble. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dh-python in Ubuntu. https://bugs.launchpad.net/bugs/2075337 Title: [SRU] py3clean fails when using alternate character set Status in cloud-init package in Ubuntu: New Status in dh-python package in Ubuntu: Invalid Status in logdata-anomaly-miner package in Ubuntu: Invalid Status in lomiri package in Ubuntu: Invalid Status in mailman3 package in Ubuntu: Invalid Status in matrix-sydent package in Ubuntu: Invalid Status in mom package in Ubuntu: Invalid Status in mopidy package in Ubuntu: Invalid Status in mpd-sima package in Ubuntu: Invalid Status in nordugrid-arc package in Ubuntu: Invalid Status in notus-scanner package in Ubuntu: Invalid Status in nrpe-ng package in Ubuntu: Invalid Status in onionprobe package in Ubuntu: Invalid Status in openscap-daemon package in Ubuntu: Invalid Status in ospd-openvas package in Ubuntu: Invalid Status in pagekite package in Ubuntu: Invalid Status in pagure package in Ubuntu: Invalid Status in pglistener package in Ubuntu: Invalid Status in policyd-rate-limit package in Ubuntu: Invalid Status in postfix-mta-sts-resolver package in Ubuntu: Invalid Status in powa-collector package in Ubuntu: Invalid Status in prelude-correlator package in Ubuntu: Invalid Status in prometheus-pgbouncer-exporter package in Ubuntu: Invalid Status in prometheus-xmpp-alerts package in Ubuntu: Invalid Status in pyro5 package in Ubuntu: Incomplete Status in pyroman package in Ubuntu: Invalid Status in python3-defaults package in Ubuntu: Fix Released Status in r4d package in Ubuntu: Invalid Status in razercfg package in Ubuntu: Invalid Status in sgt-launcher package in Ubuntu: Fix Released Status in sms4you package in Ubuntu: Invalid Status in supervisor package in Ubuntu: Invalid Status in syncplay package in Ubuntu: Invalid Status in timekpr-next package in Ubuntu: Fix Released Status in twms package in Ubuntu: Invalid Status in ubuntu-advantage-tools package in Ubuntu: New Status in vanguards package in Ubuntu: Incomplete Status in vaultlocker package in Ubuntu: Invalid Status in virtualbox package in Ubuntu: Invalid Status in voctomix-outcasts package in Ubuntu: Invalid Status in weborf package in Ubuntu: Invalid Status in xdiagnose package in Ubuntu: Fix Released Status in cloud-init source package in Jammy: Invalid Status in dh-python source package in Jammy: Invalid Status in logdata-anomaly-miner source package in Jammy: Invalid Status in lomiri source package in Jammy: Invalid Status in mailman3 source package in Jammy: Invalid Status in matrix-sydent source package in Jammy: Invalid Status in mom source package in Jammy: Invalid Status in mopidy source package in Jammy: Invalid Status in mpd-sima source package in Jammy: Invalid Status in nordugrid-arc source package in Jammy: Invalid Status in notus-scanner source package in Jammy: Invalid Status in nrpe-ng source package in Jammy: Invalid Status in onionprobe source package in Jammy: Invalid Status in openscap-daemon source package in Jammy: Invalid Status in ospd-openvas source package in Jammy: Invalid Status in pagekite source package in Jammy: Invalid Status in pagure source package in Jammy: Invalid Status in pglistener source package in Jammy: Invalid Status in policyd-rate-limit source package in Jammy: Invalid Status in postfix-mta-sts-resolver source package in Jammy: Invalid Status in powa-collector source package in Jammy: Invalid Status in prelude-correlator source package in Jammy: Invalid Status in prometheus-pgbouncer-expo
[Touch-packages] [Bug 2075337] Re: [SRU] py3clean fails when using alternate character set
Hello Robie, or anyone else affected, Accepted vanguards into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/vanguards/0.3.1-2.3ubuntu0.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-noble. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: vanguards (Ubuntu Noble) Status: Incomplete => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dh-python in Ubuntu. https://bugs.launchpad.net/bugs/2075337 Title: [SRU] py3clean fails when using alternate character set Status in cloud-init package in Ubuntu: New Status in dh-python package in Ubuntu: Invalid Status in logdata-anomaly-miner package in Ubuntu: Invalid Status in lomiri package in Ubuntu: Invalid Status in mailman3 package in Ubuntu: Invalid Status in matrix-sydent package in Ubuntu: Invalid Status in mom package in Ubuntu: Invalid Status in mopidy package in Ubuntu: Invalid Status in mpd-sima package in Ubuntu: Invalid Status in nordugrid-arc package in Ubuntu: Invalid Status in notus-scanner package in Ubuntu: Invalid Status in nrpe-ng package in Ubuntu: Invalid Status in onionprobe package in Ubuntu: Invalid Status in openscap-daemon package in Ubuntu: Invalid Status in ospd-openvas package in Ubuntu: Invalid Status in pagekite package in Ubuntu: Invalid Status in pagure package in Ubuntu: Invalid Status in pglistener package in Ubuntu: Invalid Status in policyd-rate-limit package in Ubuntu: Invalid Status in postfix-mta-sts-resolver package in Ubuntu: Invalid Status in powa-collector package in Ubuntu: Invalid Status in prelude-correlator package in Ubuntu: Invalid Status in prometheus-pgbouncer-exporter package in Ubuntu: Invalid Status in prometheus-xmpp-alerts package in Ubuntu: Invalid Status in pyro5 package in Ubuntu: Incomplete Status in pyroman package in Ubuntu: Invalid Status in python3-defaults package in Ubuntu: Fix Released Status in r4d package in Ubuntu: Invalid Status in razercfg package in Ubuntu: Invalid Status in sgt-launcher package in Ubuntu: Fix Released Status in sms4you package in Ubuntu: Invalid Status in supervisor package in Ubuntu: Invalid Status in syncplay package in Ubuntu: Invalid Status in timekpr-next package in Ubuntu: Fix Released Status in twms package in Ubuntu: Invalid Status in ubuntu-advantage-tools package in Ubuntu: New Status in vanguards package in Ubuntu: Incomplete Status in vaultlocker package in Ubuntu: Invalid Status in virtualbox package in Ubuntu: Invalid Status in voctomix-outcasts package in Ubuntu: Invalid Status in weborf package in Ubuntu: Invalid Status in xdiagnose package in Ubuntu: Fix Released Status in cloud-init source package in Jammy: Invalid Status in dh-python source package in Jammy: Invalid Status in logdata-anomaly-miner source package in Jammy: Invalid Status in lomiri source package in Jammy: Invalid Status in mailman3 source package in Jammy: Invalid Status in matrix-sydent source package in Jammy: Invalid Status in mom source package in Jammy: Invalid Status in mopidy source package in Jammy: Invalid Status in mpd-sima source package in Jammy: Invalid Status in nordugrid-arc source package in Jammy: Invalid Status in notus-scanner source package in Jammy: Invalid Status in nrpe-ng source package in Jammy: Invalid Status in onionprobe source package in Jammy: Invalid Status in openscap-daemon source package in Jammy: Invalid Status in ospd-openvas source package in Jammy: Invalid Status in pagekite source package in Jammy: Invalid Status in pagure source package in Jammy: Invalid Status in pglistener source package in Jammy: Invalid Status in policyd-rate-limit source package in Jammy: Invalid Status in postfix-mta-sts-resolver source package in Jammy: Invalid Status in powa-collector source package in Jammy: Invalid Status in prelude-correla
[Touch-packages] [Bug 2075337] Re: [SRU] py3clean fails when using alternate character set
Hello Robie, or anyone else affected, Accepted voctomix-outcasts into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/voctomix- outcasts/1.0.0-1ubuntu0.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-noble. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Also affects: voctomix-outcasts (Ubuntu) Importance: Undecided Status: New ** Changed in: voctomix-outcasts (Ubuntu) Status: New => Invalid ** Changed in: voctomix-outcasts (Ubuntu Jammy) Status: New => Invalid ** Changed in: voctomix-outcasts (Ubuntu Noble) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dh-python in Ubuntu. https://bugs.launchpad.net/bugs/2075337 Title: [SRU] py3clean fails when using alternate character set Status in cloud-init package in Ubuntu: New Status in dh-python package in Ubuntu: Invalid Status in python3-defaults package in Ubuntu: Fix Released Status in ubuntu-advantage-tools package in Ubuntu: New Status in voctomix-outcasts package in Ubuntu: Invalid Status in weborf package in Ubuntu: Invalid Status in xdiagnose package in Ubuntu: Fix Committed Status in cloud-init source package in Jammy: Invalid Status in dh-python source package in Jammy: Invalid Status in python3-defaults source package in Jammy: Fix Released Status in ubuntu-advantage-tools source package in Jammy: Invalid Status in voctomix-outcasts source package in Jammy: Invalid Status in weborf source package in Jammy: Invalid Status in xdiagnose source package in Jammy: Invalid Status in cloud-init source package in Noble: Fix Released Status in dh-python source package in Noble: Invalid Status in python3-defaults source package in Noble: Fix Released Status in ubuntu-advantage-tools source package in Noble: Fix Released Status in voctomix-outcasts source package in Noble: Fix Committed Status in weborf source package in Noble: Fix Committed Status in xdiagnose source package in Noble: Fix Committed Bug description: [ Impact ] With the current version of python3-defaults in jammy and noble, packages which utilize py3compile and py3clean in their maintscripts (which is more or less any package which includes Python modules), and which also are affected by diversions installed by dpkg-divert, will fail to install/upgrade/remove on systems with non-UTF-8 locales, which include non-ASCII characters in their localized dpkg -L messages (and which therefore produce output that is not valid UTF-8). As this has the potential to break apt upgrade, the impact is quite severe (especially if this occurs during a dist-upgrade). However, the scope is probably *fairly* limited given this only affects systems with non-UTF-8 locales (something that has not been the default for many years), and which produce non-ASCII output (e.g. French characters with diacriticals) in their localized messages for dpkg -L. [ Rectification Plan ] Firstly, python3-defaults must be patched in oracular, noble, and jammy. doko has uploaded the fix upstream and synced this to oracular. Benjamin has sponsored the noble and jammy SRUs. Next, affected packages must be patched to include a "Breaks" line on earlier versions of python3-minimal (the python3-defaults binary package containing py3clean and py3compile). Packages which install Python modules are easily selected, but those affected by diversions are (computationally) impossible to select (see comment 18 for details). Thus, determining the set of affected packages was non-trivial, but Benjamin has kindly produced such a list by empirical means (see comment 24). These will be added to the ticket as they are uploaded. [ Known affected packages ] ``` $ for section in main restricted universe multiverse; do echo "noble $section:"; sqlite3 affected.sqlite3 "SELECT package, source FROM package_affe
[Touch-packages] [Bug 2075337] Re: [SRU] py3clean fails when using alternate character set
Hello Robie, or anyone else affected, Accepted weborf into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/weborf/1.0-1ubuntu0.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-noble. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Also affects: weborf (Ubuntu) Importance: Undecided Status: New ** Changed in: weborf (Ubuntu) Status: New => Invalid ** Changed in: weborf (Ubuntu Jammy) Status: New => Invalid ** Changed in: weborf (Ubuntu Noble) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dh-python in Ubuntu. https://bugs.launchpad.net/bugs/2075337 Title: [SRU] py3clean fails when using alternate character set Status in cloud-init package in Ubuntu: New Status in dh-python package in Ubuntu: Invalid Status in python3-defaults package in Ubuntu: Fix Released Status in ubuntu-advantage-tools package in Ubuntu: New Status in weborf package in Ubuntu: Invalid Status in xdiagnose package in Ubuntu: Fix Committed Status in cloud-init source package in Jammy: Invalid Status in dh-python source package in Jammy: Invalid Status in python3-defaults source package in Jammy: Fix Released Status in ubuntu-advantage-tools source package in Jammy: Invalid Status in weborf source package in Jammy: Invalid Status in xdiagnose source package in Jammy: Invalid Status in cloud-init source package in Noble: Fix Released Status in dh-python source package in Noble: Invalid Status in python3-defaults source package in Noble: Fix Released Status in ubuntu-advantage-tools source package in Noble: Fix Released Status in weborf source package in Noble: Fix Committed Status in xdiagnose source package in Noble: Fix Committed Bug description: [ Impact ] With the current version of python3-defaults in jammy and noble, packages which utilize py3compile and py3clean in their maintscripts (which is more or less any package which includes Python modules), and which also are affected by diversions installed by dpkg-divert, will fail to install/upgrade/remove on systems with non-UTF-8 locales, which include non-ASCII characters in their localized dpkg -L messages (and which therefore produce output that is not valid UTF-8). As this has the potential to break apt upgrade, the impact is quite severe (especially if this occurs during a dist-upgrade). However, the scope is probably *fairly* limited given this only affects systems with non-UTF-8 locales (something that has not been the default for many years), and which produce non-ASCII output (e.g. French characters with diacriticals) in their localized messages for dpkg -L. [ Rectification Plan ] Firstly, python3-defaults must be patched in oracular, noble, and jammy. doko has uploaded the fix upstream and synced this to oracular. Benjamin has sponsored the noble and jammy SRUs. Next, affected packages must be patched to include a "Breaks" line on earlier versions of python3-minimal (the python3-defaults binary package containing py3clean and py3compile). Packages which install Python modules are easily selected, but those affected by diversions are (computationally) impossible to select (see comment 18 for details). Thus, determining the set of affected packages was non-trivial, but Benjamin has kindly produced such a list by empirical means (see comment 24). These will be added to the ticket as they are uploaded. [ Known affected packages ] ``` $ for section in main restricted universe multiverse; do echo "noble $section:"; sqlite3 affected.sqlite3 "SELECT package, source FROM package_affected WHERE section = '$section' and install_affected = 1 AND (remove_affected = 1 OR remove_affected ISNULL) ORDER BY package;"; echo; done noble main: cloud-init|cloud-init nvme-stas|nvme-stas python3-rtslib-fb|python-rtslib-fb targetcli-fb|targe
[Touch-packages] [Bug 2075337] Re: [SRU] py3clean fails when using alternate character set
Hello Robie, or anyone else affected, Accepted xdiagnose into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/xdiagnose/3.8.10ubuntu0.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-noble. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Tags removed: verification-done verification-done-noble ** Tags added: verification-needed verification-needed-noble ** Also affects: xdiagnose (Ubuntu) Importance: Undecided Status: New ** Changed in: xdiagnose (Ubuntu) Status: New => Fix Committed ** Changed in: xdiagnose (Ubuntu Noble) Status: New => Fix Committed ** Changed in: xdiagnose (Ubuntu Jammy) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dh-python in Ubuntu. https://bugs.launchpad.net/bugs/2075337 Title: [SRU] py3clean fails when using alternate character set Status in cloud-init package in Ubuntu: New Status in dh-python package in Ubuntu: Invalid Status in python3-defaults package in Ubuntu: Fix Released Status in ubuntu-advantage-tools package in Ubuntu: New Status in weborf package in Ubuntu: Invalid Status in xdiagnose package in Ubuntu: Fix Committed Status in cloud-init source package in Jammy: Invalid Status in dh-python source package in Jammy: Invalid Status in python3-defaults source package in Jammy: Fix Released Status in ubuntu-advantage-tools source package in Jammy: Invalid Status in weborf source package in Jammy: Invalid Status in xdiagnose source package in Jammy: Invalid Status in cloud-init source package in Noble: Fix Released Status in dh-python source package in Noble: Invalid Status in python3-defaults source package in Noble: Fix Released Status in ubuntu-advantage-tools source package in Noble: Fix Released Status in weborf source package in Noble: Fix Committed Status in xdiagnose source package in Noble: Fix Committed Bug description: [ Impact ] With the current version of python3-defaults in jammy and noble, packages which utilize py3compile and py3clean in their maintscripts (which is more or less any package which includes Python modules), and which also are affected by diversions installed by dpkg-divert, will fail to install/upgrade/remove on systems with non-UTF-8 locales, which include non-ASCII characters in their localized dpkg -L messages (and which therefore produce output that is not valid UTF-8). As this has the potential to break apt upgrade, the impact is quite severe (especially if this occurs during a dist-upgrade). However, the scope is probably *fairly* limited given this only affects systems with non-UTF-8 locales (something that has not been the default for many years), and which produce non-ASCII output (e.g. French characters with diacriticals) in their localized messages for dpkg -L. [ Rectification Plan ] Firstly, python3-defaults must be patched in oracular, noble, and jammy. doko has uploaded the fix upstream and synced this to oracular. Benjamin has sponsored the noble and jammy SRUs. Next, affected packages must be patched to include a "Breaks" line on earlier versions of python3-minimal (the python3-defaults binary package containing py3clean and py3compile). Packages which install Python modules are easily selected, but those affected by diversions are (computationally) impossible to select (see comment 18 for details). Thus, determining the set of affected packages was non-trivial, but Benjamin has kindly produced such a list by empirical means (see comment 24). These will be added to the ticket as they are uploaded. [ Known affected packages ] ``` $ for section in main restricted universe multiverse; do echo "noble $section:"; sqlite3 affected.sqlite3 "SELECT package, source FROM package_affected WHERE section = '$section' and install_affected = 1 AND (remove_affected = 1 OR remove_affected ISNULL) OR
[Touch-packages] [Bug 2075337] Re: [SRU] py3clean fails when using alternate character set
Hello Robie, or anyone else affected, Accepted vaultlocker into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/vaultlocker/1.0.6-0ubuntu1.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-noble. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Also affects: vaultlocker (Ubuntu) Importance: Undecided Status: New ** Changed in: vaultlocker (Ubuntu Noble) Status: New => Fix Committed ** Changed in: vaultlocker (Ubuntu Jammy) Status: New => Invalid ** Changed in: vaultlocker (Ubuntu) Status: New => Invalid ** Also affects: virtualbox (Ubuntu) Importance: Undecided Status: New ** Changed in: virtualbox (Ubuntu) Status: New => Invalid ** Changed in: virtualbox (Ubuntu Jammy) Status: New => Invalid ** Changed in: virtualbox (Ubuntu Noble) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dh-python in Ubuntu. https://bugs.launchpad.net/bugs/2075337 Title: [SRU] py3clean fails when using alternate character set Status in cloud-init package in Ubuntu: New Status in dh-python package in Ubuntu: Invalid Status in python3-defaults package in Ubuntu: Fix Released Status in ubuntu-advantage-tools package in Ubuntu: New Status in vaultlocker package in Ubuntu: Invalid Status in virtualbox package in Ubuntu: Invalid Status in voctomix-outcasts package in Ubuntu: Invalid Status in weborf package in Ubuntu: Invalid Status in xdiagnose package in Ubuntu: Fix Released Status in cloud-init source package in Jammy: Invalid Status in dh-python source package in Jammy: Invalid Status in python3-defaults source package in Jammy: Fix Released Status in ubuntu-advantage-tools source package in Jammy: Invalid Status in vaultlocker source package in Jammy: Invalid Status in virtualbox source package in Jammy: Invalid Status in voctomix-outcasts source package in Jammy: Invalid Status in weborf source package in Jammy: Invalid Status in xdiagnose source package in Jammy: Invalid Status in cloud-init source package in Noble: Fix Released Status in dh-python source package in Noble: Invalid Status in python3-defaults source package in Noble: Fix Released Status in ubuntu-advantage-tools source package in Noble: Fix Released Status in vaultlocker source package in Noble: Fix Committed Status in virtualbox source package in Noble: Fix Committed Status in voctomix-outcasts source package in Noble: Fix Committed Status in weborf source package in Noble: Fix Committed Status in xdiagnose source package in Noble: Fix Committed Bug description: [ Impact ] With the current version of python3-defaults in jammy and noble, packages which utilize py3compile and py3clean in their maintscripts (which is more or less any package which includes Python modules), and which also are affected by diversions installed by dpkg-divert, will fail to install/upgrade/remove on systems with non-UTF-8 locales, which include non-ASCII characters in their localized dpkg -L messages (and which therefore produce output that is not valid UTF-8). As this has the potential to break apt upgrade, the impact is quite severe (especially if this occurs during a dist-upgrade). However, the scope is probably *fairly* limited given this only affects systems with non-UTF-8 locales (something that has not been the default for many years), and which produce non-ASCII output (e.g. French characters with diacriticals) in their localized messages for dpkg -L. [ Rectification Plan ] Firstly, python3-defaults must be patched in oracular, noble, and jammy. doko has uploaded the fix upstream and synced this to oracular. Benjamin has sponsored the noble and jammy SRUs. Next, affected packages must be patched to include a "Breaks" line on earlier versions of python3-minimal (the python3-defaults binary package contain
[Touch-packages] [Bug 2075337] Please test proposed package
Hello Robie, or anyone else affected, Accepted virtualbox into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/virtualbox/7.0.16-dfsg-2ubuntu1.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-noble. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dh-python in Ubuntu. https://bugs.launchpad.net/bugs/2075337 Title: [SRU] py3clean fails when using alternate character set Status in cloud-init package in Ubuntu: New Status in dh-python package in Ubuntu: Invalid Status in python3-defaults package in Ubuntu: Fix Released Status in ubuntu-advantage-tools package in Ubuntu: New Status in vaultlocker package in Ubuntu: Invalid Status in virtualbox package in Ubuntu: Invalid Status in voctomix-outcasts package in Ubuntu: Invalid Status in weborf package in Ubuntu: Invalid Status in xdiagnose package in Ubuntu: Fix Released Status in cloud-init source package in Jammy: Invalid Status in dh-python source package in Jammy: Invalid Status in python3-defaults source package in Jammy: Fix Released Status in ubuntu-advantage-tools source package in Jammy: Invalid Status in vaultlocker source package in Jammy: Invalid Status in virtualbox source package in Jammy: Invalid Status in voctomix-outcasts source package in Jammy: Invalid Status in weborf source package in Jammy: Invalid Status in xdiagnose source package in Jammy: Invalid Status in cloud-init source package in Noble: Fix Released Status in dh-python source package in Noble: Invalid Status in python3-defaults source package in Noble: Fix Released Status in ubuntu-advantage-tools source package in Noble: Fix Released Status in vaultlocker source package in Noble: Fix Committed Status in virtualbox source package in Noble: Fix Committed Status in voctomix-outcasts source package in Noble: Fix Committed Status in weborf source package in Noble: Fix Committed Status in xdiagnose source package in Noble: Fix Committed Bug description: [ Impact ] With the current version of python3-defaults in jammy and noble, packages which utilize py3compile and py3clean in their maintscripts (which is more or less any package which includes Python modules), and which also are affected by diversions installed by dpkg-divert, will fail to install/upgrade/remove on systems with non-UTF-8 locales, which include non-ASCII characters in their localized dpkg -L messages (and which therefore produce output that is not valid UTF-8). As this has the potential to break apt upgrade, the impact is quite severe (especially if this occurs during a dist-upgrade). However, the scope is probably *fairly* limited given this only affects systems with non-UTF-8 locales (something that has not been the default for many years), and which produce non-ASCII output (e.g. French characters with diacriticals) in their localized messages for dpkg -L. [ Rectification Plan ] Firstly, python3-defaults must be patched in oracular, noble, and jammy. doko has uploaded the fix upstream and synced this to oracular. Benjamin has sponsored the noble and jammy SRUs. Next, affected packages must be patched to include a "Breaks" line on earlier versions of python3-minimal (the python3-defaults binary package containing py3clean and py3compile). Packages which install Python modules are easily selected, but those affected by diversions are (computationally) impossible to select (see comment 18 for details). Thus, determining the set of affected packages was non-trivial, but Benjamin has kindly produced such a list by empirical means (see comment 24). These will be added to the ticket as they are uploaded. [ Known affected packages ] ``` $ for section in main restricted universe multiverse; do echo "noble $section:"; sqlite3 affected.sqlite3 "SELECT package, source FROM package_a
[Touch-packages] [Bug 2075337] Re: [SRU] py3clean fails when using alternate character set
vanguard's noble debdiff has py3.12 enablement (needs separate SRU LP bug), which is needed in oracular too (FTBFS). ** Also affects: vanguards (Ubuntu) Importance: Undecided Status: New ** Changed in: vanguards (Ubuntu Jammy) Status: New => Invalid ** Changed in: vanguards (Ubuntu Noble) Status: New => Incomplete ** Changed in: vanguards (Ubuntu) Status: New => Incomplete ** Also affects: twms (Ubuntu) Importance: Undecided Status: New ** Changed in: twms (Ubuntu) Status: New => Invalid ** Changed in: twms (Ubuntu Jammy) Status: New => Invalid ** Changed in: twms (Ubuntu Noble) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dh-python in Ubuntu. https://bugs.launchpad.net/bugs/2075337 Title: [SRU] py3clean fails when using alternate character set Status in cloud-init package in Ubuntu: New Status in dh-python package in Ubuntu: Invalid Status in python3-defaults package in Ubuntu: Fix Released Status in syncplay package in Ubuntu: New Status in timekpr-next package in Ubuntu: Fix Released Status in twms package in Ubuntu: Invalid Status in ubuntu-advantage-tools package in Ubuntu: New Status in vanguards package in Ubuntu: Incomplete Status in vaultlocker package in Ubuntu: Invalid Status in virtualbox package in Ubuntu: Invalid Status in voctomix-outcasts package in Ubuntu: Invalid Status in weborf package in Ubuntu: Invalid Status in xdiagnose package in Ubuntu: Fix Released Status in cloud-init source package in Jammy: Invalid Status in dh-python source package in Jammy: Invalid Status in python3-defaults source package in Jammy: Fix Released Status in syncplay source package in Jammy: New Status in timekpr-next source package in Jammy: Invalid Status in twms source package in Jammy: Invalid Status in ubuntu-advantage-tools source package in Jammy: Invalid Status in vanguards source package in Jammy: Invalid Status in vaultlocker source package in Jammy: Invalid Status in virtualbox source package in Jammy: Invalid Status in voctomix-outcasts source package in Jammy: Invalid Status in weborf source package in Jammy: Invalid Status in xdiagnose source package in Jammy: Invalid Status in cloud-init source package in Noble: Fix Released Status in dh-python source package in Noble: Invalid Status in python3-defaults source package in Noble: Fix Released Status in syncplay source package in Noble: New Status in timekpr-next source package in Noble: Fix Committed Status in twms source package in Noble: Fix Committed Status in ubuntu-advantage-tools source package in Noble: Fix Released Status in vanguards source package in Noble: Incomplete Status in vaultlocker source package in Noble: Fix Committed Status in virtualbox source package in Noble: Fix Committed Status in voctomix-outcasts source package in Noble: Fix Committed Status in weborf source package in Noble: Fix Committed Status in xdiagnose source package in Noble: Fix Committed Bug description: [ Impact ] With the current version of python3-defaults in jammy and noble, packages which utilize py3compile and py3clean in their maintscripts (which is more or less any package which includes Python modules), and which also are affected by diversions installed by dpkg-divert, will fail to install/upgrade/remove on systems with non-UTF-8 locales, which include non-ASCII characters in their localized dpkg -L messages (and which therefore produce output that is not valid UTF-8). As this has the potential to break apt upgrade, the impact is quite severe (especially if this occurs during a dist-upgrade). However, the scope is probably *fairly* limited given this only affects systems with non-UTF-8 locales (something that has not been the default for many years), and which produce non-ASCII output (e.g. French characters with diacriticals) in their localized messages for dpkg -L. [ Rectification Plan ] Firstly, python3-defaults must be patched in oracular, noble, and jammy. doko has uploaded the fix upstream and synced this to oracular. Benjamin has sponsored the noble and jammy SRUs. Next, affected packages must be patched to include a "Breaks" line on earlier versions of python3-minimal (the python3-defaults binary package containing py3clean and py3compile). Packages which install Python modules are easily selected, but those affected by diversions are (computationally) impossible to select (see comment 18 for details). Thus, determining the set of affected packages was non-trivial, but Benjamin has kindly produced such a list by empirical means (see comment 24). These will be added to the ticket as they are uploaded. [ Known affected packages ] ``` $ for section in main restricted universe multiverse; do echo "noble $section:"; sqlite3 aff
[Touch-packages] [Bug 2075337] Please test proposed package
Hello Robie, or anyone else affected, Accepted twms into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/twms/0.07z+git20201202+bb7c3f8-2ubuntu0.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-noble. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Also affects: timekpr-next (Ubuntu) Importance: Undecided Status: New ** Changed in: timekpr-next (Ubuntu) Status: New => Fix Released ** Changed in: timekpr-next (Ubuntu Jammy) Status: New => Invalid ** Changed in: timekpr-next (Ubuntu Noble) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dh-python in Ubuntu. https://bugs.launchpad.net/bugs/2075337 Title: [SRU] py3clean fails when using alternate character set Status in cloud-init package in Ubuntu: New Status in dh-python package in Ubuntu: Invalid Status in python3-defaults package in Ubuntu: Fix Released Status in syncplay package in Ubuntu: New Status in timekpr-next package in Ubuntu: Fix Released Status in twms package in Ubuntu: Invalid Status in ubuntu-advantage-tools package in Ubuntu: New Status in vanguards package in Ubuntu: Incomplete Status in vaultlocker package in Ubuntu: Invalid Status in virtualbox package in Ubuntu: Invalid Status in voctomix-outcasts package in Ubuntu: Invalid Status in weborf package in Ubuntu: Invalid Status in xdiagnose package in Ubuntu: Fix Released Status in cloud-init source package in Jammy: Invalid Status in dh-python source package in Jammy: Invalid Status in python3-defaults source package in Jammy: Fix Released Status in syncplay source package in Jammy: New Status in timekpr-next source package in Jammy: Invalid Status in twms source package in Jammy: Invalid Status in ubuntu-advantage-tools source package in Jammy: Invalid Status in vanguards source package in Jammy: Invalid Status in vaultlocker source package in Jammy: Invalid Status in virtualbox source package in Jammy: Invalid Status in voctomix-outcasts source package in Jammy: Invalid Status in weborf source package in Jammy: Invalid Status in xdiagnose source package in Jammy: Invalid Status in cloud-init source package in Noble: Fix Released Status in dh-python source package in Noble: Invalid Status in python3-defaults source package in Noble: Fix Released Status in syncplay source package in Noble: New Status in timekpr-next source package in Noble: Fix Committed Status in twms source package in Noble: Fix Committed Status in ubuntu-advantage-tools source package in Noble: Fix Released Status in vanguards source package in Noble: Incomplete Status in vaultlocker source package in Noble: Fix Committed Status in virtualbox source package in Noble: Fix Committed Status in voctomix-outcasts source package in Noble: Fix Committed Status in weborf source package in Noble: Fix Committed Status in xdiagnose source package in Noble: Fix Committed Bug description: [ Impact ] With the current version of python3-defaults in jammy and noble, packages which utilize py3compile and py3clean in their maintscripts (which is more or less any package which includes Python modules), and which also are affected by diversions installed by dpkg-divert, will fail to install/upgrade/remove on systems with non-UTF-8 locales, which include non-ASCII characters in their localized dpkg -L messages (and which therefore produce output that is not valid UTF-8). As this has the potential to break apt upgrade, the impact is quite severe (especially if this occurs during a dist-upgrade). However, the scope is probably *fairly* limited given this only affects systems with non-UTF-8 locales (something that has not been the default for many years), and which produce non-ASCII output (e.g. French characters with diacriticals) in their localized messages for dpkg -L. [ Rectification Pl
[Touch-packages] [Bug 2075337] Please test proposed package
Hello Robie, or anyone else affected, Accepted timekpr-next into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/timekpr- next/0.5.4-1ubuntu3.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-noble. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dh-python in Ubuntu. https://bugs.launchpad.net/bugs/2075337 Title: [SRU] py3clean fails when using alternate character set Status in cloud-init package in Ubuntu: New Status in dh-python package in Ubuntu: Invalid Status in python3-defaults package in Ubuntu: Fix Released Status in syncplay package in Ubuntu: New Status in timekpr-next package in Ubuntu: Fix Released Status in twms package in Ubuntu: Invalid Status in ubuntu-advantage-tools package in Ubuntu: New Status in vanguards package in Ubuntu: Incomplete Status in vaultlocker package in Ubuntu: Invalid Status in virtualbox package in Ubuntu: Invalid Status in voctomix-outcasts package in Ubuntu: Invalid Status in weborf package in Ubuntu: Invalid Status in xdiagnose package in Ubuntu: Fix Released Status in cloud-init source package in Jammy: Invalid Status in dh-python source package in Jammy: Invalid Status in python3-defaults source package in Jammy: Fix Released Status in syncplay source package in Jammy: New Status in timekpr-next source package in Jammy: Invalid Status in twms source package in Jammy: Invalid Status in ubuntu-advantage-tools source package in Jammy: Invalid Status in vanguards source package in Jammy: Invalid Status in vaultlocker source package in Jammy: Invalid Status in virtualbox source package in Jammy: Invalid Status in voctomix-outcasts source package in Jammy: Invalid Status in weborf source package in Jammy: Invalid Status in xdiagnose source package in Jammy: Invalid Status in cloud-init source package in Noble: Fix Released Status in dh-python source package in Noble: Invalid Status in python3-defaults source package in Noble: Fix Released Status in syncplay source package in Noble: New Status in timekpr-next source package in Noble: Fix Committed Status in twms source package in Noble: Fix Committed Status in ubuntu-advantage-tools source package in Noble: Fix Released Status in vanguards source package in Noble: Incomplete Status in vaultlocker source package in Noble: Fix Committed Status in virtualbox source package in Noble: Fix Committed Status in voctomix-outcasts source package in Noble: Fix Committed Status in weborf source package in Noble: Fix Committed Status in xdiagnose source package in Noble: Fix Committed Bug description: [ Impact ] With the current version of python3-defaults in jammy and noble, packages which utilize py3compile and py3clean in their maintscripts (which is more or less any package which includes Python modules), and which also are affected by diversions installed by dpkg-divert, will fail to install/upgrade/remove on systems with non-UTF-8 locales, which include non-ASCII characters in their localized dpkg -L messages (and which therefore produce output that is not valid UTF-8). As this has the potential to break apt upgrade, the impact is quite severe (especially if this occurs during a dist-upgrade). However, the scope is probably *fairly* limited given this only affects systems with non-UTF-8 locales (something that has not been the default for many years), and which produce non-ASCII output (e.g. French characters with diacriticals) in their localized messages for dpkg -L. [ Rectification Plan ] Firstly, python3-defaults must be patched in oracular, noble, and jammy. doko has uploaded the fix upstream and synced this to oracular. Benjamin has sponsored the noble and jammy SRUs. Next, affected packages must be patched to include a "Breaks" line on earlier versions of python3-minimal (the
[Touch-packages] [Bug 2075337] Re: [SRU] py3clean fails when using alternate character set
syncplay has unrelated noise in `d/control` (comments removed); please adjust and re-upload. Thanks! ** Also affects: syncplay (Ubuntu) Importance: Undecided Status: New ** Changed in: syncplay (Ubuntu Noble) Status: New => Incomplete ** Changed in: syncplay (Ubuntu) Status: New => Invalid ** Changed in: syncplay (Ubuntu Jammy) Status: New => Invalid ** Changed in: syncplay (Ubuntu Noble) Assignee: (unassigned) => Dave Jones (waveform) ** Changed in: vanguards (Ubuntu) Assignee: (unassigned) => Dave Jones (waveform) ** Changed in: vanguards (Ubuntu Noble) Assignee: (unassigned) => Dave Jones (waveform) ** Also affects: supervisor (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dh-python in Ubuntu. https://bugs.launchpad.net/bugs/2075337 Title: [SRU] py3clean fails when using alternate character set Status in cloud-init package in Ubuntu: New Status in dh-python package in Ubuntu: Invalid Status in python3-defaults package in Ubuntu: Fix Released Status in razercfg package in Ubuntu: Invalid Status in sgt-launcher package in Ubuntu: Fix Released Status in sms4you package in Ubuntu: Invalid Status in supervisor package in Ubuntu: Invalid Status in syncplay package in Ubuntu: Invalid Status in timekpr-next package in Ubuntu: Fix Released Status in twms package in Ubuntu: Invalid Status in ubuntu-advantage-tools package in Ubuntu: New Status in vanguards package in Ubuntu: Incomplete Status in vaultlocker package in Ubuntu: Invalid Status in virtualbox package in Ubuntu: Invalid Status in voctomix-outcasts package in Ubuntu: Invalid Status in weborf package in Ubuntu: Invalid Status in xdiagnose package in Ubuntu: Fix Released Status in cloud-init source package in Jammy: Invalid Status in dh-python source package in Jammy: Invalid Status in python3-defaults source package in Jammy: Fix Released Status in razercfg source package in Jammy: Invalid Status in sgt-launcher source package in Jammy: Invalid Status in sms4you source package in Jammy: Invalid Status in supervisor source package in Jammy: Invalid Status in syncplay source package in Jammy: Invalid Status in timekpr-next source package in Jammy: Invalid Status in twms source package in Jammy: Invalid Status in ubuntu-advantage-tools source package in Jammy: Invalid Status in vanguards source package in Jammy: Invalid Status in vaultlocker source package in Jammy: Invalid Status in virtualbox source package in Jammy: Invalid Status in voctomix-outcasts source package in Jammy: Invalid Status in weborf source package in Jammy: Invalid Status in xdiagnose source package in Jammy: Invalid Status in cloud-init source package in Noble: Fix Released Status in dh-python source package in Noble: Invalid Status in python3-defaults source package in Noble: Fix Released Status in razercfg source package in Noble: New Status in sgt-launcher source package in Noble: Incomplete Status in sms4you source package in Noble: Fix Committed Status in supervisor source package in Noble: Fix Committed Status in syncplay source package in Noble: Incomplete Status in timekpr-next source package in Noble: Fix Committed Status in twms source package in Noble: Fix Committed Status in ubuntu-advantage-tools source package in Noble: Fix Released Status in vanguards source package in Noble: Incomplete Status in vaultlocker source package in Noble: Fix Committed Status in virtualbox source package in Noble: Fix Committed Status in voctomix-outcasts source package in Noble: Fix Committed Status in weborf source package in Noble: Fix Committed Status in xdiagnose source package in Noble: Fix Committed Bug description: [ Impact ] With the current version of python3-defaults in jammy and noble, packages which utilize py3compile and py3clean in their maintscripts (which is more or less any package which includes Python modules), and which also are affected by diversions installed by dpkg-divert, will fail to install/upgrade/remove on systems with non-UTF-8 locales, which include non-ASCII characters in their localized dpkg -L messages (and which therefore produce output that is not valid UTF-8). As this has the potential to break apt upgrade, the impact is quite severe (especially if this occurs during a dist-upgrade). However, the scope is probably *fairly* limited given this only affects systems with non-UTF-8 locales (something that has not been the default for many years), and which produce non-ASCII output (e.g. French characters with diacriticals) in their localized messages for dpkg -L. [ Rectification Plan ] Firstly, python3-defaults must be patched in oracular, noble, and jammy. doko has uploaded the fix upstream and synced this to oracular. Benjamin has sponso
[Touch-packages] [Bug 2075337] Please test proposed package
Hello Robie, or anyone else affected, Accepted supervisor into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/supervisor/4.2.5-1ubuntu0.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-noble. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: supervisor (Ubuntu) Status: New => Invalid ** Changed in: supervisor (Ubuntu Jammy) Status: New => Invalid ** Changed in: supervisor (Ubuntu Noble) Status: New => Fix Committed ** Also affects: sms4you (Ubuntu) Importance: Undecided Status: New ** Changed in: sms4you (Ubuntu) Status: New => Invalid ** Changed in: sms4you (Ubuntu Jammy) Status: New => Invalid ** Changed in: sms4you (Ubuntu Noble) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dh-python in Ubuntu. https://bugs.launchpad.net/bugs/2075337 Title: [SRU] py3clean fails when using alternate character set Status in cloud-init package in Ubuntu: New Status in dh-python package in Ubuntu: Invalid Status in python3-defaults package in Ubuntu: Fix Released Status in razercfg package in Ubuntu: Invalid Status in sgt-launcher package in Ubuntu: Fix Released Status in sms4you package in Ubuntu: Invalid Status in supervisor package in Ubuntu: Invalid Status in syncplay package in Ubuntu: Invalid Status in timekpr-next package in Ubuntu: Fix Released Status in twms package in Ubuntu: Invalid Status in ubuntu-advantage-tools package in Ubuntu: New Status in vanguards package in Ubuntu: Incomplete Status in vaultlocker package in Ubuntu: Invalid Status in virtualbox package in Ubuntu: Invalid Status in voctomix-outcasts package in Ubuntu: Invalid Status in weborf package in Ubuntu: Invalid Status in xdiagnose package in Ubuntu: Fix Released Status in cloud-init source package in Jammy: Invalid Status in dh-python source package in Jammy: Invalid Status in python3-defaults source package in Jammy: Fix Released Status in razercfg source package in Jammy: Invalid Status in sgt-launcher source package in Jammy: Invalid Status in sms4you source package in Jammy: Invalid Status in supervisor source package in Jammy: Invalid Status in syncplay source package in Jammy: Invalid Status in timekpr-next source package in Jammy: Invalid Status in twms source package in Jammy: Invalid Status in ubuntu-advantage-tools source package in Jammy: Invalid Status in vanguards source package in Jammy: Invalid Status in vaultlocker source package in Jammy: Invalid Status in virtualbox source package in Jammy: Invalid Status in voctomix-outcasts source package in Jammy: Invalid Status in weborf source package in Jammy: Invalid Status in xdiagnose source package in Jammy: Invalid Status in cloud-init source package in Noble: Fix Released Status in dh-python source package in Noble: Invalid Status in python3-defaults source package in Noble: Fix Released Status in razercfg source package in Noble: New Status in sgt-launcher source package in Noble: Incomplete Status in sms4you source package in Noble: Fix Committed Status in supervisor source package in Noble: Fix Committed Status in syncplay source package in Noble: Incomplete Status in timekpr-next source package in Noble: Fix Committed Status in twms source package in Noble: Fix Committed Status in ubuntu-advantage-tools source package in Noble: Fix Released Status in vanguards source package in Noble: Incomplete Status in vaultlocker source package in Noble: Fix Committed Status in virtualbox source package in Noble: Fix Committed Status in voctomix-outcasts source package in Noble: Fix Committed Status in weborf source package in Noble: Fix Committed Status in xdiagnose source package in Noble: Fix Committed Bug description: [ Impact ] With the current version of python3-defaults in jammy and noble, packa
[Touch-packages] [Bug 2075337] Please test proposed package
Hello Robie, or anyone else affected, Accepted sms4you into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/sms4you/0.0.7-2ubuntu0.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-noble. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Also affects: sgt-launcher (Ubuntu) Importance: Undecided Status: New ** Changed in: sgt-launcher (Ubuntu) Status: New => Fix Released ** Changed in: sgt-launcher (Ubuntu Jammy) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dh-python in Ubuntu. https://bugs.launchpad.net/bugs/2075337 Title: [SRU] py3clean fails when using alternate character set Status in cloud-init package in Ubuntu: New Status in dh-python package in Ubuntu: Invalid Status in python3-defaults package in Ubuntu: Fix Released Status in razercfg package in Ubuntu: Invalid Status in sgt-launcher package in Ubuntu: Fix Released Status in sms4you package in Ubuntu: Invalid Status in supervisor package in Ubuntu: Invalid Status in syncplay package in Ubuntu: Invalid Status in timekpr-next package in Ubuntu: Fix Released Status in twms package in Ubuntu: Invalid Status in ubuntu-advantage-tools package in Ubuntu: New Status in vanguards package in Ubuntu: Incomplete Status in vaultlocker package in Ubuntu: Invalid Status in virtualbox package in Ubuntu: Invalid Status in voctomix-outcasts package in Ubuntu: Invalid Status in weborf package in Ubuntu: Invalid Status in xdiagnose package in Ubuntu: Fix Released Status in cloud-init source package in Jammy: Invalid Status in dh-python source package in Jammy: Invalid Status in python3-defaults source package in Jammy: Fix Released Status in razercfg source package in Jammy: Invalid Status in sgt-launcher source package in Jammy: Invalid Status in sms4you source package in Jammy: Invalid Status in supervisor source package in Jammy: Invalid Status in syncplay source package in Jammy: Invalid Status in timekpr-next source package in Jammy: Invalid Status in twms source package in Jammy: Invalid Status in ubuntu-advantage-tools source package in Jammy: Invalid Status in vanguards source package in Jammy: Invalid Status in vaultlocker source package in Jammy: Invalid Status in virtualbox source package in Jammy: Invalid Status in voctomix-outcasts source package in Jammy: Invalid Status in weborf source package in Jammy: Invalid Status in xdiagnose source package in Jammy: Invalid Status in cloud-init source package in Noble: Fix Released Status in dh-python source package in Noble: Invalid Status in python3-defaults source package in Noble: Fix Released Status in razercfg source package in Noble: New Status in sgt-launcher source package in Noble: Incomplete Status in sms4you source package in Noble: Fix Committed Status in supervisor source package in Noble: Fix Committed Status in syncplay source package in Noble: Incomplete Status in timekpr-next source package in Noble: Fix Committed Status in twms source package in Noble: Fix Committed Status in ubuntu-advantage-tools source package in Noble: Fix Released Status in vanguards source package in Noble: Incomplete Status in vaultlocker source package in Noble: Fix Committed Status in virtualbox source package in Noble: Fix Committed Status in voctomix-outcasts source package in Noble: Fix Committed Status in weborf source package in Noble: Fix Committed Status in xdiagnose source package in Noble: Fix Committed Bug description: [ Impact ] With the current version of python3-defaults in jammy and noble, packages which utilize py3compile and py3clean in their maintscripts (which is more or less any package which includes Python modules), and which also are affected by diversions installed by dpkg-divert, will fail to install/upgrade/remove on systems with non-UTF-8 locales,
[Touch-packages] [Bug 2075337] Re: [SRU] py3clean fails when using alternate character set
The sgt-launcher upload includes this apparently unnecessary change without a description in the changelog (which is present in Oracular, as below). ` * d/control: Remove redundant python3-distutils` Could you please re-upload with that removed (preferred, if not strictly needed in the stable release) or at least described in the changelog? Thanks! ** Changed in: sgt-launcher (Ubuntu Noble) Status: New => Incomplete ** Changed in: sgt-launcher (Ubuntu Noble) Assignee: (unassigned) => Dave Jones (waveform) ** Also affects: razercfg (Ubuntu) Importance: Undecided Status: New ** Changed in: razercfg (Ubuntu) Status: New => Invalid ** Changed in: razercfg (Ubuntu Jammy) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dh-python in Ubuntu. https://bugs.launchpad.net/bugs/2075337 Title: [SRU] py3clean fails when using alternate character set Status in cloud-init package in Ubuntu: New Status in dh-python package in Ubuntu: Invalid Status in python3-defaults package in Ubuntu: Fix Released Status in razercfg package in Ubuntu: Invalid Status in sgt-launcher package in Ubuntu: Fix Released Status in sms4you package in Ubuntu: Invalid Status in supervisor package in Ubuntu: Invalid Status in syncplay package in Ubuntu: Invalid Status in timekpr-next package in Ubuntu: Fix Released Status in twms package in Ubuntu: Invalid Status in ubuntu-advantage-tools package in Ubuntu: New Status in vanguards package in Ubuntu: Incomplete Status in vaultlocker package in Ubuntu: Invalid Status in virtualbox package in Ubuntu: Invalid Status in voctomix-outcasts package in Ubuntu: Invalid Status in weborf package in Ubuntu: Invalid Status in xdiagnose package in Ubuntu: Fix Released Status in cloud-init source package in Jammy: Invalid Status in dh-python source package in Jammy: Invalid Status in python3-defaults source package in Jammy: Fix Released Status in razercfg source package in Jammy: Invalid Status in sgt-launcher source package in Jammy: Invalid Status in sms4you source package in Jammy: Invalid Status in supervisor source package in Jammy: Invalid Status in syncplay source package in Jammy: Invalid Status in timekpr-next source package in Jammy: Invalid Status in twms source package in Jammy: Invalid Status in ubuntu-advantage-tools source package in Jammy: Invalid Status in vanguards source package in Jammy: Invalid Status in vaultlocker source package in Jammy: Invalid Status in virtualbox source package in Jammy: Invalid Status in voctomix-outcasts source package in Jammy: Invalid Status in weborf source package in Jammy: Invalid Status in xdiagnose source package in Jammy: Invalid Status in cloud-init source package in Noble: Fix Released Status in dh-python source package in Noble: Invalid Status in python3-defaults source package in Noble: Fix Released Status in razercfg source package in Noble: New Status in sgt-launcher source package in Noble: Incomplete Status in sms4you source package in Noble: Fix Committed Status in supervisor source package in Noble: Fix Committed Status in syncplay source package in Noble: Incomplete Status in timekpr-next source package in Noble: Fix Committed Status in twms source package in Noble: Fix Committed Status in ubuntu-advantage-tools source package in Noble: Fix Released Status in vanguards source package in Noble: Incomplete Status in vaultlocker source package in Noble: Fix Committed Status in virtualbox source package in Noble: Fix Committed Status in voctomix-outcasts source package in Noble: Fix Committed Status in weborf source package in Noble: Fix Committed Status in xdiagnose source package in Noble: Fix Committed Bug description: [ Impact ] With the current version of python3-defaults in jammy and noble, packages which utilize py3compile and py3clean in their maintscripts (which is more or less any package which includes Python modules), and which also are affected by diversions installed by dpkg-divert, will fail to install/upgrade/remove on systems with non-UTF-8 locales, which include non-ASCII characters in their localized dpkg -L messages (and which therefore produce output that is not valid UTF-8). As this has the potential to break apt upgrade, the impact is quite severe (especially if this occurs during a dist-upgrade). However, the scope is probably *fairly* limited given this only affects systems with non-UTF-8 locales (something that has not been the default for many years), and which produce non-ASCII output (e.g. French characters with diacriticals) in their localized messages for dpkg -L. [ Rectification Plan ] Firstly, python3-defaults must be patched in oracular, noble, and jammy. doko has uploaded the fix upstream and synced this to oracular. Benjamin has sponsored
[Touch-packages] [Bug 2075337] Re: [SRU] py3clean fails when using alternate character set
The razercfg upload contains a py3.12 enablement change (thanks!) which is untagged and apparently mimics bug #2070171. Could you please tag that line/bug in the changelog, adjust (it'd be preferrable to use the same fix, if possible), and re-upload? Thanks! ** Changed in: razercfg (Ubuntu Noble) Status: New => Incomplete ** Changed in: razercfg (Ubuntu Noble) Assignee: (unassigned) => Dave Jones (waveform) ** Also affects: r4d (Ubuntu) Importance: Undecided Status: New ** Changed in: r4d (Ubuntu) Status: New => Invalid ** Changed in: r4d (Ubuntu Jammy) Status: New => Invalid ** Changed in: r4d (Ubuntu Noble) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dh-python in Ubuntu. https://bugs.launchpad.net/bugs/2075337 Title: [SRU] py3clean fails when using alternate character set Status in cloud-init package in Ubuntu: New Status in dh-python package in Ubuntu: Invalid Status in pagure package in Ubuntu: Invalid Status in pglistener package in Ubuntu: Invalid Status in policyd-rate-limit package in Ubuntu: Invalid Status in postfix-mta-sts-resolver package in Ubuntu: Invalid Status in powa-collector package in Ubuntu: Invalid Status in prelude-correlator package in Ubuntu: Invalid Status in prometheus-pgbouncer-exporter package in Ubuntu: Invalid Status in prometheus-xmpp-alerts package in Ubuntu: Invalid Status in pyro5 package in Ubuntu: Invalid Status in pyroman package in Ubuntu: Invalid Status in python3-defaults package in Ubuntu: Fix Released Status in r4d package in Ubuntu: Invalid Status in razercfg package in Ubuntu: Invalid Status in sgt-launcher package in Ubuntu: Fix Released Status in sms4you package in Ubuntu: Invalid Status in supervisor package in Ubuntu: Invalid Status in syncplay package in Ubuntu: Invalid Status in timekpr-next package in Ubuntu: Fix Released Status in twms package in Ubuntu: Invalid Status in ubuntu-advantage-tools package in Ubuntu: New Status in vanguards package in Ubuntu: Incomplete Status in vaultlocker package in Ubuntu: Invalid Status in virtualbox package in Ubuntu: Invalid Status in voctomix-outcasts package in Ubuntu: Invalid Status in weborf package in Ubuntu: Invalid Status in xdiagnose package in Ubuntu: Fix Released Status in cloud-init source package in Jammy: Invalid Status in dh-python source package in Jammy: Invalid Status in pagure source package in Jammy: Invalid Status in pglistener source package in Jammy: Invalid Status in policyd-rate-limit source package in Jammy: Invalid Status in postfix-mta-sts-resolver source package in Jammy: Invalid Status in powa-collector source package in Jammy: Invalid Status in prelude-correlator source package in Jammy: Invalid Status in prometheus-pgbouncer-exporter source package in Jammy: Invalid Status in prometheus-xmpp-alerts source package in Jammy: Invalid Status in pyro5 source package in Jammy: Invalid Status in pyroman source package in Jammy: Invalid Status in python3-defaults source package in Jammy: Fix Released Status in r4d source package in Jammy: Invalid Status in razercfg source package in Jammy: Invalid Status in sgt-launcher source package in Jammy: Invalid Status in sms4you source package in Jammy: Invalid Status in supervisor source package in Jammy: Invalid Status in syncplay source package in Jammy: Invalid Status in timekpr-next source package in Jammy: Invalid Status in twms source package in Jammy: Invalid Status in ubuntu-advantage-tools source package in Jammy: Invalid Status in vanguards source package in Jammy: Invalid Status in vaultlocker source package in Jammy: Invalid Status in virtualbox source package in Jammy: Invalid Status in voctomix-outcasts source package in Jammy: Invalid Status in weborf source package in Jammy: Invalid Status in xdiagnose source package in Jammy: Invalid Status in cloud-init source package in Noble: Fix Released Status in dh-python source package in Noble: Invalid Status in pagure source package in Noble: Incomplete Status in pglistener source package in Noble: Fix Committed Status in policyd-rate-limit source package in Noble: Fix Committed Status in postfix-mta-sts-resolver source package in Noble: Fix Committed Status in powa-collector source package in Noble: Fix Committed Status in prelude-correlator source package in Noble: Fix Committed Status in prometheus-pgbouncer-exporter source package in Noble: Incomplete Status in prometheus-xmpp-alerts source package in Noble: Fix Committed Status in pyro5 source package in Noble: Incomplete Status in pyroman source package in Noble: Fix Committed Status in python3-defaults source package in Noble: Fix Released Status in r4d source package in Noble: Fix Committed Status in razercfg source package in Noble: Inco
[Touch-packages] [Bug 2075337] Please test proposed package
Hello Robie, or anyone else affected, Accepted r4d into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/r4d/1.7-4ubuntu0.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-noble. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Also affects: pyroman (Ubuntu) Importance: Undecided Status: New ** Changed in: pyroman (Ubuntu) Status: New => Invalid ** Changed in: pyroman (Ubuntu Jammy) Status: New => Invalid ** Changed in: pyroman (Ubuntu Noble) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dh-python in Ubuntu. https://bugs.launchpad.net/bugs/2075337 Title: [SRU] py3clean fails when using alternate character set Status in cloud-init package in Ubuntu: New Status in dh-python package in Ubuntu: Invalid Status in pagure package in Ubuntu: Invalid Status in pglistener package in Ubuntu: Invalid Status in policyd-rate-limit package in Ubuntu: Invalid Status in postfix-mta-sts-resolver package in Ubuntu: Invalid Status in powa-collector package in Ubuntu: Invalid Status in prelude-correlator package in Ubuntu: Invalid Status in prometheus-pgbouncer-exporter package in Ubuntu: Invalid Status in prometheus-xmpp-alerts package in Ubuntu: Invalid Status in pyro5 package in Ubuntu: Invalid Status in pyroman package in Ubuntu: Invalid Status in python3-defaults package in Ubuntu: Fix Released Status in r4d package in Ubuntu: Invalid Status in razercfg package in Ubuntu: Invalid Status in sgt-launcher package in Ubuntu: Fix Released Status in sms4you package in Ubuntu: Invalid Status in supervisor package in Ubuntu: Invalid Status in syncplay package in Ubuntu: Invalid Status in timekpr-next package in Ubuntu: Fix Released Status in twms package in Ubuntu: Invalid Status in ubuntu-advantage-tools package in Ubuntu: New Status in vanguards package in Ubuntu: Incomplete Status in vaultlocker package in Ubuntu: Invalid Status in virtualbox package in Ubuntu: Invalid Status in voctomix-outcasts package in Ubuntu: Invalid Status in weborf package in Ubuntu: Invalid Status in xdiagnose package in Ubuntu: Fix Released Status in cloud-init source package in Jammy: Invalid Status in dh-python source package in Jammy: Invalid Status in pagure source package in Jammy: Invalid Status in pglistener source package in Jammy: Invalid Status in policyd-rate-limit source package in Jammy: Invalid Status in postfix-mta-sts-resolver source package in Jammy: Invalid Status in powa-collector source package in Jammy: Invalid Status in prelude-correlator source package in Jammy: Invalid Status in prometheus-pgbouncer-exporter source package in Jammy: Invalid Status in prometheus-xmpp-alerts source package in Jammy: Invalid Status in pyro5 source package in Jammy: Invalid Status in pyroman source package in Jammy: Invalid Status in python3-defaults source package in Jammy: Fix Released Status in r4d source package in Jammy: Invalid Status in razercfg source package in Jammy: Invalid Status in sgt-launcher source package in Jammy: Invalid Status in sms4you source package in Jammy: Invalid Status in supervisor source package in Jammy: Invalid Status in syncplay source package in Jammy: Invalid Status in timekpr-next source package in Jammy: Invalid Status in twms source package in Jammy: Invalid Status in ubuntu-advantage-tools source package in Jammy: Invalid Status in vanguards source package in Jammy: Invalid Status in vaultlocker source package in Jammy: Invalid Status in virtualbox source package in Jammy: Invalid Status in voctomix-outcasts source package in Jammy: Invalid Status in weborf source package in Jammy: Invalid Status in xdiagnose source package in Jammy: Invalid Status in cloud-init source package in Noble: Fix Released Status in dh-python source package in Noble: Invalid
[Touch-packages] [Bug 2075337] Please test proposed package
Hello Robie, or anyone else affected, Accepted pyroman into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/pyroman/0.6.2-1.1ubuntu0.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-noble. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Also affects: pyro5 (Ubuntu) Importance: Undecided Status: New ** Changed in: pyro5 (Ubuntu) Status: New => Invalid ** Changed in: pyro5 (Ubuntu Jammy) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dh-python in Ubuntu. https://bugs.launchpad.net/bugs/2075337 Title: [SRU] py3clean fails when using alternate character set Status in cloud-init package in Ubuntu: New Status in dh-python package in Ubuntu: Invalid Status in pagure package in Ubuntu: Invalid Status in pglistener package in Ubuntu: Invalid Status in policyd-rate-limit package in Ubuntu: Invalid Status in postfix-mta-sts-resolver package in Ubuntu: Invalid Status in powa-collector package in Ubuntu: Invalid Status in prelude-correlator package in Ubuntu: Invalid Status in prometheus-pgbouncer-exporter package in Ubuntu: Invalid Status in prometheus-xmpp-alerts package in Ubuntu: Invalid Status in pyro5 package in Ubuntu: Invalid Status in pyroman package in Ubuntu: Invalid Status in python3-defaults package in Ubuntu: Fix Released Status in r4d package in Ubuntu: Invalid Status in razercfg package in Ubuntu: Invalid Status in sgt-launcher package in Ubuntu: Fix Released Status in sms4you package in Ubuntu: Invalid Status in supervisor package in Ubuntu: Invalid Status in syncplay package in Ubuntu: Invalid Status in timekpr-next package in Ubuntu: Fix Released Status in twms package in Ubuntu: Invalid Status in ubuntu-advantage-tools package in Ubuntu: New Status in vanguards package in Ubuntu: Incomplete Status in vaultlocker package in Ubuntu: Invalid Status in virtualbox package in Ubuntu: Invalid Status in voctomix-outcasts package in Ubuntu: Invalid Status in weborf package in Ubuntu: Invalid Status in xdiagnose package in Ubuntu: Fix Released Status in cloud-init source package in Jammy: Invalid Status in dh-python source package in Jammy: Invalid Status in pagure source package in Jammy: Invalid Status in pglistener source package in Jammy: Invalid Status in policyd-rate-limit source package in Jammy: Invalid Status in postfix-mta-sts-resolver source package in Jammy: Invalid Status in powa-collector source package in Jammy: Invalid Status in prelude-correlator source package in Jammy: Invalid Status in prometheus-pgbouncer-exporter source package in Jammy: Invalid Status in prometheus-xmpp-alerts source package in Jammy: Invalid Status in pyro5 source package in Jammy: Invalid Status in pyroman source package in Jammy: Invalid Status in python3-defaults source package in Jammy: Fix Released Status in r4d source package in Jammy: Invalid Status in razercfg source package in Jammy: Invalid Status in sgt-launcher source package in Jammy: Invalid Status in sms4you source package in Jammy: Invalid Status in supervisor source package in Jammy: Invalid Status in syncplay source package in Jammy: Invalid Status in timekpr-next source package in Jammy: Invalid Status in twms source package in Jammy: Invalid Status in ubuntu-advantage-tools source package in Jammy: Invalid Status in vanguards source package in Jammy: Invalid Status in vaultlocker source package in Jammy: Invalid Status in virtualbox source package in Jammy: Invalid Status in voctomix-outcasts source package in Jammy: Invalid Status in weborf source package in Jammy: Invalid Status in xdiagnose source package in Jammy: Invalid Status in cloud-init source package in Noble: Fix Released Status in dh-python source package in Noble: Invalid Status in pagure source package in Noble: Incomplete Status in pgli
[Touch-packages] [Bug 2075337] Re: [SRU] py3clean fails when using alternate character set
The pyro5 upload has an unrelated/undescribed (?) change in d/control for Build-Depends(-Indep). Could you please clarify or re-upload with a description? Thanks! ** Changed in: pyro5 (Ubuntu Noble) Status: New => Incomplete ** Changed in: pyro5 (Ubuntu Noble) Assignee: (unassigned) => Dave Jones (waveform) ** Also affects: prometheus-xmpp-alerts (Ubuntu) Importance: Undecided Status: New ** Changed in: prometheus-xmpp-alerts (Ubuntu) Status: New => Invalid ** Changed in: prometheus-xmpp-alerts (Ubuntu Jammy) Status: New => Invalid ** Changed in: prometheus-xmpp-alerts (Ubuntu Noble) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dh-python in Ubuntu. https://bugs.launchpad.net/bugs/2075337 Title: [SRU] py3clean fails when using alternate character set Status in cloud-init package in Ubuntu: New Status in dh-python package in Ubuntu: Invalid Status in pagure package in Ubuntu: Invalid Status in pglistener package in Ubuntu: Invalid Status in policyd-rate-limit package in Ubuntu: Invalid Status in postfix-mta-sts-resolver package in Ubuntu: Invalid Status in powa-collector package in Ubuntu: Invalid Status in prelude-correlator package in Ubuntu: Invalid Status in prometheus-pgbouncer-exporter package in Ubuntu: Invalid Status in prometheus-xmpp-alerts package in Ubuntu: Invalid Status in pyro5 package in Ubuntu: Invalid Status in pyroman package in Ubuntu: Invalid Status in python3-defaults package in Ubuntu: Fix Released Status in r4d package in Ubuntu: Invalid Status in razercfg package in Ubuntu: Invalid Status in sgt-launcher package in Ubuntu: Fix Released Status in sms4you package in Ubuntu: Invalid Status in supervisor package in Ubuntu: Invalid Status in syncplay package in Ubuntu: Invalid Status in timekpr-next package in Ubuntu: Fix Released Status in twms package in Ubuntu: Invalid Status in ubuntu-advantage-tools package in Ubuntu: New Status in vanguards package in Ubuntu: Incomplete Status in vaultlocker package in Ubuntu: Invalid Status in virtualbox package in Ubuntu: Invalid Status in voctomix-outcasts package in Ubuntu: Invalid Status in weborf package in Ubuntu: Invalid Status in xdiagnose package in Ubuntu: Fix Released Status in cloud-init source package in Jammy: Invalid Status in dh-python source package in Jammy: Invalid Status in pagure source package in Jammy: Invalid Status in pglistener source package in Jammy: Invalid Status in policyd-rate-limit source package in Jammy: Invalid Status in postfix-mta-sts-resolver source package in Jammy: Invalid Status in powa-collector source package in Jammy: Invalid Status in prelude-correlator source package in Jammy: Invalid Status in prometheus-pgbouncer-exporter source package in Jammy: Invalid Status in prometheus-xmpp-alerts source package in Jammy: Invalid Status in pyro5 source package in Jammy: Invalid Status in pyroman source package in Jammy: Invalid Status in python3-defaults source package in Jammy: Fix Released Status in r4d source package in Jammy: Invalid Status in razercfg source package in Jammy: Invalid Status in sgt-launcher source package in Jammy: Invalid Status in sms4you source package in Jammy: Invalid Status in supervisor source package in Jammy: Invalid Status in syncplay source package in Jammy: Invalid Status in timekpr-next source package in Jammy: Invalid Status in twms source package in Jammy: Invalid Status in ubuntu-advantage-tools source package in Jammy: Invalid Status in vanguards source package in Jammy: Invalid Status in vaultlocker source package in Jammy: Invalid Status in virtualbox source package in Jammy: Invalid Status in voctomix-outcasts source package in Jammy: Invalid Status in weborf source package in Jammy: Invalid Status in xdiagnose source package in Jammy: Invalid Status in cloud-init source package in Noble: Fix Released Status in dh-python source package in Noble: Invalid Status in pagure source package in Noble: Incomplete Status in pglistener source package in Noble: Fix Committed Status in policyd-rate-limit source package in Noble: Fix Committed Status in postfix-mta-sts-resolver source package in Noble: Fix Committed Status in powa-collector source package in Noble: Fix Committed Status in prelude-correlator source package in Noble: Fix Committed Status in prometheus-pgbouncer-exporter source package in Noble: Incomplete Status in prometheus-xmpp-alerts source package in Noble: Fix Committed Status in pyro5 source package in Noble: Incomplete Status in pyroman source package in Noble: Fix Committed Status in python3-defaults source package in Noble: Fix Released Status in r4d source package in Noble: Fix Committed Status in razercfg source package in Noble: Incomplete Status in sgt-launch
[Touch-packages] [Bug 2075337] Please test proposed package
Hello Robie, or anyone else affected, Accepted prometheus-xmpp-alerts into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/prometheus-xmpp- alerts/0.5.3-1.1ubuntu0.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-noble. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Also affects: prometheus-pgbouncer-exporter (Ubuntu) Importance: Undecided Status: New ** Changed in: prometheus-pgbouncer-exporter (Ubuntu) Status: New => Invalid ** Changed in: prometheus-pgbouncer-exporter (Ubuntu Jammy) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dh-python in Ubuntu. https://bugs.launchpad.net/bugs/2075337 Title: [SRU] py3clean fails when using alternate character set Status in cloud-init package in Ubuntu: New Status in dh-python package in Ubuntu: Invalid Status in pagure package in Ubuntu: Invalid Status in pglistener package in Ubuntu: Invalid Status in policyd-rate-limit package in Ubuntu: Invalid Status in postfix-mta-sts-resolver package in Ubuntu: Invalid Status in powa-collector package in Ubuntu: Invalid Status in prelude-correlator package in Ubuntu: Invalid Status in prometheus-pgbouncer-exporter package in Ubuntu: Invalid Status in prometheus-xmpp-alerts package in Ubuntu: Invalid Status in pyro5 package in Ubuntu: Invalid Status in pyroman package in Ubuntu: Invalid Status in python3-defaults package in Ubuntu: Fix Released Status in r4d package in Ubuntu: Invalid Status in razercfg package in Ubuntu: Invalid Status in sgt-launcher package in Ubuntu: Fix Released Status in sms4you package in Ubuntu: Invalid Status in supervisor package in Ubuntu: Invalid Status in syncplay package in Ubuntu: Invalid Status in timekpr-next package in Ubuntu: Fix Released Status in twms package in Ubuntu: Invalid Status in ubuntu-advantage-tools package in Ubuntu: New Status in vanguards package in Ubuntu: Incomplete Status in vaultlocker package in Ubuntu: Invalid Status in virtualbox package in Ubuntu: Invalid Status in voctomix-outcasts package in Ubuntu: Invalid Status in weborf package in Ubuntu: Invalid Status in xdiagnose package in Ubuntu: Fix Released Status in cloud-init source package in Jammy: Invalid Status in dh-python source package in Jammy: Invalid Status in pagure source package in Jammy: Invalid Status in pglistener source package in Jammy: Invalid Status in policyd-rate-limit source package in Jammy: Invalid Status in postfix-mta-sts-resolver source package in Jammy: Invalid Status in powa-collector source package in Jammy: Invalid Status in prelude-correlator source package in Jammy: Invalid Status in prometheus-pgbouncer-exporter source package in Jammy: Invalid Status in prometheus-xmpp-alerts source package in Jammy: Invalid Status in pyro5 source package in Jammy: Invalid Status in pyroman source package in Jammy: Invalid Status in python3-defaults source package in Jammy: Fix Released Status in r4d source package in Jammy: Invalid Status in razercfg source package in Jammy: Invalid Status in sgt-launcher source package in Jammy: Invalid Status in sms4you source package in Jammy: Invalid Status in supervisor source package in Jammy: Invalid Status in syncplay source package in Jammy: Invalid Status in timekpr-next source package in Jammy: Invalid Status in twms source package in Jammy: Invalid Status in ubuntu-advantage-tools source package in Jammy: Invalid Status in vanguards source package in Jammy: Invalid Status in vaultlocker source package in Jammy: Invalid Status in virtualbox source package in Jammy: Invalid Status in voctomix-outcasts source package in Jammy: Invalid Status in weborf source package in Jammy: Invalid Status in xdiagnose source package in Jammy: Invalid Status in cloud-init source package in Noble: Fix Released Status in dh-python s
[Touch-packages] [Bug 2075337] Re: [SRU] py3clean fails when using alternate character set
The prometheus-pgbouncer-exporter has unrelated noise (removed comments) in d/control. Please adjust and re-upload. Thanks! ** Changed in: prometheus-pgbouncer-exporter (Ubuntu Noble) Status: New => Incomplete ** Changed in: prometheus-pgbouncer-exporter (Ubuntu Noble) Assignee: (unassigned) => Dave Jones (waveform) ** Also affects: prelude-correlator (Ubuntu) Importance: Undecided Status: New ** Changed in: prelude-correlator (Ubuntu) Status: New => Invalid ** Changed in: prelude-correlator (Ubuntu Jammy) Status: New => Invalid ** Changed in: prelude-correlator (Ubuntu Noble) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dh-python in Ubuntu. https://bugs.launchpad.net/bugs/2075337 Title: [SRU] py3clean fails when using alternate character set Status in cloud-init package in Ubuntu: New Status in dh-python package in Ubuntu: Invalid Status in pagure package in Ubuntu: Invalid Status in pglistener package in Ubuntu: Invalid Status in policyd-rate-limit package in Ubuntu: Invalid Status in postfix-mta-sts-resolver package in Ubuntu: Invalid Status in powa-collector package in Ubuntu: Invalid Status in prelude-correlator package in Ubuntu: Invalid Status in prometheus-pgbouncer-exporter package in Ubuntu: Invalid Status in prometheus-xmpp-alerts package in Ubuntu: Invalid Status in pyro5 package in Ubuntu: Invalid Status in pyroman package in Ubuntu: Invalid Status in python3-defaults package in Ubuntu: Fix Released Status in r4d package in Ubuntu: Invalid Status in razercfg package in Ubuntu: Invalid Status in sgt-launcher package in Ubuntu: Fix Released Status in sms4you package in Ubuntu: Invalid Status in supervisor package in Ubuntu: Invalid Status in syncplay package in Ubuntu: Invalid Status in timekpr-next package in Ubuntu: Fix Released Status in twms package in Ubuntu: Invalid Status in ubuntu-advantage-tools package in Ubuntu: New Status in vanguards package in Ubuntu: Incomplete Status in vaultlocker package in Ubuntu: Invalid Status in virtualbox package in Ubuntu: Invalid Status in voctomix-outcasts package in Ubuntu: Invalid Status in weborf package in Ubuntu: Invalid Status in xdiagnose package in Ubuntu: Fix Released Status in cloud-init source package in Jammy: Invalid Status in dh-python source package in Jammy: Invalid Status in pagure source package in Jammy: Invalid Status in pglistener source package in Jammy: Invalid Status in policyd-rate-limit source package in Jammy: Invalid Status in postfix-mta-sts-resolver source package in Jammy: Invalid Status in powa-collector source package in Jammy: Invalid Status in prelude-correlator source package in Jammy: Invalid Status in prometheus-pgbouncer-exporter source package in Jammy: Invalid Status in prometheus-xmpp-alerts source package in Jammy: Invalid Status in pyro5 source package in Jammy: Invalid Status in pyroman source package in Jammy: Invalid Status in python3-defaults source package in Jammy: Fix Released Status in r4d source package in Jammy: Invalid Status in razercfg source package in Jammy: Invalid Status in sgt-launcher source package in Jammy: Invalid Status in sms4you source package in Jammy: Invalid Status in supervisor source package in Jammy: Invalid Status in syncplay source package in Jammy: Invalid Status in timekpr-next source package in Jammy: Invalid Status in twms source package in Jammy: Invalid Status in ubuntu-advantage-tools source package in Jammy: Invalid Status in vanguards source package in Jammy: Invalid Status in vaultlocker source package in Jammy: Invalid Status in virtualbox source package in Jammy: Invalid Status in voctomix-outcasts source package in Jammy: Invalid Status in weborf source package in Jammy: Invalid Status in xdiagnose source package in Jammy: Invalid Status in cloud-init source package in Noble: Fix Released Status in dh-python source package in Noble: Invalid Status in pagure source package in Noble: Incomplete Status in pglistener source package in Noble: Fix Committed Status in policyd-rate-limit source package in Noble: Fix Committed Status in postfix-mta-sts-resolver source package in Noble: Fix Committed Status in powa-collector source package in Noble: Fix Committed Status in prelude-correlator source package in Noble: Fix Committed Status in prometheus-pgbouncer-exporter source package in Noble: Incomplete Status in prometheus-xmpp-alerts source package in Noble: Fix Committed Status in pyro5 source package in Noble: Incomplete Status in pyroman source package in Noble: Fix Committed Status in python3-defaults source package in Noble: Fix Released Status in r4d source package in Noble: Fix Committed Status in razercfg source package in Noble: Incomplete Status in sgt-launcher source
[Touch-packages] [Bug 2075337] Please test proposed package
Hello Robie, or anyone else affected, Accepted prelude-correlator into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/prelude- correlator/5.2.0-1.1ubuntu0.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-noble. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Also affects: powa-collector (Ubuntu) Importance: Undecided Status: New ** Changed in: powa-collector (Ubuntu) Status: New => Invalid ** Changed in: powa-collector (Ubuntu Jammy) Status: New => Invalid ** Changed in: powa-collector (Ubuntu Noble) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dh-python in Ubuntu. https://bugs.launchpad.net/bugs/2075337 Title: [SRU] py3clean fails when using alternate character set Status in cloud-init package in Ubuntu: New Status in dh-python package in Ubuntu: Invalid Status in pagure package in Ubuntu: Invalid Status in pglistener package in Ubuntu: Invalid Status in policyd-rate-limit package in Ubuntu: Invalid Status in postfix-mta-sts-resolver package in Ubuntu: Invalid Status in powa-collector package in Ubuntu: Invalid Status in prelude-correlator package in Ubuntu: Invalid Status in prometheus-pgbouncer-exporter package in Ubuntu: Invalid Status in prometheus-xmpp-alerts package in Ubuntu: Invalid Status in pyro5 package in Ubuntu: Invalid Status in pyroman package in Ubuntu: Invalid Status in python3-defaults package in Ubuntu: Fix Released Status in r4d package in Ubuntu: Invalid Status in razercfg package in Ubuntu: Invalid Status in sgt-launcher package in Ubuntu: Fix Released Status in sms4you package in Ubuntu: Invalid Status in supervisor package in Ubuntu: Invalid Status in syncplay package in Ubuntu: Invalid Status in timekpr-next package in Ubuntu: Fix Released Status in twms package in Ubuntu: Invalid Status in ubuntu-advantage-tools package in Ubuntu: New Status in vanguards package in Ubuntu: Incomplete Status in vaultlocker package in Ubuntu: Invalid Status in virtualbox package in Ubuntu: Invalid Status in voctomix-outcasts package in Ubuntu: Invalid Status in weborf package in Ubuntu: Invalid Status in xdiagnose package in Ubuntu: Fix Released Status in cloud-init source package in Jammy: Invalid Status in dh-python source package in Jammy: Invalid Status in pagure source package in Jammy: Invalid Status in pglistener source package in Jammy: Invalid Status in policyd-rate-limit source package in Jammy: Invalid Status in postfix-mta-sts-resolver source package in Jammy: Invalid Status in powa-collector source package in Jammy: Invalid Status in prelude-correlator source package in Jammy: Invalid Status in prometheus-pgbouncer-exporter source package in Jammy: Invalid Status in prometheus-xmpp-alerts source package in Jammy: Invalid Status in pyro5 source package in Jammy: Invalid Status in pyroman source package in Jammy: Invalid Status in python3-defaults source package in Jammy: Fix Released Status in r4d source package in Jammy: Invalid Status in razercfg source package in Jammy: Invalid Status in sgt-launcher source package in Jammy: Invalid Status in sms4you source package in Jammy: Invalid Status in supervisor source package in Jammy: Invalid Status in syncplay source package in Jammy: Invalid Status in timekpr-next source package in Jammy: Invalid Status in twms source package in Jammy: Invalid Status in ubuntu-advantage-tools source package in Jammy: Invalid Status in vanguards source package in Jammy: Invalid Status in vaultlocker source package in Jammy: Invalid Status in virtualbox source package in Jammy: Invalid Status in voctomix-outcasts source package in Jammy: Invalid Status in weborf source package in Jammy: Invalid Status in xdiagnose source package in Jammy: Invalid Status in cloud-init source package in Noble: Fix R
[Touch-packages] [Bug 2075337] Please test proposed package
Hello Robie, or anyone else affected, Accepted powa-collector into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/powa- collector/1.2.0-2ubuntu0.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-noble. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Also affects: postfix-mta-sts-resolver (Ubuntu) Importance: Undecided Status: New ** Changed in: postfix-mta-sts-resolver (Ubuntu) Status: New => Invalid ** Changed in: postfix-mta-sts-resolver (Ubuntu Jammy) Status: New => Invalid ** Changed in: postfix-mta-sts-resolver (Ubuntu Noble) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dh-python in Ubuntu. https://bugs.launchpad.net/bugs/2075337 Title: [SRU] py3clean fails when using alternate character set Status in cloud-init package in Ubuntu: New Status in dh-python package in Ubuntu: Invalid Status in pagure package in Ubuntu: Invalid Status in pglistener package in Ubuntu: Invalid Status in policyd-rate-limit package in Ubuntu: Invalid Status in postfix-mta-sts-resolver package in Ubuntu: Invalid Status in powa-collector package in Ubuntu: Invalid Status in prelude-correlator package in Ubuntu: Invalid Status in prometheus-pgbouncer-exporter package in Ubuntu: Invalid Status in prometheus-xmpp-alerts package in Ubuntu: Invalid Status in pyro5 package in Ubuntu: Invalid Status in pyroman package in Ubuntu: Invalid Status in python3-defaults package in Ubuntu: Fix Released Status in r4d package in Ubuntu: Invalid Status in razercfg package in Ubuntu: Invalid Status in sgt-launcher package in Ubuntu: Fix Released Status in sms4you package in Ubuntu: Invalid Status in supervisor package in Ubuntu: Invalid Status in syncplay package in Ubuntu: Invalid Status in timekpr-next package in Ubuntu: Fix Released Status in twms package in Ubuntu: Invalid Status in ubuntu-advantage-tools package in Ubuntu: New Status in vanguards package in Ubuntu: Incomplete Status in vaultlocker package in Ubuntu: Invalid Status in virtualbox package in Ubuntu: Invalid Status in voctomix-outcasts package in Ubuntu: Invalid Status in weborf package in Ubuntu: Invalid Status in xdiagnose package in Ubuntu: Fix Released Status in cloud-init source package in Jammy: Invalid Status in dh-python source package in Jammy: Invalid Status in pagure source package in Jammy: Invalid Status in pglistener source package in Jammy: Invalid Status in policyd-rate-limit source package in Jammy: Invalid Status in postfix-mta-sts-resolver source package in Jammy: Invalid Status in powa-collector source package in Jammy: Invalid Status in prelude-correlator source package in Jammy: Invalid Status in prometheus-pgbouncer-exporter source package in Jammy: Invalid Status in prometheus-xmpp-alerts source package in Jammy: Invalid Status in pyro5 source package in Jammy: Invalid Status in pyroman source package in Jammy: Invalid Status in python3-defaults source package in Jammy: Fix Released Status in r4d source package in Jammy: Invalid Status in razercfg source package in Jammy: Invalid Status in sgt-launcher source package in Jammy: Invalid Status in sms4you source package in Jammy: Invalid Status in supervisor source package in Jammy: Invalid Status in syncplay source package in Jammy: Invalid Status in timekpr-next source package in Jammy: Invalid Status in twms source package in Jammy: Invalid Status in ubuntu-advantage-tools source package in Jammy: Invalid Status in vanguards source package in Jammy: Invalid Status in vaultlocker source package in Jammy: Invalid Status in virtualbox source package in Jammy: Invalid Status in voctomix-outcasts source package in Jammy: Invalid Status in weborf source package in Jammy: Invalid Status in xdiagnose source package in Jammy: Invalid Status in cloud-init so
[Touch-packages] [Bug 2075337] Please test proposed package
Hello Robie, or anyone else affected, Accepted policyd-rate-limit into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/policyd- rate-limit/1.0.1.1-2.1ubuntu0.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-noble. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Also affects: pglistener (Ubuntu) Importance: Undecided Status: New ** Changed in: pglistener (Ubuntu) Status: New => Invalid ** Changed in: pglistener (Ubuntu Jammy) Status: New => Invalid ** Changed in: pglistener (Ubuntu Noble) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dh-python in Ubuntu. https://bugs.launchpad.net/bugs/2075337 Title: [SRU] py3clean fails when using alternate character set Status in cloud-init package in Ubuntu: New Status in dh-python package in Ubuntu: Invalid Status in pagure package in Ubuntu: Invalid Status in pglistener package in Ubuntu: Invalid Status in policyd-rate-limit package in Ubuntu: Invalid Status in postfix-mta-sts-resolver package in Ubuntu: Invalid Status in powa-collector package in Ubuntu: Invalid Status in prelude-correlator package in Ubuntu: Invalid Status in prometheus-pgbouncer-exporter package in Ubuntu: Invalid Status in prometheus-xmpp-alerts package in Ubuntu: Invalid Status in pyro5 package in Ubuntu: Invalid Status in pyroman package in Ubuntu: Invalid Status in python3-defaults package in Ubuntu: Fix Released Status in r4d package in Ubuntu: Invalid Status in razercfg package in Ubuntu: Invalid Status in sgt-launcher package in Ubuntu: Fix Released Status in sms4you package in Ubuntu: Invalid Status in supervisor package in Ubuntu: Invalid Status in syncplay package in Ubuntu: Invalid Status in timekpr-next package in Ubuntu: Fix Released Status in twms package in Ubuntu: Invalid Status in ubuntu-advantage-tools package in Ubuntu: New Status in vanguards package in Ubuntu: Incomplete Status in vaultlocker package in Ubuntu: Invalid Status in virtualbox package in Ubuntu: Invalid Status in voctomix-outcasts package in Ubuntu: Invalid Status in weborf package in Ubuntu: Invalid Status in xdiagnose package in Ubuntu: Fix Released Status in cloud-init source package in Jammy: Invalid Status in dh-python source package in Jammy: Invalid Status in pagure source package in Jammy: Invalid Status in pglistener source package in Jammy: Invalid Status in policyd-rate-limit source package in Jammy: Invalid Status in postfix-mta-sts-resolver source package in Jammy: Invalid Status in powa-collector source package in Jammy: Invalid Status in prelude-correlator source package in Jammy: Invalid Status in prometheus-pgbouncer-exporter source package in Jammy: Invalid Status in prometheus-xmpp-alerts source package in Jammy: Invalid Status in pyro5 source package in Jammy: Invalid Status in pyroman source package in Jammy: Invalid Status in python3-defaults source package in Jammy: Fix Released Status in r4d source package in Jammy: Invalid Status in razercfg source package in Jammy: Invalid Status in sgt-launcher source package in Jammy: Invalid Status in sms4you source package in Jammy: Invalid Status in supervisor source package in Jammy: Invalid Status in syncplay source package in Jammy: Invalid Status in timekpr-next source package in Jammy: Invalid Status in twms source package in Jammy: Invalid Status in ubuntu-advantage-tools source package in Jammy: Invalid Status in vanguards source package in Jammy: Invalid Status in vaultlocker source package in Jammy: Invalid Status in virtualbox source package in Jammy: Invalid Status in voctomix-outcasts source package in Jammy: Invalid Status in weborf source package in Jammy: Invalid Status in xdiagnose source package in Jammy: Invalid Status in cloud-init source package in Noble: Fix Released Status
[Touch-packages] [Bug 2075337] Please test proposed package
Hello Robie, or anyone else affected, Accepted postfix-mta-sts-resolver into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/postfix-mta-sts- resolver/1.1.2-1.1ubuntu0.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-noble. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Also affects: policyd-rate-limit (Ubuntu) Importance: Undecided Status: New ** Changed in: policyd-rate-limit (Ubuntu) Status: New => Invalid ** Changed in: policyd-rate-limit (Ubuntu Jammy) Status: New => Invalid ** Changed in: policyd-rate-limit (Ubuntu Noble) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dh-python in Ubuntu. https://bugs.launchpad.net/bugs/2075337 Title: [SRU] py3clean fails when using alternate character set Status in cloud-init package in Ubuntu: New Status in dh-python package in Ubuntu: Invalid Status in pagure package in Ubuntu: Invalid Status in pglistener package in Ubuntu: Invalid Status in policyd-rate-limit package in Ubuntu: Invalid Status in postfix-mta-sts-resolver package in Ubuntu: Invalid Status in powa-collector package in Ubuntu: Invalid Status in prelude-correlator package in Ubuntu: Invalid Status in prometheus-pgbouncer-exporter package in Ubuntu: Invalid Status in prometheus-xmpp-alerts package in Ubuntu: Invalid Status in pyro5 package in Ubuntu: Invalid Status in pyroman package in Ubuntu: Invalid Status in python3-defaults package in Ubuntu: Fix Released Status in r4d package in Ubuntu: Invalid Status in razercfg package in Ubuntu: Invalid Status in sgt-launcher package in Ubuntu: Fix Released Status in sms4you package in Ubuntu: Invalid Status in supervisor package in Ubuntu: Invalid Status in syncplay package in Ubuntu: Invalid Status in timekpr-next package in Ubuntu: Fix Released Status in twms package in Ubuntu: Invalid Status in ubuntu-advantage-tools package in Ubuntu: New Status in vanguards package in Ubuntu: Incomplete Status in vaultlocker package in Ubuntu: Invalid Status in virtualbox package in Ubuntu: Invalid Status in voctomix-outcasts package in Ubuntu: Invalid Status in weborf package in Ubuntu: Invalid Status in xdiagnose package in Ubuntu: Fix Released Status in cloud-init source package in Jammy: Invalid Status in dh-python source package in Jammy: Invalid Status in pagure source package in Jammy: Invalid Status in pglistener source package in Jammy: Invalid Status in policyd-rate-limit source package in Jammy: Invalid Status in postfix-mta-sts-resolver source package in Jammy: Invalid Status in powa-collector source package in Jammy: Invalid Status in prelude-correlator source package in Jammy: Invalid Status in prometheus-pgbouncer-exporter source package in Jammy: Invalid Status in prometheus-xmpp-alerts source package in Jammy: Invalid Status in pyro5 source package in Jammy: Invalid Status in pyroman source package in Jammy: Invalid Status in python3-defaults source package in Jammy: Fix Released Status in r4d source package in Jammy: Invalid Status in razercfg source package in Jammy: Invalid Status in sgt-launcher source package in Jammy: Invalid Status in sms4you source package in Jammy: Invalid Status in supervisor source package in Jammy: Invalid Status in syncplay source package in Jammy: Invalid Status in timekpr-next source package in Jammy: Invalid Status in twms source package in Jammy: Invalid Status in ubuntu-advantage-tools source package in Jammy: Invalid Status in vanguards source package in Jammy: Invalid Status in vaultlocker source package in Jammy: Invalid Status in virtualbox source package in Jammy: Invalid Status in voctomix-outcasts source package in Jammy: Invalid Status in weborf source package in Jammy: Invalid Status in xdiagnose source package in Jammy: Invalid Status in cloud-init sour
[Touch-packages] [Bug 2075337] Please test proposed package
Hello Robie, or anyone else affected, Accepted pglistener into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/pglistener/5.0-2ubuntu0.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-noble. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Also affects: pagure (Ubuntu) Importance: Undecided Status: New ** Changed in: pagure (Ubuntu) Status: New => Invalid ** Changed in: pagure (Ubuntu Jammy) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dh-python in Ubuntu. https://bugs.launchpad.net/bugs/2075337 Title: [SRU] py3clean fails when using alternate character set Status in cloud-init package in Ubuntu: New Status in dh-python package in Ubuntu: Invalid Status in pagure package in Ubuntu: Invalid Status in pglistener package in Ubuntu: Invalid Status in policyd-rate-limit package in Ubuntu: Invalid Status in postfix-mta-sts-resolver package in Ubuntu: Invalid Status in powa-collector package in Ubuntu: Invalid Status in prelude-correlator package in Ubuntu: Invalid Status in prometheus-pgbouncer-exporter package in Ubuntu: Invalid Status in prometheus-xmpp-alerts package in Ubuntu: Invalid Status in pyro5 package in Ubuntu: Invalid Status in pyroman package in Ubuntu: Invalid Status in python3-defaults package in Ubuntu: Fix Released Status in r4d package in Ubuntu: Invalid Status in razercfg package in Ubuntu: Invalid Status in sgt-launcher package in Ubuntu: Fix Released Status in sms4you package in Ubuntu: Invalid Status in supervisor package in Ubuntu: Invalid Status in syncplay package in Ubuntu: Invalid Status in timekpr-next package in Ubuntu: Fix Released Status in twms package in Ubuntu: Invalid Status in ubuntu-advantage-tools package in Ubuntu: New Status in vanguards package in Ubuntu: Incomplete Status in vaultlocker package in Ubuntu: Invalid Status in virtualbox package in Ubuntu: Invalid Status in voctomix-outcasts package in Ubuntu: Invalid Status in weborf package in Ubuntu: Invalid Status in xdiagnose package in Ubuntu: Fix Released Status in cloud-init source package in Jammy: Invalid Status in dh-python source package in Jammy: Invalid Status in pagure source package in Jammy: Invalid Status in pglistener source package in Jammy: Invalid Status in policyd-rate-limit source package in Jammy: Invalid Status in postfix-mta-sts-resolver source package in Jammy: Invalid Status in powa-collector source package in Jammy: Invalid Status in prelude-correlator source package in Jammy: Invalid Status in prometheus-pgbouncer-exporter source package in Jammy: Invalid Status in prometheus-xmpp-alerts source package in Jammy: Invalid Status in pyro5 source package in Jammy: Invalid Status in pyroman source package in Jammy: Invalid Status in python3-defaults source package in Jammy: Fix Released Status in r4d source package in Jammy: Invalid Status in razercfg source package in Jammy: Invalid Status in sgt-launcher source package in Jammy: Invalid Status in sms4you source package in Jammy: Invalid Status in supervisor source package in Jammy: Invalid Status in syncplay source package in Jammy: Invalid Status in timekpr-next source package in Jammy: Invalid Status in twms source package in Jammy: Invalid Status in ubuntu-advantage-tools source package in Jammy: Invalid Status in vanguards source package in Jammy: Invalid Status in vaultlocker source package in Jammy: Invalid Status in virtualbox source package in Jammy: Invalid Status in voctomix-outcasts source package in Jammy: Invalid Status in weborf source package in Jammy: Invalid Status in xdiagnose source package in Jammy: Invalid Status in cloud-init source package in Noble: Fix Released Status in dh-python source package in Noble: Invalid Status in pagure source package in Noble: Incomplete Status in
[Touch-packages] [Bug 2075337] Re: [SRU] py3clean fails when using alternate character set
The pagure upload has unrelated noise (removed comments) in d/control. Please adjust and re-upload. Thanks! ** Changed in: pagure (Ubuntu Noble) Status: New => Incomplete ** Changed in: pagure (Ubuntu Noble) Assignee: (unassigned) => Dave Jones (waveform) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dh-python in Ubuntu. https://bugs.launchpad.net/bugs/2075337 Title: [SRU] py3clean fails when using alternate character set Status in cloud-init package in Ubuntu: New Status in dh-python package in Ubuntu: Invalid Status in pagure package in Ubuntu: Invalid Status in pglistener package in Ubuntu: Invalid Status in policyd-rate-limit package in Ubuntu: Invalid Status in postfix-mta-sts-resolver package in Ubuntu: Invalid Status in powa-collector package in Ubuntu: Invalid Status in prelude-correlator package in Ubuntu: Invalid Status in prometheus-pgbouncer-exporter package in Ubuntu: Invalid Status in prometheus-xmpp-alerts package in Ubuntu: Invalid Status in pyro5 package in Ubuntu: Invalid Status in pyroman package in Ubuntu: Invalid Status in python3-defaults package in Ubuntu: Fix Released Status in r4d package in Ubuntu: Invalid Status in razercfg package in Ubuntu: Invalid Status in sgt-launcher package in Ubuntu: Fix Released Status in sms4you package in Ubuntu: Invalid Status in supervisor package in Ubuntu: Invalid Status in syncplay package in Ubuntu: Invalid Status in timekpr-next package in Ubuntu: Fix Released Status in twms package in Ubuntu: Invalid Status in ubuntu-advantage-tools package in Ubuntu: New Status in vanguards package in Ubuntu: Incomplete Status in vaultlocker package in Ubuntu: Invalid Status in virtualbox package in Ubuntu: Invalid Status in voctomix-outcasts package in Ubuntu: Invalid Status in weborf package in Ubuntu: Invalid Status in xdiagnose package in Ubuntu: Fix Released Status in cloud-init source package in Jammy: Invalid Status in dh-python source package in Jammy: Invalid Status in pagure source package in Jammy: Invalid Status in pglistener source package in Jammy: Invalid Status in policyd-rate-limit source package in Jammy: Invalid Status in postfix-mta-sts-resolver source package in Jammy: Invalid Status in powa-collector source package in Jammy: Invalid Status in prelude-correlator source package in Jammy: Invalid Status in prometheus-pgbouncer-exporter source package in Jammy: Invalid Status in prometheus-xmpp-alerts source package in Jammy: Invalid Status in pyro5 source package in Jammy: Invalid Status in pyroman source package in Jammy: Invalid Status in python3-defaults source package in Jammy: Fix Released Status in r4d source package in Jammy: Invalid Status in razercfg source package in Jammy: Invalid Status in sgt-launcher source package in Jammy: Invalid Status in sms4you source package in Jammy: Invalid Status in supervisor source package in Jammy: Invalid Status in syncplay source package in Jammy: Invalid Status in timekpr-next source package in Jammy: Invalid Status in twms source package in Jammy: Invalid Status in ubuntu-advantage-tools source package in Jammy: Invalid Status in vanguards source package in Jammy: Invalid Status in vaultlocker source package in Jammy: Invalid Status in virtualbox source package in Jammy: Invalid Status in voctomix-outcasts source package in Jammy: Invalid Status in weborf source package in Jammy: Invalid Status in xdiagnose source package in Jammy: Invalid Status in cloud-init source package in Noble: Fix Released Status in dh-python source package in Noble: Invalid Status in pagure source package in Noble: Incomplete Status in pglistener source package in Noble: Fix Committed Status in policyd-rate-limit source package in Noble: Fix Committed Status in postfix-mta-sts-resolver source package in Noble: Fix Committed Status in powa-collector source package in Noble: Fix Committed Status in prelude-correlator source package in Noble: Fix Committed Status in prometheus-pgbouncer-exporter source package in Noble: Incomplete Status in prometheus-xmpp-alerts source package in Noble: Fix Committed Status in pyro5 source package in Noble: Incomplete Status in pyroman source package in Noble: Fix Committed Status in python3-defaults source package in Noble: Fix Released Status in r4d source package in Noble: Fix Committed Status in razercfg source package in Noble: Incomplete Status in sgt-launcher source package in Noble: Incomplete Status in sms4you source package in Noble: Fix Committed Status in supervisor source package in Noble: Fix Committed Status in syncplay source package in Noble: Incomplete Status in timekpr-next source package in Noble: Fix Committed Status in twms source package in Noble: Fix Committed Status in ubuntu-advantage-tools source package in Noble: Fi
[Touch-packages] [Bug 2075337] Re: [SRU] py3clean fails when using alternate character set
The pagekite upload has an unrelated/undescribed (?) change in d/control for Build-Depends(-Indep). Could you please clarify or re-upload with a description? Thanks! ** Also affects: pagekite (Ubuntu) Importance: Undecided Status: New ** Changed in: pagekite (Ubuntu) Status: New => Invalid ** Changed in: pagekite (Ubuntu Jammy) Status: New => Invalid ** Changed in: pagekite (Ubuntu Noble) Status: New => Incomplete ** Changed in: pagekite (Ubuntu Noble) Assignee: (unassigned) => Dave Jones (waveform) ** Also affects: ospd-openvas (Ubuntu) Importance: Undecided Status: New ** Changed in: ospd-openvas (Ubuntu) Status: New => Invalid ** Changed in: ospd-openvas (Ubuntu Jammy) Status: New => Invalid ** Changed in: ospd-openvas (Ubuntu Noble) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dh-python in Ubuntu. https://bugs.launchpad.net/bugs/2075337 Title: [SRU] py3clean fails when using alternate character set Status in cloud-init package in Ubuntu: New Status in dh-python package in Ubuntu: Invalid Status in openscap-daemon package in Ubuntu: New Status in ospd-openvas package in Ubuntu: Invalid Status in pagekite package in Ubuntu: Invalid Status in pagure package in Ubuntu: Invalid Status in pglistener package in Ubuntu: Invalid Status in policyd-rate-limit package in Ubuntu: Invalid Status in postfix-mta-sts-resolver package in Ubuntu: Invalid Status in powa-collector package in Ubuntu: Invalid Status in prelude-correlator package in Ubuntu: Invalid Status in prometheus-pgbouncer-exporter package in Ubuntu: Invalid Status in prometheus-xmpp-alerts package in Ubuntu: Invalid Status in pyro5 package in Ubuntu: Invalid Status in pyroman package in Ubuntu: Invalid Status in python3-defaults package in Ubuntu: Fix Released Status in r4d package in Ubuntu: Invalid Status in razercfg package in Ubuntu: Invalid Status in sgt-launcher package in Ubuntu: Fix Released Status in sms4you package in Ubuntu: Invalid Status in supervisor package in Ubuntu: Invalid Status in syncplay package in Ubuntu: Invalid Status in timekpr-next package in Ubuntu: Fix Released Status in twms package in Ubuntu: Invalid Status in ubuntu-advantage-tools package in Ubuntu: New Status in vanguards package in Ubuntu: Incomplete Status in vaultlocker package in Ubuntu: Invalid Status in virtualbox package in Ubuntu: Invalid Status in voctomix-outcasts package in Ubuntu: Invalid Status in weborf package in Ubuntu: Invalid Status in xdiagnose package in Ubuntu: Fix Released Status in cloud-init source package in Jammy: Invalid Status in dh-python source package in Jammy: Invalid Status in openscap-daemon source package in Jammy: New Status in ospd-openvas source package in Jammy: Invalid Status in pagekite source package in Jammy: Invalid Status in pagure source package in Jammy: Invalid Status in pglistener source package in Jammy: Invalid Status in policyd-rate-limit source package in Jammy: Invalid Status in postfix-mta-sts-resolver source package in Jammy: Invalid Status in powa-collector source package in Jammy: Invalid Status in prelude-correlator source package in Jammy: Invalid Status in prometheus-pgbouncer-exporter source package in Jammy: Invalid Status in prometheus-xmpp-alerts source package in Jammy: Invalid Status in pyro5 source package in Jammy: Invalid Status in pyroman source package in Jammy: Invalid Status in python3-defaults source package in Jammy: Fix Released Status in r4d source package in Jammy: Invalid Status in razercfg source package in Jammy: Invalid Status in sgt-launcher source package in Jammy: Invalid Status in sms4you source package in Jammy: Invalid Status in supervisor source package in Jammy: Invalid Status in syncplay source package in Jammy: Invalid Status in timekpr-next source package in Jammy: Invalid Status in twms source package in Jammy: Invalid Status in ubuntu-advantage-tools source package in Jammy: Invalid Status in vanguards source package in Jammy: Invalid Status in vaultlocker source package in Jammy: Invalid Status in virtualbox source package in Jammy: Invalid Status in voctomix-outcasts source package in Jammy: Invalid Status in weborf source package in Jammy: Invalid Status in xdiagnose source package in Jammy: Invalid Status in cloud-init source package in Noble: Fix Released Status in dh-python source package in Noble: Invalid Status in openscap-daemon source package in Noble: New Status in ospd-openvas source package in Noble: Fix Committed Status in pagekite source package in Noble: Incomplete Status in pagure source package in Noble: Incomplete Status in pglistener source package in Noble: Fix Committed Status in policyd-rate-limit source package in Noble: Fix Commit
[Touch-packages] [Bug 2075337] Please test proposed package
Hello Robie, or anyone else affected, Accepted ospd-openvas into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ospd- openvas/22.6.2-1ubuntu0.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-noble. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Also affects: openscap-daemon (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dh-python in Ubuntu. https://bugs.launchpad.net/bugs/2075337 Title: [SRU] py3clean fails when using alternate character set Status in cloud-init package in Ubuntu: New Status in dh-python package in Ubuntu: Invalid Status in openscap-daemon package in Ubuntu: New Status in ospd-openvas package in Ubuntu: Invalid Status in pagekite package in Ubuntu: Invalid Status in pagure package in Ubuntu: Invalid Status in pglistener package in Ubuntu: Invalid Status in policyd-rate-limit package in Ubuntu: Invalid Status in postfix-mta-sts-resolver package in Ubuntu: Invalid Status in powa-collector package in Ubuntu: Invalid Status in prelude-correlator package in Ubuntu: Invalid Status in prometheus-pgbouncer-exporter package in Ubuntu: Invalid Status in prometheus-xmpp-alerts package in Ubuntu: Invalid Status in pyro5 package in Ubuntu: Invalid Status in pyroman package in Ubuntu: Invalid Status in python3-defaults package in Ubuntu: Fix Released Status in r4d package in Ubuntu: Invalid Status in razercfg package in Ubuntu: Invalid Status in sgt-launcher package in Ubuntu: Fix Released Status in sms4you package in Ubuntu: Invalid Status in supervisor package in Ubuntu: Invalid Status in syncplay package in Ubuntu: Invalid Status in timekpr-next package in Ubuntu: Fix Released Status in twms package in Ubuntu: Invalid Status in ubuntu-advantage-tools package in Ubuntu: New Status in vanguards package in Ubuntu: Incomplete Status in vaultlocker package in Ubuntu: Invalid Status in virtualbox package in Ubuntu: Invalid Status in voctomix-outcasts package in Ubuntu: Invalid Status in weborf package in Ubuntu: Invalid Status in xdiagnose package in Ubuntu: Fix Released Status in cloud-init source package in Jammy: Invalid Status in dh-python source package in Jammy: Invalid Status in openscap-daemon source package in Jammy: New Status in ospd-openvas source package in Jammy: Invalid Status in pagekite source package in Jammy: Invalid Status in pagure source package in Jammy: Invalid Status in pglistener source package in Jammy: Invalid Status in policyd-rate-limit source package in Jammy: Invalid Status in postfix-mta-sts-resolver source package in Jammy: Invalid Status in powa-collector source package in Jammy: Invalid Status in prelude-correlator source package in Jammy: Invalid Status in prometheus-pgbouncer-exporter source package in Jammy: Invalid Status in prometheus-xmpp-alerts source package in Jammy: Invalid Status in pyro5 source package in Jammy: Invalid Status in pyroman source package in Jammy: Invalid Status in python3-defaults source package in Jammy: Fix Released Status in r4d source package in Jammy: Invalid Status in razercfg source package in Jammy: Invalid Status in sgt-launcher source package in Jammy: Invalid Status in sms4you source package in Jammy: Invalid Status in supervisor source package in Jammy: Invalid Status in syncplay source package in Jammy: Invalid Status in timekpr-next source package in Jammy: Invalid Status in twms source package in Jammy: Invalid Status in ubuntu-advantage-tools source package in Jammy: Invalid Status in vanguards source package in Jammy: Invalid Status in vaultlocker source package in Jammy: Invalid Status in virtualbox source package in Jammy: Invalid Status in voctomix-outcasts source package in Jammy: Invalid Status in weborf source package in Jammy: Invalid Status in xdiagnose source p
[Touch-packages] [Bug 2075337] Re: [SRU] py3clean fails when using alternate character set
The upload for openscap-daemon has a change in d/control not described in d/changelog, which is described in Oracular: ` * d/control: Remove obsolete python3-distutils` Could you please re-upload with a description/clarification? AFAIK it is correct, since python 3.12 no longer ships python3-distutils: - Jammy: https://launchpad.net/ubuntu/jammy/+source/python3-stdlib-extensions (present) - Noble: https://launchpad.net/ubuntu/noble/+source/python3-stdlib-extensions (not present) ** Changed in: openscap-daemon (Ubuntu) Status: New => Invalid ** Changed in: openscap-daemon (Ubuntu Jammy) Status: New => Invalid ** Changed in: openscap-daemon (Ubuntu Noble) Status: New => Incomplete ** Changed in: openscap-daemon (Ubuntu Noble) Assignee: (unassigned) => Dave Jones (waveform) ** Also affects: onionprobe (Ubuntu) Importance: Undecided Status: New ** Changed in: onionprobe (Ubuntu) Status: New => Invalid ** Changed in: onionprobe (Ubuntu Jammy) Status: New => Invalid ** Changed in: onionprobe (Ubuntu Noble) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dh-python in Ubuntu. https://bugs.launchpad.net/bugs/2075337 Title: [SRU] py3clean fails when using alternate character set Status in cloud-init package in Ubuntu: New Status in dh-python package in Ubuntu: Invalid Status in notus-scanner package in Ubuntu: Invalid Status in nrpe-ng package in Ubuntu: Invalid Status in onionprobe package in Ubuntu: Invalid Status in openscap-daemon package in Ubuntu: Invalid Status in ospd-openvas package in Ubuntu: Invalid Status in pagekite package in Ubuntu: Invalid Status in pagure package in Ubuntu: Invalid Status in pglistener package in Ubuntu: Invalid Status in policyd-rate-limit package in Ubuntu: Invalid Status in postfix-mta-sts-resolver package in Ubuntu: Invalid Status in powa-collector package in Ubuntu: Invalid Status in prelude-correlator package in Ubuntu: Invalid Status in prometheus-pgbouncer-exporter package in Ubuntu: Invalid Status in prometheus-xmpp-alerts package in Ubuntu: Invalid Status in pyro5 package in Ubuntu: Invalid Status in pyroman package in Ubuntu: Invalid Status in python3-defaults package in Ubuntu: Fix Released Status in r4d package in Ubuntu: Invalid Status in razercfg package in Ubuntu: Invalid Status in sgt-launcher package in Ubuntu: Fix Released Status in sms4you package in Ubuntu: Invalid Status in supervisor package in Ubuntu: Invalid Status in syncplay package in Ubuntu: Invalid Status in timekpr-next package in Ubuntu: Fix Released Status in twms package in Ubuntu: Invalid Status in ubuntu-advantage-tools package in Ubuntu: New Status in vanguards package in Ubuntu: Incomplete Status in vaultlocker package in Ubuntu: Invalid Status in virtualbox package in Ubuntu: Invalid Status in voctomix-outcasts package in Ubuntu: Invalid Status in weborf package in Ubuntu: Invalid Status in xdiagnose package in Ubuntu: Fix Released Status in cloud-init source package in Jammy: Invalid Status in dh-python source package in Jammy: Invalid Status in notus-scanner source package in Jammy: Invalid Status in nrpe-ng source package in Jammy: Invalid Status in onionprobe source package in Jammy: Invalid Status in openscap-daemon source package in Jammy: Invalid Status in ospd-openvas source package in Jammy: Invalid Status in pagekite source package in Jammy: Invalid Status in pagure source package in Jammy: Invalid Status in pglistener source package in Jammy: Invalid Status in policyd-rate-limit source package in Jammy: Invalid Status in postfix-mta-sts-resolver source package in Jammy: Invalid Status in powa-collector source package in Jammy: Invalid Status in prelude-correlator source package in Jammy: Invalid Status in prometheus-pgbouncer-exporter source package in Jammy: Invalid Status in prometheus-xmpp-alerts source package in Jammy: Invalid Status in pyro5 source package in Jammy: Invalid Status in pyroman source package in Jammy: Invalid Status in python3-defaults source package in Jammy: Fix Released Status in r4d source package in Jammy: Invalid Status in razercfg source package in Jammy: Invalid Status in sgt-launcher source package in Jammy: Invalid Status in sms4you source package in Jammy: Invalid Status in supervisor source package in Jammy: Invalid Status in syncplay source package in Jammy: Invalid Status in timekpr-next source package in Jammy: Invalid Status in twms source package in Jammy: Invalid Status in ubuntu-advantage-tools source package in Jammy: Invalid Status in vanguards source package in Jammy: Invalid Status in vaultlocker source package in Jammy: Invalid Status in virtualbox source package in Jammy: Invalid Status in voctomix-outcasts source package in Jammy: Inv
[Touch-packages] [Bug 2075337] Please test proposed package
Hello Robie, or anyone else affected, Accepted onionprobe into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/onionprobe/1.1.2+ds-1ubuntu0.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-noble. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Also affects: nrpe-ng (Ubuntu) Importance: Undecided Status: New ** Changed in: nrpe-ng (Ubuntu) Status: New => Invalid ** Changed in: nrpe-ng (Ubuntu Jammy) Status: New => Invalid ** Changed in: nrpe-ng (Ubuntu Noble) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dh-python in Ubuntu. https://bugs.launchpad.net/bugs/2075337 Title: [SRU] py3clean fails when using alternate character set Status in cloud-init package in Ubuntu: New Status in dh-python package in Ubuntu: Invalid Status in notus-scanner package in Ubuntu: Invalid Status in nrpe-ng package in Ubuntu: Invalid Status in onionprobe package in Ubuntu: Invalid Status in openscap-daemon package in Ubuntu: Invalid Status in ospd-openvas package in Ubuntu: Invalid Status in pagekite package in Ubuntu: Invalid Status in pagure package in Ubuntu: Invalid Status in pglistener package in Ubuntu: Invalid Status in policyd-rate-limit package in Ubuntu: Invalid Status in postfix-mta-sts-resolver package in Ubuntu: Invalid Status in powa-collector package in Ubuntu: Invalid Status in prelude-correlator package in Ubuntu: Invalid Status in prometheus-pgbouncer-exporter package in Ubuntu: Invalid Status in prometheus-xmpp-alerts package in Ubuntu: Invalid Status in pyro5 package in Ubuntu: Invalid Status in pyroman package in Ubuntu: Invalid Status in python3-defaults package in Ubuntu: Fix Released Status in r4d package in Ubuntu: Invalid Status in razercfg package in Ubuntu: Invalid Status in sgt-launcher package in Ubuntu: Fix Released Status in sms4you package in Ubuntu: Invalid Status in supervisor package in Ubuntu: Invalid Status in syncplay package in Ubuntu: Invalid Status in timekpr-next package in Ubuntu: Fix Released Status in twms package in Ubuntu: Invalid Status in ubuntu-advantage-tools package in Ubuntu: New Status in vanguards package in Ubuntu: Incomplete Status in vaultlocker package in Ubuntu: Invalid Status in virtualbox package in Ubuntu: Invalid Status in voctomix-outcasts package in Ubuntu: Invalid Status in weborf package in Ubuntu: Invalid Status in xdiagnose package in Ubuntu: Fix Released Status in cloud-init source package in Jammy: Invalid Status in dh-python source package in Jammy: Invalid Status in notus-scanner source package in Jammy: Invalid Status in nrpe-ng source package in Jammy: Invalid Status in onionprobe source package in Jammy: Invalid Status in openscap-daemon source package in Jammy: Invalid Status in ospd-openvas source package in Jammy: Invalid Status in pagekite source package in Jammy: Invalid Status in pagure source package in Jammy: Invalid Status in pglistener source package in Jammy: Invalid Status in policyd-rate-limit source package in Jammy: Invalid Status in postfix-mta-sts-resolver source package in Jammy: Invalid Status in powa-collector source package in Jammy: Invalid Status in prelude-correlator source package in Jammy: Invalid Status in prometheus-pgbouncer-exporter source package in Jammy: Invalid Status in prometheus-xmpp-alerts source package in Jammy: Invalid Status in pyro5 source package in Jammy: Invalid Status in pyroman source package in Jammy: Invalid Status in python3-defaults source package in Jammy: Fix Released Status in r4d source package in Jammy: Invalid Status in razercfg source package in Jammy: Invalid Status in sgt-launcher source package in Jammy: Invalid Status in sms4you source package in Jammy: Invalid Status in supervisor source package in Jammy: Invalid Status in syncplay
[Touch-packages] [Bug 2075337] Please test proposed package
Hello Robie, or anyone else affected, Accepted nrpe-ng into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/nrpe- ng/0.2.0-1.1ubuntu0.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-noble. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Also affects: notus-scanner (Ubuntu) Importance: Undecided Status: New ** Changed in: notus-scanner (Ubuntu) Status: New => Invalid ** Changed in: notus-scanner (Ubuntu Jammy) Status: New => Invalid ** Changed in: notus-scanner (Ubuntu Noble) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dh-python in Ubuntu. https://bugs.launchpad.net/bugs/2075337 Title: [SRU] py3clean fails when using alternate character set Status in cloud-init package in Ubuntu: New Status in dh-python package in Ubuntu: Invalid Status in notus-scanner package in Ubuntu: Invalid Status in nrpe-ng package in Ubuntu: Invalid Status in onionprobe package in Ubuntu: Invalid Status in openscap-daemon package in Ubuntu: Invalid Status in ospd-openvas package in Ubuntu: Invalid Status in pagekite package in Ubuntu: Invalid Status in pagure package in Ubuntu: Invalid Status in pglistener package in Ubuntu: Invalid Status in policyd-rate-limit package in Ubuntu: Invalid Status in postfix-mta-sts-resolver package in Ubuntu: Invalid Status in powa-collector package in Ubuntu: Invalid Status in prelude-correlator package in Ubuntu: Invalid Status in prometheus-pgbouncer-exporter package in Ubuntu: Invalid Status in prometheus-xmpp-alerts package in Ubuntu: Invalid Status in pyro5 package in Ubuntu: Invalid Status in pyroman package in Ubuntu: Invalid Status in python3-defaults package in Ubuntu: Fix Released Status in r4d package in Ubuntu: Invalid Status in razercfg package in Ubuntu: Invalid Status in sgt-launcher package in Ubuntu: Fix Released Status in sms4you package in Ubuntu: Invalid Status in supervisor package in Ubuntu: Invalid Status in syncplay package in Ubuntu: Invalid Status in timekpr-next package in Ubuntu: Fix Released Status in twms package in Ubuntu: Invalid Status in ubuntu-advantage-tools package in Ubuntu: New Status in vanguards package in Ubuntu: Incomplete Status in vaultlocker package in Ubuntu: Invalid Status in virtualbox package in Ubuntu: Invalid Status in voctomix-outcasts package in Ubuntu: Invalid Status in weborf package in Ubuntu: Invalid Status in xdiagnose package in Ubuntu: Fix Released Status in cloud-init source package in Jammy: Invalid Status in dh-python source package in Jammy: Invalid Status in notus-scanner source package in Jammy: Invalid Status in nrpe-ng source package in Jammy: Invalid Status in onionprobe source package in Jammy: Invalid Status in openscap-daemon source package in Jammy: Invalid Status in ospd-openvas source package in Jammy: Invalid Status in pagekite source package in Jammy: Invalid Status in pagure source package in Jammy: Invalid Status in pglistener source package in Jammy: Invalid Status in policyd-rate-limit source package in Jammy: Invalid Status in postfix-mta-sts-resolver source package in Jammy: Invalid Status in powa-collector source package in Jammy: Invalid Status in prelude-correlator source package in Jammy: Invalid Status in prometheus-pgbouncer-exporter source package in Jammy: Invalid Status in prometheus-xmpp-alerts source package in Jammy: Invalid Status in pyro5 source package in Jammy: Invalid Status in pyroman source package in Jammy: Invalid Status in python3-defaults source package in Jammy: Fix Released Status in r4d source package in Jammy: Invalid Status in razercfg source package in Jammy: Invalid Status in sgt-launcher source package in Jammy: Invalid Status in sms4you source package in Jammy: Invalid Status in supervisor source package in Jammy: Invalid S
[Touch-packages] [Bug 2075337] Please test proposed package
Hello Robie, or anyone else affected, Accepted notus-scanner into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/notus- scanner/22.6.2-1ubuntu0.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-noble. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dh-python in Ubuntu. https://bugs.launchpad.net/bugs/2075337 Title: [SRU] py3clean fails when using alternate character set Status in cloud-init package in Ubuntu: New Status in dh-python package in Ubuntu: Invalid Status in notus-scanner package in Ubuntu: Invalid Status in nrpe-ng package in Ubuntu: Invalid Status in onionprobe package in Ubuntu: Invalid Status in openscap-daemon package in Ubuntu: Invalid Status in ospd-openvas package in Ubuntu: Invalid Status in pagekite package in Ubuntu: Invalid Status in pagure package in Ubuntu: Invalid Status in pglistener package in Ubuntu: Invalid Status in policyd-rate-limit package in Ubuntu: Invalid Status in postfix-mta-sts-resolver package in Ubuntu: Invalid Status in powa-collector package in Ubuntu: Invalid Status in prelude-correlator package in Ubuntu: Invalid Status in prometheus-pgbouncer-exporter package in Ubuntu: Invalid Status in prometheus-xmpp-alerts package in Ubuntu: Invalid Status in pyro5 package in Ubuntu: Invalid Status in pyroman package in Ubuntu: Invalid Status in python3-defaults package in Ubuntu: Fix Released Status in r4d package in Ubuntu: Invalid Status in razercfg package in Ubuntu: Invalid Status in sgt-launcher package in Ubuntu: Fix Released Status in sms4you package in Ubuntu: Invalid Status in supervisor package in Ubuntu: Invalid Status in syncplay package in Ubuntu: Invalid Status in timekpr-next package in Ubuntu: Fix Released Status in twms package in Ubuntu: Invalid Status in ubuntu-advantage-tools package in Ubuntu: New Status in vanguards package in Ubuntu: Incomplete Status in vaultlocker package in Ubuntu: Invalid Status in virtualbox package in Ubuntu: Invalid Status in voctomix-outcasts package in Ubuntu: Invalid Status in weborf package in Ubuntu: Invalid Status in xdiagnose package in Ubuntu: Fix Released Status in cloud-init source package in Jammy: Invalid Status in dh-python source package in Jammy: Invalid Status in notus-scanner source package in Jammy: Invalid Status in nrpe-ng source package in Jammy: Invalid Status in onionprobe source package in Jammy: Invalid Status in openscap-daemon source package in Jammy: Invalid Status in ospd-openvas source package in Jammy: Invalid Status in pagekite source package in Jammy: Invalid Status in pagure source package in Jammy: Invalid Status in pglistener source package in Jammy: Invalid Status in policyd-rate-limit source package in Jammy: Invalid Status in postfix-mta-sts-resolver source package in Jammy: Invalid Status in powa-collector source package in Jammy: Invalid Status in prelude-correlator source package in Jammy: Invalid Status in prometheus-pgbouncer-exporter source package in Jammy: Invalid Status in prometheus-xmpp-alerts source package in Jammy: Invalid Status in pyro5 source package in Jammy: Invalid Status in pyroman source package in Jammy: Invalid Status in python3-defaults source package in Jammy: Fix Released Status in r4d source package in Jammy: Invalid Status in razercfg source package in Jammy: Invalid Status in sgt-launcher source package in Jammy: Invalid Status in sms4you source package in Jammy: Invalid Status in supervisor source package in Jammy: Invalid Status in syncplay source package in Jammy: Invalid Status in timekpr-next source package in Jammy: Invalid Status in twms source package in Jammy: Invalid Status in ubuntu-advantage-tools source package in Jammy: Invalid Status in vanguards source package in Jammy: Invalid Status in vault
[Touch-packages] [Bug 2075337] Re: [SRU] py3clean fails when using alternate character set
For the nordugrid-arc upload: The change in `Breaks:` targets the `Package: nordugrid-arc-arex` and not `Package: python3-nordugrid-arc` (and the latter doesn't depend on the former) -- is that correct / on purpose? Sorry if I'm missing something, but IIUIC, the `Breaks` on the new python3-minimal/defaults should ensure that python version is installed before python module packages are installed (as their install triggers py3compile/py3clean). Also, there are many indentation/spacing changes which aren't required; ideally those should not be present (even if they're helpful :/). Considering the question above, if this requires a re-upload, could you please address this too, while you're at it? Thanks! ** Also affects: nordugrid-arc (Ubuntu) Importance: Undecided Status: New ** Changed in: nordugrid-arc (Ubuntu) Status: New => Invalid ** Changed in: nordugrid-arc (Ubuntu Jammy) Status: New => Invalid ** Changed in: nordugrid-arc (Ubuntu Noble) Status: New => Incomplete ** Changed in: nordugrid-arc (Ubuntu Noble) Assignee: (unassigned) => Dave Jones (waveform) ** Also affects: mpd-sima (Ubuntu) Importance: Undecided Status: New ** Changed in: mpd-sima (Ubuntu) Status: New => Invalid ** Changed in: mpd-sima (Ubuntu Jammy) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dh-python in Ubuntu. https://bugs.launchpad.net/bugs/2075337 Title: [SRU] py3clean fails when using alternate character set Status in cloud-init package in Ubuntu: New Status in dh-python package in Ubuntu: Invalid Status in logdata-anomaly-miner package in Ubuntu: Invalid Status in lomiri package in Ubuntu: Invalid Status in mailman3 package in Ubuntu: Invalid Status in matrix-sydent package in Ubuntu: Invalid Status in mom package in Ubuntu: Invalid Status in mopidy package in Ubuntu: Invalid Status in mpd-sima package in Ubuntu: Invalid Status in nordugrid-arc package in Ubuntu: Invalid Status in notus-scanner package in Ubuntu: Invalid Status in nrpe-ng package in Ubuntu: Invalid Status in onionprobe package in Ubuntu: Invalid Status in openscap-daemon package in Ubuntu: Invalid Status in ospd-openvas package in Ubuntu: Invalid Status in pagekite package in Ubuntu: Invalid Status in pagure package in Ubuntu: Invalid Status in pglistener package in Ubuntu: Invalid Status in policyd-rate-limit package in Ubuntu: Invalid Status in postfix-mta-sts-resolver package in Ubuntu: Invalid Status in powa-collector package in Ubuntu: Invalid Status in prelude-correlator package in Ubuntu: Invalid Status in prometheus-pgbouncer-exporter package in Ubuntu: Invalid Status in prometheus-xmpp-alerts package in Ubuntu: Invalid Status in pyro5 package in Ubuntu: Invalid Status in pyroman package in Ubuntu: Invalid Status in python3-defaults package in Ubuntu: Fix Released Status in r4d package in Ubuntu: Invalid Status in razercfg package in Ubuntu: Invalid Status in sgt-launcher package in Ubuntu: Fix Released Status in sms4you package in Ubuntu: Invalid Status in supervisor package in Ubuntu: Invalid Status in syncplay package in Ubuntu: Invalid Status in timekpr-next package in Ubuntu: Fix Released Status in twms package in Ubuntu: Invalid Status in ubuntu-advantage-tools package in Ubuntu: New Status in vanguards package in Ubuntu: Incomplete Status in vaultlocker package in Ubuntu: Invalid Status in virtualbox package in Ubuntu: Invalid Status in voctomix-outcasts package in Ubuntu: Invalid Status in weborf package in Ubuntu: Invalid Status in xdiagnose package in Ubuntu: Fix Released Status in cloud-init source package in Jammy: Invalid Status in dh-python source package in Jammy: Invalid Status in logdata-anomaly-miner source package in Jammy: Invalid Status in lomiri source package in Jammy: Invalid Status in mailman3 source package in Jammy: Invalid Status in matrix-sydent source package in Jammy: Invalid Status in mom source package in Jammy: Invalid Status in mopidy source package in Jammy: Invalid Status in mpd-sima source package in Jammy: Invalid Status in nordugrid-arc source package in Jammy: Invalid Status in notus-scanner source package in Jammy: Invalid Status in nrpe-ng source package in Jammy: Invalid Status in onionprobe source package in Jammy: Invalid Status in openscap-daemon source package in Jammy: Invalid Status in ospd-openvas source package in Jammy: Invalid Status in pagekite source package in Jammy: Invalid Status in pagure source package in Jammy: Invalid Status in pglistener source package in Jammy: Invalid Status in policyd-rate-limit source package in Jammy: Invalid Status in postfix-mta-sts-resolver source package in Jammy: Invalid Status in powa-collector source package in Jammy: Invalid Status in prelude-correlator source pack
[Touch-packages] [Bug 2075337] Please test proposed package
Hello Robie, or anyone else affected, Accepted mopidy into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mopidy/3.4.2-1ubuntu0.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-noble. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Also affects: mom (Ubuntu) Importance: Undecided Status: New ** Changed in: mom (Ubuntu) Status: New => Invalid ** Changed in: mom (Ubuntu Jammy) Status: New => Invalid ** Changed in: mom (Ubuntu Noble) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dh-python in Ubuntu. https://bugs.launchpad.net/bugs/2075337 Title: [SRU] py3clean fails when using alternate character set Status in cloud-init package in Ubuntu: New Status in dh-python package in Ubuntu: Invalid Status in logdata-anomaly-miner package in Ubuntu: Invalid Status in lomiri package in Ubuntu: Invalid Status in mailman3 package in Ubuntu: Invalid Status in matrix-sydent package in Ubuntu: Invalid Status in mom package in Ubuntu: Invalid Status in mopidy package in Ubuntu: Invalid Status in mpd-sima package in Ubuntu: Invalid Status in nordugrid-arc package in Ubuntu: Invalid Status in notus-scanner package in Ubuntu: Invalid Status in nrpe-ng package in Ubuntu: Invalid Status in onionprobe package in Ubuntu: Invalid Status in openscap-daemon package in Ubuntu: Invalid Status in ospd-openvas package in Ubuntu: Invalid Status in pagekite package in Ubuntu: Invalid Status in pagure package in Ubuntu: Invalid Status in pglistener package in Ubuntu: Invalid Status in policyd-rate-limit package in Ubuntu: Invalid Status in postfix-mta-sts-resolver package in Ubuntu: Invalid Status in powa-collector package in Ubuntu: Invalid Status in prelude-correlator package in Ubuntu: Invalid Status in prometheus-pgbouncer-exporter package in Ubuntu: Invalid Status in prometheus-xmpp-alerts package in Ubuntu: Invalid Status in pyro5 package in Ubuntu: Invalid Status in pyroman package in Ubuntu: Invalid Status in python3-defaults package in Ubuntu: Fix Released Status in r4d package in Ubuntu: Invalid Status in razercfg package in Ubuntu: Invalid Status in sgt-launcher package in Ubuntu: Fix Released Status in sms4you package in Ubuntu: Invalid Status in supervisor package in Ubuntu: Invalid Status in syncplay package in Ubuntu: Invalid Status in timekpr-next package in Ubuntu: Fix Released Status in twms package in Ubuntu: Invalid Status in ubuntu-advantage-tools package in Ubuntu: New Status in vanguards package in Ubuntu: Incomplete Status in vaultlocker package in Ubuntu: Invalid Status in virtualbox package in Ubuntu: Invalid Status in voctomix-outcasts package in Ubuntu: Invalid Status in weborf package in Ubuntu: Invalid Status in xdiagnose package in Ubuntu: Fix Released Status in cloud-init source package in Jammy: Invalid Status in dh-python source package in Jammy: Invalid Status in logdata-anomaly-miner source package in Jammy: Invalid Status in lomiri source package in Jammy: Invalid Status in mailman3 source package in Jammy: Invalid Status in matrix-sydent source package in Jammy: Invalid Status in mom source package in Jammy: Invalid Status in mopidy source package in Jammy: Invalid Status in mpd-sima source package in Jammy: Invalid Status in nordugrid-arc source package in Jammy: Invalid Status in notus-scanner source package in Jammy: Invalid Status in nrpe-ng source package in Jammy: Invalid Status in onionprobe source package in Jammy: Invalid Status in openscap-daemon source package in Jammy: Invalid Status in ospd-openvas source package in Jammy: Invalid Status in pagekite source package in Jammy: Invalid Status in pagure source package in Jammy: Invalid Status in pglistener source package in Jammy: Invalid Status in policyd-rate-limit source package
[Touch-packages] [Bug 2075337] Re: [SRU] py3clean fails when using alternate character set
The mpd-sima upload has an unrelated/undescribed (?) changes in d/control for Build-Depends(-Indep) and a comment removed. Could you please clarify or re-upload with a description? Thanks! ** Changed in: mpd-sima (Ubuntu Noble) Status: New => Incomplete ** Changed in: mpd-sima (Ubuntu Noble) Assignee: (unassigned) => Dave Jones (waveform) ** Also affects: mopidy (Ubuntu) Importance: Undecided Status: New ** Changed in: mopidy (Ubuntu) Status: New => Invalid ** Changed in: mopidy (Ubuntu Jammy) Status: New => Invalid ** Changed in: mopidy (Ubuntu Noble) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dh-python in Ubuntu. https://bugs.launchpad.net/bugs/2075337 Title: [SRU] py3clean fails when using alternate character set Status in cloud-init package in Ubuntu: New Status in dh-python package in Ubuntu: Invalid Status in logdata-anomaly-miner package in Ubuntu: Invalid Status in lomiri package in Ubuntu: Invalid Status in mailman3 package in Ubuntu: Invalid Status in matrix-sydent package in Ubuntu: Invalid Status in mom package in Ubuntu: Invalid Status in mopidy package in Ubuntu: Invalid Status in mpd-sima package in Ubuntu: Invalid Status in nordugrid-arc package in Ubuntu: Invalid Status in notus-scanner package in Ubuntu: Invalid Status in nrpe-ng package in Ubuntu: Invalid Status in onionprobe package in Ubuntu: Invalid Status in openscap-daemon package in Ubuntu: Invalid Status in ospd-openvas package in Ubuntu: Invalid Status in pagekite package in Ubuntu: Invalid Status in pagure package in Ubuntu: Invalid Status in pglistener package in Ubuntu: Invalid Status in policyd-rate-limit package in Ubuntu: Invalid Status in postfix-mta-sts-resolver package in Ubuntu: Invalid Status in powa-collector package in Ubuntu: Invalid Status in prelude-correlator package in Ubuntu: Invalid Status in prometheus-pgbouncer-exporter package in Ubuntu: Invalid Status in prometheus-xmpp-alerts package in Ubuntu: Invalid Status in pyro5 package in Ubuntu: Invalid Status in pyroman package in Ubuntu: Invalid Status in python3-defaults package in Ubuntu: Fix Released Status in r4d package in Ubuntu: Invalid Status in razercfg package in Ubuntu: Invalid Status in sgt-launcher package in Ubuntu: Fix Released Status in sms4you package in Ubuntu: Invalid Status in supervisor package in Ubuntu: Invalid Status in syncplay package in Ubuntu: Invalid Status in timekpr-next package in Ubuntu: Fix Released Status in twms package in Ubuntu: Invalid Status in ubuntu-advantage-tools package in Ubuntu: New Status in vanguards package in Ubuntu: Incomplete Status in vaultlocker package in Ubuntu: Invalid Status in virtualbox package in Ubuntu: Invalid Status in voctomix-outcasts package in Ubuntu: Invalid Status in weborf package in Ubuntu: Invalid Status in xdiagnose package in Ubuntu: Fix Released Status in cloud-init source package in Jammy: Invalid Status in dh-python source package in Jammy: Invalid Status in logdata-anomaly-miner source package in Jammy: Invalid Status in lomiri source package in Jammy: Invalid Status in mailman3 source package in Jammy: Invalid Status in matrix-sydent source package in Jammy: Invalid Status in mom source package in Jammy: Invalid Status in mopidy source package in Jammy: Invalid Status in mpd-sima source package in Jammy: Invalid Status in nordugrid-arc source package in Jammy: Invalid Status in notus-scanner source package in Jammy: Invalid Status in nrpe-ng source package in Jammy: Invalid Status in onionprobe source package in Jammy: Invalid Status in openscap-daemon source package in Jammy: Invalid Status in ospd-openvas source package in Jammy: Invalid Status in pagekite source package in Jammy: Invalid Status in pagure source package in Jammy: Invalid Status in pglistener source package in Jammy: Invalid Status in policyd-rate-limit source package in Jammy: Invalid Status in postfix-mta-sts-resolver source package in Jammy: Invalid Status in powa-collector source package in Jammy: Invalid Status in prelude-correlator source package in Jammy: Invalid Status in prometheus-pgbouncer-exporter source package in Jammy: Invalid Status in prometheus-xmpp-alerts source package in Jammy: Invalid Status in pyro5 source package in Jammy: Invalid Status in pyroman source package in Jammy: Invalid Status in python3-defaults source package in Jammy: Fix Released Status in r4d source package in Jammy: Invalid Status in razercfg source package in Jammy: Invalid Status in sgt-launcher source package in Jammy: Invalid Status in sms4you source package in Jammy: Invalid Status in supervisor source package in Jammy: Invalid Status in syncplay source package in Jammy: Invalid Status in timekpr-next source packag
[Touch-packages] [Bug 2075337] Please test proposed package
Hello Robie, or anyone else affected, Accepted mom into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mom/0.6.0-2.1ubuntu0.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-noble. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Also affects: matrix-sydent (Ubuntu) Importance: Undecided Status: New ** Changed in: matrix-sydent (Ubuntu) Status: New => Invalid ** Changed in: matrix-sydent (Ubuntu Jammy) Status: New => Invalid ** Changed in: matrix-sydent (Ubuntu Noble) Status: New => Fix Committed ** Also affects: mailman3 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dh-python in Ubuntu. https://bugs.launchpad.net/bugs/2075337 Title: [SRU] py3clean fails when using alternate character set Status in cloud-init package in Ubuntu: New Status in dh-python package in Ubuntu: Invalid Status in logdata-anomaly-miner package in Ubuntu: Invalid Status in lomiri package in Ubuntu: Invalid Status in mailman3 package in Ubuntu: Invalid Status in matrix-sydent package in Ubuntu: Invalid Status in mom package in Ubuntu: Invalid Status in mopidy package in Ubuntu: Invalid Status in mpd-sima package in Ubuntu: Invalid Status in nordugrid-arc package in Ubuntu: Invalid Status in notus-scanner package in Ubuntu: Invalid Status in nrpe-ng package in Ubuntu: Invalid Status in onionprobe package in Ubuntu: Invalid Status in openscap-daemon package in Ubuntu: Invalid Status in ospd-openvas package in Ubuntu: Invalid Status in pagekite package in Ubuntu: Invalid Status in pagure package in Ubuntu: Invalid Status in pglistener package in Ubuntu: Invalid Status in policyd-rate-limit package in Ubuntu: Invalid Status in postfix-mta-sts-resolver package in Ubuntu: Invalid Status in powa-collector package in Ubuntu: Invalid Status in prelude-correlator package in Ubuntu: Invalid Status in prometheus-pgbouncer-exporter package in Ubuntu: Invalid Status in prometheus-xmpp-alerts package in Ubuntu: Invalid Status in pyro5 package in Ubuntu: Invalid Status in pyroman package in Ubuntu: Invalid Status in python3-defaults package in Ubuntu: Fix Released Status in r4d package in Ubuntu: Invalid Status in razercfg package in Ubuntu: Invalid Status in sgt-launcher package in Ubuntu: Fix Released Status in sms4you package in Ubuntu: Invalid Status in supervisor package in Ubuntu: Invalid Status in syncplay package in Ubuntu: Invalid Status in timekpr-next package in Ubuntu: Fix Released Status in twms package in Ubuntu: Invalid Status in ubuntu-advantage-tools package in Ubuntu: New Status in vanguards package in Ubuntu: Incomplete Status in vaultlocker package in Ubuntu: Invalid Status in virtualbox package in Ubuntu: Invalid Status in voctomix-outcasts package in Ubuntu: Invalid Status in weborf package in Ubuntu: Invalid Status in xdiagnose package in Ubuntu: Fix Released Status in cloud-init source package in Jammy: Invalid Status in dh-python source package in Jammy: Invalid Status in logdata-anomaly-miner source package in Jammy: Invalid Status in lomiri source package in Jammy: Invalid Status in mailman3 source package in Jammy: Invalid Status in matrix-sydent source package in Jammy: Invalid Status in mom source package in Jammy: Invalid Status in mopidy source package in Jammy: Invalid Status in mpd-sima source package in Jammy: Invalid Status in nordugrid-arc source package in Jammy: Invalid Status in notus-scanner source package in Jammy: Invalid Status in nrpe-ng source package in Jammy: Invalid Status in onionprobe source package in Jammy: Invalid Status in openscap-daemon source package in Jammy: Invalid Status in ospd-openvas source package in Jammy: Invalid Status in pagekite source package in Jammy: Invalid Status in pagure source package in J
[Touch-packages] [Bug 2075337] Please test proposed package
Hello Robie, or anyone else affected, Accepted matrix-sydent into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/matrix- sydent/2.5.1-1.1ubuntu0.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-noble. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: mailman3 (Ubuntu) Status: New => Invalid ** Changed in: mailman3 (Ubuntu Jammy) Status: New => Invalid ** Changed in: mailman3 (Ubuntu Noble) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dh-python in Ubuntu. https://bugs.launchpad.net/bugs/2075337 Title: [SRU] py3clean fails when using alternate character set Status in cloud-init package in Ubuntu: New Status in dh-python package in Ubuntu: Invalid Status in logdata-anomaly-miner package in Ubuntu: Invalid Status in lomiri package in Ubuntu: Invalid Status in mailman3 package in Ubuntu: Invalid Status in matrix-sydent package in Ubuntu: Invalid Status in mom package in Ubuntu: Invalid Status in mopidy package in Ubuntu: Invalid Status in mpd-sima package in Ubuntu: Invalid Status in nordugrid-arc package in Ubuntu: Invalid Status in notus-scanner package in Ubuntu: Invalid Status in nrpe-ng package in Ubuntu: Invalid Status in onionprobe package in Ubuntu: Invalid Status in openscap-daemon package in Ubuntu: Invalid Status in ospd-openvas package in Ubuntu: Invalid Status in pagekite package in Ubuntu: Invalid Status in pagure package in Ubuntu: Invalid Status in pglistener package in Ubuntu: Invalid Status in policyd-rate-limit package in Ubuntu: Invalid Status in postfix-mta-sts-resolver package in Ubuntu: Invalid Status in powa-collector package in Ubuntu: Invalid Status in prelude-correlator package in Ubuntu: Invalid Status in prometheus-pgbouncer-exporter package in Ubuntu: Invalid Status in prometheus-xmpp-alerts package in Ubuntu: Invalid Status in pyro5 package in Ubuntu: Invalid Status in pyroman package in Ubuntu: Invalid Status in python3-defaults package in Ubuntu: Fix Released Status in r4d package in Ubuntu: Invalid Status in razercfg package in Ubuntu: Invalid Status in sgt-launcher package in Ubuntu: Fix Released Status in sms4you package in Ubuntu: Invalid Status in supervisor package in Ubuntu: Invalid Status in syncplay package in Ubuntu: Invalid Status in timekpr-next package in Ubuntu: Fix Released Status in twms package in Ubuntu: Invalid Status in ubuntu-advantage-tools package in Ubuntu: New Status in vanguards package in Ubuntu: Incomplete Status in vaultlocker package in Ubuntu: Invalid Status in virtualbox package in Ubuntu: Invalid Status in voctomix-outcasts package in Ubuntu: Invalid Status in weborf package in Ubuntu: Invalid Status in xdiagnose package in Ubuntu: Fix Released Status in cloud-init source package in Jammy: Invalid Status in dh-python source package in Jammy: Invalid Status in logdata-anomaly-miner source package in Jammy: Invalid Status in lomiri source package in Jammy: Invalid Status in mailman3 source package in Jammy: Invalid Status in matrix-sydent source package in Jammy: Invalid Status in mom source package in Jammy: Invalid Status in mopidy source package in Jammy: Invalid Status in mpd-sima source package in Jammy: Invalid Status in nordugrid-arc source package in Jammy: Invalid Status in notus-scanner source package in Jammy: Invalid Status in nrpe-ng source package in Jammy: Invalid Status in onionprobe source package in Jammy: Invalid Status in openscap-daemon source package in Jammy: Invalid Status in ospd-openvas source package in Jammy: Invalid Status in pagekite source package in Jammy: Invalid Status in pagure source package in Jammy: Invalid Status in pglistener source package in Jammy: Invalid Status in policyd-rate-limit source package in Jammy: Invalid Status in postfix-mta-s
[Touch-packages] [Bug 2075337] Please test proposed package
Hello Robie, or anyone else affected, Accepted mailman3 into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mailman3/3.3.8-3.1ubuntu0.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-noble. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Also affects: lomiri (Ubuntu) Importance: Undecided Status: New ** Changed in: lomiri (Ubuntu) Status: New => Invalid ** Changed in: lomiri (Ubuntu Jammy) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dh-python in Ubuntu. https://bugs.launchpad.net/bugs/2075337 Title: [SRU] py3clean fails when using alternate character set Status in cloud-init package in Ubuntu: New Status in dh-python package in Ubuntu: Invalid Status in logdata-anomaly-miner package in Ubuntu: Invalid Status in lomiri package in Ubuntu: Invalid Status in mailman3 package in Ubuntu: Invalid Status in matrix-sydent package in Ubuntu: Invalid Status in mom package in Ubuntu: Invalid Status in mopidy package in Ubuntu: Invalid Status in mpd-sima package in Ubuntu: Invalid Status in nordugrid-arc package in Ubuntu: Invalid Status in notus-scanner package in Ubuntu: Invalid Status in nrpe-ng package in Ubuntu: Invalid Status in onionprobe package in Ubuntu: Invalid Status in openscap-daemon package in Ubuntu: Invalid Status in ospd-openvas package in Ubuntu: Invalid Status in pagekite package in Ubuntu: Invalid Status in pagure package in Ubuntu: Invalid Status in pglistener package in Ubuntu: Invalid Status in policyd-rate-limit package in Ubuntu: Invalid Status in postfix-mta-sts-resolver package in Ubuntu: Invalid Status in powa-collector package in Ubuntu: Invalid Status in prelude-correlator package in Ubuntu: Invalid Status in prometheus-pgbouncer-exporter package in Ubuntu: Invalid Status in prometheus-xmpp-alerts package in Ubuntu: Invalid Status in pyro5 package in Ubuntu: Invalid Status in pyroman package in Ubuntu: Invalid Status in python3-defaults package in Ubuntu: Fix Released Status in r4d package in Ubuntu: Invalid Status in razercfg package in Ubuntu: Invalid Status in sgt-launcher package in Ubuntu: Fix Released Status in sms4you package in Ubuntu: Invalid Status in supervisor package in Ubuntu: Invalid Status in syncplay package in Ubuntu: Invalid Status in timekpr-next package in Ubuntu: Fix Released Status in twms package in Ubuntu: Invalid Status in ubuntu-advantage-tools package in Ubuntu: New Status in vanguards package in Ubuntu: Incomplete Status in vaultlocker package in Ubuntu: Invalid Status in virtualbox package in Ubuntu: Invalid Status in voctomix-outcasts package in Ubuntu: Invalid Status in weborf package in Ubuntu: Invalid Status in xdiagnose package in Ubuntu: Fix Released Status in cloud-init source package in Jammy: Invalid Status in dh-python source package in Jammy: Invalid Status in logdata-anomaly-miner source package in Jammy: Invalid Status in lomiri source package in Jammy: Invalid Status in mailman3 source package in Jammy: Invalid Status in matrix-sydent source package in Jammy: Invalid Status in mom source package in Jammy: Invalid Status in mopidy source package in Jammy: Invalid Status in mpd-sima source package in Jammy: Invalid Status in nordugrid-arc source package in Jammy: Invalid Status in notus-scanner source package in Jammy: Invalid Status in nrpe-ng source package in Jammy: Invalid Status in onionprobe source package in Jammy: Invalid Status in openscap-daemon source package in Jammy: Invalid Status in ospd-openvas source package in Jammy: Invalid Status in pagekite source package in Jammy: Invalid Status in pagure source package in Jammy: Invalid Status in pglistener source package in Jammy: Invalid Status in policyd-rate-limit source package in Jammy: Invalid Status in postfix-mta-sts-resolver s
[Touch-packages] [Bug 2075337] Re: [SRU] py3clean fails when using alternate character set
The lomiri upload has unrelated noise in d/control (comments removed) and a double comma in the Breaks: addition. Could you please adjust and re-upload? Thanks! ** Changed in: lomiri (Ubuntu Noble) Status: New => Incomplete ** Changed in: lomiri (Ubuntu Noble) Assignee: (unassigned) => Dave Jones (waveform) ** Also affects: logdata-anomaly-miner (Ubuntu) Importance: Undecided Status: New ** Changed in: logdata-anomaly-miner (Ubuntu) Status: New => Invalid ** Changed in: logdata-anomaly-miner (Ubuntu Jammy) Status: New => Invalid ** Changed in: logdata-anomaly-miner (Ubuntu Noble) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dh-python in Ubuntu. https://bugs.launchpad.net/bugs/2075337 Title: [SRU] py3clean fails when using alternate character set Status in cloud-init package in Ubuntu: New Status in dh-python package in Ubuntu: Invalid Status in logdata-anomaly-miner package in Ubuntu: Invalid Status in lomiri package in Ubuntu: Invalid Status in mailman3 package in Ubuntu: Invalid Status in matrix-sydent package in Ubuntu: Invalid Status in mom package in Ubuntu: Invalid Status in mopidy package in Ubuntu: Invalid Status in mpd-sima package in Ubuntu: Invalid Status in nordugrid-arc package in Ubuntu: Invalid Status in notus-scanner package in Ubuntu: Invalid Status in nrpe-ng package in Ubuntu: Invalid Status in onionprobe package in Ubuntu: Invalid Status in openscap-daemon package in Ubuntu: Invalid Status in ospd-openvas package in Ubuntu: Invalid Status in pagekite package in Ubuntu: Invalid Status in pagure package in Ubuntu: Invalid Status in pglistener package in Ubuntu: Invalid Status in policyd-rate-limit package in Ubuntu: Invalid Status in postfix-mta-sts-resolver package in Ubuntu: Invalid Status in powa-collector package in Ubuntu: Invalid Status in prelude-correlator package in Ubuntu: Invalid Status in prometheus-pgbouncer-exporter package in Ubuntu: Invalid Status in prometheus-xmpp-alerts package in Ubuntu: Invalid Status in pyro5 package in Ubuntu: Invalid Status in pyroman package in Ubuntu: Invalid Status in python3-defaults package in Ubuntu: Fix Released Status in r4d package in Ubuntu: Invalid Status in razercfg package in Ubuntu: Invalid Status in sgt-launcher package in Ubuntu: Fix Released Status in sms4you package in Ubuntu: Invalid Status in supervisor package in Ubuntu: Invalid Status in syncplay package in Ubuntu: Invalid Status in timekpr-next package in Ubuntu: Fix Released Status in twms package in Ubuntu: Invalid Status in ubuntu-advantage-tools package in Ubuntu: New Status in vanguards package in Ubuntu: Incomplete Status in vaultlocker package in Ubuntu: Invalid Status in virtualbox package in Ubuntu: Invalid Status in voctomix-outcasts package in Ubuntu: Invalid Status in weborf package in Ubuntu: Invalid Status in xdiagnose package in Ubuntu: Fix Released Status in cloud-init source package in Jammy: Invalid Status in dh-python source package in Jammy: Invalid Status in logdata-anomaly-miner source package in Jammy: Invalid Status in lomiri source package in Jammy: Invalid Status in mailman3 source package in Jammy: Invalid Status in matrix-sydent source package in Jammy: Invalid Status in mom source package in Jammy: Invalid Status in mopidy source package in Jammy: Invalid Status in mpd-sima source package in Jammy: Invalid Status in nordugrid-arc source package in Jammy: Invalid Status in notus-scanner source package in Jammy: Invalid Status in nrpe-ng source package in Jammy: Invalid Status in onionprobe source package in Jammy: Invalid Status in openscap-daemon source package in Jammy: Invalid Status in ospd-openvas source package in Jammy: Invalid Status in pagekite source package in Jammy: Invalid Status in pagure source package in Jammy: Invalid Status in pglistener source package in Jammy: Invalid Status in policyd-rate-limit source package in Jammy: Invalid Status in postfix-mta-sts-resolver source package in Jammy: Invalid Status in powa-collector source package in Jammy: Invalid Status in prelude-correlator source package in Jammy: Invalid Status in prometheus-pgbouncer-exporter source package in Jammy: Invalid Status in prometheus-xmpp-alerts source package in Jammy: Invalid Status in pyro5 source package in Jammy: Invalid Status in pyroman source package in Jammy: Invalid Status in python3-defaults source package in Jammy: Fix Released Status in r4d source package in Jammy: Invalid Status in razercfg source package in Jammy: Invalid Status in sgt-launcher source package in Jammy: Invalid Status in sms4you source package in Jammy: Invalid Status in supervisor source package in Jammy: Invalid Status in syncplay source package in Jammy: Invalid Status i
[Touch-packages] [Bug 2075337] Please test proposed package
Hello Robie, or anyone else affected, Accepted logdata-anomaly-miner into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/logdata-anomaly- miner/2.6.1-1ubuntu0.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-noble. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dh-python in Ubuntu. https://bugs.launchpad.net/bugs/2075337 Title: [SRU] py3clean fails when using alternate character set Status in cloud-init package in Ubuntu: New Status in dh-python package in Ubuntu: Invalid Status in logdata-anomaly-miner package in Ubuntu: Invalid Status in lomiri package in Ubuntu: Invalid Status in mailman3 package in Ubuntu: Invalid Status in matrix-sydent package in Ubuntu: Invalid Status in mom package in Ubuntu: Invalid Status in mopidy package in Ubuntu: Invalid Status in mpd-sima package in Ubuntu: Invalid Status in nordugrid-arc package in Ubuntu: Invalid Status in notus-scanner package in Ubuntu: Invalid Status in nrpe-ng package in Ubuntu: Invalid Status in onionprobe package in Ubuntu: Invalid Status in openscap-daemon package in Ubuntu: Invalid Status in ospd-openvas package in Ubuntu: Invalid Status in pagekite package in Ubuntu: Invalid Status in pagure package in Ubuntu: Invalid Status in pglistener package in Ubuntu: Invalid Status in policyd-rate-limit package in Ubuntu: Invalid Status in postfix-mta-sts-resolver package in Ubuntu: Invalid Status in powa-collector package in Ubuntu: Invalid Status in prelude-correlator package in Ubuntu: Invalid Status in prometheus-pgbouncer-exporter package in Ubuntu: Invalid Status in prometheus-xmpp-alerts package in Ubuntu: Invalid Status in pyro5 package in Ubuntu: Invalid Status in pyroman package in Ubuntu: Invalid Status in python3-defaults package in Ubuntu: Fix Released Status in r4d package in Ubuntu: Invalid Status in razercfg package in Ubuntu: Invalid Status in sgt-launcher package in Ubuntu: Fix Released Status in sms4you package in Ubuntu: Invalid Status in supervisor package in Ubuntu: Invalid Status in syncplay package in Ubuntu: Invalid Status in timekpr-next package in Ubuntu: Fix Released Status in twms package in Ubuntu: Invalid Status in ubuntu-advantage-tools package in Ubuntu: New Status in vanguards package in Ubuntu: Incomplete Status in vaultlocker package in Ubuntu: Invalid Status in virtualbox package in Ubuntu: Invalid Status in voctomix-outcasts package in Ubuntu: Invalid Status in weborf package in Ubuntu: Invalid Status in xdiagnose package in Ubuntu: Fix Released Status in cloud-init source package in Jammy: Invalid Status in dh-python source package in Jammy: Invalid Status in logdata-anomaly-miner source package in Jammy: Invalid Status in lomiri source package in Jammy: Invalid Status in mailman3 source package in Jammy: Invalid Status in matrix-sydent source package in Jammy: Invalid Status in mom source package in Jammy: Invalid Status in mopidy source package in Jammy: Invalid Status in mpd-sima source package in Jammy: Invalid Status in nordugrid-arc source package in Jammy: Invalid Status in notus-scanner source package in Jammy: Invalid Status in nrpe-ng source package in Jammy: Invalid Status in onionprobe source package in Jammy: Invalid Status in openscap-daemon source package in Jammy: Invalid Status in ospd-openvas source package in Jammy: Invalid Status in pagekite source package in Jammy: Invalid Status in pagure source package in Jammy: Invalid Status in pglistener source package in Jammy: Invalid Status in policyd-rate-limit source package in Jammy: Invalid Status in postfix-mta-sts-resolver source package in Jammy: Invalid Status in powa-collector source package in Jammy: Invalid Status in prelude-correlator source package in Jammy: Invalid Status in prometheus-pgbo
[Touch-packages] [Bug 2055397] Re: netplan/systemd-networkd: route metric not applied to routes to the local subnet
Thanks, Nick. There are several autopkgtests positives that are outdated (i.e., focal- updates has newer versions of the tested packages), thus listed in the update_excuses page as blocking [1]. I have requested reruns for all of those, which should clear the `Issues preventing migration` section if all goes well (not expecting failures, as they have all passed with the older/outdated version, but if they fail, the testing was worth it). Once that is finished, this should be good for release, IMHO. cheers, Mauricio [1] https://ubuntu-archive-team.ubuntu.com/proposed- migration/focal/update_excuses.html#systemd Generated: 2024.09.09 18:58:58 + ... systemd (245.4-4ubuntu3.23 to 245.4-4ubuntu3.24) ... Issues preventing migration: autopkgtest for exim4/4.93-13ubuntu1.10: amd64: Pass, arm64: Pass, armhf: Pass, ppc64el: Pass, s390x: Pass autopkgtest for linux/5.4.0-189.209: amd64: Pass, arm64: Pass, armhf: Pass, ppc64el: Pass, s390x: Pass autopkgtest for linux-aws/5.4.0-1128.138: amd64: Pass, arm64: Pass autopkgtest for linux-aws-5.15/5.15.0-1065.71~20.04.1: amd64: Pass, arm64: Pass autopkgtest for linux-azure/5.4.0-1133.140: amd64: Pass, arm64: Pass autopkgtest for linux-azure-5.15/5.15.0-1068.77~20.04.1: amd64: Pass, arm64: Pass autopkgtest for linux-azure-cvm/blacklisted: amd64: Regression ♻ autopkgtest for linux-bluefield/5.4.0-1088.95: arm64: Pass autopkgtest for linux-gcp/5.4.0-1132.141: amd64: Pass, arm64: Pass autopkgtest for linux-gcp-5.15/5.15.0-1062.70~20.04.1: amd64: Pass, arm64: Pass autopkgtest for linux-gke-5.15/blacklisted: amd64: Regression ♻ , arm64: Regression ♻ autopkgtest for linux-gkeop/5.4.0-1095.99: amd64: Pass autopkgtest for linux-gkeop-5.15/5.15.0-1048.55~20.04.1: amd64: Pass autopkgtest for linux-hwe-5.15/5.15.0-116.126~20.04.1: amd64: Pass, arm64: Pass, armhf: Pass, ppc64el: Pass, s390x: Pass autopkgtest for linux-ibm/5.4.0-1075.80: amd64: Pass autopkgtest for linux-ibm-5.15/5.15.0-1056.59~20.04.1: amd64: Pass autopkgtest for linux-intel-iotg-5.15/5.15.0-1060.66~20.04.1: amd64: Pass autopkgtest for linux-iot/5.4.0-1040.41: amd64: Pass, arm64: Pass autopkgtest for linux-kvm/5.4.0-1116.123: amd64: Pass autopkgtest for linux-lowlatency-hwe-5.15/5.15.0-113.123~20.04.1: amd64: Pass, arm64: Pass autopkgtest for linux-nvidia-tegra-5.15/5.15.0-1025.25~20.04.1: arm64: Pass autopkgtest for linux-oem-5.14/blacklisted: amd64: Regression ♻ autopkgtest for linux-oracle/5.4.0-1127.136: amd64: Pass, arm64: Pass autopkgtest for linux-oracle-5.15/5.15.0-1063.69~20.04.1: amd64: Pass, arm64: Pass autopkgtest for linux-xilinx-zynqmp/5.4.0-1047.51: arm64: Pass autopkgtest for postgresql-12/12.19-0ubuntu0.20.04.1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Ignored failure, ppc64el: Pass, s390x: Pass autopkgtest for prometheus-alertmanager/0.15.3+ds-3ubuntu1.1: amd64: Pass, arm64: Pass, armhf: Pass, ppc64el: Pass, s390x: Pass autopkgtest for snapd/2.63+20.04: amd64: Pass, arm64: Pass, armhf: No test results, ppc64el: Pass, s390x: Pass autopkgtest for zfs-linux/0.8.3-1ubuntu12.17: amd64: Pass, arm64: Pass, armhf: No test results, ppc64el: Pass, s390x: Pass -- 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/2055397 Title: netplan/systemd-networkd: route metric not applied to routes to the local subnet Status in cloud-init package in Ubuntu: Invalid Status in netplan.io package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Fix Committed Bug description: [SRU TEMPLATE] [DESCRIPTION] Cloud-init introduced a feature to configure policy routing on AWS EC2 instances with multiple NICs in https://github.com/canonical/cloud-init/commit/0ca5f31043e2d98eab31a43d9dde9bdaef1435cb targeting v24.1. Cloud-init generates the following netplan config: ``` $ cat /etc/netplan/50-cloud-init.yaml network: ethernets: ens5: dhcp4: true dhcp4-overrides: &id001 route-metric: 100 dhcp6: true dhcp6-overrides: *id001 match: macaddress: 0a:c8:ab:90:c2:fb set-name: ens5 ens6: dhcp4: true dhcp4-overrides: route-metric: 200 use-routes: true dhcp6: false match: macaddress: 0a:c6:55:a1:dc:3b routes: - table: 101 to: 0.0.0.0/0 via: 192.168.0.1 - table: 101 to: 192.168.0.0/20 routing-policy: - from: 192.168.10.212 table: 101 set-name: ens6 version: 2 ``` Which renders the following systemd-networkd config files: ``` $ cat 10-netplan-ens5.link [Match] MACAddress=0a:c8:ab:9
[Touch-packages] [Bug 2075337] Re: [SRU] py3clean fails when using alternate character set
Hello Robie, or anyone else affected, Accepted python-docker into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/python- docker/5.0.3-1ubuntu1.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-noble. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: python-docker (Ubuntu Jammy) Status: New => Invalid ** Changed in: python-docker (Ubuntu Noble) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dh-python in Ubuntu. https://bugs.launchpad.net/bugs/2075337 Title: [SRU] py3clean fails when using alternate character set Status in cloud-init package in Ubuntu: New Status in condor package in Ubuntu: Invalid Status in dh-python package in Ubuntu: Invalid Status in fenrir package in Ubuntu: Invalid Status in logdata-anomaly-miner package in Ubuntu: Invalid Status in lomiri package in Ubuntu: Invalid Status in mailman3 package in Ubuntu: Invalid Status in matrix-sydent package in Ubuntu: Invalid Status in mom package in Ubuntu: Invalid Status in mopidy package in Ubuntu: Invalid Status in mpd-sima package in Ubuntu: Invalid Status in nordugrid-arc package in Ubuntu: Invalid Status in notus-scanner package in Ubuntu: Invalid Status in nrpe-ng package in Ubuntu: Invalid Status in onionprobe package in Ubuntu: Invalid Status in openscap-daemon package in Ubuntu: Invalid Status in ospd-openvas package in Ubuntu: Invalid Status in pagekite package in Ubuntu: Invalid Status in pagure package in Ubuntu: Invalid Status in pglistener package in Ubuntu: Invalid Status in policyd-rate-limit package in Ubuntu: Invalid Status in postfix-mta-sts-resolver package in Ubuntu: Invalid Status in powa-collector package in Ubuntu: Invalid Status in prelude-correlator package in Ubuntu: Invalid Status in prometheus-pgbouncer-exporter package in Ubuntu: Invalid Status in prometheus-xmpp-alerts package in Ubuntu: Invalid Status in pyro5 package in Ubuntu: Incomplete Status in pyroman package in Ubuntu: Invalid Status in python-docker package in Ubuntu: Invalid Status in python3-defaults package in Ubuntu: Fix Released Status in r4d package in Ubuntu: Invalid Status in razercfg package in Ubuntu: Invalid Status in sgt-launcher package in Ubuntu: Fix Released Status in sms4you package in Ubuntu: Invalid Status in supervisor package in Ubuntu: Invalid Status in syncplay package in Ubuntu: Invalid Status in timekpr-next package in Ubuntu: Fix Released Status in twms package in Ubuntu: Invalid Status in ubuntu-advantage-tools package in Ubuntu: New Status in vanguards package in Ubuntu: Incomplete Status in vaultlocker package in Ubuntu: Invalid Status in virtualbox package in Ubuntu: Invalid Status in voctomix-outcasts package in Ubuntu: Invalid Status in weborf package in Ubuntu: Invalid Status in xdiagnose package in Ubuntu: Fix Released Status in cloud-init source package in Jammy: Invalid Status in condor source package in Jammy: Invalid Status in dh-python source package in Jammy: Invalid Status in fenrir source package in Jammy: Invalid Status in logdata-anomaly-miner source package in Jammy: Invalid Status in lomiri source package in Jammy: Invalid Status in mailman3 source package in Jammy: Invalid Status in matrix-sydent source package in Jammy: Invalid Status in mom source package in Jammy: Invalid Status in mopidy source package in Jammy: Invalid Status in mpd-sima source package in Jammy: Invalid Status in nordugrid-arc source package in Jammy: Invalid Status in notus-scanner source package in Jammy: Invalid Status in nrpe-ng source package in Jammy: Invalid Status in onionprobe source package in Jammy: Invalid Status in openscap-daemon source package in Jammy: Invalid Status in ospd-openvas source package in Jammy: Invalid Status in pagekite source package in Jammy:
[Touch-packages] [Bug 2080426] [NEW] module not available for python versions in universe
Public bug reported: Some Ubuntu releases may provide more than one version of Python; e.g., Jammy has python3.10 in _main_ and python3.11 in _universe_. However, the modules are only shipped for the python version in _main_, and can't be imported by python version(s) in _universe_. It's understandable that not all python versions are considered "supported" by `py3versions`, particularly if not in _main_, but... It turns out Ubuntu Pro provides support for packages in _universe_, and there are reports of this import error/failure from customers with some frequency. Could the build/delivery of the python-apt modules be considered for all python versions available in a series, independently of the component (main/universe)? Thanks! Details: --- $ lsb_release -cs jammy $ apt-cache search --names-only '^python3\.[0-9]+$' python3.10 - Interactive high-level object-oriented language (version 3.10) python3.11 - Interactive high-level object-oriented language (version 3.11) $ apt show python3.10 python3.11 2>/dev/null | grep -e Package: -e Section: Package: python3.10 Section: python Package: python3.11 Section: universe/python $ sudo apt install --yes python3-apt python3.11 python3.10 $ py3versions --help | grep supported Usage: [-v] [-h] [-d|--default] [-s|--supported] [-i|--installed] -s, --supported print the supported python3 versions -i, --installed print the installed supported python3 versions $ py3versions --supported python3.10 $ py3versions --installed # ... AND supported python3.10 $ dpkg -L python3-apt | grep -F 'apt_pkg.' # ... ONLY 3.10, NOT 3.11 /usr/lib/python3/dist-packages/apt_pkg.cpython-310-x86_64-linux-gnu.so $ python3.10 -c 'import apt_pkg'; echo $? 0 $ python3.11 -c 'import apt_pkg'; echo $? Traceback (most recent call last): File "", line 1, in ModuleNotFoundError: No module named 'apt_pkg' 1 ** Affects: python-apt (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/2080426 Title: module not available for python versions in universe Status in python-apt package in Ubuntu: New Bug description: Some Ubuntu releases may provide more than one version of Python; e.g., Jammy has python3.10 in _main_ and python3.11 in _universe_. However, the modules are only shipped for the python version in _main_, and can't be imported by python version(s) in _universe_. It's understandable that not all python versions are considered "supported" by `py3versions`, particularly if not in _main_, but... It turns out Ubuntu Pro provides support for packages in _universe_, and there are reports of this import error/failure from customers with some frequency. Could the build/delivery of the python-apt modules be considered for all python versions available in a series, independently of the component (main/universe)? Thanks! Details: --- $ lsb_release -cs jammy $ apt-cache search --names-only '^python3\.[0-9]+$' python3.10 - Interactive high-level object-oriented language (version 3.10) python3.11 - Interactive high-level object-oriented language (version 3.11) $ apt show python3.10 python3.11 2>/dev/null | grep -e Package: -e Section: Package: python3.10 Section: python Package: python3.11 Section: universe/python $ sudo apt install --yes python3-apt python3.11 python3.10 $ py3versions --help | grep supported Usage: [-v] [-h] [-d|--default] [-s|--supported] [-i|--installed] -s, --supported print the supported python3 versions -i, --installed print the installed supported python3 versions $ py3versions --supported python3.10 $ py3versions --installed # ... AND supported python3.10 $ dpkg -L python3-apt | grep -F 'apt_pkg.' # ... ONLY 3.10, NOT 3.11 /usr/lib/python3/dist-packages/apt_pkg.cpython-310-x86_64-linux-gnu.so $ python3.10 -c 'import apt_pkg'; echo $? 0 $ python3.11 -c 'import apt_pkg'; echo $? Traceback (most recent call last): File "", line 1, in ModuleNotFoundError: No module named 'apt_pkg' 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/2080426/+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 2080426] Re: module not available for python versions in universe
Product Feedback & Features Request `PF-5248`: https://warthogs.atlassian.net/browse/PF-5248 ** Tags added: pf-5248 -- 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/2080426 Title: module not available for python versions in universe Status in python-apt package in Ubuntu: New Bug description: Some Ubuntu releases may provide more than one version of Python; e.g., Jammy has python3.10 in _main_ and python3.11 in _universe_. However, the modules are only shipped for the python version in _main_, and can't be imported by python version(s) in _universe_. It's understandable that not all python versions are considered "supported" by `py3versions`, particularly if not in _main_, but... It turns out Ubuntu Pro provides support for packages in _universe_, and there are reports of this import error/failure from customers with some frequency. Could the build/delivery of the python-apt modules be considered for all python versions available in a series, independently of the component (main/universe)? Thanks! Details: --- $ lsb_release -cs jammy $ apt-cache search --names-only '^python3\.[0-9]+$' python3.10 - Interactive high-level object-oriented language (version 3.10) python3.11 - Interactive high-level object-oriented language (version 3.11) $ apt show python3.10 python3.11 2>/dev/null | grep -e Package: -e Section: Package: python3.10 Section: python Package: python3.11 Section: universe/python $ sudo apt install --yes python3-apt python3.11 python3.10 $ py3versions --help | grep supported Usage: [-v] [-h] [-d|--default] [-s|--supported] [-i|--installed] -s, --supported print the supported python3 versions -i, --installed print the installed supported python3 versions $ py3versions --supported python3.10 $ py3versions --installed # ... AND supported python3.10 $ dpkg -L python3-apt | grep -F 'apt_pkg.' # ... ONLY 3.10, NOT 3.11 /usr/lib/python3/dist-packages/apt_pkg.cpython-310-x86_64-linux-gnu.so $ python3.10 -c 'import apt_pkg'; echo $? 0 $ python3.11 -c 'import apt_pkg'; echo $? Traceback (most recent call last): File "", line 1, in ModuleNotFoundError: No module named 'apt_pkg' 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/2080426/+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 2055397] Re: netplan/systemd-networkd: route metric not applied to routes to the local subnet
The non-denylisted regressions are now cleared: systemd (245.4-4ubuntu3.23 to 245.4-4ubuntu3.24) ... Issues preventing migration: autopkgtest for linux-azure-cvm/blacklisted: amd64: Regression ♻ autopkgtest for linux-gke-5.15/blacklisted: amd64: Regression ♻ , arm64: Regression ♻ autopkgtest for linux-oem-5.14/blacklisted: amd64: Regression ♻ ... The 4 "Regression" links point to: "This package is marked to never run. To get the entry removed, contact a member of the Ubuntu Release or Canonical Ubuntu QA team." I plan to review this SRU in my next shift. -- 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/2055397 Title: netplan/systemd-networkd: route metric not applied to routes to the local subnet Status in cloud-init package in Ubuntu: Invalid Status in netplan.io package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Fix Committed Bug description: [SRU TEMPLATE] [DESCRIPTION] Cloud-init introduced a feature to configure policy routing on AWS EC2 instances with multiple NICs in https://github.com/canonical/cloud-init/commit/0ca5f31043e2d98eab31a43d9dde9bdaef1435cb targeting v24.1. Cloud-init generates the following netplan config: ``` $ cat /etc/netplan/50-cloud-init.yaml network: ethernets: ens5: dhcp4: true dhcp4-overrides: &id001 route-metric: 100 dhcp6: true dhcp6-overrides: *id001 match: macaddress: 0a:c8:ab:90:c2:fb set-name: ens5 ens6: dhcp4: true dhcp4-overrides: route-metric: 200 use-routes: true dhcp6: false match: macaddress: 0a:c6:55:a1:dc:3b routes: - table: 101 to: 0.0.0.0/0 via: 192.168.0.1 - table: 101 to: 192.168.0.0/20 routing-policy: - from: 192.168.10.212 table: 101 set-name: ens6 version: 2 ``` Which renders the following systemd-networkd config files: ``` $ cat 10-netplan-ens5.link [Match] MACAddress=0a:c8:ab:90:c2:fb [Link] Name=ens5 WakeOnLan=off $ cat 10-netplan-ens5.network [Match] MACAddress=0a:c8:ab:90:c2:fb Name=ens5 [Network] DHCP=yes LinkLocalAddressing=ipv6 [DHCP] RouteMetric=100 UseMTU=true $ cat 10-netplan-ens6.link [Match] MACAddress=0a:c6:55:a1:dc:3b [Link] Name=ens6 WakeOnLan=off $ cat 10-netplan-ens6.network [Match] MACAddress=0a:c6:55:a1:dc:3b Name=ens6 [Network] DHCP=ipv4 LinkLocalAddressing=ipv6 [Route] Destination=0.0.0.0/0 Gateway=192.168.0.1 Table=101 [Route] Destination=192.168.0.0/20 Scope=link Table=101 [RoutingPolicyRule] From=192.168.10.212 Table=101 [DHCP] RouteMetric=200 UseMTU=true ``` Which configures the instance with the following state in Ubuntu Focal: ``` $ ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: ens5: mtu 9001 qdisc mq state UP group default qlen 1000 link/ether 0a:c8:ab:90:c2:fb brd ff:ff:ff:ff:ff:ff inet 192.168.12.94/20 brd 192.168.15.255 scope global dynamic ens5 valid_lft 2087sec preferred_lft 2087sec inet6 2a05:d012:ea0:c500:6d12:2b20:5fef:a502/128 scope global dynamic noprefixroute valid_lft 440sec preferred_lft 130sec inet6 fe80::8c8:abff:fe90:c2fb/64 scope link valid_lft forever preferred_lft forever 3: ens6: mtu 9001 qdisc mq state UP group default qlen 1000 link/ether 0a:c6:55:a1:dc:3b brd ff:ff:ff:ff:ff:ff inet 192.168.10.212/20 brd 192.168.15.255 scope global dynamic ens6 valid_lft 2083sec preferred_lft 2083sec inet6 fe80::8c6:55ff:fea1:dc3b/64 scope link valid_lft forever preferred_lft forever $ ip route show default via 192.168.0.1 dev ens5 proto dhcp src 192.168.12.94 metric 100 default via 192.168.0.1 dev ens6 proto dhcp src 192.168.10.212 metric 200 192.168.0.0/20 dev ens5 proto kernel scope link src 192.168.12.94 192.168.0.0/20 dev ens6 proto kernel scope link src 192.168.10.212 192.168.0.1 dev ens5 proto dhcp scope link src 192.168.12.94 metric 100 192.168.0.1 dev ens6 proto dhcp scope link src 192.168.10.212 metric 200 $ ip rule show 0: from all lookup local 0: from 192.168.10.212 lookup 101 32766: from all lookup main 32767: from all lookup default $ ip route show table 10
[Touch-packages] [Bug 2080426] Re: module not available for python versions in universe
** Changed in: python-apt (Ubuntu) Status: New => Opinion -- 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/2080426 Title: module not available for python versions in universe Status in python-apt package in Ubuntu: Opinion Bug description: Some Ubuntu releases may provide more than one version of Python; e.g., Jammy has python3.10 in _main_ and python3.11 in _universe_. However, the modules are only shipped for the python version in _main_, and can't be imported by python version(s) in _universe_. It's understandable that not all python versions are considered "supported" by `py3versions`, particularly if not in _main_, but... It turns out Ubuntu Pro provides support for packages in _universe_, and there are reports of this import error/failure from customers with some frequency. Could the build/delivery of the python-apt modules be considered for all python versions available in a series, independently of the component (main/universe)? Thanks! Details: --- $ lsb_release -cs jammy $ apt-cache search --names-only '^python3\.[0-9]+$' python3.10 - Interactive high-level object-oriented language (version 3.10) python3.11 - Interactive high-level object-oriented language (version 3.11) $ apt show python3.10 python3.11 2>/dev/null | grep -e Package: -e Section: Package: python3.10 Section: python Package: python3.11 Section: universe/python $ sudo apt install --yes python3-apt python3.11 python3.10 $ py3versions --help | grep supported Usage: [-v] [-h] [-d|--default] [-s|--supported] [-i|--installed] -s, --supported print the supported python3 versions -i, --installed print the installed supported python3 versions $ py3versions --supported python3.10 $ py3versions --installed # ... AND supported python3.10 $ dpkg -L python3-apt | grep -F 'apt_pkg.' # ... ONLY 3.10, NOT 3.11 /usr/lib/python3/dist-packages/apt_pkg.cpython-310-x86_64-linux-gnu.so $ python3.10 -c 'import apt_pkg'; echo $? 0 $ python3.11 -c 'import apt_pkg'; echo $? Traceback (most recent call last): File "", line 1, in ModuleNotFoundError: No module named 'apt_pkg' 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/2080426/+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 2055397] Re: netplan/systemd-networkd: route metric not applied to routes to the local subnet
Today, another two (newer) packages need reruns on on latest versions (clamav, dovecot). Triggered reruns for them. Hopefully they may finish before the end of my shift today. Issues preventing migration: autopkgtest for clamav/0.103.11+dfsg-0ubuntu0.20.04.1: amd64: Pass, arm64: Pass, armhf: Pass, ppc64el: Pass, s390x: Pass autopkgtest for dovecot/1:2.3.7.2-1ubuntu3.6: amd64: Pass, arm64: Pass, armhf: Pass, i386: Not a regression, ppc64el: Pass, s390x: Pass autopkgtest for linux-azure-cvm/blacklisted: amd64: Regression ♻ autopkgtest for linux-gke-5.15/blacklisted: amd64: Regression ♻ , arm64: Regression ♻ autopkgtest for linux-oem-5.14/blacklisted: amd64: Regression ♻ -- 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/2055397 Title: netplan/systemd-networkd: route metric not applied to routes to the local subnet Status in cloud-init package in Ubuntu: Invalid Status in netplan.io package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Fix Committed Bug description: [SRU TEMPLATE] [DESCRIPTION] Cloud-init introduced a feature to configure policy routing on AWS EC2 instances with multiple NICs in https://github.com/canonical/cloud-init/commit/0ca5f31043e2d98eab31a43d9dde9bdaef1435cb targeting v24.1. Cloud-init generates the following netplan config: ``` $ cat /etc/netplan/50-cloud-init.yaml network: ethernets: ens5: dhcp4: true dhcp4-overrides: &id001 route-metric: 100 dhcp6: true dhcp6-overrides: *id001 match: macaddress: 0a:c8:ab:90:c2:fb set-name: ens5 ens6: dhcp4: true dhcp4-overrides: route-metric: 200 use-routes: true dhcp6: false match: macaddress: 0a:c6:55:a1:dc:3b routes: - table: 101 to: 0.0.0.0/0 via: 192.168.0.1 - table: 101 to: 192.168.0.0/20 routing-policy: - from: 192.168.10.212 table: 101 set-name: ens6 version: 2 ``` Which renders the following systemd-networkd config files: ``` $ cat 10-netplan-ens5.link [Match] MACAddress=0a:c8:ab:90:c2:fb [Link] Name=ens5 WakeOnLan=off $ cat 10-netplan-ens5.network [Match] MACAddress=0a:c8:ab:90:c2:fb Name=ens5 [Network] DHCP=yes LinkLocalAddressing=ipv6 [DHCP] RouteMetric=100 UseMTU=true $ cat 10-netplan-ens6.link [Match] MACAddress=0a:c6:55:a1:dc:3b [Link] Name=ens6 WakeOnLan=off $ cat 10-netplan-ens6.network [Match] MACAddress=0a:c6:55:a1:dc:3b Name=ens6 [Network] DHCP=ipv4 LinkLocalAddressing=ipv6 [Route] Destination=0.0.0.0/0 Gateway=192.168.0.1 Table=101 [Route] Destination=192.168.0.0/20 Scope=link Table=101 [RoutingPolicyRule] From=192.168.10.212 Table=101 [DHCP] RouteMetric=200 UseMTU=true ``` Which configures the instance with the following state in Ubuntu Focal: ``` $ ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: ens5: mtu 9001 qdisc mq state UP group default qlen 1000 link/ether 0a:c8:ab:90:c2:fb brd ff:ff:ff:ff:ff:ff inet 192.168.12.94/20 brd 192.168.15.255 scope global dynamic ens5 valid_lft 2087sec preferred_lft 2087sec inet6 2a05:d012:ea0:c500:6d12:2b20:5fef:a502/128 scope global dynamic noprefixroute valid_lft 440sec preferred_lft 130sec inet6 fe80::8c8:abff:fe90:c2fb/64 scope link valid_lft forever preferred_lft forever 3: ens6: mtu 9001 qdisc mq state UP group default qlen 1000 link/ether 0a:c6:55:a1:dc:3b brd ff:ff:ff:ff:ff:ff inet 192.168.10.212/20 brd 192.168.15.255 scope global dynamic ens6 valid_lft 2083sec preferred_lft 2083sec inet6 fe80::8c6:55ff:fea1:dc3b/64 scope link valid_lft forever preferred_lft forever $ ip route show default via 192.168.0.1 dev ens5 proto dhcp src 192.168.12.94 metric 100 default via 192.168.0.1 dev ens6 proto dhcp src 192.168.10.212 metric 200 192.168.0.0/20 dev ens5 proto kernel scope link src 192.168.12.94 192.168.0.0/20 dev ens6 proto kernel scope link src 192.168.10.212 192.168.0.1 dev ens5 proto dhcp scope link src 192.168.12.94 metric 100 192.168.0.1 dev ens6 proto dhcp scope link src 192.168.10.212 metric 200 $ ip rule show 0: from all lookup local 0: from 19
[Touch-packages] [Bug 1597017] Re: mount rules grant excessive permissions
Thanks, Rodrigo! There are outdated autopkgtests (i.e., ran against reverse-test-deps that now have newer versions in -updates), which I triggered reruns for. Once that looks good (hopefully during my shift today, or maybe tomorrow), I'll take a look for release. Details: --- jammy: https://ubuntu-archive-team.ubuntu.com/proposed-migration/jammy/update_excuses.html#apparmor adsys/0.9.2~22.04.2 cups/2.4.1op1-1ubuntu4.8 dovecot/1:2.3.16+dfsg1-3ubuntu2.2 libreoffice/1:7.3.7-0ubuntu0.22.04.4 libvirt/8.0.0-1ubuntu7.8 libvirt/8.0.0-1ubuntu7.9 php8.1/8.1.2-1ubuntu2.14 snapd/2.61.3+22.04 squid/5.7-0ubuntu0.22.04.3 focal: https://ubuntu-archive-team.ubuntu.com/proposed-migration/focal/update_excuses.html#apparmor dovecot/1:2.3.7.2-1ubuntu3.6 libreoffice/1:6.4.7-0ubuntu0.20.04.9 libvirt/6.0.0-0ubuntu8.16 php7.4/7.4.3-4ubuntu2.20 snapd/2.61.3+20.04 squid/4.10-1ubuntu1.9 -- 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/1597017 Title: mount rules grant excessive permissions Status in AppArmor: Fix Released Status in apparmor package in Ubuntu: Fix Released Status in apparmor source package in Focal: Fix Committed Status in apparmor source package in Jammy: Fix Committed Bug description: SRU Team; the packages for focal-proposed and jammy-proposed are intended as security updates prepared by the Ubuntu Security team (and have built in a ppa with only the security pockets enabled). However, because the fix makes mount rules in apparmor policy be treated more restrictively than they were prior to this update, we would like these packages to gain more widespread testing. Risk of Regression: The update for this issue causes the apparmor parser, the tool that translates written policy into the enforcement data structures used by the kernel, to generate more strict policy for mount rules, like the example below. They are not common in apparmor policy generally, but can appear in policies written for container managers to restrict containers, and thus can potentially break container startup. The packages prepared for focal-proposed and jammy-proposed have tested with the versions of snapd, lxc, libvirt, and docker in the ubuntu archive, but container managers outside of the ubuntu archive may run into issues, hence the need for testing and policy adjustments. Original Report: The rule mount options=(rw,make-slave) -> **, ends up allowing mount -t proc proc /mnt which it shouldn't as it should be restricted to commands with a make- slave flag To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1597017/+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
