[Bug 2079914] Re: kodi dies with "PyImport_AppendInittab() may not be called after Py_Initialize()"
** Also affects: kodi (Ubuntu Noble) Importance: Undecided Status: New ** Changed in: kodi (Ubuntu Noble) Status: New => Confirmed ** Changed in: kodi (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2079914 Title: kodi dies with "PyImport_AppendInittab() may not be called after Py_Initialize()" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kodi/+bug/2079914/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078525] Re: [SRU] zero-2-w.dtb does not exist in arm64 variant of linux-raspi
** Description changed: + [ Impact ] + + This is affecting upgraders from jammy to noble on the Raspberry Pi Zero + 2W. Specifically, flash-kernel is failing to find the expected dtb once + the noble version of flash-kernel is in place, causing it to fail. This + terminates the apt operation, breaking do-release-upgrade. + + [ Test Plan ] + + To be repeated on all supported models of Pi: + + * Install the -proposed version of flash-kernel + * Run "sudo flash-kernel" and ensure operation completes successfully + * On the Zero 2W specifically, ensure the *-zero-2-w.dtb or *-zero-2.dtb is reported in the first few lines of output (on the release version it will, erroneously, be the *-4-b.dtb instead) + + [ Regression Potential ] + + Minimal; the change uses a well-tested mechanism within flash-kernel to + probe for the correct dtb. Moreover, the change has already undergone + testing on all supported boards during the jammy .5 ISO tests (while + doing the server tests, I added my flash-kernel PPA and re-ran the + flash-kernel test), the oracular beta ISO tests, and random noble + testing in between. + + [ Original Description ] + package plymouth 24.004.60-1ubuntu7 failed to install/upgrade: installed plymouth package post-installation script subprocess returned error exit status 1 ProblemType: Package DistroRelease: Ubuntu 24.04 Package: plymouth 24.004.60-1ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-1061.64-raspi 5.15.160 Uname: Linux 5.15.0-1061-raspi aarch64 ApportVersion: 2.28.1-0ubuntu3.1 Architecture: arm64 BootLog: - + CasperMD5CheckResult: unknown CloudArchitecture: aarch64 CloudBuildName: server CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSerial: - + CloudSubPlatform: config-disk (/dev/mmcblk0p1) Date: Fri Aug 30 23:05:22 2024 ErrorMessage: installed plymouth package post-installation script subprocess returned error exit status 1 ImageMediaBuild: 20230807.2 Lspci: - + Lspci-vt: - + Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 001.Port 001: Dev 001, Class=root_hub, Driver=dwc2/1p, 480M ProcCmdLine: coherent_pool=1M 8250.nr_uarts=1 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 bcm2708_fb.fbwidth=720 bcm2708_fb.fbheight=480 bcm2708_fb.fbdepth=16 bcm2708_fb.fbswap=1 smsc95xx.macaddr=B8:27:EB:D7:09:57 vc_mem.mem_base=0x1fa0 vc_mem.mem_size=0x2000 console=ttyS0,115200 dwc_otg.lpm_enable=0 console=tty1 root=LABEL=writable rootfstype=ext4 rootwait fixrtc quiet splash cfg80211.ieee80211_regdom=UA ProcFB: 0 BCM2708 FB ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=1 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 bcm2708_fb.fbwidth=720 bcm2708_fb.fbheight=480 bcm2708_fb.fbdepth=16 bcm2708_fb.fbswap=1 smsc95xx.macaddr=B8:27:EB:D7:09:57 vc_mem.mem_base=0x1fa0 vc_mem.mem_size=0x2000 console=ttyS0,115200 dwc_otg.lpm_enable=0 console=tty1 root=LABEL=writable rootfstype=ext4 rootwait fixrtc quiet splash cfg80211.ieee80211_regdom=UA Python3Details: /usr/bin/python3.12, Python 3.12.3, python3-minimal, 3.12.3-0ubuntu2 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: - dpkg 1.22.6ubuntu6.1 - apt 2.7.14build2 + dpkg 1.22.6ubuntu6.1 + apt 2.7.14build2 SourcePackage: plymouth TextPlymouth: /usr/share/plymouth/themes/ubuntu-text/ubuntu-text.plymouth Title: package plymouth 24.004.60-1ubuntu7 failed to install/upgrade: installed plymouth package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to noble on 2024-08-30 (0 days ago) acpidump: - + mtime.conffile..etc.init.d.apport: 2024-07-22T17:59:07 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078525 Title: [SRU] zero-2-w.dtb does not exist in arm64 variant of linux-raspi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/2078525/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2077981] Re: [SRU] Add HiFive Premier P550 to database
** Changed in: flash-kernel (Ubuntu Noble) Assignee: (unassigned) => Dave Jones (waveform) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2077981 Title: [SRU] Add HiFive Premier P550 to database To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/2077981/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2081313] Re: Please merge flash-kernel 3.108 from Debian unstable
** Changed in: flash-kernel (Ubuntu) Assignee: (unassigned) => Dave Jones (waveform) ** Changed in: flash-kernel (Ubuntu) Milestone: None => later -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2081313 Title: Please merge flash-kernel 3.108 from Debian unstable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/2081313/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2081312] [NEW] flash-kernel producing boot.scr on oracular
Public bug reported: The oracular images no longer include u-boot on the boot partition at all. However, flash-kernel is still producing a boot.scr artefact on each run. This means we won't be able to unseed u-boot-rpi as planned, unless this operation is fixed. Remove U-Boot-Script-Name from all relevant Raspberry Pi entries in the db. ** Affects: flash-kernel (Ubuntu) Importance: High Assignee: Dave Jones (waveform) Status: Confirmed ** Tags: foundations-todo ** Changed in: flash-kernel (Ubuntu) Milestone: None => ubuntu-24.10 ** Changed in: flash-kernel (Ubuntu) Assignee: (unassigned) => Dave Jones (waveform) ** Changed in: flash-kernel (Ubuntu) Status: New => Confirmed ** Changed in: flash-kernel (Ubuntu) Importance: Undecided => High ** Tags added: foundations-todo -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2081312 Title: flash-kernel producing boot.scr on oracular To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/2081312/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2081313] [NEW] Please merge flash-kernel 3.108 from Debian unstable
Public bug reported: Please merge flash-kernel 3.108 from Debian unstable. Updated changelog and diff against Debian unstable to be attached below. ** Affects: flash-kernel (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2081313 Title: Please merge flash-kernel 3.108 from Debian unstable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/2081313/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060693] Re: No welcome/login sound on Ubuntu desktop
** Description changed: Under the Ubuntu desktop for Raspberry Pi, for several recent releases, the startup sound from the Yaru sound theme has failed to play both at the initial setup (from oem-config, where it used to play just before language selection), and at the greeter. This worked in Jammy (22.04), but on at least mantic (23.10) and the forthcoming noble (24.04) (and possibly earlier), this has failed. It's not due to a crash in canberra-gtk-play (used to play the sound). The only hint that something has failed appears in the oem-config.log: - Failed to play sound: Not available + Failed to play sound: Not available Unfortunately there's nothing else in the log that hints at why canberra-gtk-play is failing. There are several similar bug report, but I doubt they are related given their age (e.g. LP: #1002114 relates to ubuntu 12.04 which had a very different sound stack and predates the preinstalled desktop images). + + Additional note: the desktop login sound on oracular *is* working; it's + just the oem-config sound that isn't. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060693 Title: No welcome/login sound on Ubuntu desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcanberra/+bug/2060693/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2081287] [NEW] oem-config in oracular still display noble slides
Public bug reported: The first time setup on the Pi desktop images (run by oem-config, source package ubiquity) is still showing slides with noble's livery on them. ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2081287 Title: oem-config in oracular still display noble slides To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/2081287/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080368] Re: Support CM5
** Tags removed: block-proposed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2080368 Title: Support CM5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rpi-eeprom/+bug/2080368/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2081117] Re: Mercurial FTBFS with python 3.12.6
** Also affects: mercurial (Ubuntu Noble) Importance: Undecided Status: New ** Changed in: mercurial (Ubuntu Noble) Status: New => Confirmed ** Changed in: mercurial (Ubuntu Noble) Assignee: (unassigned) => Dave Jones (waveform) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2081117 Title: Mercurial FTBFS with python 3.12.6 To manage notifications about this bug go to: https://bugs.launchpad.net/hg/+bug/2081117/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054092] Re: [SRU] Add support for FIT images to rpi config
Updated verification case, and verified SRU as working accordingly on a
Pi 3B and Pi 4B with the noble image specified in the test plan, and the
u-boot currently in -proposed.
** Description changed:
[ Impact ]
The current u-boot-rpi package does not include support for FIT images.
Enabling this feature has been requested by an internal team.
[ Test Plan ]
To test FIT image generation:
* Flash the Ubuntu Server for Raspberry Pi 24.04.1 image [1] to an SD card
- * Place the following content in a file named "image.its":
-
+ * Boot Ubuntu Server and login
+ * cp /boot/firmware/vmlinuz .
+ * cp /boot/firmware/initrd.img .
+ * cat << EOF > image.its
/dts-v1/;
/ {
- description = "FIT payload";
- #address-cells = <2>;
- images {
- kernel {
- description = "kernel";
- data = /incbin/("vmlinux.zst");
- type = "kernel";
- arch = "arm64";
- os = "linux";
- compression = "zstd";
- load = <0x20>;
- entry = <0x20>;
- hash {
- algo = "sha1";
- };
- };
- initrd {
- description = "initramfs";
- data = /incbin/("initrd.cpio.zst");
- type = "ramdisk";
- arch = "arm64";
- os = "linux";
- compression = "none";
- hash {
- algo = "sha1";
- };
- };
- };
- configurations {
- default = "standard";
- standard {
- description = "config";
- kernel = "kernel";
- ramdisk = "initrd";
- hash {
- algo = "sha1";
- };
- };
- };
+ description = "FIT payload";
+ #address-cells = <2>;
+ images {
+ kernel {
+ description = "kernel";
+ data = /incbin/("vmlinuz");
+ type = "kernel";
+ arch = "arm64";
+ os = "linux";
+ compression = "gzip";
+ load = <0x20>;
+ entry = <0x20>;
+ hash {
+ algo = "sha1";
+ };
+ };
+ initrd {
+ description = "initramfs";
+ data = /incbin/("initrd.img");
+ type = "ramdisk";
+ arch = "arm64";
+ os = "linux";
+ compression = "none";
+ hash {
+ algo = "sha1";
+ };
+ };
+ };
+ configurations {
+ default = "standard";
+ standard {
+ description = "config";
+ kernel = "kernel";
+ ramdisk = "initrd";
+ hash {
+ algo = "sha1";
+ };
+ };
+ };
};
-
- * Run mkimage -f image.its -T flat_dt
+ EOF
+ * Run mkimage -f image.its -T flat_dt image.fit
* Observe failure with current version
* Upgrade u-boot-rpi to version in -proposed
- * Run mkimage -f image.its -T flat_dt
- * Observe successful generation of image
+ * Run mkimage -f image.its -T flat_dt image.fit
+ * Observe successful generation of image in image.fit
- To test no regression in boot operation:
+ To test no regression in boot operation (carrying on from previous
+ instructions):
- * Flash the Ubuntu Server for Raspberry Pi 24.04.1 image [1] to an SD card
* Modify the boot sequence to include u-boot. In config.txt:
- - Set kernel=uboot_rpi_4.bin (adjust as appropriate for test board)
- - Set device_tree_address=0x0300
+ - Set kernel=uboot_rpi_4.bin (adjust as appropriate for test board)
+ - Set device_tree_address=0x0300
+ - Comment out initramfs line
+ * sudo cp image.fit /boot/firmware/
* sudo reboot
+ * Interrupt u-boot
+ * setexpr loadaddr $fdt_addr + 0x10
+ * load mmc 0:1 $loadaddr image.fit
+ * bootm :kernel :initrd $fdt_addr
* Ensure boot succeeds
[1]:
http://cdimage.ubuntu.com/releases/24.04.1/release/ubuntu-24.04.1-preinstalled-
desktop-arm64+raspi.img.xz
[ Regression Potential ]
Varied; the u-boot package hasn't been used in the classic images since
focal (and jammy upgrades includes a quirk to remove it from the boot
chain), so the impact on the server and desktop images should be nil
even if it failed entirely. However, the Core images still use u-boot so
its operation should be checked on all boards supported by Core 24
(specifically the Pi 3, 4, and 5 series) by following the second part of
the test plan above.
[ Original Description ]
Support for signed FIT images has been requested; the following config
items should be enabled for the rpi 3 and 4 configurations (in both
armhf and arm64):
CONFIG_FIT=y
CONFIG_FIT_SIGNATURE=y
CONFIG_FIT_VERBOSE=y
CONFIG_FIT_PRINT=y
CONFIG_TOOLS_FIT=y
CONFIG_TOOLS_FIT_SIGNATURE=y
CONFIG_TOOLS_FIT_VERBOSE=y
CONFIG_TOOLS_FIT_PRINT=y
CONFIG_ZSTD=y
Check this doesn't affect core
[Bug 2054092] Re: [SRU] Add support for FIT images to rpi config
I've confirmed u-boot is not used on the Core 24 images. It's still present ... it's just not used, so that's something else to clean up in the gadget. Currently working on an updated verification case. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054092 Title: [SRU] Add support for FIT images to rpi config To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/u-boot/+bug/2054092/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2081117] Re: Mercurial FTBFS with python 3.12.6
** Bug watch added: bz.mercurial-scm.org/ #6917 https://bz.mercurial-scm.org/show_bug.cgi?id=6917 ** Also affects: hg via https://bz.mercurial-scm.org/show_bug.cgi?id=6917 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2081117 Title: Mercurial FTBFS with python 3.12.6 To manage notifications about this bug go to: https://bugs.launchpad.net/hg/+bug/2081117/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2081117] [NEW] Mercurial FTBFS with python 3.12.6
Public bug reported: Mercurial's patchbomb module's tests are incompatible with the email.utils changes introduced in Python 3.12.6. A trivial modification is necessary to permit the tests to pass. ** Affects: mercurial (Ubuntu) Importance: Undecided Assignee: Dave Jones (waveform) Status: Confirmed ** Changed in: mercurial (Ubuntu) Assignee: (unassigned) => Dave Jones (waveform) ** Changed in: mercurial (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2081117 Title: Mercurial FTBFS with python 3.12.6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mercurial/+bug/2081117/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054092] Re: [SRU] Add support for FIT images to rpi config
I may have been too hasty above. Apparently Core may no longer rely on u-boot either. I've reset the tags pending further investigation. If Core does indeed not require u-boot, we'll still need some means of determining that the change leaves u-boot operable (for anybody actually using it in practice, although it's not supported on Classic images). If that's the case, I'll update the second part of the verification instructions accordingly. ** Tags removed: verification-failed-noble ** Tags added: verification-needed-noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054092 Title: [SRU] Add support for FIT images to rpi config To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/u-boot/+bug/2054092/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054092] Re: [SRU] Add support for FIT images to rpi config
The first part of the test plan (generating test FIT images) has passed successfully. Unfortunately the second part, ensuring existing boot scripts continue to operate normally, has failed. I need to figure out if there's a way to support FIT images *and* support loading of kernel/initrd from straight images. This change can remain in the devel (oracular) series as firstly Classic images no longer rely on u-boot and secondly interim releases aren't used for generation of Core images (which do rely on u-boot). ** Tags removed: verification-needed-noble ** Tags added: verification-failed-noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054092 Title: [SRU] Add support for FIT images to rpi config To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/u-boot/+bug/2054092/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080368] Re: Support CM5
** Tags added: block-proposed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2080368 Title: Support CM5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rpi-eeprom/+bug/2080368/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2076152] Re: SRU: add threading to the list of modules which cannot be lazy imported
** Description changed: + [ Impact ] + + The current release of mercurial fails to start with Python 3.12.5 or + later. Although this version of Python is not currently in noble, it is + planned to be as part of noble's LTS lifecycle. + + [ Test Plan ] + + Start a noble container, install mercurial and verify it works: + + lxc launch ubuntu:n merctest + lxc shell merctest + apt update + apt install -y mercurial + hg --version + + Upgrade to a version of python >=3.12.5. Because this is not yet + available in noble, we'll use the oracular debs. Still within the + container: + + apt install ubuntu-dev-tools + pull-lp-debs python3-defaults + pull-lp-debs python3.12 + pull-lp-debs openssl + apt install ./python3_3.12.6-0ubuntu1_amd64.deb ./python3-minimal_3.12.6-0ubuntu1_amd64.deb ./libpython3-stdlib_3.12.6-0ubuntu1_amd64.deb ./libpython3.12-stdlib_3.12.6-1_amd64.deb ./python3.12-minimal_3.12.6-1_amd64.deb ./python3.12_3.12.6-1_amd64.deb ./libpython3.12-minimal_3.12.6-1_amd64.deb ./libssl3t64_3.3.1-2ubuntu1_amd64.deb ./libpython3.12t64_3.12.6-1_amd64.deb + hg --version + + At this point, mercurial should crash complaining "AttributeError: + partially initialized module 'threading' has no attribute 'RLock' (most + likely due to a circular import)" + + Upgrade mercurial to the version in noble-proposed, and re-run hg + --version to verify the fix. + + [ Regression Potential ] + + Minimal; the patch in question is already part of the mercurial release + in oracular, which has a version of python >=3.12.5. The patch itself is + minimal, simply marking two modules (threading and _weakrefset) for + standard import (not lazy), and altering a couple of test cases to deal + with modified output syntax in the later version. Mercurial itself also + has a comprehensive test suite. + + [ Original Description ] + hg fails to start with Python 3.12.5 and Python 3.13.0rc1 (see the Debian bug for details). This patch adds the threading module to the list of modules which cannot be lazy imported. We will backport Python 3.12.5 to the 24.04 LTS release, so update mercurial first to avoid later breakage. There are no code changes, except for the threading module now being loaded at startup. Test case: hg starts with Python 3.12.5 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2076152 Title: SRU: add threading to the list of modules which cannot be lazy imported To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mercurial/+bug/2076152/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2070443] Re: SRU: Fix critical regression in Mercurial 6.7.x < 6.7.4
** Changed in: mercurial (Ubuntu Noble) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2070443 Title: SRU: Fix critical regression in Mercurial 6.7.x < 6.7.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mercurial/+bug/2070443/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2076152] Re: SRU: add threading to the list of modules which cannot be lazy imported
Ah, sorry forgot I needed to update this one as well as LP: #2070443. Will put something together... ** Changed in: mercurial (Ubuntu) Status: New => Fix Released ** Changed in: mercurial (Ubuntu Noble) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2076152 Title: SRU: add threading to the list of modules which cannot be lazy imported To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mercurial/+bug/2076152/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054092] Re: [SRU] Add support for FIT images to rpi config
** Description changed:
+ [ Impact ]
+
+ The current u-boot-rpi package does not include support for FIT images.
+ Enabling this feature has been requested by an internal team.
+
+ [ Test Plan ]
+
+ To test FIT image generation:
+
+ * Flash the Ubuntu Server for Raspberry Pi 24.04.1 image [1] to an SD card
+ * Place the following content in a file named "image.its":
+
+ /dts-v1/;
+ / {
+ description = "FIT payload";
+ #address-cells = <2>;
+ images {
+ kernel {
+ description = "kernel";
+ data = /incbin/("vmlinux.zst");
+ type = "kernel";
+ arch = "arm64";
+ os = "linux";
+ compression = "zstd";
+ load = <0x20>;
+ entry = <0x20>;
+ hash {
+ algo = "sha1";
+ };
+ };
+ initrd {
+ description = "initramfs";
+ data = /incbin/("initrd.cpio.zst");
+ type = "ramdisk";
+ arch = "arm64";
+ os = "linux";
+ compression = "none";
+ hash {
+ algo = "sha1";
+ };
+ };
+ };
+ configurations {
+ default = "standard";
+ standard {
+ description = "config";
+ kernel = "kernel";
+ ramdisk = "initrd";
+ hash {
+ algo = "sha1";
+ };
+ };
+ };
+ };
+
+ * Run mkimage -f image.its -T flat_dt
+ * Observe failure with current version
+ * Upgrade u-boot-rpi to version in -proposed
+ * Run mkimage -f image.its -T flat_dt
+ * Observe successful generation of image
+
+ To test no regression in boot operation:
+
+ * Flash the Ubuntu Server for Raspberry Pi 24.04.1 image [1] to an SD card
+ * Modify the boot sequence to include u-boot. In config.txt:
+ - Set kernel=uboot_rpi_4.bin (adjust as appropriate for test board)
+ - Set device_tree_address=0x0300
+ * sudo reboot
+ * Ensure boot succeeds
+
+ [1]:
+
http://cdimage.ubuntu.com/releases/24.04.1/release/ubuntu-24.04.1-preinstalled-
+ desktop-arm64+raspi.img.xz
+
+ [ Regression Potential ]
+
+ Varied; the u-boot package hasn't been used in the classic images since
+ focal (and jammy upgrades includes a quirk to remove it from the boot
+ chain), so the impact on the server and desktop images should be nil
+ even if it failed entirely. However, the Core images still use u-boot so
+ its operation should be checked on all boards supported by Core 24
+ (specifically the Pi 3, 4, and 5 series) by following the second part of
+ the test plan above.
+
+ [ Original Description ]
+
Support for signed FIT images has been requested; the following config
items should be enabled for the rpi 3 and 4 configurations (in both
armhf and arm64):
CONFIG_FIT=y
CONFIG_FIT_SIGNATURE=y
CONFIG_FIT_VERBOSE=y
CONFIG_FIT_PRINT=y
CONFIG_TOOLS_FIT=y
CONFIG_TOOLS_FIT_SIGNATURE=y
CONFIG_TOOLS_FIT_VERBOSE=y
CONFIG_TOOLS_FIT_PRINT=y
CONFIG_ZSTD=y
Check this doesn't affect core 24 images (there will inevitably be a
size increase as a result of enabling more flags; this is probably a
good time to unseed u-boot on the pi images for oracular).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054092
Title:
[SRU] Add support for FIT images to rpi config
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/u-boot/+bug/2054092/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054092] Re: [SRU] Add support for FIT images to rpi config
** Summary changed: - Add support for FIT images to rpi config + [SRU] Add support for FIT images to rpi config -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054092 Title: [SRU] Add support for FIT images to rpi config To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/u-boot/+bug/2054092/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078761] Re: Update Raspberry Pi Firmware
I've been holding off on bumping rpi-eeprom (which is what you actually want for the Pi 5) to get the latest boot firmware into oracular in the hopes that it will work on the CM5 when that launches (LP: #2080368). Unfortunately, I don't have time to do more than one bump of the package per cycle (especially when there are added complexities of new dependencies which aren't in main -- i.e. flashrom). The SRU rules are such that this won't be back-ported to noble without a request to fix a problem you're encountering (i.e. we need to verify the change fixes something as part of an SRU test plan). If there is a specific issue you're encountering, and you've got an idea which firmware version fixes it, I can certainly look at pushing that into current releases. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078761 Title: Update Raspberry Pi Firmware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware-raspi/+bug/2078761/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080407] [NEW] Please merge rpi-imager 1.9.0
Public bug reported: New version released upstream: https://github.com/raspberrypi/rpi- imager/releases/tag/v1.9.0 ** Affects: rpi-imager (Ubuntu) Importance: Undecided Assignee: Dave Jones (waveform) Status: Confirmed ** Changed in: rpi-imager (Ubuntu) Assignee: (unassigned) => Dave Jones (waveform) ** Changed in: rpi-imager (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2080407 Title: Please merge rpi-imager 1.9.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rpi-imager/+bug/2080407/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080368] Re: Support CM5
The new version includes the signing tools for the EEPROM, which introduce a dependency on python3-pycryptodome. This is in universe, but rpi-eeprom needs to remain in main in order to be seeded on the images. As a result, I'm going to split the signing tools into their own package: rpi-eeprom-sign which can remain in universe. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2080368 Title: Support CM5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rpi-eeprom/+bug/2080368/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080368] [NEW] Support CM5
Public bug reported:
In order to provide support for the forthcoming CM5, we should
incorporate all possible boot fixes for the CM5 into the oracular
release. Of particular note are the following releases:
* https://github.com/raspberrypi/rpi-
eeprom/releases/tag/v2024.07.30-2712 -- support CM5 on the CM4IO board
* https://github.com/raspberrypi/rpi-
eeprom/releases/tag/v2024.06.05-2712 -- support for CM5 in [pi5]
conditional sections of config.txt
* https://github.com/raspberrypi/rpi-
eeprom/releases/tag/v2024.02.17-2712 -- preliminary support for CM5
Merging the current rpi-eeprom 24.0 release would incorporate these
changes. These changes should also be SRU'd to noble as part of ongoing
hardware support in the current LTS, but this can likely wait until
oracular's release.
** Affects: rpi-eeprom (Ubuntu)
Importance: High
Assignee: Dave Jones (waveform)
Status: Confirmed
** Affects: rpi-eeprom (Ubuntu Noble)
Importance: Medium
Assignee: Dave Jones (waveform)
Status: Confirmed
** Tags: foundations-todo raspi-image
** Changed in: rpi-eeprom (Ubuntu)
Assignee: (unassigned) => Dave Jones (waveform)
** Changed in: rpi-eeprom (Ubuntu)
Milestone: None => ubuntu-24.10
** Changed in: rpi-eeprom (Ubuntu)
Status: New => Confirmed
** Also affects: rpi-eeprom (Ubuntu Noble)
Importance: Undecided
Status: New
** Changed in: rpi-eeprom (Ubuntu)
Importance: Undecided => High
** Changed in: rpi-eeprom (Ubuntu Noble)
Importance: Undecided => Medium
** Changed in: rpi-eeprom (Ubuntu Noble)
Status: New => Confirmed
** Changed in: rpi-eeprom (Ubuntu Noble)
Assignee: (unassigned) => Dave Jones (waveform)
** Tags added: foundations-todo
** Tags added: raspi-image
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2080368
Title:
Support CM5
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rpi-eeprom/+bug/2080368/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078525] Re: [SRU] zero-2-w.dtb does not exist in arm64 variant of linux-raspi
Setting priorities: high for noble as this is breaking people upgrading on a Pi Zero 2W; medium for jammy as it will be needed there when LP: #2038087 is SRU'd (which turns out to be why I didn't notice this bug on jammy); low for oracular as I'm not 100% sure this fix is required in oracular (given users *must* pass through noble to get to oracular, and in theory at least shouldn't have any jammy kernels left around when they get there). ** Changed in: flash-kernel (Ubuntu) Assignee: (unassigned) => Dave Jones (waveform) ** Changed in: flash-kernel (Ubuntu Noble) Importance: Undecided => High ** Changed in: flash-kernel (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: flash-kernel (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078525 Title: [SRU] zero-2-w.dtb does not exist in arm64 variant of linux-raspi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/2078525/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2038087] Re: [FFe] flash-kernel displays wrong "selected" DTB on various Pi models
Turns out we'll need this fix (minus the 5B entries) in Jammy as well. The cause of this is why I didn't notice LP: #2078525 until jammy users started upgrading to noble. The fix there will also be required when this is backported so they should be combined for jammy at least. ** Also affects: flash-kernel (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: flash-kernel (Ubuntu Jammy) Status: New => Incomplete ** Changed in: flash-kernel (Ubuntu Jammy) Status: Incomplete => Confirmed ** Changed in: flash-kernel (Ubuntu Jammy) Assignee: (unassigned) => Dave Jones (waveform) ** Changed in: flash-kernel (Ubuntu Jammy) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2038087 Title: [FFe] flash-kernel displays wrong "selected" DTB on various Pi models To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/2038087/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078525] Re: [SRU] zero-2-w.dtb does not exist in arm64 variant of linux-raspi
This may also need fixing on oracular. Theoretically there could still be a jammy kernel hanging around after jammy->noble->oracular (it *shouldn't* happen under normal circumstances where there should at a maximum be the running kernel, last stable, and current stable installed -- but there may well be edge cases). ** Changed in: flash-kernel (Ubuntu) Status: Invalid => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078525 Title: [SRU] zero-2-w.dtb does not exist in arm64 variant of linux-raspi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/2078525/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066885] Re: On Pi desktop, numerous reports of lack of landlock supported ABI
I'm going to add linux-raspi as affected here given this is (at least partially) down to a linux-raspi configuration difference. Kernel team: is there a reason landlock is disabled in the Pi kernel? Seems to work happily on a Pi 5, but perhaps there was some incompatibility with earlier models? ** Also affects: linux-raspi (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2066885 Title: On Pi desktop, numerous reports of lack of landlock supported ABI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2066885/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066885] Re: On Pi desktop, numerous reports of lack of landlock supported ABI
Nice! Looks like this is a difference between the Ubuntu PC kernel's configuration and the Ubuntu Pi kernel's configuration. On a PC: CONFIG_LSM="landlock,lockdown,yama,integrity,apparmor" On a Pi: CONFIG_LSM="yama,integrity,apparmor" Adding "lsm=landlock,lockdown,yama,integrity,apparmor" to /boot/firmware/cmdline.txt did enable landlock successfully on a subsequent boot, and the messages mentioned in the description above do disappear. However, now touching a file in the home-directory leads to the following in the journal: Sep 10 10:36:00 kermit tracker-miner-fs-3[5442]: (tracker-extract-3:5442): GLib-GIO-WARNING **: 10:36:00.310: Error creating IO channel for /proc/self/mountinfo: Invalid argument (g-io-error-quark, 13) Sep 10 10:36:00 kermit tracker-miner-fs-3[5442]: (tracker-extract-3:5442): GLib-WARNING **: 10:36:00.361: getpwuid_r(): failed due to unknown user id (1000) Sep 10 10:36:43 kermit tracker-miner-fs-3[5494]: (tracker-extract-3:5494): GLib-GIO-WARNING **: 10:36:43.582: Error creating IO channel for /proc/self/mountinfo: Invalid argument (g-io-error-quark, 13) Sep 10 10:36:43 kermit tracker-miner-fs-3[5494]: (tracker-extract-3:5494): GLib-WARNING **: 10:36:43.631: getpwuid_r(): failed due to unknown user id (1000) However, I note this is on my rather customized desktop development Pi, and needs replicating on the bare Pi desktop image. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2066885 Title: On Pi desktop, numerous reports of lack of landlock supported ABI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2066885/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2075505] Re: Add distribution-gpg-keys 1.104+ds-2 to noble
Reviewing the status of this during a patch pilot shift: All parties
seem agreed the packaging is reasonable. AFAICT the main objection
raised on the mailing list ("who will commit to maintain this, including
SRUs/security updates?"), is answered ("[Luca is] willing to maintain
these packages for Ubuntu releases").
Is there any further reason this can't be uploaded at this point?
I'm hesitant to "just upload it" without hearing someone from the SRU
team state that the consensus requested has been reached, but equally I
don't see any further unanswered objections on the mailing list thread
(or here).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2075505
Title:
Add distribution-gpg-keys 1.104+ds-2 to noble
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/distribution-gpg-keys/+bug/2075505/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078525] Re: [SRU] zero-2-w.dtb does not exist in arm64 variant of linux-raspi
** Tags added: foundations-todo -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078525 Title: [SRU] zero-2-w.dtb does not exist in arm64 variant of linux-raspi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/2078525/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2073609] Re: [needs-packaging] openjdk-17-crac
Looks like this was uploaded by Vladimir and has migrated to the release pocket. Setting to Fix Released. ** Changed in: ubuntu Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2073609 Title: [needs-packaging] openjdk-17-crac To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2073609/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2073612] Re: [needs-packaging] openjdk-21-crac
Looks like this was uploaded by Vladimir and has migrated to the release pocket. Setting to Fix Released. ** Changed in: ubuntu Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2073612 Title: [needs-packaging] openjdk-21-crac To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2073612/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065408] Re: growroot-almost should be inhibitable from boot partition
Since noble .1 and oracular, both desktop and server images now use cloud-init so theoretically this should be simple. However, I suspect the growroot-almost service on the desktop may interfere with this. Need to double-check what happens when cloud-init's growpart:off setting is used. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065408 Title: growroot-almost should be inhibitable from boot partition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-raspi-settings/+bug/2065408/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2076899] Re: [SRU] Missing runtime dependency on six
Ran test plan locally with released and proposed versions, proposed passed as expected. ** Tags removed: verification-needed-noble ** Tags added: verification-done-noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2076899 Title: [SRU] Missing runtime dependency on six To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-certbot-dns-gandi/+bug/2076899/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2070443] Re: SRU: Fix critical regression in Mercurial 6.7.x < 6.7.4
Urgh ... one of the required patches includes a binary for the test
suite. So, that's going to be fun to include. However, I don't see any
(simple) way around it given current versions of mercurial apparently
don't even produce the type of changelog necessary to demonstrate the
corruption.
** Description changed:
+ [ Impact ]
+
+ The version of mercurial currently in noble includes a serious
+ regression that is capable of corrupting a repository.
+
+ [ Test Plan ]
+
+ This utilizes the inlined changelog example from the test suite because
+ current versions of mercurial do not produce inlined changelogs, hence
+ this is the simplest means of verifying the fix.
+
+ On a fully updated noble instance:
+
+ * sudo apt install mercurial
+ * wget
https://repo.mercurial-scm.org/hg/raw-file/3cf9e52f5e27/tests/bundles/inlined-changelog.tar
+ * tar xf inlined-changelog.tar
+ * cd inlined-changelog
+ * cat > .hg/hgrc << EOF
+ [hooks]
+ pretxnclose=hg log -r tip -T "pre-txn tip rev: {rev}\n"
+ EOF
+ * touch foo
+ * hg add foo
+ * hg commit -m foo
+ * hg verify
+
+ At this point, hg verify should show "3 integrity errors encountered!"
+ in its output.
+
+ Now update to the version of mercurial in -proposed and repeat the
+ procedure above. This time, hg verify should output no indications of
+ corruption.
+
+ [ Regression Potential ]
+
+ The patches included in the upload are only those required to fix the
+ regression, and to handle compatibility with Python 3.12.5 (see LP:
+ #2076152). The patches include a good test suite, parts of which are
+ referenced in the test plan above which includes before and after
+ versions to demonstrate we are actually fixing something. The patches
+ are directly from upstream and already incorporated into future versions
+ (which already exist in the development series).
+
+ Regressions are still possible, but the comprehensive test suite
+ included in the package, and the test plan above, should give us some
+ confidence.
+
+ [ Original Description ]
+
From mailing list mercurial-packag...@mercurial-scm.org:
Hello all,
Monday evening we got a report from a user about a critical bug that can
destroy the changelog of repositories. The bug is in Mercurial 6.7 only
and affects repositories with low number of revisions that currently
have an inlined changelog and are configured with some pretxn hooks.
We will try yank releases 6.7.1, 6.7.2 and 6.7.3 from Pypi as soon as
possible and have published a 6.7.4 that addresses this issue. Since
this is the packaging list, I urge you to also remove those versions
from your package builds and switch to 6.7.4.
You can find more info in the release notes and the changesets
mentioned:
https://wiki.mercurial-scm.org/Release6.7
If you were affected by this bug, there is a chance that you can recover your
lost index by restoring it from undo.backup.00changelog.i.bck.
Thank you and sorry for the trouble,
Raphaël
Please update package soon as possible!
Affected: Ubuntu 24.04+
These issues are fixed in 24.10.
SRU: We backport the 6.7.4 release to 24.04.
- * SRU: LP: #2076152
- * Backport the upstream .3 and .4 bug fix releases to 24.04 LTS.
- LP: #2070443.
- * Add threading and _weakrefset to the list of modules which can't be
- lazy imported. Fixes startup in Python 3.12.5 and 3.13.0rc1.
- * Skip test for hg serve profiling, broken with python 3.12.
- * Adjust test-lfs-serve-access.t expected output to account to new
- variation.
+ * SRU: LP: #2076152
+ * Backport the upstream .3 and .4 bug fix releases to 24.04 LTS.
+ LP: #2070443.
+ * Add threading and _weakrefset to the list of modules which can't be
+ lazy imported. Fixes startup in Python 3.12.5 and 3.13.0rc1.
+ * Skip test for hg serve profiling, broken with python 3.12.
+ * Adjust test-lfs-serve-access.t expected output to account to new
+ variation.
All changes in the packaging are already in 24.10.
Validation: the package builds (succeeding all tests), and the autopkg
tests succeed).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2070443
Title:
SRU: Fix critical regression in Mercurial 6.7.x < 6.7.4
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mercurial/+bug/2070443/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2076152] Re: SRU: add threading to the list of modules which cannot be lazy imported
** Changed in: mercurial (Ubuntu Noble) Assignee: (unassigned) => Dave Jones (waveform) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2076152 Title: SRU: add threading to the list of modules which cannot be lazy imported To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mercurial/+bug/2076152/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2070443] Re: SRU: Fix critical regression in Mercurial 6.7.x < 6.7.4
I'll take a look, and see if I can put a minimal patchset together. ** Changed in: mercurial (Ubuntu Noble) Assignee: (unassigned) => Dave Jones (waveform) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2070443 Title: SRU: Fix critical regression in Mercurial 6.7.x < 6.7.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mercurial/+bug/2070443/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2076152] Re: SRU: add threading to the list of modules which cannot be lazy imported
Oh, nevermind -- I see it, demandimport-threading.patch in the devel series. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2076152 Title: SRU: add threading to the list of modules which cannot be lazy imported To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mercurial/+bug/2076152/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2076152] Re: SRU: add threading to the list of modules which cannot be lazy imported
Is there a link to the Debian bug (or patch)? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2076152 Title: SRU: add threading to the list of modules which cannot be lazy imported To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mercurial/+bug/2076152/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078525] Re: [SRU] zero-2-w.dtb does not exist in arm64 variant of linux-raspi
Okay, good to know the workaround worked. Unfortunately this complicates things somewhat. I was hoping I could "simply" fix the jammy release of flash-kernel, but this could theoretically hit someone upgrading from jammy to noble when running the noble release of flash-kernel. The fix needs to handle the case that zero-2.dtb exists, but zero-2-w.dtb doesn't (the current issue), that both exist, or the potential future where zero-2.dtb *doesn't* exist but zero-2-w.dtb does. Hmmm ... may be time for a dtb probe script. ** Also affects: flash-kernel (Ubuntu Noble) Importance: Undecided Status: New ** Changed in: flash-kernel (Ubuntu Noble) Assignee: (unassigned) => Dave Jones (waveform) ** Changed in: flash-kernel (Ubuntu Noble) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078525 Title: [SRU] zero-2-w.dtb does not exist in arm64 variant of linux-raspi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/2078525/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065830] Re: package initramfs-tools 0.142ubuntu15.1 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1
*** This bug is a duplicate of bug 2078525 *** https://bugs.launchpad.net/bugs/2078525 ** This bug has been marked a duplicate of bug 2078525 [SRU] zero-2-w.dtb does not exist in arm64 variant of linux-raspi -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065830 Title: package initramfs-tools 0.142ubuntu15.1 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/2065830/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065831] Re: On upgrade to 24.04 on Pi Zero 2W, package plymouth 24.004.60-1ubuntu7 failed to install/upgrade: installed plymouth package post-installation script subprocess returned error exit s
*** This bug is a duplicate of bug 2078525 *** https://bugs.launchpad.net/bugs/2078525 ** This bug has been marked a duplicate of bug 2078525 [SRU] zero-2-w.dtb does not exist in arm64 variant of linux-raspi -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065831 Title: On upgrade to 24.04 on Pi Zero 2W, package plymouth 24.004.60-1ubuntu7 failed to install/upgrade: installed plymouth package post- installation script subprocess returned error exit status 1 [Installing into /boot/dtbs/5.15.0-1055-raspi/./bcm2710-rpi- zero-2-w.dtb ; cp: cannot stat '': No such file or directory] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/2065831/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2068834] Re: package plymouth 24.004.60-1ubuntu7 failed to install/upgrade: installed plymouth package post-installation script subprocess returned error exit status 1
*** This bug is a duplicate of bug 2078525 *** https://bugs.launchpad.net/bugs/2078525 ** This bug is no longer a duplicate of bug 2065831 On upgrade to 24.04 on Pi Zero 2W, package plymouth 24.004.60-1ubuntu7 failed to install/upgrade: installed plymouth package post-installation script subprocess returned error exit status 1 [Installing into /boot/dtbs/5.15.0-1055-raspi/./bcm2710-rpi-zero-2-w.dtb ; cp: cannot stat '': No such file or directory] ** This bug has been marked a duplicate of bug 2078525 [SRU] zero-2-w.dtb does not exist in arm64 variant of linux-raspi -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2068834 Title: package plymouth 24.004.60-1ubuntu7 failed to install/upgrade: installed plymouth package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/2068834/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2073835] Re: Default kernel commandline options on Raspberry Pi
Targetting this to focal (the last release where we used u-boot on the Pi images) and setting devel to fix-released (as later releases just use the cmdline.txt file for the Pi's bootloader). ** Also affects: flash-kernel (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: flash-kernel (Ubuntu Focal) Status: New => Confirmed ** Changed in: flash-kernel (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2073835 Title: Default kernel commandline options on Raspberry Pi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/2073835/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078524] Re: package initramfs-tools 0.142ubuntu25.1 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1
*** This bug is a duplicate of bug 2078525 *** https://bugs.launchpad.net/bugs/2078525 ** This bug has been marked a duplicate of bug 2078525 [SRU] zero-2-w.dtb does not exist in arm64 variant of linux-raspi -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078524 Title: package initramfs-tools 0.142ubuntu25.1 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/2078524/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078793] Re: gcalcli: uses python3-oauth2client
Tried this out the noble PPA this evening, but failed to get the authentication working. Specifically: following the guide at [1] everything went smoothly up until the "last part" of executing gcalcli with the generated client-id. At this point, gcalcli produced a URL to open. I needed to do this on another machine as the machine running gcalcli is a headless server with no GUI installed. I duly opened the URL on a desktop machine, authenticated as my user, allowed permissions, but then the browser attempted to navigate to a localhost:8080 URL which obviously failed. Looking on the headless server I could it had indeed opened up a local server to receive the request, but this naturally had failed at this point. My next attempt I tweaked the redirection URL to point to the headless server, but the google authentication step then complained this was an invalid redirection URL (I get the impression it *must* be localhost, which probably makes sense from a security standpoint). My last attempt, I tried opening the localhost:8080 URL on the headless server using elinks, hoping the system might be able to deal with a JS- less text-only browser, but no. Oh well, I should probably go and read up on how OAuth is meant to handle headless systems... [1]: https://github.com/insanum/gcalcli/blob/HEAD/docs/api-auth.md -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078793 Title: gcalcli: uses python3-oauth2client To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcalcli/+bug/2078793/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078525] Re: [SRU] zero-2-w.dtb does not exist in arm64 variant of linux-raspi
Argh, I'm a fool! Didn't spot I was looking at the wrong kernel version.
Though you're running the 6.8 kernel, and you've got the zero-2-w dtb
there, flash-kernel is failing when initramfs-tools is refreshing the
5.15 kernel! Can you check the output of:
ls /lib/firmware/5.15.0-1061-raspi/device-tree/broadcom/
I'm betting you *won't* see bcm2710-rpi-zero-2-w.dtb there, but that
bcm2710-rpi-zero-2.dtb is there. If that's the case, try:
sudo cp
/lib/firmware/5.15.0-1061-raspi/device-tree/broadcom/bcm2710-rpi-zero-2{,-w}.dtb
sudo apt -f install
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2078525
Title:
[SRU] zero-2-w.dtb does not exist in arm64 variant of linux-raspi
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/2078525/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2046250] Re: [FFe][needs-packaging] raspi-utils (replacement for raspberrypi-userland)
Test packages building in ppa:waveform/raspi-utils https://launchpad.net/~waveform/+archive/ubuntu/raspi-utils ** Description changed: - The raspberrypi-userland package is now deprecated upstream, with the - majority of the utilities (dtoverlay, dtmerge, vcgencmd, vclog, etc.) - moving to the raspi-utils package. We should include raspi-utils in - oracular with all the appropriate Breaks + Replaces bits to handle - replacing the existing package. + [ Impact ] + + The raspberrypi-userland package was deprecated upstream some time ago + (prior to noble in fact), with the majority of the utilities (dtoverlay, + dtmerge, vcgencmd, vclog, etc.) moving to the raspi-utils package. + Recent versions of rpi-eeprom-update (which we need to pull in to fix + other issues, e.g. LP: #2078806) now include functionality introduced + since the move to raspi-utils. + + We should include raspi-utils in oracular with all the appropriate + Breaks + Replaces bits to handle replacing the existing package. + + [ Test Plan ] + + * With EEPROM boot firmware from current Ubuntu: + + * Build the package in ppa:waveform/raspi-utils + * Test the function of the package on supported models. Specifically, on Pi 5, Pi 4, CM4, and at least one of the 2/3/3+ generation + * Especially: check vcgencmd, dtoverlay, dtparam still operate as expected as these are the major components used by other utilities + + * Update EEPROM boot firmware to current RaspiOS version and repeat + above tests. + + [ Regression Potential ] + + Given the nature of some of the utilities (e.g. low-level mailbox + communication in vcmailbox, device-tree overlay manipulation in + dtoverlay and dtparam), there is a reasonable risk that we may break + functionality by upgrading. However, these utilities tend to move in + step with the RPi firmware, and if we are updating that firmware, these + utilities should be updated too in order to minimize the risk of + regression. + + Nonetheless, the test plan should be followed on a wide variety of + models, and as much functionality should be tested as possible, with old + and new firmware to spot potential regressions. + + [ Addendum ] Note to self: don't forget to update the seeds ** Description changed: [ Impact ] + + URL: https://github.com/raspberrypi/utils + License: GPL-2 or BSD-3-Clause + Notes: The raspberrypi-userland package was deprecated upstream some time ago (prior to noble in fact), with the majority of the utilities (dtoverlay, dtmerge, vcgencmd, vclog, etc.) moving to the raspi-utils package. Recent versions of rpi-eeprom-update (which we need to pull in to fix other issues, e.g. LP: #2078806) now include functionality introduced since the move to raspi-utils. We should include raspi-utils in oracular with all the appropriate Breaks + Replaces bits to handle replacing the existing package. [ Test Plan ] * With EEPROM boot firmware from current Ubuntu: * Build the package in ppa:waveform/raspi-utils * Test the function of the package on supported models. Specifically, on Pi 5, Pi 4, CM4, and at least one of the 2/3/3+ generation * Especially: check vcgencmd, dtoverlay, dtparam still operate as expected as these are the major components used by other utilities * Update EEPROM boot firmware to current RaspiOS version and repeat above tests. [ Regression Potential ] Given the nature of some of the utilities (e.g. low-level mailbox communication in vcmailbox, device-tree overlay manipulation in dtoverlay and dtparam), there is a reasonable risk that we may break functionality by upgrading. However, these utilities tend to move in step with the RPi firmware, and if we are updating that firmware, these utilities should be updated too in order to minimize the risk of regression. Nonetheless, the test plan should be followed on a wide variety of models, and as much functionality should be tested as possible, with old and new firmware to spot potential regressions. [ Addendum ] Note to self: don't forget to update the seeds -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2046250 Title: [FFe][needs-packaging] raspi-utils (replacement for raspberrypi- userland) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/raspberrypi-userland/+bug/2046250/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2046250] Re: [needs-packaging] raspi-utils (replacement for raspberrypi-userland)
** Description changed: The raspberrypi-userland package is now deprecated upstream, with the majority of the utilities (dtoverlay, dtmerge, vcgencmd, vclog, etc.) moving to the raspi-utils package. We should include raspi-utils in - noble with all the appropriate Breaks + Replaces bits to handle + oracular with all the appropriate Breaks + Replaces bits to handle replacing the existing package. Note to self: don't forget to update the seeds ** Changed in: raspberrypi-userland (Ubuntu) Milestone: None => ubuntu-24.10 ** Summary changed: - [needs-packaging] raspi-utils (replacement for raspberrypi-userland) + [FFe][needs-packaging] raspi-utils (replacement for raspberrypi-userland) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2046250 Title: [FFe][needs-packaging] raspi-utils (replacement for raspberrypi- userland) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/raspberrypi-userland/+bug/2046250/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078806] [NEW] Support WD SN550 NVMe boot
Public bug reported: A bump to the rpi-eeprom after 2024-01-24 is required to support the Western Digital SN550 series of NVMe drives for booting on the Pi 5. The boot firmware (linux-firmware-raspi) may also require a bump for this. See https://forums.raspberrypi.com/viewtopic.php?t=364327 for full details. This should be uploaded prior to the hardware enablement freeze (Sept 16th). ** Affects: rpi-eeprom (Ubuntu) Importance: Undecided Assignee: Dave Jones (waveform) Status: Confirmed ** Changed in: rpi-eeprom (Ubuntu) Status: New => Confirmed ** Changed in: rpi-eeprom (Ubuntu) Assignee: (unassigned) => Dave Jones (waveform) ** Changed in: rpi-eeprom (Ubuntu) Milestone: None => ubuntu-24.10 ** Description changed: A bump to the rpi-eeprom after 2024-01-24 is required to support the Western Digital SN550 series of NVMe drives for booting on the Pi 5. The boot firmware (linux-firmware-raspi) may also require a bump for this. + + This should be uploaded prior to the hardware enablement freeze (Sept + 16th). ** Description changed: A bump to the rpi-eeprom after 2024-01-24 is required to support the Western Digital SN550 series of NVMe drives for booting on the Pi 5. The boot firmware (linux-firmware-raspi) may also require a bump for this. + See https://forums.raspberrypi.com/viewtopic.php?t=364327 for full + details. This should be uploaded prior to the hardware enablement freeze (Sept 16th). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078806 Title: Support WD SN550 NVMe boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rpi-eeprom/+bug/2078806/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078395] Re: [SRU] Add RSA3072 support to jammy
** Also affects: u-boot (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: u-boot (Ubuntu Jammy) Assignee: (unassigned) => Dave Jones (waveform) ** Changed in: u-boot (Ubuntu Jammy) Status: New => Confirmed ** Changed in: u-boot (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078395 Title: [SRU] Add RSA3072 support to jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/u-boot/+bug/2078395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078750] [NEW] Source build fails
Public bug reported: Source package build fails due to missing bash_completion dh module. dh- sequence-bash-completion should be in Build-Depends, not Build-Depends- Indep (which is not considered for source package builds). ** Affects: mpd-sima (Ubuntu) Importance: Undecided Assignee: Dave Jones (waveform) Status: Confirmed ** Changed in: mpd-sima (Ubuntu) Status: New => Confirmed ** Changed in: mpd-sima (Ubuntu) Assignee: (unassigned) => Dave Jones (waveform) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078750 Title: Source build fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mpd-sima/+bug/2078750/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078749] [NEW] Source build fails
Public bug reported: Source package build fails due to missing python dh module. dh-python should be in Build-Depends, not Build-Depends-Indep (which is not considered for source package builds). ** Affects: pagekite (Ubuntu) Importance: Undecided Assignee: Dave Jones (waveform) Status: Confirmed ** Changed in: pagekite (Ubuntu) Status: New => Confirmed ** Changed in: pagekite (Ubuntu) Assignee: (unassigned) => Dave Jones (waveform) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078749 Title: Source build fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pagekite/+bug/2078749/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078748] Re: Source build fails
(originally discovered during work for LP: #2075337) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078748 Title: Source build fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pyro5/+bug/2078748/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078748] [NEW] Source build fails
Public bug reported: Source package build fails due to missing python and sphinx dh modules. dh-python and python3-sphinx should be in Build-Depends, not Build- Depends-Indep (which is not considered for source package builds). ** Affects: pyro5 (Ubuntu) Importance: Undecided Assignee: Dave Jones (waveform) Status: Confirmed ** Changed in: pyro5 (Ubuntu) Status: New => Confirmed ** Changed in: pyro5 (Ubuntu) Assignee: (unassigned) => Dave Jones (waveform) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078748 Title: Source build fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pyro5/+bug/2078748/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2075337] Re: [SRU] py3clean fails when using alternate character set
@mfo re: comment 91 on nordugrid: I've re-uploaded with the (horrible :) spacing restored. The Breaks being against nordugrid-arc-arex and nothing else is indeed deliberate and correct. The bug only affects those binary packages which 1) contain python modules (which this package does) and 2) are affected by diversions (which this package is). The python3-nordugrid package satisfies the first condition, but isn't affected by diversions so it isn't affected. What may be confusing is that it isn't the only package to contain python modules in the suite. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2075337 Title: [SRU] py3clean fails when using alternate character set To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2075337/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078742] Re: Fix FTBFS on python 3.12
** Changed in: vanguards (Ubuntu Noble) Status: New => Confirmed ** Changed in: vanguards (Ubuntu Noble) Assignee: (unassigned) => Dave Jones (waveform) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078742 Title: Fix FTBFS on python 3.12 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vanguards/+bug/2078742/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078742] Re: Fix FTBFS on python 3.12
** Also affects: vanguards (Ubuntu Noble) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078742 Title: Fix FTBFS on python 3.12 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vanguards/+bug/2078742/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078742] [NEW] Fix FTBFS on python 3.12
Public bug reported: vanguards is incompatible with Python 3.12 which removes the deprecated SafeConfigParser class. ** Affects: vanguards (Ubuntu) Importance: Undecided Assignee: Dave Jones (waveform) Status: Confirmed ** Affects: vanguards (Ubuntu Noble) Importance: Undecided Status: New ** Changed in: vanguards (Ubuntu) Status: New => Confirmed ** Changed in: vanguards (Ubuntu) Assignee: (unassigned) => Dave Jones (waveform) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078742 Title: Fix FTBFS on python 3.12 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vanguards/+bug/2078742/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078525] Re: [SRU] zero-2-w.dtb does not exist in arm64 variant of linux-raspi
In the jammy linux-raspi kernel on aarch64/arm64, the bcm2710-rpi-
zero-2-w.dtb filename does not exist; instead it's called bcm2710-rpi-
zero-2.dtb. In the armhf variant of the kernel both names exist (and are
identical copies of each other).
Although technically this would appear to be kernel packaging issue,
given there is a name accessible to both architectural variants it's
going to be simpler to workaround in flash-kernel by using that common
name. In the meantime, the following workaround should permit flash-
kernel to proceed:
sudo cp /lib/firmware/$(uname
-r)/device-tree/broadcom/bcm2710-rpi-zero-2{,-w}.dtb
sudo apt -f install
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2078525
Title:
[SRU] zero-2-w.dtb does not exist in arm64 variant of linux-raspi
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/2078525/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078525] Re: package plymouth 24.004.60-1ubuntu7 failed to install/upgrade: installed plymouth package post-installation script subprocess returned error exit status 1
** Also affects: flash-kernel (Ubuntu) Importance: Undecided Status: New ** No longer affects: plymouth (Ubuntu) ** Also affects: flash-kernel (Ubuntu Jammy) Importance: Undecided Status: New ** Summary changed: - package plymouth 24.004.60-1ubuntu7 failed to install/upgrade: installed plymouth package post-installation script subprocess returned error exit status 1 + zero-2-w.dtb does not exist in arm64 variant of linux-raspi ** Changed in: flash-kernel (Ubuntu) Status: New => Invalid ** Changed in: flash-kernel (Ubuntu Jammy) Assignee: (unassigned) => Dave Jones (waveform) ** Changed in: flash-kernel (Ubuntu Jammy) Status: New => Confirmed ** Summary changed: - zero-2-w.dtb does not exist in arm64 variant of linux-raspi + [SRU] zero-2-w.dtb does not exist in arm64 variant of linux-raspi -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078525 Title: [SRU] zero-2-w.dtb does not exist in arm64 variant of linux-raspi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/2078525/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901057] Re: nut-monitor is missing
It appears nut-monitor was re-instated in noble. I haven't actually tested it works yet (and won't be able to test it until next week), but it's possible this can be set to Fix Released (if someone can check it before then?) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901057 Title: nut-monitor is missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/1901057/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 920844] Re: nut-client is missing /etc/init.d/ups-monitor for MODE=netclient (is in nut-server)
nut 2.6.4 (available in focal onwards) uses systemd units, including nut-monitor.service for MODE=netclient -- setting to "Fix Released" as I think this was resolved all the way back in focal (or possibly earlier). ** Changed in: nut (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/920844 Title: nut-client is missing /etc/init.d/ups-monitor for MODE=netclient (is in nut-server) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/920844/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1512603] Re: nut-monitor systemd service is absent in nut-client package since Ubuntu vivid
It seems this was fixed as far back as focal (at least, having checked my focal, jammy, and noble systems which use UPS' they all have valid nut-monitor.service units). Setting to "Fix Released"; if this is still an issue on a supported release, please feel free to re-open but do specify the release. ** Changed in: nut (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1512603 Title: nut-monitor systemd service is absent in nut-client package since Ubuntu vivid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/1512603/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2076909] [NEW] Updated docutils breaks reStructuredText tests
Public bug reported: Newer docutils breaks two reStructuredText tests in ruby-gitlab-markup. Generated HTML needs updating to match produced output. ** Affects: ruby-gitlab-markup (Ubuntu) Importance: Undecided Assignee: Dave Jones (waveform) Status: Confirmed ** Changed in: ruby-gitlab-markup (Ubuntu) Assignee: (unassigned) => Dave Jones (waveform) ** Changed in: ruby-gitlab-markup (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2076909 Title: Updated docutils breaks reStructuredText tests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ruby-gitlab-markup/+bug/2076909/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069827] Re: [SRU] Place cloud-init seed on boot partition for desktop images
** Description changed: + [ Impact ] + + The noble .1 release is switching the initial desktop setup wizard from + oem-config (source ubiquity) to gnome-initial-setup. The latter requires + that no user accounts exist on first boot. However, cloud-init (included + since noble) is creating a default "ubuntu" user on these images. The + gadget has been updated to include configuration for cloud-init that + will prevent user creation (as on oracular), but this configuration will + not be read without cloud-init knowing to look on the boot partition for + its seed. + + On server images, 99-fake-cloud.cfg is included (via ubuntu-raspi- + settings-server) to point cloud-init at this location. This + configuration file needs to move to ubuntu-raspi-settings (applicable to + both server and desktop images) as it already has on oracular. + + [ Test Plan ] + + For initial boot of desktop images: + * Current noble daily desktop images for Raspberry Pi fail to boot to gnome-initial-setup + * Checking /etc/passwd on the image post-first-boot reveals presence of "ubuntu" user + * Once new dailies with this change are generated, attempt to boot them + * Observe that gnome-initial-setup starts successfully + + For upgrades of existing systems: + * Boot ubuntu server for raspi (noble) + * Upgrade to proposed ubuntu-raspi-settings package(s) + * Observe /etc/cloud/cloud.cfg.d/99-fake-cloud.cfg is unchanged + * Check ownership has moved to ubuntu-raspi-settings + * Check reboot operates + + * Boot ubuntu desktop for raspi (noble) + * Observe /etc/cloud/cloud.cfg.d/99-fake-cloud.cfg does not exist + * Upgrade to proposed ubuntu-raspi-settings package(s) + * Observe /etc/cloud/cloud.cfg.d/99-fake-cloud.cfg has appeared + * Check reboot operates + + [ Where Things Can Go Wrong ] + + For server users, there should ultimately be no change to their system. + The change should merely move the "ownership" of + /etc/cloud/cloud.cfg.d/99-fake-cloud.cfg from ubuntu-raspi-settings- + server to ubuntu-raspi-settings. Nonetheless, configuration file + movements are subtle things that need careful handling and this change + should be tested on existing installs too (hence the inclusion in the + test plan above). + + For desktop users, this change should cause + /etc/cloud/cloud.cfg.d/99-fake-cloud.cfg to appear. Again, this + *shouldn't* affect the system as the only configuration present matters + on first boot only. Still, the change should be tested on existing + installs (hence the test plan above). + + [ Original Description ] + The Ubuntu Desktop for Raspberry Pi images include cloud-init since noble. The cloud-init seed is redirected to the (FAT formatted) boot partition on the Ubuntu Server for Raspberry Pi images, and for consistency and ease of use, this should be replicated for the desktop images too. We could add 99-fake-cloud.cfg to ubuntu-raspi-settings-desktop as well as ubuntu-raspi-settings-server (where it currently resides) which would allow us to remove it again in future, if that becomes necessary. However, that would necessarily create a conflict between both packages and it's conceivable that some may wish to install both (for desktop-on- server type installs). Therefore it is probably best to simply move 99-fake-cloud.cfg over to the common ubuntu-raspi-settings package, and add Breaks/Replaces to ensure the configuration is moved appropriately by dpkg. Note to self: the gadget will need updating to include the cloud-init seed on the boot partition of the desktop images. However, the seed must be *different* (don't auto-create users), and must not include network- config (as the desktop settings include a network-manager override). ** Changed in: ubuntu-raspi-settings (Ubuntu Noble) Assignee: (unassigned) => Dave Jones (waveform) ** Changed in: ubuntu-raspi-settings (Ubuntu Noble) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069827 Title: [SRU] Place cloud-init seed on boot partition for desktop images To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-raspi-settings/+bug/2069827/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069827] Re: Place cloud-init seed on boot partition for desktop images
** Also affects: ubuntu-raspi-settings (Ubuntu Noble) Importance: Undecided Status: New ** Summary changed: - Place cloud-init seed on boot partition for desktop images + [SRU] Place cloud-init seed on boot partition for desktop images -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069827 Title: [SRU] Place cloud-init seed on boot partition for desktop images To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-raspi-settings/+bug/2069827/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2076899] Re: [SRU] Missing runtime dependency on six
Proposed change upstream: https://salsa.debian.org/letsencrypt- team/certbot/certbot-dns-gandi/-/merge_requests/3 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2076899 Title: [SRU] Missing runtime dependency on six To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-certbot-dns-gandi/+bug/2076899/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2076899] Re: Missing runtime dependency on six
** Patch added: "noble.debdiff" https://bugs.launchpad.net/ubuntu/+source/python-certbot-dns-gandi/+bug/2076899/+attachment/5805404/+files/noble.debdiff ** Also affects: python-certbot-dns-gandi (Ubuntu Noble) Importance: Undecided Status: New ** Summary changed: - Missing runtime dependency on six + [SRU] Missing runtime dependency on six ** Description changed: + [ Impact ] + A missing runtime dependency on python3-six is causing noble and oracular autopkgtests to fail (it's probably missing from earlier series too, but wasn't noticed as some other dependency of certbot probably pulled it in implicitly). Will attach noble and oracular debdiffs for - sponsorship + sponsorship. + + This presumably also breaks runtime on some systems which don't + coincidentally have python3-six installed. + + [ Test Plan ] + + * Run autopkgtests on current version of package + * Observe failure due to missing python3-six module + * Run autopkgtests on proposed version of package + * Observe success + + [ Where Things Can Go Wrong ] + + The change simply adds a runtime dependency on python3-six, no changes + to the code are made and the dependency is manifestly required or the + certbot plugin cannot be imported. Presumably no-one's noticed this + until now because python3-six is so commonly installed (for various + things) that it's extremely rare for this to actually break in practice, + but it certainly breaks in the minimal autopkgtest environment. ** Changed in: python-certbot-dns-gandi (Ubuntu) Status: New => Confirmed ** Changed in: python-certbot-dns-gandi (Ubuntu Noble) Status: New => Confirmed ** Changed in: python-certbot-dns-gandi (Ubuntu) Assignee: (unassigned) => Dave Jones (waveform) ** Changed in: python-certbot-dns-gandi (Ubuntu Noble) Assignee: (unassigned) => Dave Jones (waveform) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2076899 Title: [SRU] Missing runtime dependency on six To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-certbot-dns-gandi/+bug/2076899/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2076899] [NEW] [SRU] Missing runtime dependency on six
Public bug reported: [ Impact ] A missing runtime dependency on python3-six is causing noble and oracular autopkgtests to fail (it's probably missing from earlier series too, but wasn't noticed as some other dependency of certbot probably pulled it in implicitly). Will attach noble and oracular debdiffs for sponsorship. This presumably also breaks runtime on some systems which don't coincidentally have python3-six installed. [ Test Plan ] * Run autopkgtests on current version of package * Observe failure due to missing python3-six module * Run autopkgtests on proposed version of package * Observe success [ Where Things Can Go Wrong ] The change simply adds a runtime dependency on python3-six, no changes to the code are made and the dependency is manifestly required or the certbot plugin cannot be imported. Presumably no-one's noticed this until now because python3-six is so commonly installed (for various things) that it's extremely rare for this to actually break in practice, but it certainly breaks in the minimal autopkgtest environment. ** Affects: python-certbot-dns-gandi (Ubuntu) Importance: Undecided Assignee: Dave Jones (waveform) Status: Confirmed ** Affects: python-certbot-dns-gandi (Ubuntu Noble) Importance: Undecided Assignee: Dave Jones (waveform) Status: Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2076899 Title: [SRU] Missing runtime dependency on six To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-certbot-dns-gandi/+bug/2076899/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2076899] Re: Missing runtime dependency on six
** Patch added: "oracular.debdiff" https://bugs.launchpad.net/ubuntu/+source/python-certbot-dns-gandi/+bug/2076899/+attachment/5805403/+files/oracular.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2076899 Title: [SRU] Missing runtime dependency on six To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-certbot-dns-gandi/+bug/2076899/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2075337] Re: [SRU] py3clean fails when using alternate character set
** Tags added: foundations-todo -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2075337 Title: [SRU] py3clean fails when using alternate character set To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2075337/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2075337] Re: [SRU] py3clean fails when using alternate character set
Marking dh_python as invalid; it was added originally on the theory that we may have needed to patch the prerm fallback but this has thankfully turned out to be unnecessary. ** Description changed: + [ 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. + + [ Test Plan ] + + Where $series is jammy or noble as appropriate, and $package is the name + of the affected package being SRU'd: + + $ lxc launch ubuntu:$series py3clean-test + $ lxc shell py3clean-test + # locale-gen fr_FR + Generating locales (this might take a while)... + fr_FR.ISO-8859-1... done + Generation complete. + # update-locale LANG=fr_FR + # exit + # adjust terminal to ISO-8859-1 + $ lxc shell py3clean-test + # apt update && apt install --reinstall $package + + With the current version of python3-defaults in jammy and noble this + should fail at the final apt install --reinstall step. With the proposed + version, it should succeed. + + [ What Could Go Wrong? ] + + The potential for regression is low since the python3-defaults changes + are minimal and have been reasonably tested, and the only change to + affected packages is the addition of a Breaks clause (i.e. the content + of the packages are unaffected, just the meta-data). + + The major cause for concern is that we are not 100% certain that the + Breaks addition is sufficient to fix this. The Debian policy manual is + ambiguous as to whether Breaks implies that the fixed package must be + unpacked *before* the prerm maintscript of the package it breaks is + executed; the policy manual mentions this must happen before the + "unpack" phase, but prerm scripts run *before* the unpack phase. + However, in all experiments run so far, this did indeed resolve the + problem. + + Still, as an extra hedge against failure here, we intend that the + python3-defaults SRU is released ASAP, and that we then delay a week to + allow it to propagate before releasing SRUs for the affected packages. + + [ Original Description ] + We noticed this in bug 2060769 but think it is a separate issue. dh_python3 is putting a py3clean invocation into package prerm maintainer scripts. When that runs, it explodes if the system character set is for example ISO-8859-1. This appears to affect every package for which dh_python3 has inserted a call to py3clean into the package prerm. python3-minimal 3.12.3-0ubuntu1 In this reproducer, cloud-init is at 24.1.3-0ubuntu3.3. Steps to reproduce: $ lxc launch ubuntu:noble rbasak-pro-l8n $ lxc shell rbasak-pro-l8n # locale-gen fr_FR Generating locales (this might take a while)... - fr_FR.ISO-8859-1... done + fr_FR.ISO-8859-1... done Generation complete. # update-locale LANG=fr_FR # exit # adjust terminal to ISO-8859-1 $ lxc shell rbasak-pro-l8n # apt update && apt install --reinstall cloud-init Expected results: success Actual results: Lecture des listes de paquets... Fait Construction de l'arbre des dépendances... Fait - Lecture des informations d'état... Fait + Lecture des informations d'état... Fait 0 mis à jour, 0 nouvellement installés, 1 réinstallés, 0 à enlever et 5 non mis à jour. Il est nécessaire de prendre 598 ko dans les archives. Après cette opération, 0 o d'espace disque supplémentaires seront utilisés. Réception de :1 http://arc
[Bug 2075337] Re: [SRU] py3clean fails when using alternate character set
** Summary changed: - py3clean fails when using alternate character set + [SRU] py3clean fails when using alternate character set -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2075337 Title: [SRU] py3clean fails when using alternate character set To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2075337/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2075337] Re: py3clean fails when using alternate character set
** Patch added: "lp2075337-noble.debdiff" https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/2075337/+attachment/5803632/+files/lp2075337-noble.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2075337 Title: py3clean fails when using alternate character set To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dh-python/+bug/2075337/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2075337] Re: py3clean fails when using alternate character set
** Patch added: "lp2075337-jammy.debdiff" https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/2075337/+attachment/5803631/+files/lp2075337-jammy.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2075337 Title: py3clean fails when using alternate character set To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dh-python/+bug/2075337/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2075337] Re: py3clean fails when using alternate character set
Attaching debdiffs for sponsorship in noble and jammy. For the purposes of review, the jammy diff does include one additional change to avoid using shell=True on the invocation of dpkg -L. This can be excised if necessary, but I really didn't want to leave something that ultimately runs as root doing string interpolation and then calling something via the shell, when I don't have to! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2075337 Title: py3clean fails when using alternate character set To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dh-python/+bug/2075337/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064688] Re: Merge nbd from Debian unstable for oracular
The fix for LP: #2060745 was incorporated into version 1:3.26.1-4 which is now in unstable, so this can probably just be turned into a sync request at this point. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064688 Title: Merge nbd from Debian unstable for oracular To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nbd/+bug/2064688/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054092] Re: Add support for FIT images to rpi config
Updated proposed configuration to remove already-default values ** Description changed: Support for signed FIT images has been requested; the following config items should be enabled for the rpi 3 and 4 configurations (in both armhf and arm64): - CONFIG_MULTI_DTB_FIT_UNCOMPRESS_SZ=0x8000 CONFIG_FIT=y - CONFIG_FIT_EXTERNAL_OFFSET=0x0 - CONFIG_FIT_FULL_CHECK=y + CONFIG_FIT_SIGNATURE=y CONFIG_FIT_VERBOSE=y CONFIG_FIT_PRINT=y CONFIG_TOOLS_FIT=y - CONFIG_TOOLS_FIT_FULL_CHECK=y + CONFIG_TOOLS_FIT_SIGNATURE=y + CONFIG_TOOLS_FIT_VERBOSE=y CONFIG_TOOLS_FIT_PRINT=y - CONFIG_TOOLS_FIT_RSASSA_PSS=y - CONFIG_TOOLS_FIT_SIGNATURE=y - CONFIG_TOOLS_FIT_SIGNATURE_MAX_SIZE=0x1000 - CONFIG_TOOLS_FIT_VERBOSE=y CONFIG_ZSTD=y Check this doesn't affect core 24 images (there will inevitably be a size increase as a result of enabling more flags; this is probably a good time to unseed u-boot on the pi images for oracular). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054092 Title: Add support for FIT images to rpi config To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/u-boot/+bug/2054092/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054092] Re: Add support for FIT images to rpi config
** Description changed: Support for signed FIT images has been requested; the following config items should be enabled for the rpi 3 and 4 configurations (in both armhf and arm64): CONFIG_MULTI_DTB_FIT_UNCOMPRESS_SZ=0x8000 CONFIG_FIT=y CONFIG_FIT_EXTERNAL_OFFSET=0x0 CONFIG_FIT_FULL_CHECK=y CONFIG_FIT_VERBOSE=y CONFIG_FIT_PRINT=y CONFIG_TOOLS_FIT=y CONFIG_TOOLS_FIT_FULL_CHECK=y CONFIG_TOOLS_FIT_PRINT=y CONFIG_TOOLS_FIT_RSASSA_PSS=y CONFIG_TOOLS_FIT_SIGNATURE=y CONFIG_TOOLS_FIT_SIGNATURE_MAX_SIZE=0x1000 CONFIG_TOOLS_FIT_VERBOSE=y CONFIG_ZSTD=y - Check this doesn't affect core images, and focal on classic (there will - inevitably be a size increase as a result of enabling more flags; this - is probably a good time to unseed u-boot on the pi images for noble). + Check this doesn't affect core 24 images (there will inevitably be a + size increase as a result of enabling more flags; this is probably a + good time to unseed u-boot on the pi images for oracular). ** Also affects: u-boot (Ubuntu Noble) Importance: Undecided Status: New ** Changed in: u-boot (Ubuntu Noble) Assignee: (unassigned) => Dave Jones (waveform) ** Changed in: u-boot (Ubuntu) Status: New => Confirmed ** Changed in: u-boot (Ubuntu Noble) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054092 Title: Add support for FIT images to rpi config To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/u-boot/+bug/2054092/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2075337] Re: py3clean fails when using alternate character set
Attaching debdiff for proposed changes to python3-minimal in noble ** Patch added: "noble.debdiff" https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/2075337/+attachment/5802639/+files/noble.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2075337 Title: py3clean fails when using alternate character set To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dh-python/+bug/2075337/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2075337] Re: py3clean fails when using alternate character set
Having spent some time digging into this (at the request of the SRU team), I'll summarise my findings: Firstly, the analysis is correct: py3clean is ultimately the issue; packages that both use py3clean and have diversions are affected (diversions are the only circumstances that produce localised output in dpkg-query -L). Secondly, the proposed fix upstream is also fine, though personally I'd also like to see the stdout decode use errors='replace' (there's no good reason to fail here in the event of dodgy UTF-8 in a translation, for instance). I'll attach debdiffs for noble and oracular to illustrate my intent. Thirdly, the proposed workaround for affected packages: using Breaks on python3-minimal with a version strictly less than the fixed version also appears to be sufficient (in all the cases I've tested this causes python3-minimal to be at least unpacked prior to the prerm script of the affected package being executed). So, if the fix for python3-minimal can be uploaded, it simply remains to determine which packages are affected. This is where things get tricky. Benjamin's efforts are much appreciated here, and will likely be decisive in light of the following: determining which packages use py3clean is relatively simple (pretty much anything that installs a python module). Determining which packages have diversions turns out to be extremely difficult. It's not enough to detect if a package *itself* uses dpkg-divert. Take the cloud-init case where this was first detected: the postinst calls dpkg-divert but only to *remove* an old diversion. The diversion that actually affects this package comes from usr-merge (because cloud-init still has files under the unmerged paths for various reasons). In essence, any package (foo) can cause a diversion in another package (bar) without the affected package (bar) showing any sign of this in either its source or its binary artefacts. Further, the diversion may or may not affect the package (bar) as the source of the diversion (foo) may be optional to install. Hence, there are two approaches. The thorough, but likely impractical, approach would be to apply the "Breaks" fix to all packages using py3clean: i.e. all packages that install python modules. Then there's (Benjamin's) empirical approach: attempt to install everything from the former set and see what fails. As noted above, this cannot guarantee correctness as we cannot be certain that all packages that may divert files in our target package are installed, but in practice it's probably (hopefully!) "good enough" given the rarity of diversions and avoids updates to (presumably) several thousand packages. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2075337 Title: py3clean fails when using alternate character set To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dh-python/+bug/2075337/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2075337] Re: py3clean fails when using alternate character set
Attaching debdiff for proposed changes to python3-minimal in oracular ** Patch added: "oracular.debdiff" https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/2075337/+attachment/5802638/+files/oracular.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2075337 Title: py3clean fails when using alternate character set To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dh-python/+bug/2075337/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2075352] Re: Please merge u-boot 2024.01+dfsg-5 from Debian unstable.
Test builds being built in ppa:waveform/u-boot at https://launchpad.net/~waveform/+archive/ubuntu/u-boot -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2075352 Title: Please merge u-boot 2024.01+dfsg-5 from Debian unstable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/u-boot/+bug/2075352/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2075352] Re: Please merge u-boot 2024.01+dfsg-5 from Debian unstable.
Attaching patch against Debian unstable. For ease of review, relevant commits and tags have been pushed to the following repository: https://code.launchpad.net/~waveform/ubuntu/+source/u-boot/+git/u-boot Specifically: * logical/2024.01+dfsg-1ubuntu6 represents our split-out delta on top of old/debian (2024.01+dfsg-1) * logical/2024.01+dfsg-5ubuntu1 represents our rebased delta on top of new/debian (2024.01+dfsg-5) * merge/2024.01+dfsg-5ubuntu1 adds changelog and maintainer changes on top of logical/2024.01+dfsg-5ubuntu1 Hence, the following command may produce output useful to the purposes of review: git range-diff --creation-factor=100 old/debian..logical/2024.01+dfsg-1ubuntu6 new/debian..logical/2024.01+dfsg-5ubuntu1 ** Patch added: "1-2075352.debdiff" https://bugs.launchpad.net/ubuntu/+source/u-boot/+bug/2075352/+attachment/5802176/+files/1-2075352.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2075352 Title: Please merge u-boot 2024.01+dfsg-5 from Debian unstable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/u-boot/+bug/2075352/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2075352] [NEW] Please merge u-boot 2024.01+dfsg-5 from Debian unstable.
Public bug reported: Please merge u-boot 2024.01+dfsg-5 from Debian unstable. Updated changelog and diff against Debian unstable to be attached below. ** Affects: u-boot (Ubuntu) Importance: Undecided Assignee: Dave Jones (waveform) Status: New ** Changed in: u-boot (Ubuntu) Assignee: (unassigned) => Dave Jones (waveform) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2075352 Title: Please merge u-boot 2024.01+dfsg-5 from Debian unstable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/u-boot/+bug/2075352/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2075176] [NEW] lxd cannot launch (useable) oracular container under focal's kernel
Public bug reported: We've been encountering an issue with building the Ubuntu for Raspberry Pi images for oracular for the past couple of weeks: https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu/oracular/ubuntu- preinstalled It turns out the root issue is that the builders are running focal (kernel version 5.4), the build occurs under lxd (in an oracular container), and (peculiarly to this particular build, which uses ubuntu- image) the build requires snapd to be operational within the oracular container. I replicated the issue locally with the following setup, using both jammy and focal VMs to demonstrate the issue is kernel related: * A Raspberry Pi 4B with 8GB of RAM * Booted noble (24.04) and initialized lxd: lxd init * Launch a jammy VM: lxc launch ubuntu:j jammyvm * Enter the jammy VM: lxc exec jammyvm bash * Within the jammy VM, initialize lxd: lxd init * Launch an oracular container [1]: lxc launch ubuntu-daily:o oractest -c security.nesting=true * Enter the oracular container: lxc exec oractest bash * Check snapd is operational: snap list * snap reports nothing is installed, try the hello-world snap * Exit oracular container * Exit jammy VM * Stop jammy VM: lxc stop jammyvm * Launch a focal VM: lxc launch ubuntu:f focalvm * Enter the focal VM: lxc exec focalvm bash * Within the focal VM, initialize lxd: lxd init * Launch an oracular container [1]: lxc launch ubuntu-daily:o oractest -c security.nesting=true * Enter the oracular container: lxc exec oractest bash * Check snapd is operation: snap list * Test fails with: cannot communicate with server: Get "http://localhost/v2/snaps": dial unix /run/snapd.socket: connect: connection refused * Check systemctl output: numerous failed services * Check ps output: almost nothing running (just init, effectively) * Exit oracular container I noted that lxd was version 4.0/stable/ubuntu-20.04 under the focal VM and wondered if the current lxd would resolve things, but after refreshing it to 5.21/stable it displayed the same symptoms under the oracular container within. Is there any means of making an oracular container work under a focal kernel, or do I need to request the builders are upgraded? [1]: security.nesting=true used to work around LP: #2046486 ** Affects: lxd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2075176 Title: lxd cannot launch (useable) oracular container under focal's kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/2075176/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063110] Re: rtorrent crashes on startup
This looks good: a nice minimal patch, patch has proper headers and attribution, SRU template looks well written with an easy to use test- case and a reasonable regression section, and the patch is well formed with a good version number for SRU. One minor quibble: the changelog mentions d/rules but this file isn't actually changed in the diff, it's a new patch instead. However, I'm happy to fix that on upload; sponsoring for noble. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063110 Title: rtorrent crashes on startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rtorrent/+bug/2063110/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063110] Re: rtorrent crashes on startup
** Merge proposal linked: https://code.launchpad.net/~fougner/ubuntu/+source/rtorrent/+git/rtorrent/+merge/469649 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063110 Title: rtorrent crashes on startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rtorrent/+bug/2063110/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2073359] Re: [SRU] Copy u-boot-pic64gx to Noble
Unsubscribing ubuntu-sponsors as this has been uploaded to noble now -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2073359 Title: [SRU] Copy u-boot-pic64gx to Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/u-boot-pic64gx/+bug/2073359/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069384] Re: puppetdb fails to build from source on noble
Unsubscribing ubuntu-sponsors; please re-subscribe once these points are addressed, and thank you for coming up with the minimal patch! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069384 Title: puppetdb fails to build from source on noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppetdb/+bug/2069384/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069384] Re: puppetdb fails to build from source on noble
Reviewed the current state and it seems there's a feel bits of paperwork that still need a little bit of work before this can be sponsored: * The "Where problems could occur" and "Other Info" sections in this bug haven't been updated to indicate this is now a minimal patch. The SRU team need this to be up to date when they come to review it (they're not going to read through the entire bug history to see it's no longer correct). * An update to clj-http-clojure is (presumably?) no longer required; if it isn't, it's worth closing LP: #2069390 as invalid too * The "Where problems could occur" section in this bug don't really give a sense of potential regressions. In fact, some of the bits in "Other Info" would probably be relevant here (e.g. the first point "I haven't attempted running the 7.12.1-3 binaries with the default-jdk/openjdk-21 because FTBFS in itself is an indicator of incompatibility and needs to be addressed"). * These same comments could be made regarding the related LP: #2072516 bug -- it needs updating to the fact this is now a minimal patch, and the "Where problems could occur" section needs a bit of work to suggest where things could go wrong operationally for users. * The Origin: field in patch 0009-Replace-use-of-to-pson.patch (https://git.launchpad.net/ubuntu/+source/puppetdb/diff/puppet/lib/puppet/util/puppetdb/command.rb) doesn't seem to lead anywhere useful? Just gives me a blank patch. I'm presuming there should be some branch/commit identifiers in there to indicate what should be diff'd? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069384 Title: puppetdb fails to build from source on noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppetdb/+bug/2069384/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072516] Re: autopkgtests fail on oracular & noble
Unsubscribing ubuntu-sponsors for now; see comments on LP: #2069384 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072516 Title: autopkgtests fail on oracular & noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppetdb/+bug/2072516/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2046871] Re: migrate to upstream release/coreNN branch
It looks like comment #2 and comment #3 have been addressed, as well as the concerns about upstream lacking a stable versioning convention (i.e. they have, but we've been ignoring it). I checked the upstream repo and there are indeed years of release/coreNN branches, and the proposed PPA matches the upstream release/core88 branch. One minor thing of note during a test build of the binary package: lintian warns that a dependency on dh-dkms is missing. It isn't; the package depends on dh-sequence-dkms which is a virtual provided by dh- dkms, so the warning is incorrect, but it may be worth altering the build-depends to avoid it in future. Anyway, sponsoring for oracular. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2046871 Title: migrate to upstream release/coreNN branch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/backport-iwlwifi-dkms/+bug/2046871/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072490] Re: [needs-packaging] U-Boot for Microchip PIC64GX
The ~ppa3 version now in the same PPA addresses the concerns above, and passes lintian clean; sponsoring for oracular. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072490 Title: [needs-packaging] U-Boot for Microchip PIC64GX To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2072490/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072490] Re: [needs-packaging] U-Boot for Microchip PIC64GX
It looks like Steve's comments are addressed by the current PPA version (and I'll make a note to check that MCD_tasks.c disappears in the forthcoming merge of u-boot main!). I do note there's a few lintian errors / warnings to clean up. Most are trivial and I'm happy to just deal with them myself while sponsoring, specifically: E: u-boot-pic64gx source: build-depends-indep-without-arch-indep This is because, now the u-boot-pic64gx package is riscv64 only, there are no arch-indep packages left. Trivial fix: make gcc-riscv64-linux-gnu part of build-depends instead. W: u-boot-pic64gx source: missing-license-paragraph-in-dep5-copyright gpl-2.0 [debian/copyright:126] W: u-boot-pic64gx source: missing-license-paragraph-in-dep5-copyright gpl-2.0+ [debian/copyright:119] Here the lines in d/copyright refer to GPL-2.0 instead of GPL-2 and GPL-2.0+ instead of GPL-2+. Trivial fix: delete .0 in each case W: u-boot-pic64gx source: patch-file-present-but-not-mentioned-in-series [debian/patches/riscv-update-PIC64GX-model-property.patch] This one I need a bit of guidance on. I *think* this patch is not meant to be there; if I add it to d/p/series it complains about a reversed/already applied patch so I'm guessing this patch was in an earlier bit of packaging, but was then applied upstream and so removed from d/p/series, but the patch itself didn't get removed from the directory? If so, I'm happy to just remove it while sponsoring. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072490 Title: [needs-packaging] U-Boot for Microchip PIC64GX To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2072490/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072500] Re: [SRU] Add Microchip PIC64GX Curiosity Kit support
Looks good, sponsoring for oracular -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072500 Title: [SRU] Add Microchip PIC64GX Curiosity Kit support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/2072500/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
