[Touch-packages] [Bug 2081334] Autopkgtest regression report (initramfs-tools/0.142ubuntu25.3)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted initramfs-tools (0.142ubuntu25.3) for 
noble have finished running.
The following regressions have been reported in tests triggered by the package:

zfs-linux/2.2.2-0ubuntu9 (s390x)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/noble/update_excuses.html#initramfs-tools

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank 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/2081334

Title:
  further performance improvement for dracut-install 060

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Noble:
  Fix Committed

Bug description:
  [ Impact ]

  This is a follow-up for bug #2065180 implementing the suggestion from
  comment #44 there.

  When compared to Ubuntu 23.10, creating intramfs files with update-
  initramfs takes 2 to 5 times more time on ARM devices.

  IIUC, dracut-install usage was added to initramfs-tools to speed up
  the process. But now its way slower. Even running update-initramfs on
  jammy, which doesn't use dracut-install, is way faster then the time
  taken on Noble.

  first bad commit -
  
https://github.com/dracutdevs/dracut/commit/3de4c7313260fb600507c9b87f780390b874c870

  Updating the initrd on a Raspberry Pi Zero 2W on Ubuntu 24.04 (noble)
  with initramfs-tools 0.142ubuntu25.1 takes over six minutes:

  ```
  bdrung@zero2w:~$ sudo hyperfine --warmup 1 -r 10 "update-initramfs -u"
  Benchmark 1: update-initramfs -u
    Time (mean ± σ): 402.751 s ± 5.592 s [User: 166.316 s, System: 228.909 s]
    Range (min … max): 394.380 s … 411.445 s 10 runs
  ```

  [ Test Plan ]

  1. Measure `update-initramfs -u` before the update.
  2. Log the content of the initrd before the update: `lsinitramfs 
/boot/initrd.img`
  3. update dracut-install / initramfs-tools-core
  4. Measure `update-initramfs -u`. It should be faster (the performance 
improvements on amd64 should be very small and might be within the measurement 
uncertainty).
  5. Check with lsinitramfs that the content of the newly generated initrd 
hasn't changed.

  [ Where problems could occur ]

  The code that is responsible for including the kernel modules into the
  initrd is touched. Negative consequences could be that some needed
  kernel modules will not be included any more (should be covered by the
  test case) or that building new initrds will fail.

  The initramfs-tools fix changes how manual_add_modules behaves.
  `manual_add_modules` does not copy kernel modules, but queues them for
  being copied when the newly added function `apply_add_modules` is
  called.

  I checked all instances of calls to `manual_add_modules` for possible
  regressions (see
  https://bugs.launchpad.net/ubuntu/+source/dracut/+bug/2065180/comments/15).
  Only miniramfs needs to be adjusted to also call `apply_add_modules`.
  But this change could break consumers of the `manual_add_modules`
  function that are outside of the Ubuntu archive. I googled for
  `apply_add_modules` but found no public outside users.

  [ Benchmarks ]

  Stock noble on a Raspberry Pi Zero 2W:

  ```
  bdrung@zero2w:~$ sudo hyperfine -r 5 "update-initramfs -u"
  Benchmark 1: update-initramfs -u
    Time (mean ± σ): 415.664 s ± 6.015 s [User: 166.728 s, System: 232.523 s]
    Range (min … max): 409.139 s … 422.632 s 5 runs
  ```

  noble with dracut-install 060+5-1ubuntu3.1 (with linux 6.8.0-1006.6 on
  2024-07-01):

  ```
  bdrung@zero2w:~$ sudo hyperfine --warmup 1 -r 10 "update-initramfs -u"
  Benchmark 1: update-initramfs -u
    Time (mean ± σ): 248.054 s ± 5.569 s [User: 67.410 s, System: 169.412 s]
    Range (min … max): 238.909 s … 257.384 s 10 runs
  ```

  noble with dracut-install 060+5-1ubuntu3.2 (with linux 6.8.0-1007 on
  2024-07-11):

  ```
  bdrung@zero2w:~$ sudo hyperfine --warmup 1 -r 10 "update-initramfs -u"
  Benchmark 1: update-initramfs -u
    Time (mean ± σ): 232.001 s ± 5.678 s [User: 55.456 s, System: 166.510 s]
    Range (min … max): 222.120 s … 239.610 s 10 runs
  ```

  noble with dracut-install 060+5-1ubuntu3.2 (with linux 6.8.0-1011.12
  and all updates on 2024-09-19):

  ```
  bdrung@zero2w:~$ sudo hyperfine --warmup 1 -r 10 "update-initramfs -u"
    Time (mean ± σ): 219.439 s ± 4.869 s [User: 45.626 s, System: 163.172 s]
    Range (min … max): 213.340 s … 227.411 s 10 runs
  ```

  [ Reduce manual_add_modules calls ]

  Besides making the dracut-install calls faster, group the dracut-
  install calls. Since the fix in oracular can cause regressions in
  custom hooks that rely on the current behavior, the SRU takes a safe
  approach which includes following packages (stating how many dracut-
  in

[Touch-packages] [Bug 2081020] Autopkgtest regression report (initramfs-tools/0.142ubuntu25.3)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted initramfs-tools (0.142ubuntu25.3) for 
noble have finished running.
The following regressions have been reported in tests triggered by the package:

zfs-linux/2.2.2-0ubuntu9 (s390x)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/noble/update_excuses.html#initramfs-tools

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank 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/2081020

Title:
  initrd: Ubuntu 24.04 fails to boot on UFS storage

Status in OEM Priority Project:
  Confirmed
Status in initramfs-tools package in Ubuntu:
  Fix Committed
Status in initramfs-tools source package in Noble:
  Fix Committed

Bug description:
  [Summary]

  Boot into initramfs after install 24.04 on UFS storage

  [Steps to reproduce]

  1. install ubuntu 24.04 on device with UFS storage
  2. reboot

  As additional SRU test:

  1. Store the list of files in the initrd before the package update:
  3cpio -t /boot/initrd.img > before
  2. Upgrade initramfs-tools to the fixed version
  3. Store the list of files in the initrd afterwards:
  3cpio -t /boot/initrd.img > after
  4. Compare the content of the initrd:
  diff -u before after
  5. The diff should only show (six) new kernel modules from drivers/ufs/host

  [Expected result]

  Boot into ubuntu desktop

  [Actual result]

  Boot into initramfs

  [Failure rate]

  100%

  [ Where problems could occur ]

  The initrd size will increase by 80 kB (see comment #6) and should not
  trigger people to run out of disk space.

  Generating the initrd during package upgrade could fail due to
  unrelated bugs, lack of disk space, or hardware failure.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/2081020/+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 2080223] Autopkgtest regression report (livecd-rootfs/2.765.50)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted livecd-rootfs (2.765.50) for jammy have 
finished running.
The following regressions have been reported in tests triggered by the package:

ubuntu-image/unknown (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#livecd-rootfs

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
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/2080223

Title:
  Ensure WSL instances do not rely on the Windows launcher by using the
  new build pipeline

Status in cloud-images:
  New
Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in wsl-setup package in Ubuntu:
  Fix Released
Status in livecd-rootfs source package in Jammy:
  Fix Committed
Status in ubuntu-meta source package in Jammy:
  Fix Committed
Status in wsl-setup source package in Jammy:
  Fix Committed
Status in livecd-rootfs source package in Noble:
  Fix Released
Status in ubuntu-meta source package in Noble:
  Fix Released
Status in wsl-setup source package in Noble:
  Fix Committed

Bug description:
  Note: all changes are related to each other and need to land together
  before next WSL image rebuild.

  Previously, WSL instances relied on a very lightweight build pipeline which 
was using the CPC image.
  In 22.04 we did a first step to have WSL has its own project in 
livecd-rootfs, with its own seed and image to produce a rootfs.

  However, a lot of ubuntu differentatior (enabling systemd by default,
  managing upgrade policy based on the distribution name, cloud-init
  enablement) were relying on an .exe file, ran on first launch, to
  ensure that those policies were modified.

  Microsoft is going to remove soon those launcher, and so, we won’t
  have an entrypoint to modify those policies. We thus needs to ship
  between one and three rootfs, varying on the upgrade policy (we
  produce multiple Windows applications on the store).

  This work has started on 24.04, and rely on cloud-init, (shipping pro client 
too for future wsl pro service offering). We thus needs to align our previous 
LTS on the latest state of art for WSL.
  Note that 20.04 will be more involved and will be treated separately. This is 
about aligning 22.04 and 24.04.

  What is needed in 22.04:
  - ensure livecd-rootfs can create between one and 3 tarballs, with different 
upgrade policy and enable systemd by default as a non conffiles.
  - ensure we ship the same set of default application (aligning the seed), to 
include cloud-init and other tools that developers expect on a WSL system. 
Also, the landscapes is shipped as it will be required with our new Pro on WSL 
offering. The only difference then with 24.04 is that we don»t ship 
wsl-pro-service in this SRU, but only when the beta launches.
  - ship wsl-setup:
    * it will drop some systemd experimentation (that was never enabled by 
default),
    * it’s moving all the systemd units adjustements to take into account a WSL 
environment (Microsoft kernel, being a distro inside its own namespace running 
in parallel to other distros…)
    * enable cloud init WSL datasource
    * remove core 22.04 support and installer wrapper script as we don’t ship 
snaps by default anymore nor installer.
    * report the status of cloud-init in MoTD if it fails

  What is needed in 24.04:
  - ship wsl-setup:
    * it’s moving all the systemd units adjustements to take into account a WSL 
environment (Microsoft kernel, being a distro inside its own namespace running 
in parallel to other distros…)
    * enable cloud init WSL datasource
    * remove core 22.04 support and installer wrapper script as we don’t ship 
snaps by default anymore nor installer.
    * report the status of cloud-init in MoTD if it fails

  [ Impact ]

  The impacts are primarly on new rootfses produced by our build pipeline with 
CPC. It allows CPC also to not special case 24.04 for rootfs publication.
  So, only new images could see an impact on 24.04 and 22.04 setup, which is 
easily spottable.
  The other set of impacts is on systemd units, ensuring that we have the 
systemd units executed with success as expected and have a working system in 
the end.

  Finally, aligning the set of components update in 22.04 which are the
  defaults tool installed by default, will ensure we are aligning with
  24.04.

  [ Test Plan ]

  1. Build new rootfses (with CPC), publish them on cloud-images.ubuntu.com
    -> we should see one image ending up with "ubuntults" for 22.04 image
    -> we should have 2 images for 24.04: "ubuntu" and "ubuntults".
  2. Build the Ubuntu (24.04), Ubuntu24.04 and Ub

[Touch-packages] [Bug 1597017] Autopkgtest regression report (apparmor/2.13.3-7ubuntu5.4)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted apparmor (2.13.3-7ubuntu5.4) for focal 
have finished running.
The following regressions have been reported in tests triggered by the package:

libvirt/unknown (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/focal/update_excuses.html#apparmor

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
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

[Touch-packages] [Bug 2055239] Autopkgtest regression report (ubuntu-advantage-tools/34~22.04)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted ubuntu-advantage-tools (34~22.04) for 
jammy have finished running.
The following regressions have been reported in tests triggered by the package:

software-properties/unknown (s390x)
update-motd/unknown (arm64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#ubuntu-advantage-tools

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
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/2055239

Title:
  Warning: The unit file, source configuration file or drop-ins of {apt-
  news,esm-cache}.service changed on disk. Run 'systemctl daemon-reload'
  to reload units.

Status in snapd:
  New
Status in systemd package in Ubuntu:
  Fix Released
Status in ubuntu-advantage-tools package in Ubuntu:
  Fix Released
Status in ubuntu-advantage-tools source package in Xenial:
  Fix Committed
Status in ubuntu-advantage-tools source package in Bionic:
  Fix Committed
Status in ubuntu-advantage-tools source package in Focal:
  Fix Committed
Status in ubuntu-advantage-tools source package in Jammy:
  Fix Committed
Status in systemd source package in Noble:
  Fix Released
Status in ubuntu-advantage-tools source package in Noble:
  Fix Committed

Bug description:
  [Impact]

  systemd may incorrectly mark units as needing a daemon reload,
  therefore unnecessarily printing the warning that a daemon-reload is
  needed for the changes to take effect. This is misleading to users,
  and particularly visible in cases like running apt update, since there
  is an apt hook (/etc/apt/apt.conf.d/20apt-esm-hook.conf) that starts
  two systemd services.

  [Test Plan]

  This bug can be triggered by running systemctl enable/disable on a 
non-existent unit. After that, calling systemctl start/status/etc. will show a 
false warning
  that the unit changed on disk. Hence, to test, simply:

  $ systemctl enable somethingthatdefinitelydoesnotexist.service
  $ systemctl status systemd-resolved.service 
  $ apt update

  On an effected system, warnings will be shown when calling both
  commands after the "enable non-existent unit" step.

  [Where problems could occur]

  This patch fixes a previous commit by ensuring that the
  manager->unit_file_state_outdated flag is set *only* when some
  modifications succeeded, but the overall operation failed. In cases
  where everything fails, it is not necessary to set the flag.

  Since the patch is restricted to this area, any regressions from this
  patch would most likely also be related to the NeedDaemonReload
  property of units.

  [Other information]

  The patch is from upstream:
  
https://github.com/systemd/systemd/pull/32610/commits/d69cba3bfffc7b1e3197e2a34b459db13b1e1cb7#diff-84bbf3361da4139a5620a035ebd24f50a0e4d4ece7952dc2d8b4325e6ebdf6e0L2320

  [Original Description]

  I recently started seeing the following warning messages when I run
  `apt update`.

  $ sudo apt update
  Warning: The unit file, source configuration file or drop-ins of 
apt-news.service changed on disk. Run 'systemctl daemon-reload' to reload units.
  Warning: The unit file, source configuration file or drop-ins of 
esm-cache.service changed on disk. Run 'systemctl daemon-reload' to reload 
units.
  ...

  apt-news.service for example is in /lib/systemd/system/apt-
  news.service and it's a static file managed by the package. Does the
  package maintenance script call systemd related hooks to reload the
  config whenever the package gets updated?

  $ systemctl cat apt-news.service
  # /usr/lib/systemd/system/apt-news.service
  # APT News is hosted at https://motd.ubuntu.com/aptnews.json and can include
  # timely information related to apt updates available to your system.
  ...

  $ dpkg -S /lib/systemd/system/apt-news.service
  ubuntu-pro-client: /lib/systemd/system/apt-news.service

  ProblemType: BugDistroRelease: Ubuntu 24.04
  Package: ubuntu-pro-client 31.1
  ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
  Uname: Linux 6.6.0-14-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 28 13:06:35 2024
  InstallationDate: Installed on 2024-01-08 (51 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240104)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=SourcePackage: ubuntu-advantage-tools
  UpgradeStatus: No upgrade log present (probably fresh install)
  apparmor_logs.txt:

  cloud-id.txt-error:
   Failed running command 'cloud-id' [exit(2)]. Message: REDACTED config part 
/etc/

[Touch-packages] [Bug 2055239] Autopkgtest regression report (ubuntu-advantage-tools/34~20.04)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted ubuntu-advantage-tools (34~20.04) for 
focal have finished running.
The following regressions have been reported in tests triggered by the package:

software-properties/unknown (armhf)
ubuntu-advantage-tools/unknown (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/focal/update_excuses.html#ubuntu-advantage-tools

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
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/2055239

Title:
  Warning: The unit file, source configuration file or drop-ins of {apt-
  news,esm-cache}.service changed on disk. Run 'systemctl daemon-reload'
  to reload units.

Status in snapd:
  New
Status in systemd package in Ubuntu:
  Fix Released
Status in ubuntu-advantage-tools package in Ubuntu:
  Fix Released
Status in ubuntu-advantage-tools source package in Xenial:
  Fix Committed
Status in ubuntu-advantage-tools source package in Bionic:
  Fix Committed
Status in ubuntu-advantage-tools source package in Focal:
  Fix Committed
Status in ubuntu-advantage-tools source package in Jammy:
  Fix Committed
Status in systemd source package in Noble:
  Fix Released
Status in ubuntu-advantage-tools source package in Noble:
  Fix Committed

Bug description:
  [Impact]

  systemd may incorrectly mark units as needing a daemon reload,
  therefore unnecessarily printing the warning that a daemon-reload is
  needed for the changes to take effect. This is misleading to users,
  and particularly visible in cases like running apt update, since there
  is an apt hook (/etc/apt/apt.conf.d/20apt-esm-hook.conf) that starts
  two systemd services.

  [Test Plan]

  This bug can be triggered by running systemctl enable/disable on a 
non-existent unit. After that, calling systemctl start/status/etc. will show a 
false warning
  that the unit changed on disk. Hence, to test, simply:

  $ systemctl enable somethingthatdefinitelydoesnotexist.service
  $ systemctl status systemd-resolved.service 
  $ apt update

  On an effected system, warnings will be shown when calling both
  commands after the "enable non-existent unit" step.

  [Where problems could occur]

  This patch fixes a previous commit by ensuring that the
  manager->unit_file_state_outdated flag is set *only* when some
  modifications succeeded, but the overall operation failed. In cases
  where everything fails, it is not necessary to set the flag.

  Since the patch is restricted to this area, any regressions from this
  patch would most likely also be related to the NeedDaemonReload
  property of units.

  [Other information]

  The patch is from upstream:
  
https://github.com/systemd/systemd/pull/32610/commits/d69cba3bfffc7b1e3197e2a34b459db13b1e1cb7#diff-84bbf3361da4139a5620a035ebd24f50a0e4d4ece7952dc2d8b4325e6ebdf6e0L2320

  [Original Description]

  I recently started seeing the following warning messages when I run
  `apt update`.

  $ sudo apt update
  Warning: The unit file, source configuration file or drop-ins of 
apt-news.service changed on disk. Run 'systemctl daemon-reload' to reload units.
  Warning: The unit file, source configuration file or drop-ins of 
esm-cache.service changed on disk. Run 'systemctl daemon-reload' to reload 
units.
  ...

  apt-news.service for example is in /lib/systemd/system/apt-
  news.service and it's a static file managed by the package. Does the
  package maintenance script call systemd related hooks to reload the
  config whenever the package gets updated?

  $ systemctl cat apt-news.service
  # /usr/lib/systemd/system/apt-news.service
  # APT News is hosted at https://motd.ubuntu.com/aptnews.json and can include
  # timely information related to apt updates available to your system.
  ...

  $ dpkg -S /lib/systemd/system/apt-news.service
  ubuntu-pro-client: /lib/systemd/system/apt-news.service

  ProblemType: BugDistroRelease: Ubuntu 24.04
  Package: ubuntu-pro-client 31.1
  ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
  Uname: Linux 6.6.0-14-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 28 13:06:35 2024
  InstallationDate: Installed on 2024-01-08 (51 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240104)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=SourcePackage: ubuntu-advantage-tools
  UpgradeStatus: No upgrade log present (probably fresh install)
  apparmor_logs.txt:

  cloud-id.txt-error:
   Failed running command 'cloud-id' [exit(2)]. Message: REDACTED config 

[Touch-packages] [Bug 2055239] Autopkgtest regression report (ubuntu-advantage-tools/34~18.04)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted ubuntu-advantage-tools (34~18.04) for 
bionic have finished running.
The following regressions have been reported in tests triggered by the package:

ubuntu-advantage-tools/unknown (armhf)
update-manager/1:18.04.12 (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#ubuntu-advantage-tools

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
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/2055239

Title:
  Warning: The unit file, source configuration file or drop-ins of {apt-
  news,esm-cache}.service changed on disk. Run 'systemctl daemon-reload'
  to reload units.

Status in snapd:
  New
Status in systemd package in Ubuntu:
  Fix Released
Status in ubuntu-advantage-tools package in Ubuntu:
  Fix Released
Status in ubuntu-advantage-tools source package in Xenial:
  Fix Committed
Status in ubuntu-advantage-tools source package in Bionic:
  Fix Committed
Status in ubuntu-advantage-tools source package in Focal:
  Fix Committed
Status in ubuntu-advantage-tools source package in Jammy:
  Fix Committed
Status in systemd source package in Noble:
  Fix Released
Status in ubuntu-advantage-tools source package in Noble:
  Fix Committed

Bug description:
  [Impact]

  systemd may incorrectly mark units as needing a daemon reload,
  therefore unnecessarily printing the warning that a daemon-reload is
  needed for the changes to take effect. This is misleading to users,
  and particularly visible in cases like running apt update, since there
  is an apt hook (/etc/apt/apt.conf.d/20apt-esm-hook.conf) that starts
  two systemd services.

  [Test Plan]

  This bug can be triggered by running systemctl enable/disable on a 
non-existent unit. After that, calling systemctl start/status/etc. will show a 
false warning
  that the unit changed on disk. Hence, to test, simply:

  $ systemctl enable somethingthatdefinitelydoesnotexist.service
  $ systemctl status systemd-resolved.service 
  $ apt update

  On an effected system, warnings will be shown when calling both
  commands after the "enable non-existent unit" step.

  [Where problems could occur]

  This patch fixes a previous commit by ensuring that the
  manager->unit_file_state_outdated flag is set *only* when some
  modifications succeeded, but the overall operation failed. In cases
  where everything fails, it is not necessary to set the flag.

  Since the patch is restricted to this area, any regressions from this
  patch would most likely also be related to the NeedDaemonReload
  property of units.

  [Other information]

  The patch is from upstream:
  
https://github.com/systemd/systemd/pull/32610/commits/d69cba3bfffc7b1e3197e2a34b459db13b1e1cb7#diff-84bbf3361da4139a5620a035ebd24f50a0e4d4ece7952dc2d8b4325e6ebdf6e0L2320

  [Original Description]

  I recently started seeing the following warning messages when I run
  `apt update`.

  $ sudo apt update
  Warning: The unit file, source configuration file or drop-ins of 
apt-news.service changed on disk. Run 'systemctl daemon-reload' to reload units.
  Warning: The unit file, source configuration file or drop-ins of 
esm-cache.service changed on disk. Run 'systemctl daemon-reload' to reload 
units.
  ...

  apt-news.service for example is in /lib/systemd/system/apt-
  news.service and it's a static file managed by the package. Does the
  package maintenance script call systemd related hooks to reload the
  config whenever the package gets updated?

  $ systemctl cat apt-news.service
  # /usr/lib/systemd/system/apt-news.service
  # APT News is hosted at https://motd.ubuntu.com/aptnews.json and can include
  # timely information related to apt updates available to your system.
  ...

  $ dpkg -S /lib/systemd/system/apt-news.service
  ubuntu-pro-client: /lib/systemd/system/apt-news.service

  ProblemType: BugDistroRelease: Ubuntu 24.04
  Package: ubuntu-pro-client 31.1
  ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
  Uname: Linux 6.6.0-14-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 28 13:06:35 2024
  InstallationDate: Installed on 2024-01-08 (51 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240104)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=SourcePackage: ubuntu-advantage-tools
  UpgradeStatus: No upgrade log present (probably fresh install)
  apparmor_logs.txt:

  cloud-id.txt-error:
   Failed running command 'cloud-id' [exit(2)]. Message: REDACTED config 

[Touch-packages] [Bug 2055239] Autopkgtest regression report (ubuntu-advantage-tools/34~24.04)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted ubuntu-advantage-tools (34~24.04) for 
noble have finished running.
The following regressions have been reported in tests triggered by the package:

ubuntu-advantage-tools/unknown (armhf)
update-motd/unknown (armhf)
wsl-pro-service/unknown (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/noble/update_excuses.html#ubuntu-advantage-tools

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
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/2055239

Title:
  Warning: The unit file, source configuration file or drop-ins of {apt-
  news,esm-cache}.service changed on disk. Run 'systemctl daemon-reload'
  to reload units.

Status in snapd:
  New
Status in systemd package in Ubuntu:
  Fix Released
Status in ubuntu-advantage-tools package in Ubuntu:
  Fix Released
Status in ubuntu-advantage-tools source package in Xenial:
  Fix Committed
Status in ubuntu-advantage-tools source package in Bionic:
  Fix Committed
Status in ubuntu-advantage-tools source package in Focal:
  Fix Committed
Status in ubuntu-advantage-tools source package in Jammy:
  Fix Committed
Status in systemd source package in Noble:
  Fix Released
Status in ubuntu-advantage-tools source package in Noble:
  Fix Committed

Bug description:
  [Impact]

  systemd may incorrectly mark units as needing a daemon reload,
  therefore unnecessarily printing the warning that a daemon-reload is
  needed for the changes to take effect. This is misleading to users,
  and particularly visible in cases like running apt update, since there
  is an apt hook (/etc/apt/apt.conf.d/20apt-esm-hook.conf) that starts
  two systemd services.

  [Test Plan]

  This bug can be triggered by running systemctl enable/disable on a 
non-existent unit. After that, calling systemctl start/status/etc. will show a 
false warning
  that the unit changed on disk. Hence, to test, simply:

  $ systemctl enable somethingthatdefinitelydoesnotexist.service
  $ systemctl status systemd-resolved.service 
  $ apt update

  On an effected system, warnings will be shown when calling both
  commands after the "enable non-existent unit" step.

  [Where problems could occur]

  This patch fixes a previous commit by ensuring that the
  manager->unit_file_state_outdated flag is set *only* when some
  modifications succeeded, but the overall operation failed. In cases
  where everything fails, it is not necessary to set the flag.

  Since the patch is restricted to this area, any regressions from this
  patch would most likely also be related to the NeedDaemonReload
  property of units.

  [Other information]

  The patch is from upstream:
  
https://github.com/systemd/systemd/pull/32610/commits/d69cba3bfffc7b1e3197e2a34b459db13b1e1cb7#diff-84bbf3361da4139a5620a035ebd24f50a0e4d4ece7952dc2d8b4325e6ebdf6e0L2320

  [Original Description]

  I recently started seeing the following warning messages when I run
  `apt update`.

  $ sudo apt update
  Warning: The unit file, source configuration file or drop-ins of 
apt-news.service changed on disk. Run 'systemctl daemon-reload' to reload units.
  Warning: The unit file, source configuration file or drop-ins of 
esm-cache.service changed on disk. Run 'systemctl daemon-reload' to reload 
units.
  ...

  apt-news.service for example is in /lib/systemd/system/apt-
  news.service and it's a static file managed by the package. Does the
  package maintenance script call systemd related hooks to reload the
  config whenever the package gets updated?

  $ systemctl cat apt-news.service
  # /usr/lib/systemd/system/apt-news.service
  # APT News is hosted at https://motd.ubuntu.com/aptnews.json and can include
  # timely information related to apt updates available to your system.
  ...

  $ dpkg -S /lib/systemd/system/apt-news.service
  ubuntu-pro-client: /lib/systemd/system/apt-news.service

  ProblemType: BugDistroRelease: Ubuntu 24.04
  Package: ubuntu-pro-client 31.1
  ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
  Uname: Linux 6.6.0-14-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 28 13:06:35 2024
  InstallationDate: Installed on 2024-01-08 (51 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240104)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=SourcePackage: ubuntu-advantage-tools
  UpgradeStatus: No upgrade log present (probably fresh install)
  apparmor_logs.txt:

  cloud-id.txt-error:
   Failed running command 'cloud-id' [exit(2)]. M

[Touch-packages] [Bug 2055239] Autopkgtest regression report (ubuntu-advantage-tools/34~16.04)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted ubuntu-advantage-tools (34~16.04) for 
xenial have finished running.
The following regressions have been reported in tests triggered by the package:

ubuntu-advantage-tools/unknown (arm64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/xenial/update_excuses.html#ubuntu-advantage-tools

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
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/2055239

Title:
  Warning: The unit file, source configuration file or drop-ins of {apt-
  news,esm-cache}.service changed on disk. Run 'systemctl daemon-reload'
  to reload units.

Status in snapd:
  New
Status in systemd package in Ubuntu:
  Fix Released
Status in ubuntu-advantage-tools package in Ubuntu:
  Fix Released
Status in ubuntu-advantage-tools source package in Xenial:
  Fix Committed
Status in ubuntu-advantage-tools source package in Bionic:
  Fix Committed
Status in ubuntu-advantage-tools source package in Focal:
  Fix Committed
Status in ubuntu-advantage-tools source package in Jammy:
  Fix Committed
Status in systemd source package in Noble:
  Fix Released
Status in ubuntu-advantage-tools source package in Noble:
  Fix Committed

Bug description:
  [Impact]

  systemd may incorrectly mark units as needing a daemon reload,
  therefore unnecessarily printing the warning that a daemon-reload is
  needed for the changes to take effect. This is misleading to users,
  and particularly visible in cases like running apt update, since there
  is an apt hook (/etc/apt/apt.conf.d/20apt-esm-hook.conf) that starts
  two systemd services.

  [Test Plan]

  This bug can be triggered by running systemctl enable/disable on a 
non-existent unit. After that, calling systemctl start/status/etc. will show a 
false warning
  that the unit changed on disk. Hence, to test, simply:

  $ systemctl enable somethingthatdefinitelydoesnotexist.service
  $ systemctl status systemd-resolved.service 
  $ apt update

  On an effected system, warnings will be shown when calling both
  commands after the "enable non-existent unit" step.

  [Where problems could occur]

  This patch fixes a previous commit by ensuring that the
  manager->unit_file_state_outdated flag is set *only* when some
  modifications succeeded, but the overall operation failed. In cases
  where everything fails, it is not necessary to set the flag.

  Since the patch is restricted to this area, any regressions from this
  patch would most likely also be related to the NeedDaemonReload
  property of units.

  [Other information]

  The patch is from upstream:
  
https://github.com/systemd/systemd/pull/32610/commits/d69cba3bfffc7b1e3197e2a34b459db13b1e1cb7#diff-84bbf3361da4139a5620a035ebd24f50a0e4d4ece7952dc2d8b4325e6ebdf6e0L2320

  [Original Description]

  I recently started seeing the following warning messages when I run
  `apt update`.

  $ sudo apt update
  Warning: The unit file, source configuration file or drop-ins of 
apt-news.service changed on disk. Run 'systemctl daemon-reload' to reload units.
  Warning: The unit file, source configuration file or drop-ins of 
esm-cache.service changed on disk. Run 'systemctl daemon-reload' to reload 
units.
  ...

  apt-news.service for example is in /lib/systemd/system/apt-
  news.service and it's a static file managed by the package. Does the
  package maintenance script call systemd related hooks to reload the
  config whenever the package gets updated?

  $ systemctl cat apt-news.service
  # /usr/lib/systemd/system/apt-news.service
  # APT News is hosted at https://motd.ubuntu.com/aptnews.json and can include
  # timely information related to apt updates available to your system.
  ...

  $ dpkg -S /lib/systemd/system/apt-news.service
  ubuntu-pro-client: /lib/systemd/system/apt-news.service

  ProblemType: BugDistroRelease: Ubuntu 24.04
  Package: ubuntu-pro-client 31.1
  ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
  Uname: Linux 6.6.0-14-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 28 13:06:35 2024
  InstallationDate: Installed on 2024-01-08 (51 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240104)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=SourcePackage: ubuntu-advantage-tools
  UpgradeStatus: No upgrade log present (probably fresh install)
  apparmor_logs.txt:

  cloud-id.txt-error:
   Failed running command 'cloud-id' [exit(2)]. Message: REDACTED config part 
/etc/cloud/cloud.cfg.d/99-in

[Touch-packages] [Bug 2075337] Autopkgtest regression report (python-docker/5.0.3-1ubuntu1.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted python-docker (5.0.3-1ubuntu1.1) for 
noble have finished running.
The following regressions have been reported in tests triggered by the package:

magnum/18.0.0-0ubuntu1 (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/noble/update_excuses.html#python-docker

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
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:
  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 python-docker 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:
  Inva

[Touch-packages] [Bug 2077290] Autopkgtest regression report (gtk+3.0/3.24.41-4ubuntu1.2)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted gtk+3.0 (3.24.41-4ubuntu1.2) for noble 
have finished running.
The following regressions have been reported in tests triggered by the package:

apport/unknown (armhf)
bookletimposer/unknown (armhf)
dogtail/0.9.11-12 (armhf)
gnome-mastermind/0.4.0-4build2 (armhf)
gspell/1.12.2-1build4 (armhf)
gtksourceview4/unknown (armhf)
lablgtk3/3.1.4-1build3 (armhf)
libreoffice/4:24.2.5-0ubuntu0.24.04.2 (armhf)
netmate/unknown (armhf)
openjdk-21/21.0.4+7-1ubuntu2~24.04 (arm64)
openssh/1:9.6p1-3ubuntu13.5 (ppc64el)
slic3r-prusa/2.7.2+dfsg-1build2 (arm64)
surf/unknown (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/noble/update_excuses.html#gtk+3.0

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2077290

Title:
  [SRU] GLArea transparency broken

Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Noble:
  Fix Committed

Bug description:
  [Impact]

  In Noble a GtkGlArea widget with transparency doesn't show the GTK
  widgets beneath it correctly. This was a regression fixed in
  
https://gitlab.gnome.org/GNOME/gtk/-/commit/6754765a5a849ecbdd5c5fa60b5a6f80a968133e
  (released in 3.24.42).

  [Test Case]

  Run gdkgears:
  $ apt source gtk+3.0
  $ cd src/gtk+3.0-3.24.41
  $ meson _build
  $ ninja -C _build
  $ ./_build/tests/gdkgears
  Click "Alpha" checkbox.

  Expected results:
  Gears are shown with Gtk window background behind them.

  Observed results:
  Uninitialized buffer is shown behind gears (commonly looks like repeated 
contents of old window frames).

  [Regression potential]

  Issues can be expected in GTK3 widgets with a transparent background.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/2077290/+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 2078720] Autopkgtest regression report (apt/2.4.13)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted apt (2.4.13) for jammy have finished 
running.
The following regressions have been reported in tests triggered by the package:

apport/2.20.11-0ubuntu82.6 (s390x)
apt/2.4.13 (s390x)
auto-apt-proxy/14 (s390x)
debspawn/0.5.2-1 (arm64)
dgit/9.15 (armhf)
gcc-11/11.4.0-1ubuntu1~22.04 (arm64)
libqapt/3.0.5-1ubuntu1 (armhf)
ruby-debian/unknown (armhf)
sbuild/0.81.2ubuntu6 (arm64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#apt

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/2078720

Title:
  Upgrading from jammy to noble results in a linux-headers package being
  in a broken state

Status in apt package in Ubuntu:
  New
Status in linux-aws package in Ubuntu:
  Confirmed
Status in linux-gcp package in Ubuntu:
  Confirmed
Status in ubuntu-release-upgrader package in Ubuntu:
  Fix Released
Status in apt source package in Jammy:
  Fix Committed
Status in linux-aws source package in Jammy:
  New
Status in linux-gcp source package in Jammy:
  New
Status in apt source package in Noble:
  New
Status in linux-aws source package in Noble:
  New
Status in linux-gcp source package in Noble:
  New
Status in ubuntu-release-upgrader source package in Noble:
  In Progress

Bug description:
  (For APT SRU versioning, see https://wiki.ubuntu.com/AptUpdates)

  [Impact]
  Obsolete packages can be removed despite still having reverse dependencies 
installed, for example:

  Now that 24.04.1 has been released, 22.04 users are encouraged to upgrade to 
24.04 via the `do-release-upgrade` command. This issue was seen whilst testing 
this upgrade path.
  Upgrading and later rebooting a jammy GCP instance results in 
`linux-headers-6.5.0-1025-gcp` being a broken state.

  ```
  $ sudo apt install
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  You might want to run 'apt --fix-broken install' to correct these.
  The following packages have unmet dependencies:
   linux-headers-6.5.0-1025-gcp : Depends: linux-gcp-6.5-headers-6.5.0-1025 but 
it is not installable
  E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or 
specify a solution).
  ```
  `linux-gcp-6.5-headers-6.5.0-1025` is a dependency of 
`linux-image-6.5.0-1025-gcp` which is also not removed during the upgrade.

  ```
  $ apt-cache rdepends linux-headers-6.5.0-1025-gcp
  linux-headers-6.5.0-1025-gcp
  Reverse Depends:
    linux-image-6.5.0-1025-gcp
  $ apt-cache rdepends linux-image-6.5.0-1025-gcp
  linux-image-6.5.0-1025-gcp
  Reverse Depends:
  ```

  Running `apt --fix-broken install` resolves the error.
  ```
  $ sudo apt --fix-broken install
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  Correcting dependencies... Done
  The following packages will be REMOVED:
    linux-headers-6.5.0-1025-gcp
  0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
  After this operation, 27.9 MB disk space will be freed.
  Do you want to continue? [Y/n] y
  (Reading database ... 83770 files and directories currently installed.)
  Removing linux-headers-6.5.0-1025-gcp (6.5.0-1025.27~22.04.1) ...
  $ sudo apt install
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
  ```

  This issue was also observed after upgrading a jammy AWS instance to
  noble.

  ```
  $ sudo apt install
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  You might want to run 'apt --fix-broken install' to correct these.
  The following packages have unmet dependencies:
   linux-headers-6.5.0-1024-aws : Depends: linux-aws-6.5-headers-6.5.0-1024 but 
it is not installable
  E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or 
specify a solution).
  ```

  [Test plan]

  ## Jammy APT verification

  To prepare the VMs, follow the following scheme:

  $ lxc launch ubuntu:jammy jammy-to-noble --vm

  If using lxc shell or exec to connect to it, also perform the step
  below:

  $ lxc exec jammy-to-noble apt-mark lxd-agent-launcher # otherwise it
  resets

  On this jammy VM, edit /etc/update-manager/release-upgrades and set
  Prompt to "normal" (since release upgrades to noble via the lts prompt
  are temporarily blocked due to this bug)

  If this test run is meant to test the fix, then at this point you
  should install apt from jammy proposed. Otherwise, continue directly
  with the release upgrade.

  Then to continue with 

[Touch-packages] [Bug 2077741] Autopkgtest regression report (ubuntu-settings/24.04.5)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted ubuntu-settings (24.04.5) for noble 
have finished running.
The following regressions have been reported in tests triggered by the package:

network-manager/1.46.0-1ubuntu2 (arm64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/noble/update_excuses.html#ubuntu-settings

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu.
https://bugs.launchpad.net/bugs/2077741

Title:
  No default background  set for GNOME-Greeter

Status in ubuntu-settings package in Ubuntu:
  Fix Released
Status in ubuntu-settings source package in Noble:
  Fix Committed

Bug description:
  [ Impact ]

  While using Gnome-Initial-Setup launched from GDM (when no user > 1000
  is present on the machine), no background is set on GNOME-Greeter,
  leading to a solid blue background wallpaper.

  Gnome-Initial-Setup is currently used on OEM shipped devices to
  provide a first user setup flow. We plan to also use it for a
  Raspberry Pi first user flow. We have received lots of feedback that
  the solid blue background is not in line with the Flutter installer
  and looks like an error occurred / the wallpaper failed to load.

  By updating /usr/share/glib-2.0/schemas/10_ubuntu-
  settings.gschema.override with:

  ```
  # for GDM/DM
  # FIXME: move to :Ubuntu-Greeter once upstream supports this, see LP: #1788

  [org.gnome.desktop.interface:GNOME-Greeter]
  gtk-theme = 'Yaru'
  icon-theme = 'Yaru'
  cursor-theme = 'Yaru'
  font-name = 'Ubuntu 11'
  monospace-font-name = 'Ubuntu Mono 13'
  font-antialiasing = 'rgba'

  [org.gnome.login-screen]
  logo='/usr/share/plymouth/ubuntu-logo.png'

  + [org.gnome.desktop.background:GNOME-Greeter]
  + picture-uri = 'file:///usr/share/backgrounds/warty-final-ubuntu.png'
  + picture-uri-dark = 'file:///usr/share/backgrounds/ubuntu-wallpaper-d.png'
  + show-desktop-icons = false
  ```

  I was able to add in one. This will help improve the GIS installer
  flow for Raspberry Pi we plan to support in 24.10 and the OEMs

  ubuntu-settings:
    Installed: 24.04.3
  Ubuntu version: 24.04 LTS

  [ Test Plan ]

  To test this change, you can follow the test plan for Gnome-Initial-
  Setup up to the point where you have launched the GDM Gnome-Initial-
  Setup session and Gnome-Initial-Setup has appeared. You should see the
  default Ubuntu wallpaper, not a solid blue wallpaper, behind Gnome-
  Initial-Setup.

  https://wiki.ubuntu.com/DesktopTeam/TestPlans/GnomeInitialSetup

  
  [ Where problems could occur ]

  If the path to the wallpaper is invalid, the session reverts to its
  blue background, returning to its current state.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2077741/+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 2003027] Autopkgtest regression report (procps/2:4.0.4-4ubuntu3.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted procps (2:4.0.4-4ubuntu3.1) for noble 
have finished running.
The following regressions have been reported in tests triggered by the package:

c-icap/unknown (armhf)
dbus-test-runner/19.04.0-1build2 (s390x)
patroni/3.2.2-2 (s390x)
pslist/unknown (ppc64el)
ruby-em-socksify/unknown (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/noble/update_excuses.html#procps

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to procps in Ubuntu.
https://bugs.launchpad.net/bugs/2003027

Title:
  fq_codel qdisc compiled but not enabled on 22.10

Status in Ubuntu:
  Fix Released
Status in procps package in Ubuntu:
  Fix Released
Status in The Noble Numbat:
  Confirmed
Status in procps source package in Noble:
  Fix Committed
Status in The Oracular Oriole:
  Fix Released
Status in procps source package in Oracular:
  Fix Released

Bug description:
  [ Impact ]
  Starting with Ubuntu 22.10, the default qdisc regressed to pfifo_fast. This 
is due to a change we merged from Debian, removing systemd's 
/usr/lib/50-default.conf file. pfifo_fast does not prevent bufferbloat issues, 
severely degrading networking performance on Ubuntu systems.

  [ Test Plan ]
  On an Ubuntu VM, check that net.core.default_qdisc is set to 'fq_codel'. `tc 
qdisc show` should also confirm fq_codel is being used.

  halves@noble-vm:~$ sysctl net.core.default_qdisc
  net.core.default_qdisc = fq_codel

  halves@noble-vm:~$ tc qdisc show
  qdisc noqueue 0: dev lo root refcnt 2
  qdisc mq 0: dev enp5s0 root
  qdisc fq_codel 0: dev enp5s0 parent :1 limit 10240p flows 1024 quantum 1514 
target 5ms interval 100ms memory_limit 32Mb ecn drop_batch 64

  [ Where Problems Could Occur ]
  Users relying on the default pfifo_fast qdisc could see different networking 
behavior. Although fq_codel should be an across-the-board improvement over 
pfifo_fast, we could monitor network latency stats and throughput to make sure 
no weird regressions arise from the qdisc scheduler.

  [ Other Info ]
  Instead of adding a sysctl.conf file, Debian has decided to change their 
default kernel configs to use fq_codel. This has the disadvantage of being 
"hidden" from end users, instead of being a queryable setting in e.g. 
/etc/sysctl.d/, and all kernel documentation still refers to pfifo_fast as 
being the default.

  Systemd's /usr/lib/50-default.conf file includes a lot of other
  settings that are either overruled elsewhere (e.g. from procps) or are
  entirely missing from our stable releases. Introducing a diff from
  Debian to ship this file only for the net.core.default_qdisc changes
  seems excessive, so having a dedicated place under procps where other
  similar toggles are already present seems like the more appropriate
  solution.

  --
  [ Original Description ]
  fq_codel has been the default in ubuntu since #1436945

  It is also now the default in debian. Somewhere between 22.04 and
  22.10 though, it stopped being enabled by systemd? (it used to be
  enabled there via a sysctl), and thus 22.10 (I tried both ubuntu
  server and ubuntu studio) doesn't have it on. I rather *immediately*
  noticed this huge regression (I run my ethernet at 100Mbit, and thus
  immediately saw 400+ms latency) - and I hope it can be fixed in the
  next release?

  it can also be made the default via compiling it into the kernel as a
  kernel default.

  Aggh! death to fifos!

  root@localhost:~# sysctl -a | grep qdisc
  net.core.default_qdisc = pfifo_fast

  disc pfifo_fast 0: dev eth0 parent :1 bands 3 priomap 1 2 2 2 1 2 0 0 1 1 1 1 
1 1 1 1
   Sent 5250 bytes 53 pkt (dropped 0, overlimits 0 requeues 0)
   backlog 0b 0p requeues 0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/2003027/+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 2077490] Autopkgtest regression report (linux-firmware/20220329.git681281e4-0ubuntu3.33)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-firmware 
(20220329.git681281e4-0ubuntu3.33) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:

linux-firmware-raspi/unknown (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#linux-firmware

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank 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/2077490

Title:
  Error: out of memory while booting after installing the linux-firmware
  in proposed

Status in initramfs-tools package in Ubuntu:
  Invalid
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Jammy:
  Fix Committed

Bug description:
  [Impact]

  I found that there are some machines in cert lab can't boot after
  installing the linux-frimware in proposed with 6.8.0-40 kernel.

  After selecting booting with the 6.8.0-40 kernel, it shows error: out
  of memory on the screen then freeze.

  There aren't any journal logs available, since they froze at very
  early stage.

  Following are the machines got impacted for now
  https://certification.canonical.com/hardware/202306-31695/
  https://certification.canonical.com/hardware/202306-31696/

  Problem details:

  The linux-firmware package provides new (gigantic) firmware blobs and
  symlinks to directories that contain those. initramfs-tools can't
  handle the directory symlinks and puts multiple copies of the same
  blobs into the initrd blowing it up to a size where it becomes
  problematic on some machines.

  [Test Case]

  Verify the affected machine boots again with the updated firmware
  package.

  Install updated linux-firmware package and confirm that there are no
  duplicate firmware files in /lib/firmware and inside the initrd. Also
  verify that there are no broken symlinks.

  [Where Problems Could Occur]

  If the new symlinks are broken, we end up with drivers not finding
  their firmwares which results in non-functional HW components.

  [Notes]

  This is not a general solution for the problem of the ever growing
  size of the initrd. It just alleviate it some.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2077490/+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 2077685] Autopkgtest regression report (python-apt/2.7.7ubuntu3)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted python-apt (2.7.7ubuntu3) for noble 
have finished running.
The following regressions have been reported in tests triggered by the package:

apport/2.28.1-0ubuntu3.1 (arm64, armhf, ppc64el)
apt/2.7.14build2 (arm64)
ubuntu-advantage-tools/unknown (armhf)
ubuntu-dev-tools/unknown (s390x)
unattended-upgrades/unknown (s390x)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/noble/update_excuses.html#python-apt

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/2077685

Title:
  python3-apt_2.7.7ubuntu2 uninstallable on armhf

Status in apt package in Ubuntu:
  Triaged
Status in python-apt package in Ubuntu:
  Fix Released
Status in apt source package in Noble:
  Triaged
Status in python-apt source package in Noble:
  Fix Committed

Bug description:
  The python-apt 2.7.7ubuntu2 update has a versioned dependency on
  libapt-pkg6.0t64 (>= 2.8.1) (on armhf only). Presumably there's an
  armhf-only symbols difference resulting in the armhf package (and
  *only* the armhf package - none of i386, amd64, ppc64el, s390x, or
  riscv64 are affected) picking up this tighter dependency.

  The version of apt which could satisfy this is still in -proposed:
  ```
   apt | 2.7.14build2| noble   | source, amd64, arm64, armhf, i386, 
ppc64el, riscv64, s390x
   apt | 2.8.2   | noble-proposed  | source, amd64, arm64, armhf, i386, 
ppc64el, riscv64, s390x
  ```

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2077685/+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 2075337] Autopkgtest regression report (ubuntu-advantage-tools/33.2~24.04.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted ubuntu-advantage-tools (33.2~24.04.1) 
for noble have finished running.
The following regressions have been reported in tests triggered by the package:

update-motd/3.12 (i386)
wsl-pro-service/0.1.4 (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/noble/update_excuses.html#ubuntu-advantage-tools

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
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 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 Committed
Status in ubuntu-advantage-tools source package in Jammy:
  Invalid
Status in cloud-init source package in Noble:
  Fix Committed
Status in dh-python source package in Noble:
  Invalid
Status in python3-defaults source package in Noble:
  Fix Committed
Status in ubuntu-advantage-tools 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|targetcli-fb
  ubiquity|ubiquity
  ubiquity-frontend-debconf|ubiquity
  ubiquity-frontend-gtk|ubiquity
  ubuntu-drivers-common|ubuntu-drivers-common
  ubuntu-pro-client|ubuntu-advantage-tools
  walinuxagent|walinuxagent

  noble restricted:

  noble universe:
  a2d|a2d
  apertium-apy|apertium-apy
  blueman|blueman
  borgmatic|borgmatic
  condor|condor
  cpupower-gui|cpupower-gui
  debomatic|debomatic
  dell-recovery|dell-recovery
  deluge-web|deluge
  depthcharge-tools|depthcharge-tools
  dhcpy6d|dhcpy6d
  dkimpy-milter|dkimpy-milter
  fenrir|fenrir
  galileo|galileo
  glances|glances
  graphite-carbon|graphite-carbon
  grokmirror|grokmirror
  guerillabackup|guerillabackup
  ionit|ionit
  jupyterhub|jupyterhub
  liquidctl|liquidctl
  localslackirc|localslackirc
  logdata-anomaly-miner|logdata-anomaly-miner
  lomiri|lomiri
  mailman3|mailman3
  mailman3-full|mailman3
  matrix-sydent|matrix-sydent
  mom|mom
  mopidy|mopidy
  mpd-sima|mpd-sima
  nordugrid-arc-arex|nordugrid-arc
  notus-scanner|notus-scanner
  nrpe-ng|nrpe-ng
  onionprobe|onionprobe
  openscap-daemon|openscap-daemon
  ospd-openvas|ospd-openvas
  pagekite|pagekite
  pagure|pagure
  pagure-ev-server|pagure
  pagure-milters|pagure
  pglistener|pglistener
  pol

[Touch-packages] [Bug 2063200] Autopkgtest regression report (shadow/1:4.13+dfsg1-4ubuntu3.2)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted shadow (1:4.13+dfsg1-4ubuntu3.2) for 
noble have finished running.
The following regressions have been reported in tests triggered by the package:

mysql-8.0/8.0.37-0ubuntu0.24.04.1 (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/noble/update_excuses.html#shadow

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
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-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2076340] Autopkgtest regression report (postgresql-16/16.4-0ubuntu0.24.04.2)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted postgresql-16 (16.4-0ubuntu0.24.04.2) 
for noble have finished running.
The following regressions have been reported in tests triggered by the package:

dbconfig-common/unknown (armhf)
exim4/4.97-4ubuntu4.1 (ppc64el)
extra-window-functions/unknown (armhf)
hypopg/unknown (armhf)
isc-kea/2.4.1-3build3 (armhf)
jsquery/unknown (armhf)
libreoffice/unknown (armhf)
minetest/5.6.1+dfsg+~1.9.0mt8+dfsg-4build3 (armhf)
postgresql-prioritize/unknown (armhf)
sysbench/unknown (s390x)
tds-fdw/unknown (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/noble/update_excuses.html#postgresql-16

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
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 Released
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 p

[Touch-packages] [Bug 2064672] Autopkgtest regression report (apparmor/4.0.1really4.0.1-0ubuntu0.24.04.3)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted apparmor 
(4.0.1really4.0.1-0ubuntu0.24.04.3) for noble have finished running.
The following regressions have been reported in tests triggered by the package:

libextractor/unknown (armhf)
libreoffice/4:24.2.5-0ubuntu0.24.04.1 (arm64)
stress-ng/unknown (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/noble/update_excuses.html#apparmor

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
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/2064672

Title:
  [SRU] - fixes for apparmor on noble

Status in apparmor package in Ubuntu:
  In Progress
Status in apparmor source package in Noble:
  Fix Committed

Bug description:
  [ Impact ]

  This SRU has several fixes:

  add unconfined profile for tuxedo-control-center (Bug 2046844)
  fix issues appointed by coverity
  fix samba profile (https://gitlab.com/apparmor/apparmor/-/issues/386)
  fix redefinition of _ which caused an issue with translation, failing 
aa-enforce (https://gitlab.com/apparmor/apparmor/-/issues/387)
  add mount test for CVE-2016-1585 (Bug 1597017 and Bug 2023814)
  add network inet mediation documentation to apparmor.d
  fix inet conditionals to only generate rules for inet family 
(https://gitlab.com/apparmor/apparmor/-/issues/384)
  add unconfined wike profile (Bug 2060810)
  add unconfined foliate profile (Bug 2060767)
  fix chromium_browser profile 
(https://gitlab.com/apparmor/apparmor/-/merge_requests/1208)
  add profiles for Transmission family of Bittorrent clients
  add profile for unshare utility (Bug 2046844)
  add profile for bwrap utility (Bug 2046844)
  fix unconfined firefox profile to support mozilla.org download (Bug 2056297)
  fix getattr and setattr perm mapping on mqueue rules 
(https://gitlab.com/apparmor/apparmor/-/issues/377 and 
https://gitlab.com/apparmor/apparmor/-/issues/378)
  fix inet tests (https://gitlab.com/apparmor/apparmor/-/issues/376)
  fix sshd profile (Bug 2060100)
  fix apparmor tools to allow mount destination globbing 
(https://gitlab.com/apparmor/apparmor/-/issues/381)
  fix firefox profile (https://gitlab.com/apparmor/apparmor/-/issues/380)
  move pam-related permissions to abstractions/authentication 
(https://bugzilla.opensuse.org/show_bug.cgi?id=1220032)
  fix condition in policydb serialization to only encode xtable if 
kernel_supports_permstable32
  relax mount rules in utils to fix use of virtiofs and other file-system types

  [ Test Plan ]

  * Make sure to reboot after upgrading (Bug 2072811)
  This has been extensively tested via the AppArmor regression test
  script in the QA Regression Testing repo:
  https://git.launchpad.net/qa-regression-testing/tree/scripts/test-apparmor.py

  Steps:
  $ git clone https://git.launchpad.net/qa-regression-testing
  $ ./scripts/make-test-tarball ./scripts/test-apparmor.py 
  Copying: test-apparmor.py
  Copying: testlib.py
  Copying: install-packages
  Copying: packages-helper
  Copying: apparmor/

  Test files: /tmp/qrt-test-apparmor.tar.gz

  To run, copy the tarball somewhere, then do:
  $ tar -zxf qrt-test-apparmor.tar.gz
  $ cd ./qrt-test-apparmor
  $ sudo ./install-packages test-apparmor.py
  $ ./test-apparmor.py -v

  This script runs various tests against the installed apparmor
  package, as well as building and running the various upstream
  regression and other test suites against this installed package:
    - 
https://gitlab.com/apparmor/apparmor/-/tree/master/tests/regression/apparmor?ref_type=heads
    - 
https://gitlab.com/apparmor/apparmor/-/tree/master/utils/test?ref_type=heads
    - 
https://gitlab.com/apparmor/apparmor/-/tree/master/parser/tst?ref_type=heads
    - 
https://gitlab.com/apparmor/apparmor/-/tree/master/libraries/libapparmor/testsuite?ref_type=heads

  The final test output was:

  --
  Ran 62 tests in 1977.045s

  OK (skipped=3)

  georgia@sec-noble-amd64:~$ apt policy apparmor
  apparmor:
Installed: 4.0.1really4.0.1-0ubuntu0.24.04.3
Candidate: 4.0.1really4.0.1-0ubuntu0.24.04.3

  Run additional tests:

  1. Install wike and make sure the wike window opens when executed:
  $ sudo apt install wike
  $ wike

  2. Install foliate, download test epub and make sure it opens as expected:
  $ sudo apt install foliate
  $ wget 
https://github.com/daisy/epub-accessibility-tests/releases/download/fundamental-2.0/Fundamental-Accessibility-Tests-Basic-Functionality-v2.0.0.epub
  $ foliate Fundamental-Accessibility-Tests-Basic-Functionality-v2.0.0.epub

  3. Install transmission and make sure it starts properly:
  $ sudo apt install transmission
  $ transmission-gtk

  4. 

[Touch-packages] [Bug 2046844] Autopkgtest regression report (apparmor/4.0.1really4.0.1-0ubuntu0.24.04.3)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted apparmor 
(4.0.1really4.0.1-0ubuntu0.24.04.3) for noble have finished running.
The following regressions have been reported in tests triggered by the package:

libextractor/unknown (armhf)
libreoffice/4:24.2.5-0ubuntu0.24.04.1 (arm64)
stress-ng/unknown (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/noble/update_excuses.html#apparmor

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
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/2046844

Title:
  AppArmor user namespace creation restrictions cause many applications
  to crash with SIGTRAP

Status in AppArmor:
  New
Status in Wike:
  New
Status in akonadiconsole package in Ubuntu:
  Fix Released
Status in akregator package in Ubuntu:
  Fix Released
Status in angelfish package in Ubuntu:
  Fix Released
Status in apparmor package in Ubuntu:
  Fix Released
Status in bubblewrap package in Ubuntu:
  Fix Committed
Status in cantor package in Ubuntu:
  Fix Released
Status in devhelp package in Ubuntu:
  Fix Released
Status in digikam package in Ubuntu:
  Fix Released
Status in epiphany-browser package in Ubuntu:
  Fix Released
Status in evolution package in Ubuntu:
  Fix Released
Status in falkon package in Ubuntu:
  Fix Released
Status in firefox package in Ubuntu:
  Confirmed
Status in foliate package in Ubuntu:
  Fix Committed
Status in freecad package in Ubuntu:
  Invalid
Status in geary package in Ubuntu:
  Fix Released
Status in ghostwriter package in Ubuntu:
  Fix Released
Status in gnome-packagekit package in Ubuntu:
  Invalid
Status in goldendict-webengine package in Ubuntu:
  Fix Released
Status in guix package in Ubuntu:
  Confirmed
Status in kalgebra package in Ubuntu:
  Fix Released
Status in kchmviewer package in Ubuntu:
  Fix Released
Status in kdeplasma-addons package in Ubuntu:
  Fix Released
Status in kgeotag package in Ubuntu:
  Fix Released
Status in kiwix package in Ubuntu:
  Incomplete
Status in kmail package in Ubuntu:
  Fix Released
Status in konqueror package in Ubuntu:
  Fix Released
Status in kontact package in Ubuntu:
  Fix Released
Status in loupe package in Ubuntu:
  Fix Released
Status in marble package in Ubuntu:
  Fix Released
Status in notepadqq package in Ubuntu:
  Fix Released
Status in opam package in Ubuntu:
  Fix Released
Status in pageedit package in Ubuntu:
  Fix Released
Status in plasma-desktop package in Ubuntu:
  Fix Released
Status in plasma-welcome package in Ubuntu:
  Fix Released
Status in privacybrowser package in Ubuntu:
  Invalid
Status in qmapshack package in Ubuntu:
  Fix Released
Status in qutebrowser package in Ubuntu:
  Fix Released
Status in rssguard package in Ubuntu:
  Fix Released
Status in steam package in Ubuntu:
  Fix Released
Status in supercollider package in Ubuntu:
  Fix Released
Status in tellico package in Ubuntu:
  Fix Released
Status in tor package in Ubuntu:
  Confirmed
Status in wike package in Ubuntu:
  Fix Committed
Status in apparmor source package in Noble:
  Fix Committed

Bug description:
  Hi, I run Ubuntu development branch 24.04 and I have a problem with
  Epiphany browser 45.1-1 (Gnome Web): program doesn't launch, and I get
  this error

  $ epiphany
  bwrap: Creating new namespace failed: Permission denied

  ** (epiphany:12085): ERROR **: 14:44:35.023: Failed to fully launch 
dbus-proxy: Le processus fils s’est terminé avec le code 1
  Trappe pour point d'arrêt et de trace (core dumped)

  $ epiphany
  bwrap: Creating new namespace failed: Permission denied

  ** (epiphany:30878): ERROR **: 22:22:26.926: Failed to fully launch 
dbus-proxy: Le processus fils s’est terminé avec le code 1
  Trappe pour point d'arrêt et de trace (core dumped)

  Thanks for your help!

To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/2046844/+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 2060100] Autopkgtest regression report (apparmor/4.0.1really4.0.1-0ubuntu0.24.04.3)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted apparmor 
(4.0.1really4.0.1-0ubuntu0.24.04.3) for noble have finished running.
The following regressions have been reported in tests triggered by the package:

libextractor/unknown (armhf)
libreoffice/4:24.2.5-0ubuntu0.24.04.1 (arm64)
stress-ng/unknown (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/noble/update_excuses.html#apparmor

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
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/2060100

Title:
  denials from sshd in noble

Status in apparmor package in Ubuntu:
  Confirmed
Status in apparmor source package in Noble:
  Fix Committed

Bug description:
  2024-03-27T00:10:28.929314-04:00 image-ubuntu64 kernel: audit:
  type=1400 audit(1711512628.920:155): apparmor="DENIED"
  operation="bind" class="net" profile="/usr/sbin/sshd" pid=1290
  comm="sshd" family="unix" sock_type="stream" protocol=0
  requested_mask="bind" denied_mask="bind"
  addr="@63cf34db7fbab75f/bus/sshd/system"

  2024-03-27T00:41:09.791826-04:00 image-ubuntu64 kernel: audit:
  type=1107 audit(1711514469.771:333907): pid=703 uid=101
  auid=4294967295 ses=4294967295 subj=unconfined msg='apparmor="DENIED"
  operation="dbus_method_call"  bus="system"
  path="/org/freedesktop/login1"
  interface="org.freedesktop.login1.Manager"
  member="CreateSessionWithPIDFD" mask="send"
  name="org.freedesktop.login1" pid=4528 label="/usr/sbin/sshd"
  peer_pid=688 peer_label="unconfined"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2060100/+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 2072811] Autopkgtest regression report (apparmor/4.0.1really4.0.1-0ubuntu0.24.04.3)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted apparmor 
(4.0.1really4.0.1-0ubuntu0.24.04.3) for noble have finished running.
The following regressions have been reported in tests triggered by the package:

libextractor/unknown (armhf)
libreoffice/4:24.2.5-0ubuntu0.24.04.1 (arm64)
stress-ng/unknown (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/noble/update_excuses.html#apparmor

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
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/2072811

Title:
  Apparmor: New update broke flatpak with `apparmor="DENIED"`

Status in apparmor package in Ubuntu:
  Fix Released
Status in apparmor source package in Noble:
  Fix Committed
Status in apparmor source package in Oracular:
  Fix Released

Bug description:
  The recent apparmor update appear to have broken some flatpak's ability to 
save file, e.g.:
  - org.keepassxc.KeePassXC
  - org.ksnip.ksnip

  It seems update introduced a new profile ("/etc/apparmor.d/bwrap-
  userns-restrict"), which is causing the issue below.

   To reproduce 

  (I'm using KeepassXC as example, but same issue for ksnip):

  1. Install and run KeepassXC

  ```bash
  flatpak install org.keepassxc.KeePassXC
  flatpak run org.keepassxc.KeePassXC
  ```

  2. Got error: "Access error for config file
  /home//.var/app/org.keepassxc.KeePassXC/config/keepassxc/keepassxc.ini"

  Looking at `journalctl -f`, I see these apparmor DENIED entries:

  ```txt
  Jul 12 09:44:36 ubuntu2404 systemd[2144]: Started 
app-flatpak-org.keepassxc.KeePassXC-4010.scope.
  Jul 12 09:44:37 ubuntu2404 kernel: kauditd_printk_skb: 6 callbacks suppressed
  Jul 12 09:44:37 ubuntu2404 kernel: audit: type=1400 
audit(1720741477.106:310): apparmor="DENIED" operation="link" class="file" 
info="Failed name lookup - deleted entry" error=-2 profile="bwrap" 
name="/home//.var/app/org.keepassxc.KeePassXC/config/keepassxc/#317211" 
pid=4021 comm="keepassxc" requested_mask="l" denied_mask="l" fsuid=1000 
ouid=1000
  Jul 12 09:44:37 ubuntu2404 kernel: audit: type=1400 
audit(1720741477.106:311): apparmor="DENIED" operation="link" class="file" 
profile="bwrap" 
name="/home//.var/app/org.keepassxc.KeePassXC/config/keepassxc/keepassxc.ini"
 pid=4021 comm="keepassxc" requested_mask="l" denied_mask="l" fsuid=1000 
ouid=1000 
target="/home//.var/app/org.keepassxc.KeePassXC/config/keepassxc/#317211"
  Jul 12 09:44:37 ubuntu2404 kernel: audit: type=1400 
audit(1720741477.106:312): apparmor="DENIED" operation="link" class="file" 
info="Failed name lookup - deleted entry" error=-2 profile="unpriv_bwrap" 
name="/home//.var/app/org.keepassxc.KeePassXC/config/keepassxc/#317211" 
pid=4021 comm="keepassxc" requested_mask="l" denied_mask="l" fsuid=1000 
ouid=1000
  Jul 12 09:44:37 ubuntu2404 kernel: audit: type=1400 
audit(1720741477.106:313): apparmor="DENIED" operation="link" class="file" 
profile="unpriv_bwrap" 
name="/home//.var/app/org.keepassxc.KeePassXC/config/keepassxc/keepassxc.ini"
 pid=4021 comm="keepassxc" requested_mask="l" denied_mask="l" fsuid=1000 
ouid=1000 
target="/home//.var/app/org.keepassxc.KeePassXC/config/keepassxc/#317211"
  Jul 12 09:44:37 ubuntu2404 kernel: audit: type=1400 
audit(1720741477.341:314): apparmor="DENIED" operation="link" class="file" 
info="Failed name lookup - deleted entry" error=-2 profile="bwrap" 
name="/home//.var/app/org.keepassxc.KeePassXC/config/keepassxc/#317214" 
pid=4021 comm="keepassxc" requested_mask="l" denied_mask="l" fsuid=1000 
ouid=1000
  Jul 12 09:44:37 ubuntu2404 kernel: audit: type=1400 
audit(1720741477.341:315): apparmor="DENIED" operation="link" class="file" 
profile="bwrap" 
name="/home//.var/app/org.keepassxc.KeePassXC/config/keepassxc/keepassxc.ini"
 pid=4021 comm="keepassxc" requested_mask="l" denied_mask="l" fsuid=1000 
ouid=1000 
target="/home//.var/app/org.keepassxc.KeePassXC/config/keepassxc/#317214"
  Jul 12 09:44:37 ubuntu2404 kernel: audit: type=1400 
audit(1720741477.341:316): apparmor="DENIED" operation="link" class="file" 
info="Failed name lookup - deleted entry" error=-2 profile="unpriv_bwrap" 
name="/home//.var/app/org.keepassxc.KeePassXC/config/keepassxc/#317214" 
pid=4021 comm="keepassxc" requested_mask="l" denied_mask="l" fsuid=1000 
ouid=1000
  Jul 12 09:44:37 ubuntu2404 kernel: audit: type=1400 
audit(1720741477.341:317): apparmor="DENIED" operation="link" class="file" 
profile="unpriv_bwrap" 
name="/home//.var/app/org.keepassxc.KeePassXC/config/keepassxc/keepassxc.ini"
 pid=4021 comm="keepassxc" requested_mask="l" denied_mask="l" fsuid=1000 
ouid=1000 
target="/home//.var/app/org.keepassxc.KeePassXC/config/kee

[Touch-packages] [Bug 2069433] Autopkgtest regression report (software-properties/0.99.49.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted software-properties (0.99.49.1) for 
noble have finished running.
The following regressions have been reported in tests triggered by the package:

software-properties-qt/unknown (amd64, arm64, armhf, ppc64el, s390x)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/noble/update_excuses.html#software-properties

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/2069433

Title:
  Enabling new pockets does not enable deb-src for them, even if source
  code is enabled

Status in software-properties package in Ubuntu:
  Fix Released
Status in software-properties source package in Noble:
  Fix Committed

Bug description:
  [Impact]
  If you have Source Code enabled, and you change the pockets configuration to 
"all pockets", it will add -backports without source code. The Source Code flag 
will still be set in the UI, but after a reload, you can see it is in a mixed 
state.

  This is more notable now, because this splits up the deb822 paragraph
  into two: One for the deb, and one for deb-src, whereas it should
  remain one.

  [Test plan]
  1. Turn on source code, save and refresh sources, close app
  2. Turn "recommended updates" to "all updates", observe that -backports got 
added with deb-src, to the existing paragraph.

  [Where problems could occur]
  This incurs a performance regression, as we need to check the state of the 
source code flag after reloading sources. That said, this is of course 
necessary for the source code flag to be correct after reloading modified 
sources (it gets reset to False when reloading). And since we run in a dbus 
service, we may just be reloading without having made the changes ourselves, so 
we can't just cache the old value and restore it.

  That said, software-properties already times out on my oracular
  system.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2069433/+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 2073742] Autopkgtest regression report (software-properties/0.99.49.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted software-properties (0.99.49.1) for 
noble have finished running.
The following regressions have been reported in tests triggered by the package:

software-properties-qt/unknown (amd64, arm64, armhf, ppc64el, s390x)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/noble/update_excuses.html#software-properties

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/2073742

Title:
  [SRU] Enable support for Dalmation Cloud Archive

Status in software-properties package in Ubuntu:
  Fix Released
Status in software-properties source package in Noble:
  Fix Committed
Status in software-properties source package in Oracular:
  Fix Released

Bug description:
  Please add support for:

     cloud-archive:dalmation
     cloud-archive:dalmation-proposed

  This will also need to be SRU'd back to noble.

  [Impact]
  End users have to manually enable the dalmation cloud archive pockets.

  [Test case]
  sudo add-apt-repository cloud-archive:dalmation
  sudo add-apt-repository cloud-archive:dalmation-proposed
  apt policy python3-openstackclient

  Verify that the expected version is available to "apt policy", and
  report that version in the SRU verification bug comment.

  [Regression potential]
  Limited - just a data item addition

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2073742/+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 2061214] Autopkgtest regression report (software-properties/0.99.49)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted software-properties (0.99.49) for noble 
have finished running.
The following regressions have been reported in tests triggered by the package:

software-properties-qt/unknown (amd64, arm64, armhf, ppc64el, s390x)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/noble/update_excuses.html#software-properties

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/2061214

Title:
  [SRU] Software Sources is not compatible with deb822

Status in software-properties package in Ubuntu:
  Fix Released
Status in software-properties-qt package in Ubuntu:
  Fix Released
Status in software-properties source package in Noble:
  Fix Committed
Status in software-properties-qt source package in Noble:
  Fix Released

Bug description:
  [ Impact ]

  Ubuntu 24.04 now uses deb822 to represent software sources for deb
  packages, instead of /etc/apt/sources.list. The complete rationale for
  this change can be found here: https://discourse.ubuntu.com/t/spec-
  apt-deb822-sources-by-default/29333

  software-properties has two graphical frontends for editing these
  software sources, one is GTK-based and the other is Qt-based. When the
  underlying change to deb822 sources was made, the GTK-based frontend
  and the DBus backend interface gained support.

  The original bug report shown below informed us of the lack of deb822
  support in the Qt frontend, which results in a broken, non-functional
  interface when attempting to view or edit most values on the first two
  tabs. The fix for this is to implement a Qt dialog for deb822 sources
  that somewhat matches the existing GTK interface.

  [ Test Plan ]

  Install software-properties-qt 0.99.48 or earlier.

  Reproducing the bug:
   1. From the menu, open Software Sources. Alternatively, run `sudo -E 
software-properties-qt` in a terminal.
   2. Observe that all four checkboxes on the Ubuntu Software tab (main, 
universe, restricted, and multiverse) are unchecked.
   3. Move to the Other Software tab and observe that there are no items in the 
list.

  Upgrade to software-properties-qt 0.99.49.

  Intended functionality:
   1. From the menu, open Software Sources. Alternatively, run `sudo -E 
software-properties-qt` in a terminal.
   2. Observe that one or more checkboxes on the Ubuntu Software tab 
(representing main, universe, restricted, or multiverse) are checked. Toggle 
one or more of the checkboxes.
   3. Using a text editor of some kind (perhaps Vim), confirm that 
/etc/apt/sources.list.d/ubuntu.sources reflects your changes.
   4. Switch to the Other Software tab, there should be one item in the list.
   5. Select that item, then click Edit at the bottom of the dialog. Make a 
modification to every field on the screen, or a combination of fields you would 
like to test. All fields should work.
   6. Click the OK button at the bottom of the dialog to confirm the changes, 
then click Edit for that item again. The changes you made should be reflected 
(meaning, the changes were saved.)
   7. Using a text editor of some kind (perhaps Vim), confirm that 
/etc/apt/sources.list.d/ubuntu.sources reflects your changes.

  [ Where problems could occur ]

  This is well-tested code. That being said, the following small edge cases 
exist:
   - If you create a very large amount of rows, it infinitely expands the 
dialog without a scroll wheel. This is the same functionality as the GTK 
frontend.
   - Error validation is not performed on the deb822 lines, they are simply 
written to the ubuntu.sources file. This is good as a starting point, but also 
relies on the appropriate update notifier handling these errors. This is the 
same functionality as the GTK frontend.

  In a future update, this functionality could be broken by one or more of the 
following underlying changes:
   - Changes to the software-properties backend which are only implemented for 
the GTK frontend.
   - Changes to the location or formatting of the ubuntu.sources file.
   - Regressions in the Python bindings for Qt 5, which are rare but possible.
   - Regressions in Python itself.

  [ Other Info ]
   
  Ubuntu Studio's live ISO and installed system are affected by this. Only 
Lubuntu's installed system is affected by this.

  [ Original Report ]

  Upgrading Lubuntu Jammy to Lubuntu Noble using TUI results in
  "Software sources" not correctly updated after upgrade. Prompt= shows
  normal and not LTS

  Used command sudo do-release-upgrade -d

  Otherwise the upgrade is good

  see attached screenshot

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: sof

[Touch-packages] [Bug 2060721] Autopkgtest regression report (apt/2.8.2)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted apt (2.8.2) for noble have finished 
running.
The following regressions have been reported in tests triggered by the package:

apport/2.28.1-0ubuntu3.1 (armhf)
apt/2.8.2 (armhf, s390x)
auto-apt-proxy/14.1 (ppc64el, s390x)
cron/3.0pl1-184ubuntu2 (arm64, s390x)
dgit/11.8 (arm64, s390x)
gcc-11/11.4.0-9ubuntu1 (arm64)
gcc-12/12.3.0-17ubuntu1 (amd64, s390x)
gcc-13/13.2.0-23ubuntu4 (arm64, armhf)
gcc-14/unknown (armhf, s390x)
gcc-snapshot/1:20240117-1ubuntu1 (amd64, arm64, s390x)
open-build-service/unknown (armhf, s390x)
postgresql-debversion/unknown (s390x)
python-apt/unknown (s390x)
reportbug/unknown (s390x)
reprotest/unknown (s390x)
ubuntu-advantage-tools/unknown (s390x)
unattended-upgrades/unknown (s390x)
update-notifier/unknown (s390x)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/noble/update_excuses.html#apt

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/2060721

Title:
  APT 2.8.0: Promote weak key warnings to errors

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Noble:
  Fix Committed

Bug description:
  ⚠️ Only land this in the release/updates pocket after PPAs have been
  resigned

  (This bumps the apt version to 2.8.0. APT uses the odd/even number
  system, with 2.7.x being the development series for 2.8, and this is
  the only change left for the 2.8 release, save for some minor
  translation/test suite improvements)

  (Please also look at bug 2073126 for the follow-up changes to mitigate
  regression potential).

  [Impact]
  APT is currently just warning about keys that it should be rejecting to give 
Launchpad time to resign PPAs. This needs to be bumped to an error such that 
the crypto policy is fully implemented and we only trust keys that are still 
being trusted. #2055193

  A warning provides some help right now to third-parties to fix their
  repositories, but it's not *safe*: A repository could have multiple
  signing keys and be signed by a good key now, then later, a previous
  key still in trusted.gpg.d could be revoked and we'd degrade to
  warnings, which, given that we update in the background automatically,
  the user may not see.

  Other fixes:
  - The test suite has been made less flaky in two places
  - Documentation translation has been unfuzzied for URL changes in 2.7.14

  [Test plan]
  The vast regression test suite prevents regression in other components. 
Additional tests are:

  1. (promotion to error) Take a repository that has a weak RSA key warning, 
upgrade apt and check that it is an error
  2. (still valid) Check that the main Ubuntu repositories and/or resigned PPAs 
work correctly.

  We don't have any tests for the test changes or the documentation
  translation URL unfuzzying.

  [Where problems could occur]
  apt will start to fail updates of repositories with weak signing keys, but it 
will have warned users about that before. Given that it is still early in the 
cycle, and we only enable updates from 22.04.1 for 24.04.1, this seems the 
right tradeoff for future security.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2060721/+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 2073126] Autopkgtest regression report (apt/2.8.2)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted apt (2.8.2) for noble have finished 
running.
The following regressions have been reported in tests triggered by the package:

apport/2.28.1-0ubuntu3.1 (armhf)
apt/2.8.2 (armhf, s390x)
auto-apt-proxy/14.1 (ppc64el, s390x)
cron/3.0pl1-184ubuntu2 (arm64, s390x)
dgit/11.8 (arm64, s390x)
gcc-11/11.4.0-9ubuntu1 (arm64)
gcc-12/12.3.0-17ubuntu1 (amd64, s390x)
gcc-13/13.2.0-23ubuntu4 (arm64, armhf)
gcc-14/unknown (armhf, s390x)
gcc-snapshot/1:20240117-1ubuntu1 (amd64, arm64, s390x)
open-build-service/unknown (armhf, s390x)
postgresql-debversion/unknown (s390x)
python-apt/unknown (s390x)
reportbug/unknown (s390x)
reprotest/unknown (s390x)
ubuntu-advantage-tools/unknown (s390x)
unattended-upgrades/unknown (s390x)
update-notifier/unknown (s390x)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/noble/update_excuses.html#apt

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/2073126

Title:
  More nuanced public key algorithm revocation

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Noble:
  Fix Committed
Status in apt source package in Oracular:
  Fix Released

Bug description:
  (This is uploaded to noble as 2.8.1 per
  https://wiki.ubuntu.com/AptUpdates)

  [Impact]
  We have received feedback from users that use NIST-P256 keys for their 
repositories that are upset about receiving a warning. APT 2.8.0 in 
noble-proposed would bump the warning to an error, breaking them.

  We also revoked additional ECC curves, which may still be considered
  trusted, so we should not bump them to errors.

  Also existing users may have third-party repositories that use
  1024-bit RSA keys and we have not adequately informed them yet
  perhaps.

  [Solution]
  Hence we will restore all elliptic curve keys of 256 or more bit to trusted:

  
">=rsa2048,ed25519,ed448,nistp256,nistp384,nistp512,brainpoolP256r1,brainpoolP320r1,brainpoolP384r1,brainpoolP512r1,secp256k1";

  At the same time we will also introduce a more nuanced approach to
  revocations by introducing a 'next' level that issues a warning if the
  key is not allowed in it and a 'future' level that will issue an audit
  message with the --audit option.

  For the next level, we will set it to:

  ">=rsa2048,ed25519,ed448,nistp256,nistp384,nistp512"

  This means we restrict warnings to Brainpool curves and the secp256k1
  key, which we have not received any feedback about them being used
  yet.

  For the future level, we will take a strong approach to best practices
  as it is only seen when explictly running with --audit and the
  intention is to highlight best practices. It will be set to

  ">=rsa3072,ed25519,ed448";

  Which corresponds to the NIST recommendations for 2031 (and as little
  curves as possible).

  We are also introducing a mitigation for existing 24.04 systems to not
  upgrade the policy yet; by creating an apt.conf.d configuration file
  that temporarily allows the 1024-bit RSA keys if upgraded from apt
  2.7.x; with the plan to remove them in 24.04.2.

  [Test plan]
  Tests are included in the library unit tests for parsing the specification 
strings; we have also included a test for the gpgv method to ensure that it 
produces the correct outcome for both 'next' and 'future' revoked keys.

  A spot check with a 1024-bit RSA repository and a 4096 RSA repository
  would still be nice.

  Check a clean install of apt/an upgrade from mantic vs an existing
  noble system:

  - An existing noble system should create 
/etc/apt/apt.conf.d/00-temporary-rsa1024 and continue to trust weak RSA 
signatures with a warning
  - Bootstrap a new noble with proposed enabled using e.g. mmdebstrap and check 
that this is not the case
  - Also check upgrading from mantic directly to proposed and ensure that 1024R 
repositories are rejected.

  [Where problems could occur]
  There could of course be bugs in the implementation of the new feature; this 
could result in verification of files failing. This also happens if you specify 
an invalid `next` or `future` string.

  There cannot be any false positives: The new levels are only
  *additional* checks, anything not in the `Assert-Pubkey-Algo` list is
  still revoked.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2073126/+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] Autopkgtest regression report (postgresql-16/16.3-0ubuntu0.24.04.2)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted postgresql-16 (16.3-0ubuntu0.24.04.2) 
for noble have finished running.
The following regressions have been reported in tests triggered by the package:

bacula/13.0.4-1build3 (armhf)
dbconfig-common/unknown (armhf)
extra-window-functions/unknown (armhf)
gvmd/23.1.0-1ubuntu3 (armhf)
postgresql-16/16.3-0ubuntu0.24.04.2 (armhf)
prefix/1.2.10-2 (armhf)
slony1-2/unknown (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/noble/update_excuses.html#postgresql-16

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
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:
  New
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:
  New
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:
  New
Status in lapack package in Ubuntu:
  New
Status in libdeflate package in Ubuntu:
  New
Status in libseccomp package in Ubuntu:
  New
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 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 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) and s390x (LP:
  #2064538).

  Impact: These are no change uploads on architectures other than
  ppc64el and s390x. All of those packages already built

[Touch-packages] [Bug 2076340] Autopkgtest regression report (mysql-8.0/8.0.39-0ubuntu0.24.04.2)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted mysql-8.0 (8.0.39-0ubuntu0.24.04.2) for 
noble have finished running.
The following regressions have been reported in tests triggered by the package:

bacula/13.0.4-1build3 (arm64)
mysql-8.0/8.0.39-0ubuntu0.24.04.2 (s390x)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/noble/update_excuses.html#mysql-8.0

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
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:
  New
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:
  New
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:
  New
Status in lapack package in Ubuntu:
  New
Status in libdeflate package in Ubuntu:
  New
Status in libseccomp package in Ubuntu:
  New
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 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 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) and s390x (LP:
  #2064538).

  Impact: These are no change uploads on architectures other than
  ppc64el and s390x. All of those packages already built successful in
  oracular with the changed build flags.

  We will validate picking up the changed build flags by inspecting the
  log files on ppc64el and s

[Touch-packages] [Bug 2055239] Autopkgtest regression report (systemd/255.4-1ubuntu8.4)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted systemd (255.4-1ubuntu8.4) for noble 
have finished running.
The following regressions have been reported in tests triggered by the package:

aide/unknown (armhf)
apport/unknown (armhf)
apt/2.7.14build2 (s390x)
casync/unknown (armhf)
cockpit/unknown (armhf)
comitup/1.39-1 (armhf)
dhcpcd/unknown (armhf)
dropbear/unknown (armhf)
freeradius/unknown (armhf)
golang-github-coreos-go-systemd/unknown (armhf)
initramfs-tools/0.142ubuntu25.1 (armhf)
libcamera/0.2.0-3fakesync1build6 (armhf)
libsoup3/3.4.4-5build2 (armhf)
libvirt/10.0.0-2ubuntu8.3 (armhf)
mariadb/unknown (armhf)
netplan.io/1.0-2ubuntu1.2 (arm64, armhf)
nghttp2/unknown (armhf)
nix/unknown (armhf)
ovn/24.03.2-0ubuntu0.24.04.1 (arm64)
pgagroal/unknown (armhf)
policykit-1/unknown (armhf)
remctl/unknown (armhf)
sks/1.1.6+git20210302.c3ba6d5a-4build2 (armhf)
snapd/2.63+24.04ubuntu0.1 (s390x)
speech-dispatcher/unknown (armhf)
systemd-hwe/unknown (armhf)
tang/unknown (armhf)
tmux/unknown (armhf)
util-linux/2.39.3-9ubuntu6 (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/noble/update_excuses.html#systemd

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
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/2055239

Title:
  Warning: The unit file, source configuration file or drop-ins of {apt-
  news,esm-cache}.service changed on disk. Run 'systemctl daemon-reload'
  to reload units.

Status in snapd:
  New
Status in systemd package in Ubuntu:
  Fix Released
Status in ubuntu-advantage-tools package in Ubuntu:
  Invalid
Status in systemd source package in Noble:
  Fix Committed
Status in ubuntu-advantage-tools source package in Noble:
  Invalid

Bug description:
  [Impact]

  systemd may incorrectly mark units as needing a daemon reload,
  therefore unnecessarily printing the warning that a daemon-reload is
  needed for the changes to take effect. This is misleading to users,
  and particularly visible in cases like running apt update, since there
  is an apt hook (/etc/apt/apt.conf.d/20apt-esm-hook.conf) that starts
  two systemd services.

  [Test Plan]

  This bug can be triggered by running systemctl enable/disable on a 
non-existent unit. After that, calling systemctl start/status/etc. will show a 
false warning
  that the unit changed on disk. Hence, to test, simply:

  $ systemctl enable somethingthatdefinitelydoesnotexist.service
  $ systemctl status systemd-resolved.service 
  $ apt update

  On an effected system, warnings will be shown when calling both
  commands after the "enable non-existent unit" step.

  [Where problems could occur]

  This patch fixes a previous commit by ensuring that the
  manager->unit_file_state_outdated flag is set *only* when some
  modifications succeeded, but the overall operation failed. In cases
  where everything fails, it is not necessary to set the flag.

  Since the patch is restricted to this area, any regressions from this
  patch would most likely also be related to the NeedDaemonReload
  property of units.

  [Other information]

  The patch is from upstream:
  
https://github.com/systemd/systemd/pull/32610/commits/d69cba3bfffc7b1e3197e2a34b459db13b1e1cb7#diff-84bbf3361da4139a5620a035ebd24f50a0e4d4ece7952dc2d8b4325e6ebdf6e0L2320

  [Original Description]

  I recently started seeing the following warning messages when I run
  `apt update`.

  $ sudo apt update
  Warning: The unit file, source configuration file or drop-ins of 
apt-news.service changed on disk. Run 'systemctl daemon-reload' to reload units.
  Warning: The unit file, source configuration file or drop-ins of 
esm-cache.service changed on disk. Run 'systemctl daemon-reload' to reload 
units.
  ...

  apt-news.service for example is in /lib/systemd/system/apt-
  news.service and it's a static file managed by the package. Does the
  package maintenance script call systemd related hooks to reload the
  config whenever the package gets updated?

  $ systemctl cat apt-news.service
  # /usr/lib/systemd/system/apt-news.service
  # APT News is hosted at https://motd.ubuntu.com/aptnews.json and can include
  # timely information related to apt updates available to your system.
  ...

  $ dpkg -S /lib/systemd/system/apt-news.service
  ubuntu-pro-client: /lib/systemd/system/apt-news.service

  ProblemType: BugDistroRelease: Ubuntu 24.04
  Package: ubuntu-pro-client 31.1
  ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
  Uname: Linux 6.6.0-14-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 28 13:06:35 2024
  InstallationDate: Installed on 

[Touch-packages] [Bug 2076340] Autopkgtest regression report (zlib/1:1.3.dfsg-3.1ubuntu2.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted zlib (1:1.3.dfsg-3.1ubuntu2.1) for 
noble have finished running.
The following regressions have been reported in tests triggered by the package:

bacula/13.0.4-1build3 (armhf)
boost1.83/1.83.0-2.1ubuntu3 (arm64)
dolfin/2019.2.0~legacy20240219.1c52e83-1ubuntu4 (armhf)
dvisvgm/3.2.1+ds-1build1 (armhf)
gcc-10/10.5.0-4ubuntu2 (arm64)
gcc-11/11.4.0-9ubuntu1 (arm64)
gcc-snapshot/1:20240117-1ubuntu1 (armhf)
glib2.0/2.80.0-6ubuntu3.1 (armhf)
gwama/unknown (armhf)
haxe/1:4.3.3-1build2 (armhf)
libreoffice/4:24.2.5-0ubuntu0.24.04.1 (armhf)
libreoffice/unknown (arm64)
libwebsockets/4.3.3-1.1build3 (armhf)
nginx/1.24.0-2ubuntu7 (arm64)
octave/8.4.0-1build5 (armhf)
openjdk-21/21.0.4+7-1ubuntu2~24.04 (armhf)
opensaml/3.2.1-4.1build2 (armhf)
pristine-tar/1.50+nmu2build1 (armhf)
prometheus-cpp/1.0.2-2build2 (armhf)
protobuf/3.21.12-8.2build1 (armhf)
python-bx/0.11.0-4 (armhf)
qpdf/unknown (armhf)
r-cran-bio3d/2.4-4-1 (armhf)
rpm/unknown (armhf)
rspamd/unknown (armhf)
ruby-gnome/3.5.1-1build4 (armhf)
ruby3.2/3.2.3-1ubuntu0.24.04.1 (armhf)
rust-debcargo/unknown (armhf)
rust-grcov/unknown (armhf)
rust-libheif-sys/1.16.2-5 (armhf)
rustc/1.75.0+dfsg0ubuntu1-0ubuntu7 (armhf)
samba/2:4.19.5+dfsg-4ubuntu9 (armhf)
samtools-legacy/0.1.19+dfsg-6ubuntu1 (armhf)
scotch/unknown (armhf)
seaview/unknown (armhf)
seqtk/unknown (armhf)
simage/unknown (armhf)
sks/1.1.6+git20210302.c3ba6d5a-4build2 (armhf)
smalt/unknown (armhf)
sox/unknown (armhf)
spoa/unknown (armhf)
stress-ng/unknown (armhf)
sudo/unknown (armhf)
sumo/unknown (armhf)
swi-prolog/unknown (armhf)
yoshimi/unknown (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/noble/update_excuses.html#zlib

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
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:
  New
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:
  New
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:
  New
Status in lapack package in Ubuntu:
  New
Status in libdeflate package in Ubuntu:
  New
Status in libseccomp package in Ubuntu:
  New
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 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 packag

[Touch-packages] [Bug 2076340] Autopkgtest regression report (util-linux/2.39.3-9ubuntu6.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted util-linux (2.39.3-9ubuntu6.1) for 
noble have finished running.
The following regressions have been reported in tests triggered by the package:

agenda.app/unknown (armhf)
asterisk/unknown (armhf)
cmake-extras/1.7-2 (arm64)
ganeti-instance-debootstrap/unknown (s390x)
gnocchi/unknown (armhf)
gsequencer/unknown (armhf)
libdap/unknown (armhf)
netplan.io/1.0-2ubuntu1.2 (arm64)
ola/unknown (armhf)
openjdk-21/unknown (armhf)
openjdk-8/8u422-b05-1~24.04 (armhf)
rsyslog/unknown (arm64)
swupdate/2023.12.1+dfsg-1ubuntu5 (armhf)
urlview/unknown (armhf)
vm/unknown (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/noble/update_excuses.html#util-linux

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
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:
  New
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:
  New
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:
  New
Status in lapack package in Ubuntu:
  New
Status in libdeflate package in Ubuntu:
  New
Status in libseccomp package in Ubuntu:
  New
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 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 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 

[Touch-packages] [Bug 2076340] Autopkgtest regression report (systemd/255.4-1ubuntu8.4)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted systemd (255.4-1ubuntu8.4) for noble 
have finished running.
The following regressions have been reported in tests triggered by the package:

aide/unknown (armhf)
apport/unknown (armhf)
apt/2.7.14build2 (s390x)
casync/unknown (armhf)
cockpit/unknown (armhf)
comitup/1.39-1 (armhf)
dhcpcd/unknown (armhf)
dropbear/unknown (armhf)
freeradius/unknown (armhf)
golang-github-coreos-go-systemd/unknown (armhf)
initramfs-tools/0.142ubuntu25.1 (armhf)
libcamera/0.2.0-3fakesync1build6 (armhf)
libsoup3/3.4.4-5build2 (armhf)
libvirt/10.0.0-2ubuntu8.3 (armhf)
mariadb/unknown (armhf)
netplan.io/1.0-2ubuntu1.2 (arm64, armhf)
nghttp2/unknown (armhf)
nix/unknown (armhf)
ovn/24.03.2-0ubuntu0.24.04.1 (arm64)
pgagroal/unknown (armhf)
policykit-1/unknown (armhf)
remctl/unknown (armhf)
sks/1.1.6+git20210302.c3ba6d5a-4build2 (armhf)
snapd/2.63+24.04ubuntu0.1 (s390x)
speech-dispatcher/unknown (armhf)
systemd-hwe/unknown (armhf)
tang/unknown (armhf)
tmux/unknown (armhf)
util-linux/2.39.3-9ubuntu6 (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/noble/update_excuses.html#systemd

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
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:
  New
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:
  New
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:
  New
Status in lapack package in Ubuntu:
  New
Status in libdeflate package in Ubuntu:
  New
Status in libseccomp package in Ubuntu:
  New
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 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 C

[Touch-packages] [Bug 2076340] Autopkgtest regression report (qemu/1:8.2.2+ds-0ubuntu1.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted qemu (1:8.2.2+ds-0ubuntu1.1) for noble 
have finished running.
The following regressions have been reported in tests triggered by the package:

glance/unknown (armhf)
glib2.0/2.80.0-6ubuntu3.1 (armhf)
kworkflow/unknown (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/noble/update_excuses.html#qemu

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
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:
  New
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:
  New
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:
  New
Status in lapack package in Ubuntu:
  New
Status in libdeflate package in Ubuntu:
  New
Status in libseccomp package in Ubuntu:
  New
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 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 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) and s390x (LP:
  #2064538).

  Impact: These are no change uploads on architectures other than
  ppc64el and s390x. All of those packages already built successful in
  oracular with the changed build flags.

  We will validate picking up the changed build flags by inspecting the
  log files on ppc64el and s3

[Touch-packages] [Bug 2076340] Autopkgtest regression report (xz-utils/5.6.1+really5.4.5-1build0.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted xz-utils (5.6.1+really5.4.5-1build0.1) 
for noble have finished running.
The following regressions have been reported in tests triggered by the package:

apt/2.7.14build2 (arm64, armhf)
binutils/2.42-4ubuntu2 (armhf)
boost1.74/1.74.0+ds1-23.1ubuntu3 (arm64)
cmake/3.28.3-1build7 (armhf)
dovecot/1:2.3.21+dfsg1-2ubuntu5 (armhf)
dymo-cups-drivers/unknown (armhf)
freedom-maker/unknown (armhf)
golang-github-smira-go-xz/unknown (armhf)
kronosnet/unknown (armhf)
lintian-brush/0.152ubuntu1 (armhf)
mender-client/unknown (armhf)
morbig/unknown (armhf)
open-build-service/unknown (armhf)
rust-gweather-sys/unknown (armhf)
snapd/2.63+24.04ubuntu0.1 (s390x)
vtk9/unknown (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/noble/update_excuses.html#xz-utils

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
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:
  New
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:
  New
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:
  New
Status in lapack package in Ubuntu:
  New
Status in libdeflate package in Ubuntu:
  New
Status in libseccomp package in Ubuntu:
  New
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 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 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 

[Touch-packages] [Bug 2076340] Autopkgtest regression report (libzstd/1.5.5+dfsg2-2build1.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted libzstd (1.5.5+dfsg2-2build1.1) for 
noble have finished running.
The following regressions have been reported in tests triggered by the package:

apt/2.7.14build2 (s390x)
boost1.74/1.74.0+ds1-23.1ubuntu3 (arm64)
boost1.83/1.83.0-2.1ubuntu3 (arm64)
dovecot/1:2.3.21+dfsg1-2ubuntu5 (armhf)
gcc-12/unknown (armhf)
initramfs-tools/0.142ubuntu25.1 (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/noble/update_excuses.html#libzstd

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
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:
  New
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:
  New
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:
  New
Status in lapack package in Ubuntu:
  New
Status in libdeflate package in Ubuntu:
  New
Status in libseccomp package in Ubuntu:
  New
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 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 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) and s390x (LP:
  #2064538).

  Impact: These are no change uploads on architectures other than
  ppc64el and s390x. All of those packages already built successful in
  oracular with

[Touch-packages] [Bug 2076340] Autopkgtest regression report (icu/74.2-1ubuntu3.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted icu (74.2-1ubuntu3.1) for noble have 
finished running.
The following regressions have been reported in tests triggered by the package:

boost1.83/1.83.0-2.1ubuntu3 (arm64)
libreoffice/4:24.2.5-0ubuntu0.24.04.1 (armhf)
mysql-8.0/unknown (s390x)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/noble/update_excuses.html#icu

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
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:
  New
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:
  New
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:
  New
Status in lapack package in Ubuntu:
  New
Status in libdeflate package in Ubuntu:
  New
Status in libseccomp package in Ubuntu:
  New
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 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 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) and s390x (LP:
  #2064538).

  Impact: These are no change uploads on architectures other than
  ppc64el and s390x. All of those packages already built successful in
  oracular with the changed build flags.

  We will validate picking up the changed build flags by inspecting the
  log files 

[Touch-packages] [Bug 2076340] Autopkgtest regression report (postgresql-common/257build1.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted postgresql-common (257build1.1) for 
noble have finished running.
The following regressions have been reported in tests triggered by the package:

check-postgres/2.26.0-1 (arm64)
django-reversion/5.0.12-1 (arm64)
mediawiki-extension-codemirror/4.0.0~git20221204.b897975-1 (armhf)
postgresql-16/16.3-0ubuntu0.24.04.1 (armhf)
sqitch/unknown (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/noble/update_excuses.html#postgresql-common

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
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:
  New
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:
  New
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:
  New
Status in lapack package in Ubuntu:
  New
Status in libdeflate package in Ubuntu:
  New
Status in libseccomp package in Ubuntu:
  New
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 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 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) and s390x (LP:
  #2064538).

  Impact: These are no change uploads on architectures other than
  ppc64el and s390x. All of those packages already built successful in
  oracular

[Touch-packages] [Bug 2076340] Autopkgtest regression report (lapack/3.12.0-3build1.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted lapack (3.12.0-3build1.1) for noble 
have finished running.
The following regressions have been reported in tests triggered by the package:

arrayfire/unknown (armhf)
emmax/unknown (armhf)
octave-ltfat/unknown (armhf)
octave-optim/unknown (armhf)
prime-phylo/unknown (armhf)
psi4/unknown (armhf)
r-cran-lavasearch2/unknown (armhf)
r-cran-logspline/2.1.21-1 (armhf)
r-cran-msm/unknown (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/noble/update_excuses.html#lapack

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
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:
  New
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:
  New
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:
  New
Status in lapack package in Ubuntu:
  New
Status in libdeflate package in Ubuntu:
  New
Status in libseccomp package in Ubuntu:
  New
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 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 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) and s390x (LP:
  #2064538).

  Impact: These are no change uploads on architectures other than
  ppc64el and s390x. All of those packages alre

[Touch-packages] [Bug 2076340] Autopkgtest regression report (curl/8.5.0-2ubuntu10.3)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted curl (8.5.0-2ubuntu10.3) for noble have 
finished running.
The following regressions have been reported in tests triggered by the package:

apache2/2.4.58-1ubuntu8.4 (armhf)
asymptote/2.87+ds-1build2 (armhf)
cimg/3.2.1+dfsg-1 (armhf)
cmake/3.28.3-1build7 (armhf)
cod-tools/3.8.1+dfsg-1build3 (armhf)
cpanminus/1.7047-1 (armhf)
cryfs/0.11.4-1build5 (armhf)
curl/unknown (armhf)
debci/3.9 (armhf)
feh/3.10.1-1ubuntu0.1 (armhf)
flask-limiter/3.5.1-1 (armhf)
flask-restful/unknown (armhf)
fwupd/1.9.16-1 (arm64)
fwupd/unknown (armhf)
glances/unknown (armhf)
gnupod-tools/unknown (armhf)
gunicorn/unknown (armhf)
hddemux/0.5-1ubuntu3 (arm64)
hoteldruid/unknown (armhf)
ironic/unknown (armhf)
isc-kea/unknown (armhf)
libnginx-mod-http-geoip2/unknown (armhf)
libnginx-mod-http-headers-more-filter/unknown (armhf)
libreoffice/4:24.2.5-0ubuntu0.24.04.1 (arm64)
libreoffice/unknown (armhf)
libsoup3/3.4.4-5build2 (armhf)
mediawiki/unknown (armhf)
mediawiki-extension-youtube/1.9.3~git20221020.e005c0b-1 (armhf)
mediawiki-skin-greystuff/1.2.5~git20220922.60bda8c-2 (armhf)
munin/2.0.75-1ubuntu1 (armhf)
nagios-plugins-contrib/unknown (armhf)
orthanc-wsi/unknown (armhf)
pkg-perl-tools/0.78 (armhf)
placement/unknown (armhf)
poppler/unknown (armhf)
repmgr/unknown (armhf)
rsyslog/8.2312.0-3ubuntu9 (armhf)
ruby-ethon/0.16.0-1ubuntu1 (armhf)
rust-curl-sys/0.4.67-2 (armhf)
rust-debcargo/unknown (armhf)
rustc/1.75.0+dfsg0ubuntu1-0ubuntu7 (armhf)
strongswan/unknown (armhf)
swupdate/2023.12.1+dfsg-1ubuntu5 (armhf)
weborf/1.0-1build2 (armhf)
xmltooling/3.2.4-2.1build3 (s390x)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/noble/update_excuses.html#curl

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
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:
  New
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:
  New
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:
  New
Status in lapack package in Ubuntu:
  New
Status in libdeflate package in Ubuntu:
  New
Status in libseccomp package in Ubuntu:
  New
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 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:

[Touch-packages] [Bug 2076340] Autopkgtest regression report (openssh/1:9.6p1-3ubuntu13.5)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted openssh (1:9.6p1-3ubuntu13.5) for noble 
have finished running.
The following regressions have been reported in tests triggered by the package:

cryptsetup/2:2.7.0-1ubuntu4 (arm64)
fence-agents/4.12.1-2~exp1ubuntu4 (armhf)
libnet-openssh-perl/unknown (armhf)
mosh/1.4.0-1ubuntu3 (armhf)
snapd/2.63+24.04ubuntu0.1 (s390x)
ssh-agent-filter/unknown (armhf)
xen-tools/4.9.2-1 (arm64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/noble/update_excuses.html#openssh

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
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:
  New
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:
  New
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:
  New
Status in lapack package in Ubuntu:
  New
Status in libdeflate package in Ubuntu:
  New
Status in libseccomp package in Ubuntu:
  New
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 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 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) and s390x (LP:
  #2064538).

  Impact: These are no change uploads on architectures other than
  ppc64el and s390x. All of those packages already built s

[Touch-packages] [Bug 2076340] Autopkgtest regression report (lz4/1.9.4-1build1.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted lz4 (1.9.4-1build1.1) for noble have 
finished running.
The following regressions have been reported in tests triggered by the package:

apt/2.7.14build2 (arm64, s390x)
borgbackup/unknown (armhf)
mysql-8.0/8.0.39-0ubuntu0.24.04.1 (arm64)
rust-lz4-sys/unknown (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/noble/update_excuses.html#lz4

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
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:
  New
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:
  New
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:
  New
Status in lapack package in Ubuntu:
  New
Status in libdeflate package in Ubuntu:
  New
Status in libseccomp package in Ubuntu:
  New
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 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 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) and s390x (LP:
  #2064538).

  Impact: These are no change uploads on architectures other than
  ppc64el and s390x. All of those packages already built successful in
  oracular with the changed build flags.

  We will validate picking up the changed build flags by inspe

[Touch-packages] [Bug 2076340] Autopkgtest regression report (nettle/3.9.1-2.2build1.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted nettle (3.9.1-2.2build1.1) for noble 
have finished running.
The following regressions have been reported in tests triggered by the package:

curl/8.5.0-2ubuntu10.2 (armhf)
libarchive/unknown (armhf)
libjcat/unknown (armhf)
lighttpd/1.4.74-1ubuntu3 (armhf)
opendht/unknown (armhf)
openldap/2.6.7+dfsg-1~exp1ubuntu8 (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/noble/update_excuses.html#nettle

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
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:
  New
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:
  New
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:
  New
Status in lapack package in Ubuntu:
  New
Status in libdeflate package in Ubuntu:
  New
Status in libseccomp package in Ubuntu:
  New
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 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 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) and s390x (LP:
  #2064538).

  Impact: These are no change uploads on architectures other than
  ppc64el and s390x. All of those packages already built successful in
  oracular with the changed build flags.

  W

[Touch-packages] [Bug 2076340] Autopkgtest regression report (libseccomp/2.5.5-1ubuntu3.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted libseccomp (2.5.5-1ubuntu3.1) for noble 
have finished running.
The following regressions have been reported in tests triggered by the package:

apt/2.7.14build2 (s390x)
chrony/4.5-1ubuntu4.1 (arm64)
lxc/unknown (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/noble/update_excuses.html#libseccomp

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
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:
  New
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:
  New
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:
  New
Status in lapack package in Ubuntu:
  New
Status in libdeflate package in Ubuntu:
  New
Status in libseccomp package in Ubuntu:
  New
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 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 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) and s390x (LP:
  #2064538).

  Impact: These are no change uploads on architectures other than
  ppc64el and s390x. All of those packages already built successful in
  oracular with the changed build flags.

  We will validate picking up the changed build flags by inspecting the
  log files on ppc64el and s39

[Touch-packages] [Bug 2076340] Autopkgtest regression report (dbus/1.14.10-4ubuntu4.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted dbus (1.14.10-4ubuntu4.1) for noble 
have finished running.
The following regressions have been reported in tests triggered by the package:

apport/2.28.1-0ubuntu3.1 (armhf)
dbus-python/unknown (armhf)
dogtail/0.9.11-12 (armhf)
golang-github-containernetworking-plugins/1.1.1+ds1-3ubuntu0.24.04.1 (armhf)
gtg/0.6-7 (armhf)
ibus/1.5.29-2 (armhf)
libreoffice/4:24.2.5-0ubuntu0.24.04.1 (arm64, armhf)
pyatspi/2.46.1-1 (armhf)
snapd/unknown (s390x)
software-properties/unknown (amd64, arm64, armhf, i386, ppc64el, s390x)
sssd/2.9.4-1.1ubuntu6.1 (arm64)
tuned/2.21.0-1ubuntu2 (arm64)
vlc/3.0.20-3build6 (arm64)
xdg-dbus-proxy/unknown (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/noble/update_excuses.html#dbus

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
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:
  New
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:
  New
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:
  New
Status in lapack package in Ubuntu:
  New
Status in libdeflate package in Ubuntu:
  New
Status in libseccomp package in Ubuntu:
  New
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 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 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 batc

[Touch-packages] [Bug 2076340] Autopkgtest regression report (bzip2/1.0.8-5.1build0.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted bzip2 (1.0.8-5.1build0.1) for noble 
have finished running.
The following regressions have been reported in tests triggered by the package:

boost1.74/1.74.0+ds1-23.1ubuntu3 (arm64)
cmake/3.28.3-1build7 (armhf)
dose3/7.0.0-4build3 (armhf)
dovecot/1:2.3.21+dfsg1-2ubuntu5 (armhf)
mariadb/1:10.11.8-0ubuntu0.24.04.1 (armhf)
mariadb/unknown (s390x)
nix/2.18.1+dfsg-1ubuntu5 (armhf)
onscripter/20220816-1build1 (armhf)
pgbackrest/2.50-1build2 (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/noble/update_excuses.html#bzip2

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
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:
  New
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:
  New
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:
  New
Status in lapack package in Ubuntu:
  New
Status in libdeflate package in Ubuntu:
  New
Status in libseccomp package in Ubuntu:
  New
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 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 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) and s390x (LP:
  #2064538).

  Impact: These are no change uploads on architectures othe

[Touch-packages] [Bug 2076340] Autopkgtest regression report (gnutls28/3.8.3-1.1ubuntu3.2)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted gnutls28 (3.8.3-1.1ubuntu3.2) for noble 
have finished running.
The following regressions have been reported in tests triggered by the package:

apt/2.7.14build2 (s390x)
cmake/unknown (armhf)
curl/8.5.0-2ubuntu10.2 (armhf)
gavl/unknown (armhf)
glewlwyd/2.7.6+ds-2build2 (armhf)
gsasl/2.2.1-1willsync1build2 (armhf)
libgwenhywfar/unknown (armhf)
libjcat/unknown (armhf)
ncbi-tools6/unknown (armhf)
opendht/unknown (armhf)
rsyslog/8.2312.0-3ubuntu9 (arm64)
srt/unknown (armhf)
wireshark/4.2.2-1.1build3 (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/noble/update_excuses.html#gnutls28

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
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:
  New
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:
  New
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:
  New
Status in lapack package in Ubuntu:
  New
Status in libdeflate package in Ubuntu:
  New
Status in libseccomp package in Ubuntu:
  New
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 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 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) and s390x (LP:
  #20645

[Touch-packages] [Bug 2075337] Autopkgtest regression report (python3-defaults/3.12.3-0ubuntu2)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted python3-defaults (3.12.3-0ubuntu2) for 
noble have finished running.
The following regressions have been reported in tests triggered by the package:

backblaze-b2/1.3.8-6 (arm64)
bitstruct/8.15.1-1build3 (armhf)
boost1.74/1.74.0+ds1-23.1ubuntu3 (arm64)
boost1.83/1.83.0-2.1ubuntu3 (amd64)
cachy/0.3.0-4 (armhf)
check-patroni/unknown (s390x)
cmake/unknown (s390x)
colorspacious/1.1.2-5 (i386)
cov-core/unknown (s390x)
coz-profiler/unknown (s390x)
cppimport/22.08.02-2 (arm64)
crowdsec/1.4.6-6ubuntu0.24.04.1 (armhf)
csound/unknown (s390x)
cython-legacy/0.29.37-2ubuntu1 (s390x)
dh-cargo/unknown (s390x)
dh-ros/0.13.4 (amd64, arm64, armhf, i386, ppc64el, s390x)
django-auth-ldap/4.6.0-1 (armhf)
dolfin/2019.2.0~legacy20240219.1c52e83-1ubuntu4 (s390x)
dulwich/unknown (s390x)
gcc-13/13.2.0-23ubuntu4 (armhf, s390x)
gcc-14/14-20240412-0ubuntu1 (armhf)
gcc-9/9.5.0-6ubuntu2 (armhf)
git-delete-merged-branches/unknown (armhf)
git-filter-repo/2.38.0-2 (s390x)
gitless/0.8.8-4 (armhf)
glueviz/1.17.1+dfsg-1 (armhf)
gtk+2.0/2.24.33-4ubuntu1.1 (armhf)
hatop/0.8.2-2 (armhf)
hplip/3.23.12+dfsg0-0ubuntu5 (armhf)
ikiwiki-hosting/0.20220716-2 (arm64, armhf)
isc-kea/2.4.1-3build3 (armhf)
jc/1.25.1-1 (amd64, arm64, armhf, ppc64el, s390x)
jinja2/3.1.2-1ubuntu1.1 (s390x)
libmediainfo/24.01+dfsg-1build2 (s390x)
libreoffice/4:24.2.5-0ubuntu0.24.04.1 (arm64)
libreoffice/unknown (armhf, s390x)
lilypond/unknown (armhf)
m2crypto/0.40.1-2build2 (arm64, armhf)
mdtraj/1.9.9-1ubuntu2 (arm64)
netplan.io/1.0-2ubuntu1.2 (s390x)
neutron/unknown (s390x)
nibabel/5.2.1-1 (s390x)
npm2deb/0.3.0-12 (arm64)
numpy/1:1.26.4+ds-6ubuntu1 (armhf)
offpunk/2.2-1 (arm64, armhf, ppc64el, s390x)
onioncircuits/0.8.1-1 (armhf)
oscrypto/1.3.0-5 (armhf)
pacemaker/2.1.6-5ubuntu2 (armhf)
palettable/unknown (s390x)
passenger/6.0.17+ds-1ubuntu5 (arm64, s390x)
paste/unknown (armhf)
pastedeploy/3.1-1 (armhf)
pastedeploy/unknown (s390x)
patroni/3.2.2-2 (arm64)
pdb2pqr/3.6.1+dfsg-1 (armhf)
peptidebuilder/unknown (armhf)
petsc/3.19.6+dfsg1-2.2ubuntu2 (armhf)
pgq/unknown (armhf)
pgxnclient/unknown (armhf)
pipenv/2023.12.1+ds-1 (s390x)
podman-compose/1.0.6-1 (s390x)
postfix/3.8.6-1build2 (armhf)
prometheus-xmpp-alerts/unknown (armhf)
pwdsphinx/1.0.18-3 (armhf)
pyacidobasic/unknown (armhf)
pybluez/unknown (armhf)
pydantic/1.10.14-1 (armhf)
pydbus/unknown (armhf)
pydocstyle/unknown (s390x)
pyethash/unknown (armhf)
pyfuse3/3.3.0-0.1 (armhf)
pykeepass/unknown (s390x)
pylabels/unknown (armhf)
pylama/unknown (armhf)
pyninjotiff/0.4.0-3 (s390x)
pynormaliz/unknown (armhf)
pyproject-metadata/unknown (armhf)
pyprojroot/unknown (armhf)
pyrr/0.10.3-6 (i386)
pyspread/unknown (armhf)
pyswarms/unknown (armhf)
pytest-mpi/0.6-5 (armhf)
pytest-testinfra/unknown (s390x)
pytest-tornado/unknown (armhf)
pytest-twisted/1.14.0-3 (armhf)
python-aalib/0.4-3 (s390x)
python-airspeed/unknown (armhf)
python-ansible-compat/4.1.11-1 (s390x)
python-argon2/unknown (armhf)
python-authlib/unknown (armhf)
python-av/11.0.0-4build1 (armhf, s390x)
python-axolotl-curve25519/unknown (armhf)
python-bids-validator/1.14.1-1 (arm64, i386, ppc64el, s390x)
python-blessed/unknown (armhf)
python-bumps/unknown (armhf)
python-bx/unknown (s390x)
python-cai/unknown (armhf)
python-cassandra-driver/3.29.0-3build2 (armhf)
python-cepces/unknown (armhf)
python-certvalidator/unknown (armhf)
python-cffi/unknown (armhf)
python-clevercsv/0.8.2+ds-1build2 (armhf)
python-click/unknown (armhf)
python-click-default-group/unknown (armhf)
python-cmarkgfm/unknown (armhf)
python-consolekit/unknown (s390x)
python-cron-descriptor/unknown (armhf)
python-cryptography-vectors/41.0.7-2 (armhf)
python-daphne/4.0.0-1 (armhf)
python-datetimerange/unknown (armhf)
python-deprecation-alias/unknown (s390x)
python-django/3:4.2.11-1ubuntu1.2 (s390x)
python-django/unknown (armhf)
python-django-braces/unknown (armhf)
python-django-js-asset/unknown (armhf)
python-django-libsass/unknown (armhf)
python-django-navtag/unknown (armhf)
python-django-object-actions/unknown (armhf)
python-django-postgres-extra/unknown (armhf)
python-django-ratelimit/unknown (armhf)
python-django-split-settings/1.1.0-1 (armhf)
python-django-storages/1.14.2-1 (amd64, arm64, armhf, i386, ppc64el, s390x)
python-dogpile.cache/1.1.8-3 (s390x)
python-drizzle/unknown (armhf)
python-duckpy/3.2.0-3build1 (armhf, ppc64el, s390x)
python-exceptiongroup/1.2.0-1 (amd64, arm64, armhf, ppc64el)
python-executing/2.0.1-0.1 (s390x)
python-fabio/2023.6.0-3.1build1 (arm64, armhf)
python-fisx/unknown (armhf)
python-flask-marshmallow/unknown (armhf)
python-formencode/2.0.1-2ubuntu1 (s390x)
python-fusepy/unknown (armhf)
python-git/3.1.37-3 (s390x)
python-h5netcdf/1.3.0-1 (s390x)
python-hacking/unknown (armhf)
python-hashids/unknown (s390x)
python-html2text/unknown (armhf)
python-igraph/unknown (armhf)
python-ijson/unknown (armhf)
python-itemloaders/1.1.0-1 (amd64, arm64, ppc64el, s390x)
python-itemloaders/unknown (armhf)
python-itsdangerous/unknown (armhf, s390x)
python-laspy/unknow

[Touch-packages] [Bug 2076340] Autopkgtest regression report (cyrus-sasl2/2.1.28+dfsg1-5ubuntu3.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted cyrus-sasl2 (2.1.28+dfsg1-5ubuntu3.1) 
for noble have finished running.
The following regressions have been reported in tests triggered by the package:

librdkafka/unknown (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/noble/update_excuses.html#cyrus-sasl2

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
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:
  New
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:
  New
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:
  New
Status in lapack package in Ubuntu:
  New
Status in libdeflate package in Ubuntu:
  New
Status in libseccomp package in Ubuntu:
  New
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 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 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) and s390x (LP:
  #2064538).

  Impact: These are no change uploads on architectures other than
  ppc64el and s390x. All of those packages already built successful in
  oracular with the changed build flags.

  We will validate picking up the changed build flags by inspecting the
  log files on ppc64el and s390x.

To manage notifications about this

[Touch-packages] [Bug 2075337] Autopkgtest regression report (python3-defaults/3.10.6-1~22.04.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted python3-defaults (3.10.6-1~22.04.1) for 
jammy have finished running.
The following regressions have been reported in tests triggered by the package:

adsys/0.14.1~22.04 (arm64)
android-platform-system-core/1:10.0.0+r36-9 (arm64)
apbs/3.0.0+dfsg1-3build2 (amd64, arm64, armhf, s390x)
apparmor/3.0.4-2ubuntu2.3 (arm64)
astropy/5.0.2-1 (amd64)
automake-1.16/1:1.16.5-1.3 (armhf, s390x)
bambam/1.1.2+dfsg-3 (amd64, armhf, s390x)
bdebstrap/0.4.0-1 (s390x)
billiard/3.6.4.0-2 (amd64, ppc64el)
binoculars/0.0.10-1.1 (armhf)
binutils/2.38-4ubuntu2.6 (i386)
boost1.74/1.74.0-14ubuntu3 (arm64, armhf)
booth/1.0-237-gdd88847-4ubuntu2.2 (armhf)
ccdproc/2.3.0-2 (armhf)
ceilometer/2:18.1.0-0ubuntu1 (armhf)
chardet/4.0.0-1 (armhf)
cherrypy3/18.6.1-4 (arm64, armhf)
click-man/0.4.1-2 (armhf)
cloudpickle/2.0.0-1 (amd64, arm64, armhf, ppc64el, s390x)
cluster-glue/1.0.12-20ubuntu3 (amd64, arm64)
cmake-extras/1.6-1 (armhf)
colorclass/2.2.0-2.2 (armhf)
construct/2.10.67+dfsg1-1 (armhf)
crmsh/4.3.1-1ubuntu3 (armhf)
cryptominisat/5.8.0+dfsg1-2 (amd64, arm64, ppc64el, s390x)
dart/6.12.1+dfsg4-11build2 (armhf)
dasbus/unknown (s390x)
deap/1.3.1-3build1 (armhf)
diffoscope/205 (amd64, arm64, armhf, ppc64el, s390x)
dj-database-url/unknown (armhf)
dj-static/0.0.6-6 (armhf)
django-axes/5.24.0-1 (ppc64el)
django-q/1.3.9-3 (armhf)
django-tables/2.4.1-2 (armhf)
djoser/2.1.0-1 (armhf)
dnstwist/0~20220131-1 (amd64, armhf, ppc64el, s390x)
dolfin/2019.2.0~git20210928.3eacdb4-3build1 (amd64, arm64, ppc64el)
dothost/0.2-6 (armhf)
dovecot/1:2.3.16+dfsg1-3ubuntu2.2 (armhf)
dulwich/0.20.31-1.1build1 (s390x)
dulwich/unknown (armhf)
elementpath/2.5.0-1 (armhf)
evolution-data-server/3.44.4-0ubuntu1.1 (armhf)
faiss/1.7.2-5 (armhf)
fakesleep/0.1-2 (armhf)
fast5/0.6.5-6build1 (armhf)
fenics-dolfinx/1:0.3.0-13build1 (armhf)
fetchmail/6.4.27-1 (amd64)
firewalld/1.1.1-1ubuntu1 (arm64)
firewalld/unknown (armhf)
flask-migrate/unknown (s390x)
foo2zjs/20200505dfsg0-2ubuntu2.22.04.1 (armhf)
freeradius/3.0.26~dfsg~git20220223.1.00ed0241fa-0ubuntu3.2 (armhf)
galpy/1.6.0.post0-2build2 (armhf)
gau2grid/unknown (armhf)
gdspy/unknown (armhf)
geneagrapher/1.0c2+git20200719-1 (s390x)
gnome-photos/unknown (s390x)
heartbeat/1:3.0.6-12build1 (armhf)
heat/1:18.0.1-0ubuntu1.1 (armhf)
ikiwiki-hosting/0.20180719-2 (armhf)
ipywidgets/6.0.0-9 (armhf)
jaraco.text/unknown (armhf)
lammps/20220106.git7586adbb6a+ds1-2 (armhf)
ledger-autosync/1.0.3.7.g69f30ea-2 (armhf, s390x)
liblinear/2.3.0+dfsg-5 (armhf)
libproxy/unknown (armhf)
libreoffice/1:7.3.7-0ubuntu0.22.04.5 (arm64, armhf)
libsoup3/3.0.7-0ubuntu1 (s390x)
libvirt-python/unknown (armhf)
linux-aws-6.2/blacklisted (amd64, arm64)
linux-aws-6.5/unknown (arm64)
linux-azure-6.2/blacklisted (amd64, arm64)
linux-gcp-6.2/blacklisted (amd64, arm64)
linux-hwe-5.19/blacklisted (amd64, arm64, armhf, ppc64el, s390x)
linux-hwe-6.2/blacklisted (amd64, arm64, armhf, ppc64el, s390x)
linux-lowlatency-hwe-5.19/blacklisted (amd64, arm64)
linux-lowlatency-hwe-6.2/blacklisted (amd64, arm64)
linux-oem-6.0/blacklisted (amd64)
linux-oracle-6.2/blacklisted (arm64)
llvm-toolchain-12/1:12.0.1-19ubuntu3 (arm64)
mutatormath/3.0.1-1 (armhf)
mypy/0.942-1ubuntu1 (armhf)
nemo/5.2.4-1 (armhf)
network-manager/1.36.6-0ubuntu2 (arm64)
nghttp2/unknown (armhf)
nibabel/3.2.2-1 (s390x)
nodejs/12.22.9~dfsg-1ubuntu3.6 (s390x)
npm2deb/0.3.0-10 (s390x)
obsub/0.2-4 (arm64)
ola/unknown (arm64)
openrazer/3.2.0+dfsg-3 (armhf)
ostree/2022.2-3 (s390x)
panko/1:10.0.0-0ubuntu1 (armhf)
paramiko/2.9.3-0ubuntu1.2 (s390x)
parsero/unknown (armhf)
patroni/2.1.3-1 (s390x)
porechop/unknown (armhf)
postfix/3.6.4-1ubuntu1.3 (arm64)
protontricks/unknown (armhf)
py-ubjson/unknown (armhf)
pycxx/unknown (armhf)
pyemd/0.5.1-2build3 (armhf)
pygeoip/unknown (armhf)
pygresql/1:5.1.2-1build4 (armhf)
pykeepass/unknown (armhf)
pymarkups/3.1.3-2 (armhf)
pyninjotiff/0.4.0-1 (armhf)
pypuppetdb/2.2.0-1 (armhf)
pyqt5webengine/unknown (armhf)
pysha3/unknown (armhf)
pysmi/unknown (armhf)
pystemmer/unknown (armhf)
pysurfer/unknown (armhf)
pytest-dependency/unknown (armhf)
pytest-forked/unknown (armhf)
pytest-tornasync/unknown (armhf)
python-aiosmtpd/unknown (armhf)
python-av/unknown (armhf)
python-avro/unknown (arm64)
python-bids-validator/1.9.2-1 (amd64, arm64, armhf, ppc64el, s390x)
python-boltons/unknown (armhf)
python-certbot/unknown (armhf)
python-cleo/unknown (armhf)
python-click-default-group/unknown (armhf)
python-coverage/6.2+dfsg1-2build1 (armhf)
python-cups/unknown (armhf)
python-cutadapt/unknown (armhf)
python-daphne/3.0.2-1 (armhf)
python-debian/0.1.43ubuntu1.1 (arm64)
python-django/2:3.2.12-2ubuntu1.13 (s390x)
python-django-gravatar2/1.4.4-2 (s390x)
python-django-modelcluster/unknown (armhf)
python-django-mptt/unknown (armhf)
python-djvulibre/unknown (armhf)
python-docker/unknown (armhf)
python-docxcompose/unknown (armhf)
python-epimodels/unknown (armhf)
python-eventlet/0.30.2-5ubuntu2 (s390x)
python-exchangelib/4.6.1-1ubuntu1 (amd64, arm64, armhf, ppc64el, s390x)

[Touch-packages] [Bug 2076340] Autopkgtest regression report (rustc/1.75.0+dfsg0ubuntu1-0ubuntu7.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted rustc (1.75.0+dfsg0ubuntu1-0ubuntu7.1) 
for noble have finished running.
The following regressions have been reported in tests triggered by the package:

dh-cargo/unknown (armhf)
rust-isolang/unknown (s390x)
rust-unicode-width/unknown (armhf)
rust-wayland-scanner/0.31.0-1build1 (armhf)
rust-wayland-scanner/unknown (s390x)
rustc/1.75.0+dfsg0ubuntu1-0ubuntu7.1 (armhf, s390x)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/noble/update_excuses.html#rustc

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
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:
  New
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:
  New
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:
  New
Status in lapack package in Ubuntu:
  New
Status in libdeflate package in Ubuntu:
  New
Status in libseccomp package in Ubuntu:
  New
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:
  New
Status in qemu package in Ubuntu:
  New
Status in runc-app package in Ubuntu:
  New
Status in rustc package in Ubuntu:
  New
Status in s390-tools 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 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) and s390x (LP:
  #2064538).

  Impact: These are no change uploads on architectures other than
  ppc64el and s390x. All of those packages already built successful in
  oracular 

[Touch-packages] [Bug 2076340] Autopkgtest regression report (p11-kit/0.25.3-4ubuntu2.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted p11-kit (0.25.3-4ubuntu2.1) for noble 
have finished running.
The following regressions have been reported in tests triggered by the package:

sssd/unknown (s390x)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/noble/update_excuses.html#p11-kit

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
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:
  New
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:
  New
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:
  New
Status in lapack package in Ubuntu:
  New
Status in libdeflate package in Ubuntu:
  New
Status in libseccomp package in Ubuntu:
  New
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:
  New
Status in qemu package in Ubuntu:
  New
Status in runc-app package in Ubuntu:
  New
Status in rustc package in Ubuntu:
  New
Status in s390-tools 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 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) and s390x (LP:
  #2064538).

  Impact: These are no change uploads on architectures other than
  ppc64el and s390x. All of those packages already built successful in
  oracular with the changed build flags.

  We will validate picking up the changed build flags by inspecting the
  log files on ppc64el and s390x.

To manage notifications about this bug go to:
https://bugs.launchpad.net

[Touch-packages] [Bug 2076340] Autopkgtest regression report (python-greenlet/3.0.3-0ubuntu5.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted python-greenlet (3.0.3-0ubuntu5.1) for 
noble have finished running.
The following regressions have been reported in tests triggered by the package:

cinder/unknown (armhf, s390x)
heat/unknown (s390x)
httpbin/unknown (s390x)
manila/1:18.0.1-0ubuntu2 (arm64)
manila/unknown (armhf)
nova/unknown (s390x)
python-futurist/2.4.1-3 (arm64)
python-futurist/unknown (armhf, s390x)
python-oslo.privsep/unknown (armhf, s390x)
python-oslo.service/3.4.0-0ubuntu1 (arm64)
python-oslo.service/unknown (armhf)
python-pynvim/unknown (s390x)
python-werkzeug/3.0.1-3ubuntu0.1 (armhf)
sqlacodegen/unknown (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/noble/update_excuses.html#python-greenlet

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
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:
  New
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:
  New
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:
  New
Status in lapack package in Ubuntu:
  New
Status in libdeflate package in Ubuntu:
  New
Status in libseccomp package in Ubuntu:
  New
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:
  New
Status in qemu package in Ubuntu:
  New
Status in runc-app package in Ubuntu:
  New
Status in rustc package in Ubuntu:
  New
Status in s390-tools 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 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 t

[Touch-packages] [Bug 2076340] Autopkgtest regression report (runc-app/1.1.12-0ubuntu3.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted runc-app (1.1.12-0ubuntu3.1) for noble 
have finished running.
The following regressions have been reported in tests triggered by the package:

opengcs/0.3.4+dfsg2-0ubuntu10 (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/noble/update_excuses.html#runc-app

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
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:
  New
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:
  New
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:
  New
Status in lapack package in Ubuntu:
  New
Status in libdeflate package in Ubuntu:
  New
Status in libseccomp package in Ubuntu:
  New
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:
  New
Status in qemu package in Ubuntu:
  New
Status in runc-app package in Ubuntu:
  New
Status in rustc package in Ubuntu:
  New
Status in s390-tools 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 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) and s390x (LP:
  #2064538).

  Impact: These are no change uploads on architectures other than
  ppc64el and s390x. All of those packages already built successful in
  oracular with the changed build flags.

  We will validate picking up the changed build flags by inspecting the
  log files on ppc64el and s390x.

To manage notifications about this bug go to:
https:/

[Touch-packages] [Bug 2064656] Autopkgtest regression report (gsettings-desktop-schemas/46.1-0ubuntu1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted gsettings-desktop-schemas 
(46.1-0ubuntu1) for noble have finished running.
The following regressions have been reported in tests triggered by the package:

at-spi2-core/unknown (arm64)
glib2.0/2.80.0-6ubuntu3.1 (arm64)
notify-osd/0.9.35+20.04.20191129-0ubuntu4 (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/noble/update_excuses.html#gsettings-desktop-schemas

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gsettings-desktop-schemas
in Ubuntu.
https://bugs.launchpad.net/bugs/2064656

Title:
  gnome-shell spams the journal with `Failed to parse translated string
  '„24h“' for key 'clock-format' in schema
  'org.gnome.desktop.interface': 0:expected value` multiple times every
  second for users using the lt_LT , ru_RU, Indonesian (id)  and maybe
  other locales

Status in GSettings Desktop Schemas:
  Fix Released
Status in gsettings-desktop-schemas package in Ubuntu:
  Fix Released
Status in gsettings-desktop-schemas source package in Noble:
  Fix Committed

Bug description:
  Impact
  --
  The systemd journal gets a lot of warnings about an incorrect translation for 
the default Ubuntu Desktop when used with certain languages including Georgian, 
Indonesian, Lithuanian, and Russian.

  This issue is much worse if someone has enabled the show Seconds
  option in the top bar clock.

  This issue is being fixed by packaging the new bugfix release of
  gsettings-desktop-schemas 46.1. There were only translation updates in
  this release.

  https://gitlab.gnome.org/GNOME/gsettings-desktop-
  schemas/-/compare/46.0...46.1

  Test Case
  -
  1. Open a terminal and run sudo apt install language-pack-gnome-lt
  2. Close the terminal
  3. Open the Settings app (gnome-control-center)
  4. In the side bar, click System, then Date & Time. Turn on Seconds.
  5. Close the Settings app.
  6. Open the Language Support app.
  You can click Remind me later if you see a warning that says "The language 
support is not installed completely."
  7. Drag Lietuvių to the top of the list.
  8. Log out
  9. Log back in.
  10. Open a terminal and run journalctl -f. You should not see any of the 
clock-format warnings mentioned in the Original Bug Report below.

  What Could Go Wrong
  ---
  As a component of GNOME core, there is a micro-release exception for 
gsettings-desktop-schemas.

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  Other Info
  --
  Because gsettings-desktop-schemas is included in Ubuntu language packs, this 
issue is actually only fixed with a language pack update. Ubuntu currently only 
updates language packs shortly before Ubuntu LTS point releases.

  Therefore, we will need to push this update without being able to
  verify the Test Case first.

  Original Bug Report
  ---
  After upgrading to Ubuntu 24.04 LTS I ran journalctl -f and noticed that 
gnome-shell was spamming errors at the rate of 12 lines every second:

  geg. 02 18:29:19 blynas gnome-shell[3980]: Failed to parse translated string 
'„24h“' for key 'clock-format' in schema 'org.gnome.desktop.interface': 
0:expected value
  geg. 02 18:29:19 blynas gnome-shell[3980]: Using untranslated default instead.
  geg. 02 18:29:20 blynas gnome-shell[3980]: Failed to parse translated string 
'„24h“' for key 'clock-format' in schema 'org.gnome.desktop.interface': 
0:expected value
  geg. 02 18:29:20 blynas gnome-shell[3980]: Using untranslated default instead.
  geg. 02 18:29:20 blynas gnome-shell[3980]: Failed to parse translated string 
'„24h“' for key 'clock-format' in schema 'org.gnome.desktop.interface': 
0:expected value
  geg. 02 18:29:20 blynas gnome-shell[3980]: Using untranslated default instead.
  geg. 02 18:29:20 blynas gnome-shell[3980]: Failed to parse translated string 
'„24h“' for key 'clock-format' in schema 'org.gnome.desktop.interface': 
0:expected value
  geg. 02 18:29:20 blynas gnome-shell[3980]: Using untranslated default instead.
  geg. 02 18:29:20 blynas gnome-shell[3980]: Failed to parse translated string 
'„24h“' for key 'clock-format' in schema 'org.gnome.desktop.interface': 
0:expected value
  geg. 02 18:29:20 blynas gnome-shell[3980]: Using untranslated default instead.
  geg. 02 18:29:20 blynas gnome-shell[3980]: Failed to parse translated string 
'„24h“' for key 'clock-format' in schema 'org.gnome.desktop.interface': 
0:expected value
  geg. 02 18:29:20 blynas gnome-shell[3980]: Using untranslated default instead.
  geg. 02 18:29:20 blynas gnome-shell[3980]: Failed to parse translated string 
'„24h“' for key 'clock-format' in schema 'org.gnome.desktop.interface': 
0:expected valu

[Touch-packages] [Bug 2072775] Autopkgtest regression report (gnome-online-accounts/3.50.4-0ubuntu2)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted gnome-online-accounts (3.50.4-0ubuntu2) 
for noble have finished running.
The following regressions have been reported in tests triggered by the package:

gvfs/1.54.0-1ubuntu2 (s390x)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/noble/update_excuses.html#gnome-online-accounts

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gnome-online-accounts in
Ubuntu.
https://bugs.launchpad.net/bugs/2072775

Title:
  Fastmail's WebDav, CalDav and CardDav is buggy

Status in gnome-online-accounts package in Ubuntu:
  Fix Released
Status in gnome-online-accounts source package in Noble:
  Fix Committed

Bug description:
  SRU Note
  
  We are using the exception to mention this bug in the SRU changelog for bug 
tracking but will not do individual verification of this fix before promoting 
to -updates.

  https://wiki.ubuntu.com/StableReleaseUpdates#Bug_references_in_changelogs

  Impact
  ==
  The new WebDav etc feature in Ubuntu 24.04 LTS does not support fastmail.com 
(or a different provider, mailbox.org) natively.

  This was fixed in
  https://gitlab.gnome.org/GNOME/gnome-online-accounts/-/commit/2efd2129
  and
  https://gitlab.gnome.org/GNOME/gnome-online-accounts/-/commit/cc6c0948
  which are included in gnome-online-accounts 3.50.1

  Test Case
  =
  None

  What Could Go Wrong
  ===
  See master bug for gnome-online-accounts 3.50.3 update LP: #2072782

  Original Bug Report
  ===
  Even though GNOME Online Accounts now natively supports WebDav, CalDav and 
CardDav, it doesn't work with Fastmail. This bug was recognised upstream, and 
has been fixed upstream in 3.50.1.

  Could Ubuntu release gnome-online-accounts 3.50.1 or newer in the
  Ubuntu 24.04 "updates" or "backports" repositories?

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: gnome-online-accounts 3.50.0-4ubuntu2
  ProcVersionSignature: Ubuntu 6.8.0-36.36-generic 6.8.4
  Uname: Linux 6.8.0-36-generic x86_64
  ApportVersion: 2.28.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jul 11 15:15:21 2024
  InstallationDate: Installed on 2021-06-24 (1113 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: gnome-online-accounts
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/2072775/+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 2072782] Autopkgtest regression report (gnome-online-accounts/3.50.4-0ubuntu2)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted gnome-online-accounts (3.50.4-0ubuntu2) 
for noble have finished running.
The following regressions have been reported in tests triggered by the package:

gvfs/1.54.0-1ubuntu2 (s390x)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/noble/update_excuses.html#gnome-online-accounts

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gnome-online-accounts in
Ubuntu.
https://bugs.launchpad.net/bugs/2072782

Title:
  Update gnome-online-accounts to 3.50.4

Status in gnome-online-accounts package in Ubuntu:
  Fix Committed
Status in gnome-online-accounts source package in Noble:
  Fix Committed

Bug description:
  Impact
  ==
  This is a new bugfix release in the stable 3.50.x series.

  It significantly improves the usability of the new "Microsoft 365"
  provider. However, that UI improvement changed translatable strings.
  See Other Info below.

  https://gitlab.gnome.org/GNOME/gnome-online-
  accounts/-/blob/3.50.4/NEWS

  It also improves the new WebDAV account type for Fastmail users. LP:
  #2072775

  Test Cases
  ==
  The autopkgtests for gnome-online-accounts should complete successfully

  Complete Test Case 2 (Google) from
  https://wiki.ubuntu.com/DesktopTeam/TestPlans/OnlineAccounts

  What Could Go Wrong
  ===
  gnome-online-accounts is included by default in Ubuntu Desktop, Edubuntu, 
Ubuntu Budgie & Ubuntu Cinnamon.

  If gnome-online-accounts is broken, people using Ubuntu may not
  receive notifications for emails and calendar appointments. This can
  be mitigated somewhat by using online services via a web browser and
  enabling notifications in their web browser.

  Before Ubuntu 24.04 LTS, gnome-online-accounts used webkit2gtk to
  handle authentication. By using the browser, gnome-online-accounts can
  handle many additional types of authentication and is more resilient
  to API changes and restrictions from the online service providers.

  GNOME Online Accounts is part of GNOME Core and is included in the
  GNOME micro release exception

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  Other Info
  ==
  This update includes changes to translatable strings. This package uses 
Ubuntu language packs. Because language packs are only updated shortly before 
each Ubuntu LTS point release, ideally this update will be included before the 
language packs are updated.

  The Ubuntu Desktop team considers the effect of changing translatable
  strings to be low because the changed strings were very new and
  weren't translated much. The strings are part of the Microsoft 365
  feature that is new in GNOME 46. The updated strings have been
  available upstream since late May and the translation coverage is
  better although still incomplete. We will likely do another SRU to
  include another upstream bugfix release (with updated translations)
  before Ubuntu 24.04.2.

  An update to translatable strings like this after a GNOME .0 release
  is very unusual. However, it was approved by the GNOME Release Team.
  Screenshots and more info at
  https://gitlab.gnome.org/Teams/Translation/Coordination/-/issues/158

  The backend library .symbols file indicates one removed symbol. It has
  been upstream's opinion for many years that the backend library is
  internal API and is subject to change. gnome-control-center is the
  only user of the backend API for Ubuntu 24.04 LTS and it never used
  that symbol. There is a separate frontend library, libgoa-1.0-0b,
  where it would be a serious issue if symbols were removed without the
  soname being bumped.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/2072782/+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 2072775] Autopkgtest regression report (gnome-online-accounts/3.50.4-0ubuntu1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted gnome-online-accounts (3.50.4-0ubuntu1) 
for noble have finished running.
The following regressions have been reported in tests triggered by the package:

gvfs/1.54.0-1ubuntu2 (s390x)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/noble/update_excuses.html#gnome-online-accounts

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gnome-online-accounts in
Ubuntu.
https://bugs.launchpad.net/bugs/2072775

Title:
  Fastmail's WebDav, CalDav and CardDav is buggy

Status in gnome-online-accounts package in Ubuntu:
  Fix Released
Status in gnome-online-accounts source package in Noble:
  Fix Committed

Bug description:
  SRU Note
  
  We are using the exception to mention this bug in the SRU changelog for bug 
tracking but will not do individual verification of this fix before promoting 
to -updates.

  https://wiki.ubuntu.com/StableReleaseUpdates#Bug_references_in_changelogs

  Impact
  ==
  The new WebDav etc feature in Ubuntu 24.04 LTS does not support fastmail.com 
(or a different provider, mailbox.org) natively.

  This was fixed in
  https://gitlab.gnome.org/GNOME/gnome-online-accounts/-/commit/2efd2129
  and
  https://gitlab.gnome.org/GNOME/gnome-online-accounts/-/commit/cc6c0948
  which are included in gnome-online-accounts 3.50.1

  Test Case
  =
  None

  What Could Go Wrong
  ===
  See master bug for gnome-online-accounts 3.50.3 update LP: #2072782

  Original Bug Report
  ===
  Even though GNOME Online Accounts now natively supports WebDav, CalDav and 
CardDav, it doesn't work with Fastmail. This bug was recognised upstream, and 
has been fixed upstream in 3.50.1.

  Could Ubuntu release gnome-online-accounts 3.50.1 or newer in the
  Ubuntu 24.04 "updates" or "backports" repositories?

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: gnome-online-accounts 3.50.0-4ubuntu2
  ProcVersionSignature: Ubuntu 6.8.0-36.36-generic 6.8.4
  Uname: Linux 6.8.0-36-generic x86_64
  ApportVersion: 2.28.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jul 11 15:15:21 2024
  InstallationDate: Installed on 2021-06-24 (1113 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: gnome-online-accounts
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/2072775/+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 2072782] Autopkgtest regression report (gnome-online-accounts/3.50.4-0ubuntu1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted gnome-online-accounts (3.50.4-0ubuntu1) 
for noble have finished running.
The following regressions have been reported in tests triggered by the package:

gvfs/1.54.0-1ubuntu2 (s390x)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/noble/update_excuses.html#gnome-online-accounts

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gnome-online-accounts in
Ubuntu.
https://bugs.launchpad.net/bugs/2072782

Title:
  Update gnome-online-accounts to 3.50.4

Status in gnome-online-accounts package in Ubuntu:
  Fix Committed
Status in gnome-online-accounts source package in Noble:
  Fix Committed

Bug description:
  Impact
  ==
  This is a new bugfix release in the stable 3.50.x series.

  It significantly improves the usability of the new "Microsoft 365"
  provider. However, that UI improvement changed translatable strings.
  See Other Info below.

  https://gitlab.gnome.org/GNOME/gnome-online-
  accounts/-/blob/3.50.4/NEWS

  It also improves the new WebDAV account type for Fastmail users. LP:
  #2072775

  Test Cases
  ==
  The autopkgtests for gnome-online-accounts should complete successfully

  Complete Test Case 2 (Google) from
  https://wiki.ubuntu.com/DesktopTeam/TestPlans/OnlineAccounts

  What Could Go Wrong
  ===
  gnome-online-accounts is included by default in Ubuntu Desktop, Edubuntu, 
Ubuntu Budgie & Ubuntu Cinnamon.

  If gnome-online-accounts is broken, people using Ubuntu may not
  receive notifications for emails and calendar appointments. This can
  be mitigated somewhat by using online services via a web browser and
  enabling notifications in their web browser.

  Before Ubuntu 24.04 LTS, gnome-online-accounts used webkit2gtk to
  handle authentication. By using the browser, gnome-online-accounts can
  handle many additional types of authentication and is more resilient
  to API changes and restrictions from the online service providers.

  GNOME Online Accounts is part of GNOME Core and is included in the
  GNOME micro release exception

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  Other Info
  ==
  This update includes changes to translatable strings. This package uses 
Ubuntu language packs. Because language packs are only updated shortly before 
each Ubuntu LTS point release, ideally this update will be included before the 
language packs are updated.

  The Ubuntu Desktop team considers the effect of changing translatable
  strings to be low because the changed strings were very new and
  weren't translated much. The strings are part of the Microsoft 365
  feature that is new in GNOME 46. The updated strings have been
  available upstream since late May and the translation coverage is
  better although still incomplete. We will likely do another SRU to
  include another upstream bugfix release (with updated translations)
  before Ubuntu 24.04.2.

  An update to translatable strings like this after a GNOME .0 release
  is very unusual. However, it was approved by the GNOME Release Team.
  Screenshots and more info at
  https://gitlab.gnome.org/Teams/Translation/Coordination/-/issues/158

  The backend library .symbols file indicates one removed symbol. It has
  been upstream's opinion for many years that the backend library is
  internal API and is subject to change. gnome-control-center is the
  only user of the backend API for Ubuntu 24.04 LTS and it never used
  that symbol. There is a separate frontend library, libgoa-1.0-0b,
  where it would be a serious issue if symbols were removed without the
  soname being bumped.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/2072782/+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] Autopkgtest regression report (libdeflate/1.19-1build1.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted libdeflate (1.19-1build1.1) for noble 
have finished running.
The following regressions have been reported in tests triggered by the package:

htslib/unknown (s390x)
libdeflate/unknown (s390x)
lighttpd/1.4.74-1ubuntu3 (armhf)
lighttpd/unknown (s390x)
notcurses/unknown (s390x)
plink2/unknown (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/noble/update_excuses.html#libdeflate

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
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:
  New
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:
  New
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:
  New
Status in lapack package in Ubuntu:
  New
Status in libdeflate package in Ubuntu:
  New
Status in libseccomp package in Ubuntu:
  New
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:
  New
Status in qemu package in Ubuntu:
  New
Status in runc-app package in Ubuntu:
  New
Status in rustc package in Ubuntu:
  New
Status in s390-tools 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 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) and s390x (LP:
  #2064538).

  Impact: These are no change uploads on architectures other than
  ppc64el and s390x. All of those packages already built successful in
  oracular with the changed build flags.

  We will validate picking up the change

[Touch-packages] [Bug 2076340] Autopkgtest regression report (golang-1.22/1.22.2-2ubuntu0.2)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted golang-1.22 (1.22.2-2ubuntu0.2) for 
noble have finished running.
The following regressions have been reported in tests triggered by the package:

golang-1.22/unknown (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/noble/update_excuses.html#golang-1.22

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
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:
  New
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:
  New
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:
  New
Status in lapack package in Ubuntu:
  New
Status in libdeflate package in Ubuntu:
  New
Status in libseccomp package in Ubuntu:
  New
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:
  New
Status in qemu package in Ubuntu:
  New
Status in runc-app package in Ubuntu:
  New
Status in rustc package in Ubuntu:
  New
Status in s390-tools 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 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) and s390x (LP:
  #2064538).

  Impact: These are no change uploads on architectures other than
  ppc64el and s390x. All of those packages already built successful in
  oracular with the changed build flags.

  We will validate picking up the changed build flags by inspecting the
  log files on ppc64el and s390x.

To manage notifications about this bug go to:
https://bug

[Touch-packages] [Bug 2072775] Autopkgtest regression report (gnome-online-accounts/3.50.4-0ubuntu1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted gnome-online-accounts (3.50.4-0ubuntu1) 
for noble have finished running.
The following regressions have been reported in tests triggered by the package:

gvfs/1.54.0-1ubuntu2 (s390x)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/noble/update_excuses.html#gnome-online-accounts

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gnome-online-accounts in
Ubuntu.
https://bugs.launchpad.net/bugs/2072775

Title:
  Fastmail's WebDav, CalDav and CardDav is buggy

Status in gnome-online-accounts package in Ubuntu:
  Fix Released
Status in gnome-online-accounts source package in Noble:
  Fix Committed

Bug description:
  SRU Note
  
  We are using the exception to mention this bug in the SRU changelog for bug 
tracking but will not do individual verification of this fix before promoting 
to -updates.

  https://wiki.ubuntu.com/StableReleaseUpdates#Bug_references_in_changelogs

  Impact
  ==
  The new WebDav etc feature in Ubuntu 24.04 LTS does not support fastmail.com 
(or a different provider, mailbox.org) natively.

  This was fixed in
  https://gitlab.gnome.org/GNOME/gnome-online-accounts/-/commit/2efd2129
  and
  https://gitlab.gnome.org/GNOME/gnome-online-accounts/-/commit/cc6c0948
  which are included in gnome-online-accounts 3.50.1

  Test Case
  =
  None

  What Could Go Wrong
  ===
  See master bug for gnome-online-accounts 3.50.3 update LP: #2072782

  Original Bug Report
  ===
  Even though GNOME Online Accounts now natively supports WebDav, CalDav and 
CardDav, it doesn't work with Fastmail. This bug was recognised upstream, and 
has been fixed upstream in 3.50.1.

  Could Ubuntu release gnome-online-accounts 3.50.1 or newer in the
  Ubuntu 24.04 "updates" or "backports" repositories?

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: gnome-online-accounts 3.50.0-4ubuntu2
  ProcVersionSignature: Ubuntu 6.8.0-36.36-generic 6.8.4
  Uname: Linux 6.8.0-36-generic x86_64
  ApportVersion: 2.28.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jul 11 15:15:21 2024
  InstallationDate: Installed on 2021-06-24 (1113 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: gnome-online-accounts
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/2072775/+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 2072782] Autopkgtest regression report (gnome-online-accounts/3.50.4-0ubuntu1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted gnome-online-accounts (3.50.4-0ubuntu1) 
for noble have finished running.
The following regressions have been reported in tests triggered by the package:

gvfs/1.54.0-1ubuntu2 (s390x)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/noble/update_excuses.html#gnome-online-accounts

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gnome-online-accounts in
Ubuntu.
https://bugs.launchpad.net/bugs/2072782

Title:
  Update gnome-online-accounts to 3.50.4

Status in gnome-online-accounts package in Ubuntu:
  Fix Committed
Status in gnome-online-accounts source package in Noble:
  Fix Committed

Bug description:
  Impact
  ==
  This is a new bugfix release in the stable 3.50.x series.

  It significantly improves the usability of the new "Microsoft 365"
  provider. However, that UI improvement changed translatable strings.
  See Other Info below.

  https://gitlab.gnome.org/GNOME/gnome-online-
  accounts/-/blob/3.50.4/NEWS

  It also improves the new WebDAV account type for Fastmail users. LP:
  #2072775

  Test Cases
  ==
  The autopkgtests for gnome-online-accounts should complete successfully

  Complete Test Case 2 (Google) from
  https://wiki.ubuntu.com/DesktopTeam/TestPlans/OnlineAccounts

  What Could Go Wrong
  ===
  gnome-online-accounts is included by default in Ubuntu Desktop, Edubuntu, 
Ubuntu Budgie & Ubuntu Cinnamon.

  If gnome-online-accounts is broken, people using Ubuntu may not
  receive notifications for emails and calendar appointments. This can
  be mitigated somewhat by using online services via a web browser and
  enabling notifications in their web browser.

  Before Ubuntu 24.04 LTS, gnome-online-accounts used webkit2gtk to
  handle authentication. By using the browser, gnome-online-accounts can
  handle many additional types of authentication and is more resilient
  to API changes and restrictions from the online service providers.

  GNOME Online Accounts is part of GNOME Core and is included in the
  GNOME micro release exception

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  Other Info
  ==
  This update includes changes to translatable strings. This package uses 
Ubuntu language packs. Because language packs are only updated shortly before 
each Ubuntu LTS point release, ideally this update will be included before the 
language packs are updated.

  The Ubuntu Desktop team considers the effect of changing translatable
  strings to be low because the changed strings were very new and
  weren't translated much. The strings are part of the Microsoft 365
  feature that is new in GNOME 46. The updated strings have been
  available upstream since late May and the translation coverage is
  better although still incomplete. We will likely do another SRU to
  include another upstream bugfix release (with updated translations)
  before Ubuntu 24.04.2.

  An update to translatable strings like this after a GNOME .0 release
  is very unusual. However, it was approved by the GNOME Release Team.
  Screenshots and more info at
  https://gitlab.gnome.org/Teams/Translation/Coordination/-/issues/158

  The backend library .symbols file indicates one removed symbol. It has
  been upstream's opinion for many years that the backend library is
  internal API and is subject to change. gnome-control-center is the
  only user of the backend API for Ubuntu 24.04 LTS and it never used
  that symbol. There is a separate frontend library, libgoa-1.0-0b,
  where it would be a serious issue if symbols were removed without the
  soname being bumped.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/2072782/+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 2072775] Autopkgtest regression report (gnome-online-accounts/3.50.4-0ubuntu1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted gnome-online-accounts (3.50.4-0ubuntu1) 
for noble have finished running.
The following regressions have been reported in tests triggered by the package:

gvfs/1.54.0-1ubuntu2 (s390x)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/noble/update_excuses.html#gnome-online-accounts

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gnome-online-accounts in
Ubuntu.
https://bugs.launchpad.net/bugs/2072775

Title:
  Fastmail's WebDav, CalDav and CardDav is buggy

Status in gnome-online-accounts package in Ubuntu:
  Fix Released
Status in gnome-online-accounts source package in Noble:
  Fix Committed

Bug description:
  SRU Note
  
  We are using the exception to mention this bug in the SRU changelog for bug 
tracking but will not do individual verification of this fix before promoting 
to -updates.

  https://wiki.ubuntu.com/StableReleaseUpdates#Bug_references_in_changelogs

  Impact
  ==
  The new WebDav etc feature in Ubuntu 24.04 LTS does not support fastmail.com 
(or a different provider, mailbox.org) natively.

  This was fixed in
  https://gitlab.gnome.org/GNOME/gnome-online-accounts/-/commit/2efd2129
  and
  https://gitlab.gnome.org/GNOME/gnome-online-accounts/-/commit/cc6c0948
  which are included in gnome-online-accounts 3.50.1

  Test Case
  =
  None

  What Could Go Wrong
  ===
  See master bug for gnome-online-accounts 3.50.3 update LP: #2072782

  Original Bug Report
  ===
  Even though GNOME Online Accounts now natively supports WebDav, CalDav and 
CardDav, it doesn't work with Fastmail. This bug was recognised upstream, and 
has been fixed upstream in 3.50.1.

  Could Ubuntu release gnome-online-accounts 3.50.1 or newer in the
  Ubuntu 24.04 "updates" or "backports" repositories?

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: gnome-online-accounts 3.50.0-4ubuntu2
  ProcVersionSignature: Ubuntu 6.8.0-36.36-generic 6.8.4
  Uname: Linux 6.8.0-36-generic x86_64
  ApportVersion: 2.28.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jul 11 15:15:21 2024
  InstallationDate: Installed on 2021-06-24 (1113 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: gnome-online-accounts
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/2072775/+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 2072782] Autopkgtest regression report (gnome-online-accounts/3.50.4-0ubuntu1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted gnome-online-accounts (3.50.4-0ubuntu1) 
for noble have finished running.
The following regressions have been reported in tests triggered by the package:

gvfs/1.54.0-1ubuntu2 (s390x)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/noble/update_excuses.html#gnome-online-accounts

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gnome-online-accounts in
Ubuntu.
https://bugs.launchpad.net/bugs/2072782

Title:
  Update gnome-online-accounts to 3.50.4

Status in gnome-online-accounts package in Ubuntu:
  Fix Committed
Status in gnome-online-accounts source package in Noble:
  Fix Committed

Bug description:
  Impact
  ==
  This is a new bugfix release in the stable 3.50.x series.

  It significantly improves the usability of the new "Microsoft 365"
  provider. However, that UI improvement changed translatable strings.
  See Other Info below.

  https://gitlab.gnome.org/GNOME/gnome-online-
  accounts/-/blob/3.50.4/NEWS

  It also improves the new WebDAV account type for Fastmail users. LP:
  #2072775

  Test Cases
  ==
  The autopkgtests for gnome-online-accounts should complete successfully

  Complete Test Case 2 (Google) from
  https://wiki.ubuntu.com/DesktopTeam/TestPlans/OnlineAccounts

  What Could Go Wrong
  ===
  gnome-online-accounts is included by default in Ubuntu Desktop, Edubuntu, 
Ubuntu Budgie & Ubuntu Cinnamon.

  If gnome-online-accounts is broken, people using Ubuntu may not
  receive notifications for emails and calendar appointments. This can
  be mitigated somewhat by using online services via a web browser and
  enabling notifications in their web browser.

  Before Ubuntu 24.04 LTS, gnome-online-accounts used webkit2gtk to
  handle authentication. By using the browser, gnome-online-accounts can
  handle many additional types of authentication and is more resilient
  to API changes and restrictions from the online service providers.

  GNOME Online Accounts is part of GNOME Core and is included in the
  GNOME micro release exception

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  Other Info
  ==
  This update includes changes to translatable strings. This package uses 
Ubuntu language packs. Because language packs are only updated shortly before 
each Ubuntu LTS point release, ideally this update will be included before the 
language packs are updated.

  The Ubuntu Desktop team considers the effect of changing translatable
  strings to be low because the changed strings were very new and
  weren't translated much. The strings are part of the Microsoft 365
  feature that is new in GNOME 46. The updated strings have been
  available upstream since late May and the translation coverage is
  better although still incomplete. We will likely do another SRU to
  include another upstream bugfix release (with updated translations)
  before Ubuntu 24.04.2.

  An update to translatable strings like this after a GNOME .0 release
  is very unusual. However, it was approved by the GNOME Release Team.
  Screenshots and more info at
  https://gitlab.gnome.org/Teams/Translation/Coordination/-/issues/158

  The backend library .symbols file indicates one removed symbol. It has
  been upstream's opinion for many years that the backend library is
  internal API and is subject to change. gnome-control-center is the
  only user of the backend API for Ubuntu 24.04 LTS and it never used
  that symbol. There is a separate frontend library, libgoa-1.0-0b,
  where it would be a serious issue if symbols were removed without the
  soname being bumped.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/2072782/+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] Autopkgtest regression report (dotnet8/8.0.107-8.0.7-0ubuntu1~24.04.2)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted dotnet8 
(8.0.107-8.0.7-0ubuntu1~24.04.2) for noble have finished running.
The following regressions have been reported in tests triggered by the package:

dotnet8/unknown (s390x)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/noble/update_excuses.html#dotnet8

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
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:
  New
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:
  New
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:
  New
Status in lapack package in Ubuntu:
  New
Status in libdeflate package in Ubuntu:
  New
Status in libseccomp package in Ubuntu:
  New
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:
  New
Status in qemu package in Ubuntu:
  New
Status in runc-app package in Ubuntu:
  New
Status in rustc package in Ubuntu:
  New
Status in s390-tools 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 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) and s390x (LP:
  #2064538).

  Impact: These are no change uploads on architectures other than
  ppc64el and s390x. All of those packages already built successful in
  oracular with the changed build flags.

  We will validate picking up the changed build flags by inspecting the
  log files on ppc64el and s390x.

To manage notifications about this bug go to:
https://bu

[Touch-packages] [Bug 2076340] Autopkgtest regression report (containerd-app/1.7.12-0ubuntu4.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted containerd-app (1.7.12-0ubuntu4.1) for 
noble have finished running.
The following regressions have been reported in tests triggered by the package:

containerd-app/unknown (s390x)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/noble/update_excuses.html#containerd-app

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
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:
  New
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:
  New
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:
  New
Status in lapack package in Ubuntu:
  New
Status in libdeflate package in Ubuntu:
  New
Status in libseccomp package in Ubuntu:
  New
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:
  New
Status in qemu package in Ubuntu:
  New
Status in runc-app package in Ubuntu:
  New
Status in rustc package in Ubuntu:
  New
Status in s390-tools 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 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) and s390x (LP:
  #2064538).

  Impact: These are no change uploads on architectures other than
  ppc64el and s390x. All of those packages already built successful in
  oracular with the changed build flags.

  We will validate picking up the changed build flags by inspecting the
  log files on ppc64el and s390x.

To manage notifications about this bug go to:
ht

[Touch-packages] [Bug 2060666] Autopkgtest regression report (krb5/1.17-6ubuntu4.7)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted krb5 (1.17-6ubuntu4.7) for focal have 
finished running.
The following regressions have been reported in tests triggered by the package:

evolution-data-server/unknown (armhf)
freeipa/unknown (s390x)
moonshot-gss-eap/1.0.1-6build1 (arm64, armhf)
nfs-utils/unknown (s390x)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/focal/update_excuses.html#krb5

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to krb5 in Ubuntu.
https://bugs.launchpad.net/bugs/2060666

Title:
  [SRU] Memory leak in krb5 version 1.17

Status in krb5 package in Ubuntu:
  Fix Released
Status in krb5 source package in Focal:
  Fix Committed

Bug description:
  [ Impact ]

  Commit 
https://github.com/krb5/krb5/commit/1cd2821c19b2b95e39d5fc2f451a035585a40fa5
  altered the memory management of krb5_gss_inquire_cred(), introducing defcred 
to act as
  an owner pointer when the function must acquire a default credential.
  The commit neglected to update the code to release the default cred
  along the successful path. The old code does not trigger because
  cred_handle is now reassigned, so the default credential is leaked.

  Resulting gradual increase in memory usage (memory leak) and eventual
  crash.

  [ Test Plan ]

  Setup 3 VMs:

  1. Windows Server act as Domain controller (AD)
  2. Windows machine AD Joined with Ostress installed. (Ostress is part of RML 
utilities 
https://learn.microsoft.com/en-us/troubleshoot/sql/tools/replay-markup-language-utility)
  3. SQL on Linux AD Joined ( configuration steps 
https://learn.microsoft.com/en-us/sql/linux/sql-server-linux-ad-auth-adutil-tutorial?view=sql-server-ver16)

  On the Machine with OStress create a file (name it disconnect.ini)
  with the following content under the same folder “C:\Program
  Files\Microsoft Corporation\RMLUtils” where OStress is installed.

  disconnect.ini
  ==

  [Connection Options]
  LoginTimeout=30
  QuotedIdentifier=Off
  AutocommitMode=On
  DisconnectPct=100.0
  MaxThreadErrors=0

  [Query Options]
  NoSQLBindCol=Off
  NoResultDisplay=Off
  PrepareExecute=Off
  ExecuteAsync=Off
  RollbackOnCancel=Off
  QueryTimeout=0
  QueryDelay=0
  MaxRetries=0
  BatchDisconnectPct=0.0
  CancelPct=0.00
  CancelDelay=0
  CancelDelayMin=0
  CursorType=
  CursorConcurrency=
  RowFetchDelay=0

  [Replay Options]
  Sequencing Options=global sequence
  ::Sequencing Options=global sequence, dtc replay
  DTC Timeout=
  DTC Machine=(local)
  Playback Coordinator=(local)
  StartSeqNum=
  StopSeqNum=
  TimeoutFactor=1.0

  Run the following command to start the load using Ostress, change
  Server name (-S) accordingly and the number of threads (-n) as needed.

  Start 4 different CMD consoles and use the following different commands for 
each CMD window:
  1. ostress.exe -E -S -Q"select * from sys.all_objects" -q 
-cdisconnect.ini -n40 -r999 -oc:\temp\log01 -T146
  2. ostress.exe -E -S -Q"select * from sys.all_views" -q 
-cdisconnect.ini -n40 -r999 -oc:\temp\log02 -T146
  3. ostress.exe -E -S -Q"select * from sys.all_columns" -q 
-cdisconnect.ini -n40 -r999 -oc:\temp\log03 -T146
  4. ostress.exe -E -S -Q"select * from sys.all_parameters" -q 
-cdisconnect.ini -n40 -r999 -oc:\temp\log04 -T146

  After a run of about 5 hours, the memory usage for this is expected to be 
around 5G with the fix.
  Without the fix, it was observed that it reached around ~22G in 5 hours. 
Hence the increase in 
  memory usage can be observed if the ostress.exe programs are let to run 
longer.

  [ Where problems could occur ]

   The fix may not fix the memory leak or could result in releasing the memory
   early in a different code path, and thus resulting in crashes.
   
   A mitigating fact is that the fix has been in Ubuntu since at least 22.04 and
   they do not exhibit any issues.
   
   Likewise I've previously provided the fix in a PPA 
https://launchpad.net/~pponnuvel/+archive/ubuntu/krb5-focal
   to user who's been hit by this issue. They've tested and confirmed it fixes 
the memory leak.
   
  [ Other Info ]

  The commit
  https://github.com/krb5/krb5/commit/098f874f3b50dd2c46c0a574677324b5f6f3a1a8
  fixes the leak.

  The fix has been included in newer krb5 releases (Jammy, and Noble
  have the releases with the fix).

  Bionic doesn't have the commit the introduced the memory leak in the first 
place.
  So this will be a Focal-only backport.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/2060666/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https:

[Touch-packages] [Bug 2055239] Autopkgtest regression report (systemd/255.4-1ubuntu8.3)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted systemd (255.4-1ubuntu8.3) for noble 
have finished running.
The following regressions have been reported in tests triggered by the package:

389-ds-base/unknown (s390x)
aide/unknown (s390x)
apport/2.28.1-0ubuntu3 (arm64, s390x)
appstream/unknown (s390x)
apt/unknown (armhf, s390x)
asterisk/unknown (armhf)
at-spi2-core/unknown (armhf)
bind9/unknown (s390x)
bolt/unknown (s390x)
casper/unknown (armhf)
casync/unknown (s390x)
ceph/unknown (s390x)
certspotter/unknown (s390x)
clevis/unknown (armhf, s390x)
clutter-1.0/1.26.4+git2779b932+dfsg-7build3 (armhf)
collectd/unknown (s390x)
comitup/unknown (s390x)
corosync/unknown (armhf)
corosync-qdevice/unknown (s390x)
coturn/4.6.1-1build4 (armhf)
coturn/unknown (s390x)
cron/3.0pl1-184ubuntu2 (ppc64el)
csync2/unknown (s390x)
cups/unknown (s390x)
dbus/1.14.10-4ubuntu4 (arm64)
debci/unknown (armhf)
dhcpcd/unknown (s390x)
dovecot/1:2.3.21+dfsg1-2ubuntu5 (arm64)
exim4/4.97-4ubuntu4.1 (ppc64el)
fetchmail/6.4.38-1ubuntu4 (arm64)
fetchmail/unknown (armhf)
fluidsynth/unknown (armhf, s390x)
freedom-maker/0.33 (armhf)
freedom-maker/unknown (arm64)
gvfs/1.54.0-1ubuntu2 (s390x)
haproxy/unknown (armhf)
incus/unknown (armhf)
init-system-helpers/unknown (s390x)
initramfs-tools/unknown (armhf)
libcamera/unknown (armhf, s390x)
libinput/unknown (s390x)
libreswan/unknown (arm64, s390x)
libsdl2/unknown (s390x)
libsfml/unknown (s390x)
libusbauth-configparser/unknown (armhf)
libvirt/unknown (armhf)
lighttpd/unknown (s390x)
mariadb/1:10.11.8-0ubuntu0.24.04.1 (arm64, armhf, s390x)
mediawiki/1:1.39.7-1 (amd64, armhf)
monitoring-plugins-systemd/unknown (armhf)
mosquitto/2.0.18-1build3 (arm64, armhf)
mpd/0.23.14-2build5 (armhf)
munin/unknown (s390x)
mutter/unknown (arm64)
ndctl/unknown (s390x)
netplan.io/1.0-2ubuntu1.2 (arm64, s390x)
nftables/unknown (s390x)
nghttp2/unknown (armhf)
nix/unknown (armhf)
nut/unknown (s390x)
openbsd-inetd/unknown (s390x)
openssh/1:9.6p1-3ubuntu13.4 (s390x)
ostree/2024.5-1build2 (s390x)
pam/unknown (s390x)
pdns-recursor/unknown (s390x)
php8.3/8.3.6-0ubuntu0.24.04.1 (armhf)
php8.3/unknown (s390x)
policykit-1/124-2ubuntu1 (amd64)
polkit-qt-1/0.200.0-1build4 (armhf)
polkit-qt-1/unknown (s390x)
postgresql-16/16.3-0ubuntu0.24.04.1 (armhf)
procps/2:4.0.4-4ubuntu3 (armhf)
prometheus-homeplug-exporter/unknown (s390x)
prometheus-ipmi-exporter/1.8.0-1ubuntu0.24.04.1 (armhf)
prometheus-ipmi-exporter/unknown (s390x)
prometheus-postfix-exporter/unknown (s390x)
prometheus-squid-exporter/1.10.4+ds-1ubuntu0.24.04.1 (armhf)
pulseaudio/unknown (armhf, s390x)
puppet-agent/8.4.0-1 (armhf)
remctl/3.18-1.1build2 (armhf)
rsyslog/8.2312.0-3ubuntu9 (arm64)
rust-whoami/unknown (s390x)
samba/2:4.19.5+dfsg-4ubuntu9 (s390x)
sbws/unknown (armhf)
seatd/unknown (armhf, s390x)
snapd/unknown (s390x)
swupdate/2023.12.1+dfsg-1ubuntu5 (armhf)
swupdate/unknown (s390x)
systemd-cron/unknown (armhf)
systemd-hwe/unknown (armhf)
upower/1.90.3-1 (arm64)
upower/unknown (armhf)
usbauth/unknown (armhf)
util-linux/unknown (arm64)
webhook/unknown (s390x)
wireshark/unknown (s390x)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/noble/update_excuses.html#systemd

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
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/2055239

Title:
  Warning: The unit file, source configuration file or drop-ins of {apt-
  news,esm-cache}.service changed on disk. Run 'systemctl daemon-reload'
  to reload units.

Status in snapd:
  New
Status in systemd package in Ubuntu:
  Fix Released
Status in ubuntu-advantage-tools package in Ubuntu:
  Invalid
Status in systemd source package in Noble:
  Fix Committed
Status in ubuntu-advantage-tools source package in Noble:
  Invalid

Bug description:
  [Impact]

  systemd may incorrectly mark units as needing a daemon reload,
  therefore unnecessarily printing the warning that a daemon-reload is
  needed for the changes to take effect. This is misleading to users,
  and particularly visible in cases like running apt update, since there
  is an apt hook (/etc/apt/apt.conf.d/20apt-esm-hook.conf) that starts
  two systemd services.

  [Test Plan]

  This bug can be triggered by running systemctl enable/disable on a 
non-existent unit. After that, calling systemctl start/status/etc. will show a 
false warning
  that the unit changed on disk. Hence, to test, simply:

  $ systemctl enable somethingthatdefinitelydoesnotexist.service
  $ systemctl status systemd-resolved.service 
  $ apt update

  On an effected system, warnings will be shown when calling both
  commands after the "enable non-existent unit" step.

  [Where problems could occur]

  This patch fixes a previous c

[Touch-packages] [Bug 2072574] Autopkgtest regression report (ubuntu-settings/24.04.4)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted ubuntu-settings (24.04.4) for noble 
have finished running.
The following regressions have been reported in tests triggered by the package:

network-manager/1.46.0-1ubuntu2 (arm64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/noble/update_excuses.html#ubuntu-settings

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu.
https://bugs.launchpad.net/bugs/2072574

Title:
  Drop obsolete evolution-data-server notify-with-tray override

Status in ubuntu-settings package in Ubuntu:
  Fix Released
Status in ubuntu-settings source package in Noble:
  Fix Committed

Bug description:
  Impact
  --
  Calendar notifications currently pop up a full app window instead of as a 
normal notification.

  The normal notifications respect the Do Not Disturb setting, but the
  full app window does not.

  Test Case 1
  ---
  From Ubuntu Desktop…
  1. Add your Google account to GNOME Settings > Online Accounts
  2. Add a calendar event to Google Calendar with a notification in advance
  3. When it is time for the notification, you should see a GNOME Shell 
notification. You can click on the notification to see the full Reminders 
window.

  Test Case 2
  ---
  From Ubuntu Unity 24.04 LTS…
  1. Open a terminal and run this command:
  sudo apt install gnome-online-accounts-gtk
  2. Close the terminal
  3. Add a calendar event to Google Calendar with a notification in advance
  4. When it is time for the notification, you should see a notification 
pop-up. You can click OK on the notification to see the full Reminders window.

  What Could Go Wrong
  ---
  The ubuntu-settings package is shipped by default with Ubuntu Desktop, Ubuntu 
Unity, and Edubuntu. Edubuntu is practically the same as Ubuntu Desktop as far 
as the desktop experience goes with one additional GNOME Shell extension to 
sort the Show Apps view alphabetically.

  This is a small default change that can be easily changed (see Revert
  instructions below).

  I guess this could go bad if someone counts on getting event
  notifications even though they have turned on Do Not Disturb. I'm
  sorry but it is intended that Do Not Disturb not show notifications
  like this.

  Other Info
  --
  I believe this override was originally added in 2011 for Unity's benefit LP: 
#757805
  It was also helpful for GNOME in early GNOME 3 days with the unusual 
messaging tray that was later dropped.

  These days, GNOME Shell notifications work well, better than a
  separate popup window.

  Revert to Previous Behavior
  ---
  If you prefer the original Ubuntu 24.04 LTS behavior, do one of the following:

  1. Run this in a terminal:
  gsettings set org.gnome.evolution-data-server.calendar notify-with-tray false

  2. Or install Evolution. In ☰ > Edit > Preferences > Calendar and
  Tasks, turn on "Display Reminder window with notifications"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2072574/+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] Autopkgtest regression report (livecd-rootfs/2.765.45)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted livecd-rootfs (2.765.45) for jammy have 
finished running.
The following regressions have been reported in tests triggered by the package:

livecd-rootfs/2.765.45 (s390x)
livecd-rootfs/unknown (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#livecd-rootfs

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
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 Committed
Status in ubuntu-meta source package in Jammy:
  Fix Committed

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 2036467] Autopkgtest regression report (e2fsprogs/1.46.5-2ubuntu1.2)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted e2fsprogs (1.46.5-2ubuntu1.2) for jammy 
have finished running.
The following regressions have been reported in tests triggered by the package:

aide/0.17.4-1 (armhf)
diffoscope/205 (amd64)
diffoscope/unknown (arm64, armhf)
fsarchiver/unknown (arm64)
initramfs-tools/0.140ubuntu13.4 (arm64)
livecd-rootfs/unknown (arm64)
moonshot-gss-eap/unknown (arm64)
postfix/unknown (armhf)
tomb/2.9+dfsg1-1 (armhf)
tomb/unknown (arm64)
virt-manager/unknown (arm64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#e2fsprogs

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu.
https://bugs.launchpad.net/bugs/2036467

Title:
  Resizing cloud-images occasionally fails due to superblock checksum
  mismatch in resize2fs

Status in cloud-images:
  New
Status in e2fsprogs package in Ubuntu:
  Fix Released
Status in e2fsprogs source package in Trusty:
  Won't Fix
Status in e2fsprogs source package in Xenial:
  Won't Fix
Status in e2fsprogs source package in Bionic:
  Won't Fix
Status in e2fsprogs source package in Focal:
  Fix Committed
Status in e2fsprogs source package in Jammy:
  Fix Committed
Status in e2fsprogs source package in Lunar:
  Won't Fix
Status in e2fsprogs source package in Mantic:
  Won't Fix
Status in e2fsprogs source package in Noble:
  Fix Committed
Status in e2fsprogs source package in Oracular:
  Fix Released

Bug description:
  [Impact]

  This is a long running bug plaguing cloud-images, where on a rare
  occasion resize2fs would fail and the image would not resize to fit
  the entire disk.

  Online resizes would fail due to a superblock checksum mismatch, where
  the superblock in memory differs from what is currently on disk due to
  changes made to the image.

  $ resize2fs /dev/nvme1n1p1
  resize2fs 1.47.0 (5-Feb-2023)
  resize2fs: Superblock checksum does not match superblock while trying to open 
/dev/nvme1n1p1
  Couldn't find valid filesystem superblock.

  Changing the read of the superblock to Direct I/O solves the issue.

  [Testcase]

  Start an c5.large instance on AWS, and attach a 60gb gp3 volume for
  use as a scratch disk.

  Run the following script, courtesy of Krister Johansen and his team:

     #!/usr/bin/bash
     set -euxo pipefail

     while true
     do
     parted /dev/nvme1n1 mklabel gpt mkpart primary 2048s 2099200s
     sleep .5
     mkfs.ext4 /dev/nvme1n1p1
     mount -t ext4 /dev/nvme1n1p1 /mnt
     stress-ng --temp-path /mnt -D 4 &
     STRESS_PID=$!
     sleep 1
     growpart /dev/nvme1n1 1
     resize2fs /dev/nvme1n1p1
     kill $STRESS_PID
     wait $STRESS_PID
     umount /mnt
     wipefs -a /dev/nvme1n1p1
     wipefs -a /dev/nvme1n1
     done

  Test packages are available in the following ppa:

  https://launchpad.net/~mruffell/+archive/ubuntu/lp2036467-test

  If you install the test packages, the race no longer occurs.

  [Where problems could occur]

  We are changing how resize2fs reads the superblock from underlying
  disks.

  If a regression were to occur, resize2fs could fail to resize offline
  or online volumes. As all cloud-images are online resized during their
  initial boot, this could have a large impact to public and private
  clouds should a regression occur.

  [Other info]

  Upstream mailing list discussion:
  https://lore.kernel.org/linux-ext4/20230605225221.ga5...@templeofstupid.com/
  https://lore.kernel.org/linux-ext4/20230609042239.ga1436...@mit.edu/

  This was fixed in the below commit upstream:

  commit 43a498e938887956f393b5e45ea6ac79cc5f4b84
  Author: Theodore Ts'o 
  Date: Thu, 15 Jun 2023 00:17:01 -0400
  Subject: resize2fs: use Direct I/O when reading the superblock for
   online resizes
  Link: 
https://git.kernel.org/pub/scm/fs/ext2/e2fsprogs.git/commit/?id=43a498e938887956f393b5e45ea6ac79cc5f4b84

  The commit has not been tagged to any release. All supported Ubuntu
  releases require this fix, and need to be published in standard non-
  ESM archives to be picked up in cloud images.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/2036467/+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 2036467] Autopkgtest regression report (e2fsprogs/1.47.0-2.4~exp1ubuntu4.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted e2fsprogs (1.47.0-2.4~exp1ubuntu4.1) 
for noble have finished running.
The following regressions have been reported in tests triggered by the package:

ceph/unknown (s390x)
cryptsetup/2:2.7.0-1ubuntu4 (arm64)
diffoscope/unknown (armhf)
ganeti-instance-debootstrap/unknown (s390x)
glusterfs/unknown (s390x)
inetutils/unknown (s390x)
initramfs-tools/0.142ubuntu25.1 (armhf)
krb5/1.20.1-6ubuntu2 (armhf)
manila/unknown (s390x)
moonshot-gss-eap/1.0.1-6ubuntu6 (armhf)
openssh/unknown (s390x)
swupdate/unknown (armhf)
weresync/unknown (arm64, s390x)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/noble/update_excuses.html#e2fsprogs

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu.
https://bugs.launchpad.net/bugs/2036467

Title:
  Resizing cloud-images occasionally fails due to superblock checksum
  mismatch in resize2fs

Status in cloud-images:
  New
Status in e2fsprogs package in Ubuntu:
  Fix Released
Status in e2fsprogs source package in Trusty:
  Won't Fix
Status in e2fsprogs source package in Xenial:
  Won't Fix
Status in e2fsprogs source package in Bionic:
  Won't Fix
Status in e2fsprogs source package in Focal:
  Fix Committed
Status in e2fsprogs source package in Jammy:
  Fix Committed
Status in e2fsprogs source package in Lunar:
  Won't Fix
Status in e2fsprogs source package in Mantic:
  Won't Fix
Status in e2fsprogs source package in Noble:
  Fix Committed
Status in e2fsprogs source package in Oracular:
  Fix Released

Bug description:
  [Impact]

  This is a long running bug plaguing cloud-images, where on a rare
  occasion resize2fs would fail and the image would not resize to fit
  the entire disk.

  Online resizes would fail due to a superblock checksum mismatch, where
  the superblock in memory differs from what is currently on disk due to
  changes made to the image.

  $ resize2fs /dev/nvme1n1p1
  resize2fs 1.47.0 (5-Feb-2023)
  resize2fs: Superblock checksum does not match superblock while trying to open 
/dev/nvme1n1p1
  Couldn't find valid filesystem superblock.

  Changing the read of the superblock to Direct I/O solves the issue.

  [Testcase]

  Start an c5.large instance on AWS, and attach a 60gb gp3 volume for
  use as a scratch disk.

  Run the following script, courtesy of Krister Johansen and his team:

     #!/usr/bin/bash
     set -euxo pipefail

     while true
     do
     parted /dev/nvme1n1 mklabel gpt mkpart primary 2048s 2099200s
     sleep .5
     mkfs.ext4 /dev/nvme1n1p1
     mount -t ext4 /dev/nvme1n1p1 /mnt
     stress-ng --temp-path /mnt -D 4 &
     STRESS_PID=$!
     sleep 1
     growpart /dev/nvme1n1 1
     resize2fs /dev/nvme1n1p1
     kill $STRESS_PID
     wait $STRESS_PID
     umount /mnt
     wipefs -a /dev/nvme1n1p1
     wipefs -a /dev/nvme1n1
     done

  Test packages are available in the following ppa:

  https://launchpad.net/~mruffell/+archive/ubuntu/lp2036467-test

  If you install the test packages, the race no longer occurs.

  [Where problems could occur]

  We are changing how resize2fs reads the superblock from underlying
  disks.

  If a regression were to occur, resize2fs could fail to resize offline
  or online volumes. As all cloud-images are online resized during their
  initial boot, this could have a large impact to public and private
  clouds should a regression occur.

  [Other info]

  Upstream mailing list discussion:
  https://lore.kernel.org/linux-ext4/20230605225221.ga5...@templeofstupid.com/
  https://lore.kernel.org/linux-ext4/20230609042239.ga1436...@mit.edu/

  This was fixed in the below commit upstream:

  commit 43a498e938887956f393b5e45ea6ac79cc5f4b84
  Author: Theodore Ts'o 
  Date: Thu, 15 Jun 2023 00:17:01 -0400
  Subject: resize2fs: use Direct I/O when reading the superblock for
   online resizes
  Link: 
https://git.kernel.org/pub/scm/fs/ext2/e2fsprogs.git/commit/?id=43a498e938887956f393b5e45ea6ac79cc5f4b84

  The commit has not been tagged to any release. All supported Ubuntu
  releases require this fix, and need to be published in standard non-
  ESM archives to be picked up in cloud images.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/2036467/+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 2073126] Autopkgtest regression report (apt/2.8.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted apt (2.8.1) for noble have finished 
running.
The following regressions have been reported in tests triggered by the package:

apport/2.28.1-0ubuntu3 (s390x)
auto-apt-proxy/14.1 (armhf, s390x)
cron/3.0pl1-184ubuntu2 (arm64)
dgit/11.8 (arm64)
gcc-10/10.5.0-4ubuntu2 (arm64)
gcc-11/11.4.0-9ubuntu1 (armhf)
gcc-13/13.2.0-23ubuntu4 (arm64, armhf)
gcc-13/unknown (s390x)
gcc-14/14-20240412-0ubuntu1 (armhf)
gcc-snapshot/1:20240117-1ubuntu1 (arm64, armhf)
ubiquity/24.04.5 (armhf)
update-notifier/unknown (s390x)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/noble/update_excuses.html#apt

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/2073126

Title:
  More nuanced public key algorithm revocation

Status in apt package in Ubuntu:
  Fix Committed
Status in apt source package in Noble:
  Fix Committed
Status in apt source package in Oracular:
  Fix Committed

Bug description:
  (This is uploaded to noble as 2.8.1 per
  https://wiki.ubuntu.com/AptUpdates)

  [Impact]
  We have received feedback from users that use NIST-P256 keys for their 
repositories that are upset about receiving a warning. APT 2.8.0 in 
noble-proposed would bump the warning to an error, breaking them.

  We also revoked additional ECC curves, which may still be considered
  trusted, so we should not bump them to errors.

  Also existing users may have third-party repositories that use
  1024-bit RSA keys and we have not adequately informed them yet
  perhaps.

  [Solution]
  Hence we will restore all elliptic curve keys of 256 or more bit to trusted:

  
">=rsa2048,ed25519,ed448,nistp256,nistp384,nistp512,brainpoolP256r1,brainpoolP320r1,brainpoolP384r1,brainpoolP512r1,secp256k1";

  At the same time we will also introduce a more nuanced approach to
  revocations by introducing a 'next' level that issues a warning if the
  key is not allowed in it and a 'future' level that will issue an audit
  message with the --audit option.

  For the next level, we will set it to:

  ">=rsa2048,ed25519,ed448,nistp256,nistp384,nistp512"

  This means we restrict warnings to Brainpool curves and the secp256k1
  key, which we have not received any feedback about them being used
  yet.

  For the future level, we will take a strong approach to best practices
  as it is only seen when explictly running with --audit and the
  intention is to highlight best practices. It will be set to

  ">=rsa3072,ed25519,ed448";

  Which corresponds to the NIST recommendations for 2031 (and as little
  curves as possible).

  We are also introducing a mitigation for existing 24.04 systems to not
  upgrade the policy yet; by creating an apt.conf.d configuration file
  that temporarily allows the 1024-bit RSA keys if upgraded from apt
  2.7.x; with the plan to remove them in 24.04.2.

  [Test plan]
  Tests are included in the library unit tests for parsing the specification 
strings; we have also included a test for the gpgv method to ensure that it 
produces the correct outcome for both 'next' and 'future' revoked keys.

  A spot check with a 1024-bit RSA repository and a 4096 RSA repository
  would still be nice.

  Check a clean install of apt/an upgrade from mantic vs an existing
  noble system:

  - An existing noble system should create 
/etc/apt/apt.conf.d/00-temporary-rsa1024 and continue to trust weak RSA 
signatures with a warning
  - Bootstrap a new noble with proposed enabled using e.g. mmdebstrap and check 
that this is not the case
  - Also check upgrading from mantic directly to proposed and ensure that 1024R 
repositories are rejected.

  [Where problems could occur]
  There could of course be bugs in the implementation of the new feature; this 
could result in verification of files failing. This also happens if you specify 
an invalid `next` or `future` string.

  There cannot be any false positives: The new levels are only
  *additional* checks, anything not in the `Assert-Pubkey-Algo` list is
  still revoked.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2073126/+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 2060721] Autopkgtest regression report (apt/2.8.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted apt (2.8.1) for noble have finished 
running.
The following regressions have been reported in tests triggered by the package:

apport/2.28.1-0ubuntu3 (s390x)
auto-apt-proxy/14.1 (armhf, s390x)
cron/3.0pl1-184ubuntu2 (arm64)
dgit/11.8 (arm64)
gcc-10/10.5.0-4ubuntu2 (arm64)
gcc-11/11.4.0-9ubuntu1 (armhf)
gcc-13/13.2.0-23ubuntu4 (arm64, armhf)
gcc-13/unknown (s390x)
gcc-14/14-20240412-0ubuntu1 (armhf)
gcc-snapshot/1:20240117-1ubuntu1 (arm64, armhf)
ubiquity/24.04.5 (armhf)
update-notifier/unknown (s390x)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/noble/update_excuses.html#apt

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/2060721

Title:
  APT 2.8.0: Promote weak key warnings to errors

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Noble:
  Fix Committed

Bug description:
  ⚠️ Only land this in the release/updates pocket after PPAs have been
  resigned

  (This bumps the apt version to 2.8.0. APT uses the odd/even number
  system, with 2.7.x being the development series for 2.8, and this is
  the only change left for the 2.8 release, safe for some minor
  translation/test suite improvements)

  (Please also look at bug 2073126 for the follow-up changes to mitigate
  regression potential).

  [Impact]
  APT is currently just warning about keys that it should be rejecting to give 
Launchpad time to resign PPAs. This needs to be bumped to an error such that 
the crypto policy is fully implemented and we only trust keys that are still 
being trusted. #2055193

  A warning provides some help right now to third-parties to fix their
  repositories, but it's not *safe*: A repository could have multiple
  signing keys and be signed by a good key now, then later, a previous
  key still in trusted.gpg.d could be revoked and we'd degrade to
  warnings, which, given that we update in the background automatically,
  the user may not see.

  Other fixes:
  - The test suite has been made less flaky in two places
  - Documentation translation has been unfuzzied for URL changes in 2.7.14

  [Test plan]
  The vast regression test suite prevents regression in other components. 
Additional tests are:

  1. (promotion to error) Take a repository that has a weak RSA key warning, 
upgrade apt and check that it is an error
  2. (still valid) Check that the main Ubuntu repositories and/or resigned PPAs 
work correctly.

  We don't have any tests for the test changes or the documentation
  translation URL unfuzzying.

  [Where problems could occur]
  apt will start to fail updates of repositories with weak signing keys, but it 
will have warned users about that before. Given that it is still early in the 
cycle, and we only enable updates from 22.04.1 for 24.04.1, this seems the 
right tradeoff for future security.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2060721/+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 2067240] Autopkgtest regression report (modemmanager/1.20.0-1~ubuntu22.04.4)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted modemmanager (1.20.0-1~ubuntu22.04.4) 
for jammy have finished running.
The following regressions have been reported in tests triggered by the package:

cinnamon-control-center/5.2.1-2 (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#modemmanager

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to modemmanager in Ubuntu.
https://bugs.launchpad.net/bugs/2067240

Title:
  [SRU] Add Quectel EM061K-GL/EM160/RM520N PID information to support
  WWAN LVFS

Status in OEM Priority Project:
  Confirmed
Status in modemmanager package in Ubuntu:
  Fix Released
Status in modemmanager source package in Jammy:
  Fix Committed

Bug description:
  [ Impact ]

  The modemmanager v1.20.0 doesn't have Quectel EM061K-GL/EM160/RM520N PID 
information,
  and the modemmanger won't recognize these WWAN modems on some next-gen Lenovo 
laptops.
  (lp: #2045276)

  [ Test Plan ]

  Under Jammy environment, with latest linux-oem kernel installed,
  check output of `mmcli -L` to see if the modems are properly recognized.

  Modems to check:
  - EM061K-GL
  - EM160
  - EM160

  [ Where problems could occur ]

  EM160R-GL(1.22.0):
  
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/1059/diffs

  EM061K-GL(1.22.0):
  
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/1057/diffs

  RM520N-GL(1.22.0):
  
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/1052/diffs
  
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/1077/diffs

  All these changes are merged, and they only introduce new PIDs for
  initial supports, which do not affect existing ones.

  Noble contains these changes, so, only SRU jammy and mantic.

  [ Other Info ]

  These patches are proved work with the test version on my PPA:
  https://launchpad.net/~pseudoc/+archive/ubuntu/nate

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/2067240/+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 2062522] Autopkgtest regression report (tzdata/2024a-3ubuntu1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted tzdata (2024a-3ubuntu1) for noble have 
finished running.
The following regressions have been reported in tests triggered by the package:

chrony/unknown (ppc64el)
golang-github-lib-pq/1.10.9-2 (amd64, arm64)
pandas/2.1.4+dfsg-7 (arm64)
prometheus-alertmanager/0.26.0+ds-1 (armhf)
python-tempora/unknown (ppc64el)
reposurgeon/4.38-1 (ppc64el)
ruby-tzinfo/unknown (ppc64el)
tzdata/2024a-3ubuntu1 (armhf)
tzdata/unknown (ppc64el)
ubuntu-dev-tools/0.201ubuntu2 (amd64, arm64, armhf, i386, ppc64el, s390x)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/noble/update_excuses.html#tzdata

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tzdata in Ubuntu.
https://bugs.launchpad.net/bugs/2062522

Title:
   std::chrono::locate_zone("Asia/Chungking") fails

Status in glibc package in Ubuntu:
  New
Status in tzdata package in Ubuntu:
  Fix Committed
Status in tzdata source package in Noble:
  Fix Committed

Bug description:
  [ Impact ]

  forwarded from
  https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114770

  ```
  #include 
  int main()
  {
    (void) std::chrono::locate_zone("Asia/Chungking");
  }
  ```

  With the latest tzdata (version 2024a-2) on Debian Sid this fails:

  terminate called after throwing an instance of 'std::runtime_error'
    what():  tzdb: cannot locate zone: Asia/Chungking
  Aborted (core dumped)

  The problem is a Debian patch that enables link chaining, so that one link 
can have another link as its target:
  
https://sources.debian.org/patches/tzdata/2024a-2/ziguard.awk-Move-link-to-link-feature-from-vanguard-to-ma.patch/

  This feature was added to tzdata in 2022, but isn't compatible with
  the expectations of the C++20 standard. When chrono::locate_zone finds
  a link, it expects its target to be a zone, not another link.

  [ Test Plan ]

  1. Install tzdata-legacy
  2. Create `testcase.cpp`:

  ```
  #include 
  int main()
  {
    (void) std::chrono::locate_zone("Asia/Chungking");
  }
  ```

  3. Compile: `g++ -std=c++20 -o testcase testcase.cpp`
  4. Run: `./testcase`

  The test case should not crash.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/2062522/+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 2056758] Autopkgtest regression report (apport/2.28.1-0ubuntu3)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted apport (2.28.1-0ubuntu3) for noble have 
finished running.
The following regressions have been reported in tests triggered by the package:

ubuntu-release-upgrader/1:24.04.16 (arm64, armhf, ppc64el, s390x)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/noble/update_excuses.html#apport

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/2056758

Title:
  ubuntu-bug doesn't let me file bugs for Snap thunderbird

Status in Apport:
  Fix Committed
Status in apport package in Ubuntu:
  Fix Committed
Status in thunderbird package in Ubuntu:
  Invalid
Status in apport source package in Noble:
  Fix Committed

Bug description:
  I'm trying to report a bug in the new Snap for Thunderbird.

  When I run "ubuntu-bug thunderbird", it:
  * Collects information correctly after I input the sudo password
  * Opens a page like 
https://bugs.launchpad.net/distros/+filebug/a9564134-dfa6-11ee-85a7-c7116d9f638e?,
 which does not seem to be valid.

  This is not the case for Firefox, which works fine with ubuntu-bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: apport 2.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4
  Uname: Linux 6.8.0-11-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashReports:
   640:1000:124:483410:2024-03-11 14:47:26.874792575 +0400:2024-03-11 
14:47:27.874792575 
+0400:/var/crash/_opt_Citrix_ICAClient_util_storebrowse.1000.crash
   640:0:124:29135:2024-03-10 17:02:30.124656623 +0400:2024-03-10 
17:02:30.124656623 +0400:/var/crash/_usr_share_apport_apport.0.crash
  CurrentDesktop: KDE
  Date: Mon Mar 11 16:54:18 2024
  InstallationDate: Installed on 2022-08-29 (560 days ago)
  InstallationMedia: Kubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to noble on 2024-02-23 (17 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/2056758/+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] Autopkgtest regression report (glib2.0/2.80.0-6ubuntu3)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted glib2.0 (2.80.0-6ubuntu3) for noble 
have finished running.
The following regressions have been reported in tests triggered by the package:

apport/2.28.1-0ubuntu2 (ppc64el)
cluster-glue/1.0.12-22.1ubuntu3 (ppc64el)
cpdb-backend-cups/2.0~b5-0ubuntu6 (armhf)
cpdb-libs/2.0~b5-1.2build1 (armhf)
dbus-test-runner/19.04.0-1build2 (arm64)
lasi/unknown (arm64)
libsoup2.4/2.74.3-6ubuntu1 (arm64, ppc64el)
mender-client/3.4.0+ds1-5build3 (armhf)
snapd-glib/1.64-0ubuntu5 (ppc64el, s390x)
software-properties/unknown (amd64, arm64, armhf, i386, ppc64el, s390x)
surf/2.1+git20221016-6build2 (armhf)
ymuse/0.22-1build2 (s390x)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/noble/update_excuses.html#glib2.0

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
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:
  Fix Committed

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 2060721] Autopkgtest regression report (apt/2.8.0)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted apt (2.8.0) for noble have finished 
running.
The following regressions have been reported in tests triggered by the package:

apport/2.28.1-0ubuntu2 (ppc64el)
auto-apt-proxy/14.1 (arm64)
autopkgtest/5.34ubuntu2 (amd64, arm64, ppc64el)
cron/3.0pl1-184ubuntu2 (s390x)
gcc-12/12.3.0-17ubuntu1 (armhf)
sbuild/0.85.7 (amd64, armhf, i386, s390x)
update-manager/1:24.04.6 (amd64, arm64, armhf, ppc64el, s390x)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/noble/update_excuses.html#apt

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/2060721

Title:
  APT 2.8.0: Promote weak key warnings to errors

Status in apt package in Ubuntu:
  Incomplete
Status in apt source package in Noble:
  Fix Committed

Bug description:
  ⚠️ Only land this in the release/updates pocket after PPAs have been
  resigned

  (This bumps the apt version to 2.8.0. APT uses the odd/even number
  system, with 2.7.x being the development series for 2.8, and this is
  the only change left for the 2.8 release, safe for some minor
  translation/test suite improvements)

  (This will be uploaded after the beta and may be released before noble
  release, as a zero day SRU or within the weeks following the release)

  [Impact]
  APT is currently just warning about keys that it should be rejecting to give 
Launchpad time to resign PPAs. This needs to be bumped to an error such that 
the crypto policy is fully implemented and we only trust keys that are still 
being trusted. #2055193

  A warning provides some help right now to third-parties to fix their
  repositories, but it's not *safe*: A repository could have multiple
  signing keys and be signed by a good key now, then later, a previous
  key still in trusted.gpg.d could be revoked and we'd degrade to
  warnings, which, given that we update in the background automatically,
  the user may not see.

  Other fixes:
  - The test suite has been made less flaky in two places
  - Documentation translation has been unfuzzied for URL changes in 2.7.14

  [Test plan]
  The vast regression test suite prevents regression in other components. 
Additional tests are:

  1. (promotion to error) Take a repository that has a weak key warning, 
upgrade apt and check that it is an error
  2. (still valid) Check that the main Ubuntu repositories and/or resigned PPAs 
work correctly.

  We don't have any tests for the test changes or the documentation
  translation URL unfuzzying.

  [Where problems could occur]
  apt will start to fail updates of repositories with weak signing keys, but it 
will have warned users about that before. Given that it is still early in the 
cycle, and we only enable updates for 24.04.1, this seems the right tradeoff 
for future security.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2060721/+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 2061214] Autopkgtest regression report (software-properties/0.99.49)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted software-properties (0.99.49) for noble 
have finished running.
The following regressions have been reported in tests triggered by the package:

software-properties-qt/unknown (amd64, arm64, armhf, i386, ppc64el,
s390x)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/noble/update_excuses.html#software-properties

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/2061214

Title:
  [SRU] Software Sources is not compatible with deb822

Status in software-properties package in Ubuntu:
  Fix Committed
Status in software-properties-qt package in Ubuntu:
  Fix Released
Status in software-properties source package in Noble:
  Fix Committed
Status in software-properties-qt source package in Noble:
  Fix Released

Bug description:
  [ Impact ]

  Ubuntu 24.04 now uses deb822 to represent software sources for deb
  packages, instead of /etc/apt/sources.list. The complete rationale for
  this change can be found here: https://discourse.ubuntu.com/t/spec-
  apt-deb822-sources-by-default/29333

  software-properties has two graphical frontends for editing these
  software sources, one is GTK-based and the other is Qt-based. When the
  underlying change to deb822 sources was made, the GTK-based frontend
  and the DBus backend interface gained support.

  The original bug report shown below informed us of the lack of deb822
  support in the Qt frontend, which results in a broken, non-functional
  interface when attempting to view or edit most values on the first two
  tabs. The fix for this is to implement a Qt dialog for deb822 sources
  that somewhat matches the existing GTK interface.

  [ Test Plan ]

  Install software-properties-qt 0.99.48 or earlier.

  Reproducing the bug:
   1. From the menu, open Software Sources. Alternatively, run `sudo -E 
software-properties-qt` in a terminal.
   2. Observe that all four checkboxes on the Ubuntu Software tab (main, 
universe, restricted, and multiverse) are unchecked.
   3. Move to the Other Software tab and observe that there are no items in the 
list.

  Upgrade to software-properties-qt 0.99.49.

  Intended functionality:
   1. From the menu, open Software Sources. Alternatively, run `sudo -E 
software-properties-qt` in a terminal.
   2. Observe that one or more checkboxes on the Ubuntu Software tab 
(representing main, universe, restricted, or multiverse) are checked. Toggle 
one or more of the checkboxes.
   3. Using a text editor of some kind (perhaps Vim), confirm that 
/etc/apt/sources.list.d/ubuntu.sources reflects your changes.
   4. Switch to the Other Software tab, there should be one item in the list.
   5. Select that item, then click Edit at the bottom of the dialog. Make a 
modification to every field on the screen, or a combination of fields you would 
like to test. All fields should work.
   6. Click the OK button at the bottom of the dialog to confirm the changes, 
then click Edit for that item again. The changes you made should be reflected 
(meaning, the changes were saved.)
   7. Using a text editor of some kind (perhaps Vim), confirm that 
/etc/apt/sources.list.d/ubuntu.sources reflects your changes.

  [ Where problems could occur ]

  This is well-tested code. That being said, the following small edge cases 
exist:
   - If you create a very large amount of rows, it infinitely expands the 
dialog without a scroll wheel. This is the same functionality as the GTK 
frontend.
   - Error validation is not performed on the deb822 lines, they are simply 
written to the ubuntu.sources file. This is good as a starting point, but also 
relies on the appropriate update notifier handling these errors. This is the 
same functionality as the GTK frontend.

  In a future update, this functionality could be broken by one or more of the 
following underlying changes:
   - Changes to the software-properties backend which are only implemented for 
the GTK frontend.
   - Changes to the location or formatting of the ubuntu.sources file.
   - Regressions in the Python bindings for Qt 5, which are rare but possible.
   - Regressions in Python itself.

  [ Other Info ]
   
  Ubuntu Studio's live ISO and installed system are affected by this. Only 
Lubuntu's installed system is affected by this.

  [ Original Report ]

  Upgrading Lubuntu Jammy to Lubuntu Noble using TUI results in
  "Software sources" not correctly updated after upgrade. Prompt= shows
  normal and not LTS

  Used command sudo do-release-upgrade -d

  Otherwise the upgrade is good

  see attached screenshot

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Packa

[Touch-packages] [Bug 1980836] Autopkgtest regression report (poppler/22.02.0-2ubuntu0.4)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted poppler (22.02.0-2ubuntu0.4) for jammy 
have finished running.
The following regressions have been reported in tests triggered by the package:

xapers/0.9.0-1 (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#poppler

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to poppler in Ubuntu.
https://bugs.launchpad.net/bugs/1980836

Title:
  Regression in Ubuntu 22.04: Content of form field stored invisibly

Status in Poppler:
  Fix Released
Status in evince package in Ubuntu:
  Invalid
Status in poppler package in Ubuntu:
  Triaged
Status in evince source package in Jammy:
  Invalid
Status in poppler source package in Jammy:
  Fix Committed

Bug description:
  [ Impact ]

  The bug causes text entered in certain PDF form fields to be stored
  but both displayed and printed white (on white background).

  [ Test Plan ]

  1. Download the attached 230-muster-01.pdf.
  2. Try to input to any of the main content fields starting with 06-09 
("Anrede des Zahlungspflichtigen etc").
  3. Observe that it does not work.
  4. Install the updated poppler package versions
  5. Try the same fields and see they're functoning properly now with visible 
text.
  6. Test also that the fields like "Aktenzeichen", "TL-Nr." or 
"Buchungsstelle" that weren't broken, continue to work.

  [ Where problems could occur ]

  It is a merged upstream fix to Annot.cc file that fixed two upstream
  bugs https://gitlab.freedesktop.org/poppler/poppler/-/issues/1189 and
  https://gitlab.freedesktop.org/poppler/poppler/-/issues/1267.

  There are no indications of upstream regressions caused by this fix,
  and it was released in upstream stable release 22.08.0 (Ubuntu 22.04
  LTS has version based on 22.02.0).

  However, since it's an individual cherry-pick there could always be a
  PDF somewhere having issues with this, so it's useful to let it be
  tested with various files in addition to the problematic ones.

  --- original report ---

  Evince on Ubuntu 22.04 is not able to handle some PDF forms correctly
  anymore that it was able to handle on Ubuntu 21.10 and on Ubuntu
  20.04.

  The symptom is that one can edit the form content and also save it,
  but that the entered text is only visible when the form field is
  focused and in edit mode. Otherwise the text it is invisible, also on
  printouts.

  Such bugs have been reported against Evince for a long time (e.g.,
  https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/265033) but I
  am reporting this as a new bug because for the current form with which
  I am experiencing this it is a regression.

  I have attached the problematic form with two form fields filled out, one in 
the upper left corner and the big one in the lower half.
  I have produced this by taking the original, empty form (produced by somebody 
else) and first opened it in Evince 41.4, which I have installed from the snap 
package (revision 1017) on Ubuntu 22.04. I entered text in the upper left field 
and saved the form.
  Then I opened the PDF in Evince 42.3 from the apt package of Ubuntu 22.04 and 
entered text in the big field and saved the form.

  Evince 3.36 on Ubuntu 20.04 has the same (correct) behavior as Evince
  41.4.

  When I open the PDF again, only the text in the first field is
  visible. The text in the second field is visible only if I click into
  the field. The visibility of the field contents is the same for Evince
  41.4 (snap), Evince 42.3 (apt), and Okular 20.12.3 (snap). So it seems
  that the problem is with Evince 42.3 incorrectly saving the field
  content, not with displaying it.

  Firefox shows and prints the content of both fields, though.

  Note that I cannot switch back to Evince 41 because for some other
  forms that I have the exact same problem happens only with the old
  version and the new version fixes it. So it seems that something
  changed that fixed it for some forms and broke it for others.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: evince 42.3-0ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35
  Uname: Linux 5.15.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul  6 14:32:27 2022
  InstallationDate: Installed on 2021-11-26 (222 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  RebootRequiredPkgs: Error: path contained symlinks.
  Snap.Changes:
   ID   Status  Spawn  Bereit 
Zusammenfassung
   137  Done2022-07-06T12:48:33+02:00  2022-07-06T

[Touch-packages] [Bug 2053146] Autopkgtest regression report (openssh/1:8.9p1-3ubuntu0.7)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted openssh (1:8.9p1-3ubuntu0.7) for jammy 
have finished running.
The following regressions have been reported in tests triggered by the package:

backdoor-factory/unknown (armhf)
gvfs/1.48.2-0ubuntu1 (arm64)
libssh/0.9.6-2ubuntu0.22.04.3 (i386)
piuparts/1.1.5 (amd64)
sbuild/0.81.2ubuntu6 (arm64, ppc64el, s390x)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#openssh

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/2053146

Title:
  openssh 8.9p1 for Jammy auth2-gss patch for gssapi-keyex method is
  slightly wrong

Status in openssh package in Ubuntu:
  Fix Released
Status in openssh source package in Jammy:
  Fix Committed
Status in openssh source package in Mantic:
  Fix Committed
Status in openssh source package in Noble:
  Fix Released

Bug description:
  [ Impact ]

  The gssapi-keyex authentication mechanism has been inadvertently
  broken in openssh. It comes from a distro patch[1], and while the
  patch still applied, it was no longer correct.

  Without the fix, sshd will fail to start if gssapi-keyex is listed in
  the AuthenticationMethods of the server, and if not, sshd will still
  start, but gssapi-keyex will not be available.

  
  [ Test Plan ]

  This update adds a new autopkgtest to the package, which tests both
  gssapi-with-mic ("normal" gssapi, which is not affected by this bug),
  and gssapi-keyex, which, before this update, does not work.

  The test plan is to run the new ssh-gssapi autopkgtest and verify it
  succeeds.

  
  [ Where problems could occur ]

  ssh is a critical piece of infrastructure, and problems with it could
  have catastrophic consequences. The service itself has a test command
  before it starts up to verify the syntax of the config file, but that
  test is not applied on shutdown, so a restart with an invalid config
  file could still leave sshd dead.

  The patch adds a change to an authentication structure, but that
  change is already present in the upstream code, and we are just
  updating it in the new gssapi-keyex code (introduced by the distro[1]
  patch, already present). Therefore, mistakes here should manifest
  themselves just in the gssapi-keyex code, which wasn't working anyway.
  Effectively, though, we are enabling a new authentication mechanism in
  sshd, one that was not supposed to have been removed, but was broken
  by mistake.

  
  [ Other Info ]

  The fact no-one noticed this problem for more than two years could be
  telling that there are not many users of this authentication mechanism
  out there. The same applies to debian: it has also been broken for a
  while there. Maybe we should drop it for future ubuntu releases, since
  upstream refuses to take it in.

  [ Original Description ]

  The Authmethod struct now have 4 entries but the initialization of the
  method_gsskeyex in the debian/patches/gssapi.patch only have 3
  entries.

  The struct was changed in upstream commit 
dbb339f015c33d63484261d140c84ad875a9e548 as
  ===
  @@ -104,7 +104,8 @@ struct Authctxt {

   struct Authmethod {
  char*name;
  -   int (*userauth)(struct ssh *);
  +   char*synonym;
  +   int (*userauth)(struct ssh *, const char *);
  int *enabled;
   };

  ===

  The incorrect code does
  ===
  +Authmethod method_gsskeyex = {
  +   "gssapi-keyex",
  +   userauth_gsskeyex,
  +   &options.gss_authentication
  +};
  ===
  but should have a NULL between the "gssapi-keyex" string and userauth_gsskeyex

  This is now (change from Focal) causing gssapi-keyex to be disabled.

  ===
  lsb_release -rd
  Description:  Ubuntu 22.04.3 LTS
  Release:  22.04

  ===
  apt-cache policy openssh-server
  openssh-server:
    Installed: 1:8.9p1-3ubuntu0.6
    Candidate: 1:8.9p1-3ubuntu0.6
    Version table:
   *** 1:8.9p1-3ubuntu0.6 500
  500 http://faiserver.hpc2n.umu.se/mirrors/ubuntu/ubuntu 
jammy-updates/main amd64 Packages
  500 http://faiserver.hpc2n.umu.se/mirrors/ubuntu/ubuntu 
jammy-security/main amd64 Packages
  100 /var/lib/dpkg/status
   1:8.9p1-3 500
  500 http://faiserver.hpc2n.umu.se/mirrors/ubuntu/ubuntu jammy/main 
amd64 Packages

  ===

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2053146/+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 2053146] Autopkgtest regression report (openssh/1:9.3p1-1ubuntu3.3)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted openssh (1:9.3p1-1ubuntu3.3) for mantic 
have finished running.
The following regressions have been reported in tests triggered by the package:

gvfs/1.52.0-1 (arm64, i386)
libssh/0.10.5-3ubuntu1.2 (i386)
piuparts/1.1.7 (amd64)
pkg-perl-tools/0.76 (arm64)
vagrant/2.3.4+dfsg-1ubuntu1 (arm64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/mantic/update_excuses.html#openssh

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/2053146

Title:
  openssh 8.9p1 for Jammy auth2-gss patch for gssapi-keyex method is
  slightly wrong

Status in openssh package in Ubuntu:
  Fix Released
Status in openssh source package in Jammy:
  Fix Committed
Status in openssh source package in Mantic:
  Fix Committed
Status in openssh source package in Noble:
  Fix Released

Bug description:
  [ Impact ]

  The gssapi-keyex authentication mechanism has been inadvertently
  broken in openssh. It comes from a distro patch[1], and while the
  patch still applied, it was no longer correct.

  Without the fix, sshd will fail to start if gssapi-keyex is listed in
  the AuthenticationMethods of the server, and if not, sshd will still
  start, but gssapi-keyex will not be available.

  
  [ Test Plan ]

  This update adds a new autopkgtest to the package, which tests both
  gssapi-with-mic ("normal" gssapi, which is not affected by this bug),
  and gssapi-keyex, which, before this update, does not work.

  The test plan is to run the new ssh-gssapi autopkgtest and verify it
  succeeds.

  
  [ Where problems could occur ]

  ssh is a critical piece of infrastructure, and problems with it could
  have catastrophic consequences. The service itself has a test command
  before it starts up to verify the syntax of the config file, but that
  test is not applied on shutdown, so a restart with an invalid config
  file could still leave sshd dead.

  The patch adds a change to an authentication structure, but that
  change is already present in the upstream code, and we are just
  updating it in the new gssapi-keyex code (introduced by the distro[1]
  patch, already present). Therefore, mistakes here should manifest
  themselves just in the gssapi-keyex code, which wasn't working anyway.
  Effectively, though, we are enabling a new authentication mechanism in
  sshd, one that was not supposed to have been removed, but was broken
  by mistake.

  
  [ Other Info ]

  The fact no-one noticed this problem for more than two years could be
  telling that there are not many users of this authentication mechanism
  out there. The same applies to debian: it has also been broken for a
  while there. Maybe we should drop it for future ubuntu releases, since
  upstream refuses to take it in.

  [ Original Description ]

  The Authmethod struct now have 4 entries but the initialization of the
  method_gsskeyex in the debian/patches/gssapi.patch only have 3
  entries.

  The struct was changed in upstream commit 
dbb339f015c33d63484261d140c84ad875a9e548 as
  ===
  @@ -104,7 +104,8 @@ struct Authctxt {

   struct Authmethod {
  char*name;
  -   int (*userauth)(struct ssh *);
  +   char*synonym;
  +   int (*userauth)(struct ssh *, const char *);
  int *enabled;
   };

  ===

  The incorrect code does
  ===
  +Authmethod method_gsskeyex = {
  +   "gssapi-keyex",
  +   userauth_gsskeyex,
  +   &options.gss_authentication
  +};
  ===
  but should have a NULL between the "gssapi-keyex" string and userauth_gsskeyex

  This is now (change from Focal) causing gssapi-keyex to be disabled.

  ===
  lsb_release -rd
  Description:  Ubuntu 22.04.3 LTS
  Release:  22.04

  ===
  apt-cache policy openssh-server
  openssh-server:
    Installed: 1:8.9p1-3ubuntu0.6
    Candidate: 1:8.9p1-3ubuntu0.6
    Version table:
   *** 1:8.9p1-3ubuntu0.6 500
  500 http://faiserver.hpc2n.umu.se/mirrors/ubuntu/ubuntu 
jammy-updates/main amd64 Packages
  500 http://faiserver.hpc2n.umu.se/mirrors/ubuntu/ubuntu 
jammy-security/main amd64 Packages
  100 /var/lib/dpkg/status
   1:8.9p1-3 500
  500 http://faiserver.hpc2n.umu.se/mirrors/ubuntu/ubuntu jammy/main 
amd64 Packages

  ===

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2053146/+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 2056187] Autopkgtest regression report (initramfs-tools/0.140ubuntu13.5)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted initramfs-tools (0.140ubuntu13.5) for 
jammy have finished running.
The following regressions have been reported in tests triggered by the package:

clevis/18-1ubuntu1 (arm64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#initramfs-tools

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank 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/2056187

Title:
  fails to configure BOOTIF when using iscsi

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in open-iscsi package in Ubuntu:
  Invalid
Status in initramfs-tools source package in Focal:
  Fix Committed
Status in open-iscsi source package in Focal:
  New
Status in initramfs-tools source package in Jammy:
  Fix Committed
Status in open-iscsi source package in Jammy:
  New

Bug description:
  [ Impact ]

   * MAAS cannot PXE-boot a machine that has iSCSI disks

   * Focal is the default Ubuntu distribution deployed by MAAS, so we should
 back-port this to ensure it works out-of-the-box.

  [ Test Plan ]

   * reproducing this issue requires a machine with iSCSI disks (Cisco UCS 
Manager
   in the original report), and a MAAS controller (3.4 or better)

   * the issue can be observed by simply enlisting the machine in MAAS. It will
   fail to boot due to the missing BOOTIF configuration.

  [ Where problems could occur ]

   * the problematic code was an attempt to fix LP#2037202, so we should watch 
out
   for regressions.

  [ Original report ]

  we have a bad interaction between initramfs-tools and open-iscsi,
  resulting in the boot interface not being configured.

  when the iscsi has a static address, the script `local-top/iscsi` from
  open-iscsi creates a /run/net-$DEVICE.conf file for the iscsi
  interface. The existence of this file makes configure_networking()
  skip configuring the BOOTIF later due to this code in
  `scripts/functions`:

  for x in /run/net-"${DEVICE}".conf /run/net-*.conf ; do
  if [ -e "$x" ]; then
  IP=done
  break
  fi
  done

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2056187/+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] Autopkgtest regression report (coreutils/8.32-4.1ubuntu1.2)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted coreutils (8.32-4.1ubuntu1.2) for jammy 
have finished running.
The following regressions have been reported in tests triggered by the package:

coreutils/unknown (arm64, ppc64el, s390x)
dotnet6/6.0.127-0ubuntu1~22.04.1 (amd64, arm64)
linux-gcp-5.19/5.19.0-1030.32~22.04.1 (arm64)
linux-gcp-6.2/6.2.0-1021.23~22.04.1 (arm64)
linux-hwe-5.19/5.19.0-50.50 (arm64)
linux-hwe-6.5/6.5.0-27.28~22.04.1 (arm64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#coreutils

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
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
  mountpo

[Touch-packages] [Bug 2051895] Autopkgtest regression report (pulseaudio/1:16.1+dfsg1-2ubuntu4.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted pulseaudio (1:16.1+dfsg1-2ubuntu4.1) 
for mantic have finished running.
The following regressions have been reported in tests triggered by the package:

libopenmpt/0.7.2-1 (i386)
libsdl2/2.28.3+dfsg-2 (i386)
pipewire/0.3.79-2 (i386)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/mantic/update_excuses.html#pulseaudio

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/2051895

Title:
  Lenovo XT99 BT headset can't work in HFP profile

Status in HWE Next:
  New
Status in pulseaudio package in Ubuntu:
  Fix Committed
Status in pulseaudio source package in Jammy:
  Fix Committed
Status in pulseaudio source package in Mantic:
  Fix Committed
Status in pulseaudio source package in Noble:
  Fix Committed

Bug description:
  [Summary]
  When use the ThinkPluse xt99 bluetooth head set to run the test 
com.canonical.certification::bluetooth/audio_record_playback, it cannot record 
the sound and playback.
  It seems this device cannot switch to Hand free mode in this platform.

  [Steps to reproduce]
  Connect the ThinkPluse xt99, use the Handfree mode, then try to record some 
voice.

  [Expected result]
  The bluetooth headset ThinkPluse xt99 can use as a MIC to input sound.

  [Actual result]
  The bluetooth headset xt99 cannot work in the Handfree mode.

  [Failure rate]
  100%

  [Impact]
  With the current Ubuntu 22.04 oem image, we try to connect the LENOVO
  XT99 bt headset and let it work in HFP mode, we select HFP profile
  from gnome sound-setting, but the microphone will not auto change to
  bt microphone and the bt output could not work too. So this BT headset
  could only work in A2DP mode with the current 22.04 OEM image.

  And we tried ubuntu 22.04 generic image, mantic image and noble image,
  none of them could make the headset work in HFP mode.

  [Fix]
  Cherry-pick a pulseaudio commit from upstream.

  [Test]
  I installed ubuntu 22.04 and 23.10 on 2 different Thinkpad laptops, then 
upgraded the pulseaudio from my ppa (ppa:hui.wang/pa-testing), in theory my 
change only affects bluetooth audio devices, it will not bring any impact to 
non-audio bluetooth devices, here I did the test with 7 bluetooth audio devices 
and 2 non-audio devices:

  BT audio devices (pairing, connection, re-connection, playback and capture 
all worked well):
  PLT_BBTGO2 (headset)
  Xiaomi Air3 SE (headset)
  Crusher Wireless (headset)
  SOAIY S18 (sound box)
  HK Soho Wireless (headset)
  Thinkplus XT99 (headset)
  Wl-1000X (headset)

  BT non-audio devices (pairing, connection, re-connection, key input all 
worked well):
  BT3.0 Keyboard
  The Pinao 2 keyboard

  
  [Where problems could occur]
  This change will impact bt headset negotiation process in the pulseaudio,
  so the possiblity of regression is limited to bt headset, it could make
  the bt headset fail to connect, but this possibility is very low, we tested
  the patch with different bt headset and bt speaker, all worked well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2051895/+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 2051895] Autopkgtest regression report (pulseaudio/1:15.99.1+dfsg1-1ubuntu2.2)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted pulseaudio (1:15.99.1+dfsg1-1ubuntu2.2) 
for jammy have finished running.
The following regressions have been reported in tests triggered by the package:

libsdl2/2.0.20+dfsg-2ubuntu1.22.04.1 (i386)
pipewire/0.3.48-1ubuntu3 (i386)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#pulseaudio

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/2051895

Title:
  Lenovo XT99 BT headset can't work in HFP profile

Status in HWE Next:
  New
Status in pulseaudio package in Ubuntu:
  Fix Committed
Status in pulseaudio source package in Jammy:
  Fix Committed
Status in pulseaudio source package in Mantic:
  Fix Committed
Status in pulseaudio source package in Noble:
  Fix Committed

Bug description:
  [Summary]
  When use the ThinkPluse xt99 bluetooth head set to run the test 
com.canonical.certification::bluetooth/audio_record_playback, it cannot record 
the sound and playback.
  It seems this device cannot switch to Hand free mode in this platform.

  [Steps to reproduce]
  Connect the ThinkPluse xt99, use the Handfree mode, then try to record some 
voice.

  [Expected result]
  The bluetooth headset ThinkPluse xt99 can use as a MIC to input sound.

  [Actual result]
  The bluetooth headset xt99 cannot work in the Handfree mode.

  [Failure rate]
  100%

  [Impact]
  With the current Ubuntu 22.04 oem image, we try to connect the LENOVO
  XT99 bt headset and let it work in HFP mode, we select HFP profile
  from gnome sound-setting, but the microphone will not auto change to
  bt microphone and the bt output could not work too. So this BT headset
  could only work in A2DP mode with the current 22.04 OEM image.

  And we tried ubuntu 22.04 generic image, mantic image and noble image,
  none of them could make the headset work in HFP mode.

  [Fix]
  Cherry-pick a pulseaudio commit from upstream.

  [Test]
  I installed ubuntu 22.04 and 23.10 on 2 different Thinkpad laptops, then 
upgraded the pulseaudio from my ppa (ppa:hui.wang/pa-testing), in theory my 
change only affects bluetooth audio devices, it will not bring any impact to 
non-audio bluetooth devices, here I did the test with 7 bluetooth audio devices 
and 2 non-audio devices:

  BT audio devices (pairing, connection, re-connection, playback and capture 
all worked well):
  PLT_BBTGO2 (headset)
  Xiaomi Air3 SE (headset)
  Crusher Wireless (headset)
  SOAIY S18 (sound box)
  HK Soho Wireless (headset)
  Thinkplus XT99 (headset)
  Wl-1000X (headset)

  BT non-audio devices (pairing, connection, re-connection, key input all 
worked well):
  BT3.0 Keyboard
  The Pinao 2 keyboard

  
  [Where problems could occur]
  This change will impact bt headset negotiation process in the pulseaudio,
  so the possiblity of regression is limited to bt headset, it could make
  the bt headset fail to connect, but this possibility is very low, we tested
  the patch with different bt headset and bt speaker, all worked well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2051895/+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] Autopkgtest regression report (debootstrap/1.0.118ubuntu1.13)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted debootstrap (1.0.118ubuntu1.13) for 
focal have finished running.
The following regressions have been reported in tests triggered by the package:

debuerreotype/0.10-1 (amd64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/focal/update_excuses.html#debootstrap

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
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] Autopkgtest regression report (debootstrap/1.0.126+nmu1ubuntu0.7)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted debootstrap (1.0.126+nmu1ubuntu0.7) for 
jammy have finished running.
The following regressions have been reported in tests triggered by the package:

debuerreotype/0.14-1 (ppc64el)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#debootstrap

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
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 2052739] Autopkgtest regression report (tzdata/2024a-0ubuntu0.23.10)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted tzdata (2024a-0ubuntu0.23.10) for 
mantic have finished running.
The following regressions have been reported in tests triggered by the package:

astropy/5.3.2-1 (arm64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/mantic/update_excuses.html#tzdata

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tzdata in Ubuntu.
https://bugs.launchpad.net/bugs/2052739

Title:
  tzdata 2024a release

Status in tzdata package in Ubuntu:
  Fix Released
Status in tzdata source package in Focal:
  Fix Committed
Status in tzdata source package in Jammy:
  Fix Committed
Status in tzdata source package in Mantic:
  Fix Committed

Bug description:
  [ Impact ]

  The 2024a release contains the following changes:

  * Kazakhstan unifies on UTC+5 beginning 2024-03-01.
  * Palestine springs forward a week later after Ramadan.
  * zic no longer pretends to support indefinite-past DST.
  * localtime no longer mishandles Ciudad Juárez in 2422.

  [ Test Plan ]

  Test cases were added to the autopkgtest to cover the testing:

  * python: test_2024a
  * python-icu: test_2024a (only for focal and newer)

  So the test plan is to check that the autopkgtest succeeds.

  [ Other Info ]

  The autopkgtest for chrony is flaky on jammy and newer (see bug
  #2002910).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2052739/+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 2052739] Autopkgtest regression report (tzdata/2024a-0ubuntu0.22.04)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted tzdata (2024a-0ubuntu0.22.04) for jammy 
have finished running.
The following regressions have been reported in tests triggered by the package:

chrony/4.2-2ubuntu2 (s390x)
mtail/3.0.0~rc48-3 (amd64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#tzdata

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tzdata in Ubuntu.
https://bugs.launchpad.net/bugs/2052739

Title:
  tzdata 2024a release

Status in tzdata package in Ubuntu:
  Fix Released
Status in tzdata source package in Focal:
  Fix Committed
Status in tzdata source package in Jammy:
  Fix Committed
Status in tzdata source package in Mantic:
  Fix Committed

Bug description:
  [ Impact ]

  The 2024a release contains the following changes:

  * Kazakhstan unifies on UTC+5 beginning 2024-03-01.
  * Palestine springs forward a week later after Ramadan.
  * zic no longer pretends to support indefinite-past DST.
  * localtime no longer mishandles Ciudad Juárez in 2422.

  [ Test Plan ]

  Test cases were added to the autopkgtest to cover the testing:

  * python: test_2024a
  * python-icu: test_2024a (only for focal and newer)

  So the test plan is to check that the autopkgtest succeeds.

  [ Other Info ]

  The autopkgtest for chrony is flaky on jammy and newer (see bug
  #2002910).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2052739/+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 2040465] Autopkgtest regression report (openldap/2.5.17+dfsg-0ubuntu0.22.04.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted openldap (2.5.17+dfsg-0ubuntu0.22.04.1) 
for jammy have finished running.
The following regressions have been reported in tests triggered by the package:

exim4/4.95-4ubuntu2.5 (ppc64el)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#openldap

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openldap in Ubuntu.
https://bugs.launchpad.net/bugs/2040465

Title:
  New upstream microrelease 2.5.17

Status in openldap package in Ubuntu:
  Invalid
Status in openldap source package in Jammy:
  Fix Committed

Bug description:
  [ Impact ]

   * MRE for the latest stable OpenLDAP 2.5.x release, 2.5.17.

  This update includes bugfixes only following the SRU policy exception
  defined at https://wiki.ubuntu.com/OpenLDAPUpdates.

  [ Major Changes ]

   * See the list of bugs fixed in this release here:

  https://lists.openldap.org/hyperkitty/list/openldap-
  annou...@openldap.org/thread/XRQE4CVQDLTG4EYPKVEU2L76DYGIFR2Q/

  [ Test Plan ]

   * Upstream gitlab pipeline results:

  
https://git.openldap.org/openldap/openldap/-/commit/99a124bb434052a71cf4ff115d0f949f6c6b7208/pipelines?ref=OPENLDAP_REL_ENG_2_5

   * Upstream "call for testing":

  https://lists.openldap.org/hyperkitty/list/openldap-
  techni...@openldap.org/thread/4744NWC2HJP7L24WOUMZF4VCYGGUMRI7/

   * As described in the MRE wiki page for OpenLDAP, the test plan is to
  build the package in a PPA and make sure that (1) all build-time tests
  pass and (2) all autopkgtest runs (from reverse dependencies) also
  pass.

   * Build log (amd64) confirming that the build-time testsuite has been 
performed and completed successfully:
- 
https://launchpadlibrarian.net/679769800/buildlog_ubuntu-jammy-amd64.openldap_2.5.16+dfsg-0ubuntu0.22.04.1~ppa1_BUILDING.txt.gz

  [ Where problems could occur ]

   * Upstream tests are always executed during build-time. There are
  many reverse dependencies whose dep8 tests depend on OpenLDAP so the
  coverage is good. Nevertheless, there is always a risk for something
  to break since we are dealing with a microrelease upgrade. Whenever a
  test failure is detected, we will be on top of it and make sure it
  doesn't affect existing users.

  [ Other Info ]

   * This is a reoccurring MRE. See below for links to previous OpenLDAP
  MREs.

   * CVEs fixed by this release:
 - None.

  Current versions in supported releases that got updates:
   openldap | 2.5.16+dfsg-0ubuntu0.22.04.2 | jammy-security  | source

  Special cases:
  - None.

  Previous MREs for OpenLDAP:
  - https://pad.lv/1977627
  - https://pad.lv/1983618
  - https://pad.lv/2007625
  - https://pad.lv/2027079
  - https://pad.lv/2029170

  As usual we test and prep from the PPA and then push through
  SRU/Security as applicable.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/2040465/+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 1995790] Autopkgtest regression report (apt/2.7.3ubuntu0.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted apt (2.7.3ubuntu0.1) for mantic have 
finished running.
The following regressions have been reported in tests triggered by the package:

apport/2.27.0-0ubuntu5 (amd64)
apt/2.7.3ubuntu0.1 (armhf)
auto-apt-proxy/14.1 (arm64)
livecd-rootfs/23.10.57 (ppc64el)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/mantic/update_excuses.html#apt

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1995790

Title:
  regression: ?garbage does not work correctly in install commands

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Jammy:
  Fix Committed
Status in apt source package in Lunar:
  Won't Fix
Status in apt source package in Mantic:
  Fix Committed
Status in apt source package in Noble:
  Fix Released

Bug description:
  [Impact]
  The '?garbage' pattern doesn't work with install/remove commands which is 
confusing, and the fix for it is trivial.

  [Test plan]
  Successful autopkgtest. The comprehensive test suite run as an autopkgtest 
has been updated in test/integration/test-apt-get-autoremove to test for the 
correct behavior of '?garbage' with install and remove.

  [Where problems could occur]
  You can see we had to tweak the test suite in a bunch of places because it 
relies on exact debug output format and because we now call "markandsweep" 
there's additional mark flags in the debug output. It's unlikely that this is a 
problem for others.

  We have not seen regressions in noble in the past 2 weeks or noble-
  proposed since 2023-11-23 (it was stuck for other reasons there),
  hence other places the code change may affect have been thoroughly
  exercised in the builders and autopkgtest runners.

  [Original bug report]
  The awesome apt has a some wonderful tips on their EXAMPLES section (printed 
below). The choice of name to "garbage" might not have been the best but the 
function is extremely useful.

  $ man apt-patterns | sed '/EXAMPLES/,/^[^ ]/!d;/^[^ ]/d'
     apt remove ?garbage
     Remove all packages that are automatically installed and no longer 
needed -
     same as apt autoremove

     apt purge ?config-files
     Purge all packages that only have configuration files left

     apt list '~i !~M (~slibs|~sperl|~spython)'
     List all manually-installed packages in sections matching libs, 
perl, or
     python.

  Lets mark a package as automatically installed, and use the examples.

  $ sudo apt-mark auto shotwell
  shotwell set to automatically installed.

  $ sudo apt remove ?garbage
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  The following packages were automatically installed and are no longer 
required:
    libraw20 shotwell shotwell-common
  Use 'sudo apt autoremove' to remove them.
  0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

  $ sudo apt autoremove
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  The following packages will be REMOVED:
    libraw20 shotwell shotwell-common
  0 upgraded, 0 newly installed, 3 to remove and 0 not upgraded.
  After this operation, 9.806 kB disk space will be freed.
  Do you want to continue? [Y/n] N
  Abort.

  Apt-patterns works as it should everywhere else, as far as I can see,
  it works wonders with ie `apt list '~g|~c'` and many other
  applications. I used `apt purge '~g|~c'` successfully in Ubuntu 20.04
  for years, so I feel this is a regression.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: apt 2.4.8
  ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60
  Uname: Linux 5.15.0-52-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov  6 10:57:52 2022
  SourcePackage: apt
  UpgradeStatus: Upgraded to jammy on 2022-03-26 (224 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1995790/+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 2051181] Autopkgtest regression report (apt/2.7.3ubuntu0.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted apt (2.7.3ubuntu0.1) for mantic have 
finished running.
The following regressions have been reported in tests triggered by the package:

apport/2.27.0-0ubuntu5 (amd64)
apt/2.7.3ubuntu0.1 (armhf)
auto-apt-proxy/14.1 (arm64)
livecd-rootfs/23.10.57 (ppc64el)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/mantic/update_excuses.html#apt

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/2051181

Title:
  apt cannot upgrade phased updates if the current security version is
  same as updates

Status in apt package in Ubuntu:
  Fix Committed
Status in apt source package in Jammy:
  Fix Committed
Status in apt source package in Mantic:
  Fix Committed
Status in apt source package in Noble:
  Fix Committed

Bug description:
  [Impact]
  A package that has the same version in -security and -updates, with the 
latter having a Phased-Update-Percentage set is subject to phasing which is not 
expected by the security team.

  [Test plan]
  An automatic test case has been added to apt's comprehensive integration test 
suite that simulates the problem. Passing of the autopkgtests is a successful 
test.

  [Where problems could occur]
  The fix in question changes the behavior, some people may have relied on 
that, but also this should not have happened server side (normally security 
updates do not receive a value but the real one in this case went a different 
route).

  Otherwise the fix is fairly contained, it removes a single OtherVer++
  increment which made it go one version below the current version, so
  we do not expect any problems; setting aside the usual regression
  potential from bugs in the compiler and so on.

  [Original bug report]
  When I finished installation with Jammy 22.04.3, I noticed that 
nvidia-driver-535 cannot be upgrade by either `apt upgrade` nor `apt 
dist-upgrade`.

  Below is the log of apt upgrade:
  ubuntu@ubuntu:~$ sudo apt -o Debug::pkgProblemResolver=1 upgrade --dry-run

[2/1878]
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  Entering ResolveByKeep 10%
    Dependencies are not satisfied for nvidia-driver-535:amd64 < 
535.129.03-0ubuntu0.22.04.1 | 535.154.05-0ubuntu0.22.04.1 @ii pumH NPb Ib >
  Package nvidia-driver-535:amd64 nvidia-driver-535:amd64 Depends on 
nvidia-dkms-535:amd64 < none | 535.154.05-0ubuntu0.22.04.1 @un umH > (<= 
535.129.03-1)
    Keeping Package linux-modules-nvidia-535-oem-22.04c:amd64 due to Depends
    Dependencies are not satisfied for 
linux-modules-nvidia-535-oem-22.04c:amd64 < 6.1.0-1027.27 | 6.1.0-1028.28+2 @ii 
umH Ib >
  Keeping package linux-modules-nvidia-535-oem-22.04c:amd64
    Dependencies are not satisfied for 
linux-modules-nvidia-535-oem-22.04c:amd64 < 6.1.0-1027.27 | 6.1.0-1028.28+2 @ii 
umH Ib >
  Package linux-modules-nvidia-535-oem-22.04c:amd64 
linux-modules-nvidia-535-oem-22.04c:amd64 Depends on 
linux-modules-nvidia-535-6.1.0-1027-oem:amd64 < 6.1.0-1027.27 -> 
6.1.0-1027.27+1 @ii umU Ib > (= 6.1.0-1027.27)
    Keeping Package linux-modules-nvidia-535-6.1.0-1027-oem:amd64 due to Depends
    Dependencies are not satisfied for 
linux-modules-nvidia-535-6.1.0-1028-oem:amd64 < none -> 6.1.0-1028.28+2 @un uN 
Ib >
  Keeping package linux-modules-nvidia-535-6.1.0-1028-oem:amd64
    Dependencies are not satisfied for 
linux-modules-nvidia-535-6.1.0-1027-oem:amd64 < 6.1.0-1027.27 | 6.1.0-1027.27+1 
@ii umH Ib >
  Keeping package linux-modules-nvidia-535-6.1.0-1027-oem:amd64
    Dependencies are not satisfied for 
linux-modules-nvidia-535-6.1.0-1027-oem:amd64 < 6.1.0-1027.27 | 6.1.0-1027.27+1 
@ii umH Ib >
  Package linux-modules-nvidia-535-6.1.0-1027-oem:amd64 
linux-modules-nvidia-535-6.1.0-1027-oem:amd64 Depends on 
linux-signatures-nvidia-6.1.0-1027-oem:amd64 < 6.1.0-1027.27 -> 6.1.0-1027.27+1 
@ii umU > (= 6.1.0-1027.27)
    Keeping Package linux-signatures-nvidia-6.1.0-1027-oem:amd64 due to Depends
    Dependencies are not satisfied for 
linux-modules-nvidia-535-6.1.0-1027-oem:amd64 < 6.1.0-1027.27 | 6.1.0-1027.27+1 
@ii umH Ib >
    Dependencies are not satisfied for 
linux-modules-nvidia-535-6.1.0-1027-oem:amd64 < 6.1.0-1027.27 | 6.1.0-1027.27+1 
@ii umH Ib >
    Dependencies are not satisfied for 
linux-modules-nvidia-535-6.1.0-1027-oem:amd64 < 6.1.0-1027.27 | 6.1.0-1027.27+1 
@ii umH Ib >
  Package linux-modules-nvidia-535-6.1.0-1027-oem:amd64 
linux-modules-nvidia-535-6.1.0-1027-oem:amd64 Depends on 
linux-objects-nvidia-535-6.1.0-1027-oem:amd6

[Touch-packages] [Bug 2051181] Autopkgtest regression report (apt/2.4.12)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted apt (2.4.12) for jammy have finished 
running.
The following regressions have been reported in tests triggered by the package:

livecd-rootfs/2.765.38 (amd64, arm64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#apt

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/2051181

Title:
  apt cannot upgrade phased updates if the current security version is
  same as updates

Status in apt package in Ubuntu:
  Fix Committed
Status in apt source package in Jammy:
  Fix Committed
Status in apt source package in Mantic:
  Fix Committed
Status in apt source package in Noble:
  Fix Committed

Bug description:
  [Impact]
  A package that has the same version in -security and -updates, with the 
latter having a Phased-Update-Percentage set is subject to phasing which is not 
expected by the security team.

  [Test plan]
  An automatic test case has been added to apt's comprehensive integration test 
suite that simulates the problem. Passing of the autopkgtests is a successful 
test.

  [Where problems could occur]
  The fix in question changes the behavior, some people may have relied on 
that, but also this should not have happened server side (normally security 
updates do not receive a value but the real one in this case went a different 
route).

  Otherwise the fix is fairly contained, it removes a single OtherVer++
  increment which made it go one version below the current version, so
  we do not expect any problems; setting aside the usual regression
  potential from bugs in the compiler and so on.

  [Original bug report]
  When I finished installation with Jammy 22.04.3, I noticed that 
nvidia-driver-535 cannot be upgrade by either `apt upgrade` nor `apt 
dist-upgrade`.

  Below is the log of apt upgrade:
  ubuntu@ubuntu:~$ sudo apt -o Debug::pkgProblemResolver=1 upgrade --dry-run

[2/1878]
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  Entering ResolveByKeep 10%
    Dependencies are not satisfied for nvidia-driver-535:amd64 < 
535.129.03-0ubuntu0.22.04.1 | 535.154.05-0ubuntu0.22.04.1 @ii pumH NPb Ib >
  Package nvidia-driver-535:amd64 nvidia-driver-535:amd64 Depends on 
nvidia-dkms-535:amd64 < none | 535.154.05-0ubuntu0.22.04.1 @un umH > (<= 
535.129.03-1)
    Keeping Package linux-modules-nvidia-535-oem-22.04c:amd64 due to Depends
    Dependencies are not satisfied for 
linux-modules-nvidia-535-oem-22.04c:amd64 < 6.1.0-1027.27 | 6.1.0-1028.28+2 @ii 
umH Ib >
  Keeping package linux-modules-nvidia-535-oem-22.04c:amd64
    Dependencies are not satisfied for 
linux-modules-nvidia-535-oem-22.04c:amd64 < 6.1.0-1027.27 | 6.1.0-1028.28+2 @ii 
umH Ib >
  Package linux-modules-nvidia-535-oem-22.04c:amd64 
linux-modules-nvidia-535-oem-22.04c:amd64 Depends on 
linux-modules-nvidia-535-6.1.0-1027-oem:amd64 < 6.1.0-1027.27 -> 
6.1.0-1027.27+1 @ii umU Ib > (= 6.1.0-1027.27)
    Keeping Package linux-modules-nvidia-535-6.1.0-1027-oem:amd64 due to Depends
    Dependencies are not satisfied for 
linux-modules-nvidia-535-6.1.0-1028-oem:amd64 < none -> 6.1.0-1028.28+2 @un uN 
Ib >
  Keeping package linux-modules-nvidia-535-6.1.0-1028-oem:amd64
    Dependencies are not satisfied for 
linux-modules-nvidia-535-6.1.0-1027-oem:amd64 < 6.1.0-1027.27 | 6.1.0-1027.27+1 
@ii umH Ib >
  Keeping package linux-modules-nvidia-535-6.1.0-1027-oem:amd64
    Dependencies are not satisfied for 
linux-modules-nvidia-535-6.1.0-1027-oem:amd64 < 6.1.0-1027.27 | 6.1.0-1027.27+1 
@ii umH Ib >
  Package linux-modules-nvidia-535-6.1.0-1027-oem:amd64 
linux-modules-nvidia-535-6.1.0-1027-oem:amd64 Depends on 
linux-signatures-nvidia-6.1.0-1027-oem:amd64 < 6.1.0-1027.27 -> 6.1.0-1027.27+1 
@ii umU > (= 6.1.0-1027.27)
    Keeping Package linux-signatures-nvidia-6.1.0-1027-oem:amd64 due to Depends
    Dependencies are not satisfied for 
linux-modules-nvidia-535-6.1.0-1027-oem:amd64 < 6.1.0-1027.27 | 6.1.0-1027.27+1 
@ii umH Ib >
    Dependencies are not satisfied for 
linux-modules-nvidia-535-6.1.0-1027-oem:amd64 < 6.1.0-1027.27 | 6.1.0-1027.27+1 
@ii umH Ib >
    Dependencies are not satisfied for 
linux-modules-nvidia-535-6.1.0-1027-oem:amd64 < 6.1.0-1027.27 | 6.1.0-1027.27+1 
@ii umH Ib >
  Package linux-modules-nvidia-535-6.1.0-1027-oem:amd64 
linux-modules-nvidia-535-6.1.0-1027-oem:amd64 Depends on 
linux-objects-nvidia-535-6.1.0-1027-oem:amd64 < 6.1.0-1027.27 -> 
6.1.0-1027.27+1 @ii umU > (= 6.1.0-1027.27)
    Keeping Package linux

[Touch-packages] [Bug 1995790] Autopkgtest regression report (apt/2.4.12)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted apt (2.4.12) for jammy have finished 
running.
The following regressions have been reported in tests triggered by the package:

livecd-rootfs/2.765.38 (amd64, arm64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#apt

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1995790

Title:
  regression: ?garbage does not work correctly in install commands

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Jammy:
  Fix Committed
Status in apt source package in Lunar:
  Won't Fix
Status in apt source package in Mantic:
  Fix Committed
Status in apt source package in Noble:
  Fix Released

Bug description:
  [Impact]
  The '?garbage' pattern doesn't work with install/remove commands which is 
confusing, and the fix for it is trivial.

  [Test plan]
  Successful autopkgtest. The comprehensive test suite run as an autopkgtest 
has been updated in test/integration/test-apt-get-autoremove to test for the 
correct behavior of '?garbage' with install and remove.

  [Where problems could occur]
  You can see we had to tweak the test suite in a bunch of places because it 
relies on exact debug output format and because we now call "markandsweep" 
there's additional mark flags in the debug output. It's unlikely that this is a 
problem for others.

  We have not seen regressions in noble in the past 2 weeks or noble-
  proposed since 2023-11-23 (it was stuck for other reasons there),
  hence other places the code change may affect have been thoroughly
  exercised in the builders and autopkgtest runners.

  [Original bug report]
  The awesome apt has a some wonderful tips on their EXAMPLES section (printed 
below). The choice of name to "garbage" might not have been the best but the 
function is extremely useful.

  $ man apt-patterns | sed '/EXAMPLES/,/^[^ ]/!d;/^[^ ]/d'
     apt remove ?garbage
     Remove all packages that are automatically installed and no longer 
needed -
     same as apt autoremove

     apt purge ?config-files
     Purge all packages that only have configuration files left

     apt list '~i !~M (~slibs|~sperl|~spython)'
     List all manually-installed packages in sections matching libs, 
perl, or
     python.

  Lets mark a package as automatically installed, and use the examples.

  $ sudo apt-mark auto shotwell
  shotwell set to automatically installed.

  $ sudo apt remove ?garbage
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  The following packages were automatically installed and are no longer 
required:
    libraw20 shotwell shotwell-common
  Use 'sudo apt autoremove' to remove them.
  0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

  $ sudo apt autoremove
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  The following packages will be REMOVED:
    libraw20 shotwell shotwell-common
  0 upgraded, 0 newly installed, 3 to remove and 0 not upgraded.
  After this operation, 9.806 kB disk space will be freed.
  Do you want to continue? [Y/n] N
  Abort.

  Apt-patterns works as it should everywhere else, as far as I can see,
  it works wonders with ie `apt list '~g|~c'` and many other
  applications. I used `apt purge '~g|~c'` successfully in Ubuntu 20.04
  for years, so I feel this is a regression.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: apt 2.4.8
  ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60
  Uname: Linux 5.15.0-52-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov  6 10:57:52 2022
  SourcePackage: apt
  UpgradeStatus: Upgraded to jammy on 2022-03-26 (224 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1995790/+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 2042587] Autopkgtest regression report (dnsmasq/2.86-1.1ubuntu0.5)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted dnsmasq (2.86-1.1ubuntu0.5) for jammy 
have finished running.
The following regressions have been reported in tests triggered by the package:

systemd/249.11-0ubuntu3.11 (ppc64el)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#dnsmasq

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/2042587

Title:
  jammy's version breaks existing dhcp scripts with relay

Status in dnsmasq package in Ubuntu:
  Fix Released
Status in dnsmasq source package in Jammy:
  Fix Committed

Bug description:
  [ Impact ]

  When upgrading from focal to jammy, existing dnsmasq dhcp-scripts
  stopped working in an environment where a DHCP relay is in use.
  Instead of the expected client IP address, the script gets the _relay_
  IP address as an argument.

  This was fixed in 2.87, therefore making only jammy carry an affected
  package.

  [ Test Plan ]

  To easily test this on a single machine, a test script is being
  provided to setup networking and dnsmasq configuration.

  # Launch a jammy VM

  lxc launch ubuntu-daily:jammy j-dnsmasq-2042587 --vm

  # open a root shell in that VM. All subsequent commands must be
  executed as root in that VM

  lxc shell j-dnsmasq-2042587

  # download test script

  wget
  
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/2042587/+attachment/5738174/+files/setup-
  and-server.sh

  # make it executable

  chmod +x setup-and-server.sh

  # install dnsmasq. Ignore the postinst error (because systemd-resolved
  is also running and there is a port conflict)

  apt update && apt install dnsmasq -y

  # run the setup script. It will configure things and start dnsmasq
  ready to be tested

  ./setup-and-server.sh

  # in another root session inside the vm (so run "lxc shell
  j-dnsmasq-2042587" in another terminal), run the proposed commands
  from the setup script (and press ctrl-c after the result is shown):

  No DHCP relay:

    ip netns exec client dhclient -d -v p2

  The setup script should log an IP that is not a relay. For example:
  dnsmasq-dhcp: DHCPDISCOVER(p1) aa:a0:9d:00:5b:d6
  dnsmasq-dhcp: DHCPOFFER(p1) 192.168.47.150 aa:a0:9d:00:5b:d6
  dnsmasq-dhcp: DHCPREQUEST(p1) 192.168.47.150 aa:a0:9d:00:5b:d6
  dnsmasq-dhcp: DHCPACK(p1) 192.168.47.150 aa:a0:9d:00:5b:d6 j-dnsmasq-2042587
  ###
  IP = 192.168.47.150
  ###

  With DHCP relay set to 192.168.47.9, IP should NOT be that address:

    ip netns exec client dhclient -d -v p2 -g 192.168.47.9

  With the affected dnsmasq package, we will see an error:
  dnsmasq-dhcp: DHCPREQUEST(p1) 192.168.47.150 aa:a0:9d:00:5b:d6
  dnsmasq-dhcp: DHCPACK(p1) 192.168.47.150 aa:a0:9d:00:5b:d6 j-dnsmasq-2042587
  ###
  IP = 192.168.47.9
  TEST FAILED
  ###

  The error is that the obtained IP is that of the dhcp relay (provided
  via the -g option).

  With the fixed dnsmasq package, "TEST FAILED" must not appear, and the
  IP should not be that of the provided dhcp relay.

  [ Where problems could occur ]

  If the fix is incorrect, it would mean the dhcp-script would get an incorrect 
IP again, or perhaps we could have crashes in dnsmasq when dealing with buffers 
and pointers if the dhcp-script option is in use.
  This fix was committed upstream a few months after the bug was introduced, so 
it took a while to be noticed.

  [ Other Info ]
  Not at this time.

  [ Original description ]

  When upgrading from focal to jammy, existing dnsmasq dhcp-scripts
  stopped working in an environment where a DHCP relay is in use.
  Instead of the expected client IP address, the script gets the _relay_
  IP address as an argument. From dnsmasq documentation for --dhcp-
  script:

  > The arguments to the process are "add", "old" or "del", the MAC
  address of the host (or DUID for IPv6) , the IP address, and the
  hostname, if known.

  I believe the change has been inadverently made in upstream commit
  527c3c7d0d3bb4bf5fad699f10cf0d1a45a54692
  
(https://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=blobdiff;f=src/helper.c;h=02340a01c00031db0cc682c8a4a279cfc1db574e;hp=d81de9622e6d484a264496b2cd3638b4e15e9677;hb=527c3c7d0d3bb4bf5fad699f10cf0d1a45a54692;hpb=fcb4dcaf7cc8a86ac2533b933161b6455f75bf8f)
  as the commit message only speaks about inet_ntoa replacement and not
  the behavioral change it also introduces (previously the relay address
  was only set to the environment variable, now it effectively overrides
  the prevoiusly set client's IP address).

  dnsmasq 2.86-1.1ubuntu0.3 / Ubuntu 22.04

To man

[Touch-packages] [Bug 2045570] Autopkgtest regression report (dnsmasq/2.86-1.1ubuntu0.5)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted dnsmasq (2.86-1.1ubuntu0.5) for jammy 
have finished running.
The following regressions have been reported in tests triggered by the package:

systemd/249.11-0ubuntu3.11 (ppc64el)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#dnsmasq

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/2045570

Title:
  dnsmasq crash when no servers in resolv.conf

Status in dnsmasq package in Ubuntu:
  Fix Released
Status in dnsmasq source package in Jammy:
  Fix Committed

Bug description:
  [ Impact ]

  dnsmasq "keeps an eye" on /etc/resolv.conf, and reloads it whenever
  the file is updated. When that happens and for some reason there were
  no "nameserver" declarations in the updated file, dnsmasq can crash.

  Here is a log of a reproducer:
  $ dig +short @127.0.0.1 ubuntu.com
  ;; communications error to 127.0.0.1#53: timed out
  ;; communications error to 127.0.0.1#53: connection refused
  ;; communications error to 127.0.0.1#53: connection refused
  ;; no servers could be reached

  We can see the startup, then when resolv.conf is read again and no 
nameservers were found, and the crash:
  Jan 03 13:57:13 j-dnsmasq-2045570 dnsmasq[1507]: started, version 2.86 
cachesize 150
  Jan 03 13:57:13 j-dnsmasq-2045570 dnsmasq[1507]: DNS service limited to local 
subnets
  Jan 03 13:57:13 j-dnsmasq-2045570 dnsmasq[1507]: compile time options: IPv6 
GNU-getopt DBus no-UBus i18n IDN2 DHCP DHCPv6 no-Lua TFTP conntrack ipset auth 
cryptohash DNSSEC loop-detect inotify dumpfile
  Jan 03 13:57:13 j-dnsmasq-2045570 dnsmasq[1507]: reading /etc/resolv.conf
  Jan 03 13:57:13 j-dnsmasq-2045570 dnsmasq[1507]: using nameserver 
10.0.100.1#53
  Jan 03 13:57:13 j-dnsmasq-2045570 dnsmasq[1507]: read /etc/hosts - 7 addresses
  Jan 03 13:57:13 j-dnsmasq-2045570 systemd[1]: Started dnsmasq - A lightweight 
DHCP and caching DNS server.
  Jan 03 13:58:01 j-dnsmasq-2045570 dnsmasq[1507]: no servers found in 
/etc/resolv.conf, will retry
  Jan 03 13:58:22 j-dnsmasq-2045570 systemd[1]: dnsmasq.service: Main process 
exited, code=dumped, status=11/SEGV
  Jan 03 13:58:22 j-dnsmasq-2045570 systemd[1]: dnsmasq.service: Failed with 
result 'core-dump'.

  dnsmasq has provisions for this situation, we can see that in the
  13:58:01 message where it says it will retry, but due to this bug, it
  crashes instead.

  The problem was introduced[1] in version 2.86, and fixed in 2.87, so
  only jammy is affected.

  1. 
https://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=patch;h=d290630d31f4517ab26392d00753d1397f9a4114;hp=d2ad5dc073aaacaf22b117f16106282a73586803
  The commit message says:
  """
  This problem was introduced in 2.86.
  """

  And indeed, I wasn't able to crash 2.80 shipped in focal.

  [ Test Plan ]
  It might take a few tries to reproduce the bug, but here is the general 
outline. Also keep in mind that it's important to use a DNS name that isn't 
cached already by a previous query.

  # Create a jammy lxd container

  lxc launch ubuntu-daily:jammy j-dnsmasq-2045570

  # Enter the container

  lxc shell j-dnsmasq-2045570

  # From now on, all commands should be executed in the container.
  # Install dnsmasq, and disable systemd-resolved

  apt update && apt install -y dnsmasq

  # Disable systemd-resolved, and start dnsmasq

  systemctl disable --now systemd-resolved
  systemctl enable --now dnsmasq

  # In one terminal inside the container, watch the dnsmasq logs:

  journalctl -u dnsmasq.service -f

  # In another terminal, remove /etc/resolv.conf and create a new one, empty
  rm /etc/resolv.conf
  echo "nameserver 1.1.1.1" > /etc/resolv.conf

  # restart dnsmasq
  systemctl restart dnsmasq.service

  # Perform a dns query

  dig @127.0.0.1 +short linux.com

  # Comment the namserver directive in resolv.conf
  echo "#nameserver 1.1.1.1" > /etc/resolv.conf

  # Observe in the dnsmasq logs that it notices the change with a
  message like:

  Jan 03 14:14:51 j-dnsmasq-2045570 dnsmasq[2274]: no servers found in
  /etc/resolv.conf, will retry

  # Perform a *different* DNS query

  dig @127.0.0.1 +short ubuntu.com

  # Observe in the dnsmasq logs that it crashes.
  Jan 03 13:58:22 j-dnsmasq-2045570 systemd[1]: dnsmasq.service: Main process 
exited, code=dumped, status=11/SEGV
  Jan 03 13:58:22 j-dnsmasq-2045570 systemd[1]: dnsmasq.service: Failed with 
result 'core-dump'.

  If it doesn't crash right away, repeat these steps a few times, but using a 
different domain name each time:
  - add "nameserver 127.0.0.1" to /etc/resolv.conf
  - observe that dnsmasq notices the change to the file