The verification passed for focal:
ubuntu@ubuntu:~$ apt-cache policy linux-firmware-raspi2
linux-firmware-raspi2:
Installed: 3-0ubuntu2~20.04.1
Candidate: 4-0ubuntu0~20.04.1
Version table:
4-0ubuntu0~20.04.1 500
500 http://ports.ubuntu.com/ubuntu-ports focal-proposed/multiverse
The verification passed for groovy.
ubuntu@ubuntu:~$ apt-cache policy linux-firmware-raspi2
linux-firmware-raspi2:
Installed: 2-0ubuntu2
Candidate: 4-0ubuntu0~20.10.1
Version table:
4-0ubuntu0~20.10.1 500
500 http://ports.ubuntu.com/ubuntu-ports groovy-proposed/restricted
The verification passed for groovy.
ubuntu@ubuntu:~$ apt-cache policy linux-firmware-raspi2
linux-firmware-raspi2:
Installed: 2-0ubuntu2
Candidate: 4-0ubuntu0~20.10.1
Version table:
4-0ubuntu0~20.10.1 500
500 http://ports.ubuntu.com/ubuntu-ports groovy-proposed/restricted
** Description changed:
[SRU Information]
- Needs completing. See comment 5 below.
+ [Impact]
+
+ The same file was provided by two packages, causing errors when
+ upgrading.
+
+ [Test Case]
+
+ * Boot an ubuntu image on a Raspberry Pi.
+ * "sudo apt update"
+ * "sudo apt upgrade"
+ *
** Changed in: linux-firmware-raspi2 (Ubuntu Focal)
Assignee: (unassigned) => William Wilson (jawn-smith)
** Changed in: linux-firmware-raspi2 (Ubuntu Groovy)
Assignee: (unassigned) => William Wilson (jawn-smith)
--
You received this bug notification because you are a member of
** Changed in: linux-firmware-raspi2 (Ubuntu Focal)
Assignee: (unassigned) => William Wilson (jawn-smith)
** Changed in: linux-firmware-raspi2 (Ubuntu Groovy)
Assignee: (unassigned) => William Wilson (jawn-smith)
--
You received this bug notification because you are a member of
** Tags added: verification-needed verification-needed-focal
verification-needed-groovy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1912905
Title:
Can't find WLAN device on RPI-CM4L with 20.10
** Changed in: pi-bluetooth (Ubuntu Focal)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1921915
Title:
Bluetooth controller not detected on CM4
To
** Tags removed: verification-needed verification-needed-groovy
** Tags added: verification-done verification-done-groovy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1925971
Title:
SRU bluetooth
The verification passed for Groovy.
*** On Pi 400 **
ubuntu@ubuntu:~$ apt-cache policy pi-bluetooth linux-firmware-raspi2
pi-bluetooth:
Installed: 0.1.15ubuntu1
Candidate: 0.1.15ubuntu1.1~20.10.1
Version table:
0.1.15ubuntu1.1~20.10.1 500
500
The verification passed for Groovy.
*** On Pi 400 **
ubuntu@ubuntu:~$ apt-cache policy pi-bluetooth linux-firmware-raspi2
pi-bluetooth:
Installed: 0.1.15ubuntu1
Candidate: 0.1.15ubuntu1.1~20.10.1
Version table:
0.1.15ubuntu1.1~20.10.1 500
500
The verification passed for focal.
* On Pi 400 **
ubuntu@ubuntu:~$ apt-cache policy bluez pi-bluetooth linux-firmware-raspi2
bluez:
Installed: 5.53-0ubuntu3
Candidate: 5.53-0ubuntu3.1
Version table:
5.53-0ubuntu3.1 500
500 http://ports.ubuntu.com/ubuntu-ports
** Tags added: verification-done-focal verification-needed verification-
needed-groovy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1925971
Title:
SRU bluetooth fixes and CVEs to focal and groovy
-bluetooth (Ubuntu)
Assignee: (unassigned) => William Wilson (jawn-smith)
** Changed in: pi-bluetooth (Ubuntu Focal)
Assignee: (unassigned) => William Wilson (jawn-smith)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
] Device 28:11:A5:D5:CB:47 Name: LE-reserved_M
[CHG] Device 28:11:A5:D5:CB:47 Alias: LE-reserved_M
[NEW] Device E2:70:8C:88:51:C0 E2-70-8C-88-51-C0
[bluetooth]#
** Changed in: linux-firmware-raspi2 (Ubuntu)
Assignee: (unassigned) => William Wilson (jawn-smith)
** Changed in: linux-firmw
This bug was fixed in u-boot-menu version 4.0.3ubuntu2
** Changed in: u-boot-menu (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/1927231
Title:
** Description changed:
[Impact]
* Without the pi-bluetooth changes in hirsute, bluetooth will not work
on the Pi 400 or CM4.
[Test Case]
* Boot the Ubuntu Server for Pi 20.04 image on a Raspberry Pi 400.
- * "bluetoothctl"
- * "list" and verify there is no available
** Tags added: verification-needed verification-needed-focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926378
Title:
SRU pi-bluetooth from hirsute to focal to enable all models
To manage
Some merge markers were left around in the script and manpage. The
attached patch removes them.
** Patch added: "lp1927231.debdiff"
https://bugs.launchpad.net/ubuntu/+source/u-boot-menu/+bug/1927231/+attachment/5495353/+files/lp1927231.debdiff
--
You received this bug notification because
Seb, The builds were failing in the launchpad build farm. The official
package builds are failing on multiple architectures with various "out
of memory" errors, and preventing this package from migrating out of
-proposed. Debian builds don't seem to be affected, so I would think
they wouldn't want
The verification passed for groovy:
ubuntu@ubuntu:~$ apt-cache policy apport
apport:
Installed: 2.20.11-0ubuntu50.5
Candidate: 2.20.11-0ubuntu50.6
Version table:
2.20.11-0ubuntu50.6 500
500 http://ports.ubuntu.com/ubuntu-ports groovy-proposed/main arm64
Packages
***
The verification passed for focal:
ubuntu@ubuntu:~$ apt-cache policy apport
apport:
Installed: 2.20.11-0ubuntu27.16
Candidate: 2.20.11-0ubuntu27.17
Version table:
2.20.11-0ubuntu27.17 500
500 http://ports.ubuntu.com/ubuntu-ports focal-proposed/main armhf
Packages
***
** Description changed:
[Impact]
* Without the pi-bluetooth changes in hirsute, bluetooth will not work
on the Pi 400 or CM4.
[Test Case]
* Boot the Ubuntu Server for Pi 20.04 image on a Raspberry Pi 400.
- * Verify the command `bluetoothctl devices` fails with the
-
** Patch added: "lp1921915_focal.debdiff"
https://bugs.launchpad.net/ubuntu/+source/pi-bluetooth/+bug/1926378/+attachment/5492937/+files/lp1921915_focal.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The attached patch enables Bluetooth on the new Pi 400, and CM4
hardware.
** Description changed:
[Impact]
* Without the pi-bluetooth changes in hirsute, bluetooth will not work
- on the Pi 4, 400 or CM4.
+ on the Pi 400 or CM4.
[Test Case]
- * Boot the Ubuntu Server for Pi
** Description changed:
[Impact]
* Without the pi-bluetooth changes in hirsute, bluetooth will not work
on the Pi 4, 400 or CM4.
[Test Case]
- * Boot the Ubuntu Desktop for Pi image on a Raspberry Pi 4.
- * Start the Settings application and switch to the Bluetooth tab
- *
Public bug reported:
[Impact]
* Without the pi-bluetooth changes in hirsute, bluetooth will not work
on the Pi 4, 400 or CM4.
[Test Case]
* Boot the Ubuntu Desktop for Pi image on a Raspberry Pi 4.
* Start the Settings application and switch to the Bluetooth tab
* Verify that Bluetooth is
** Description changed:
- Hirsute has some patches that address CVEs and enable bluetooth/wifi on
- the CM4 and 400. They need to be SRU'd to focal and groovy.
+ [Impact]
+
+ Without these patches, Bluetooth is inoperable on the CM4 and Pi 400
+
+ [Test Case]
+
+ * Boot the Ubuntu Desktop for
** Description changed:
- Under later versions of the Ubuntu kernel (5.8) on the CM4 and
- (possibly?) some models of the Pi 400, the bluetooth controller is not
- activated by the pi-bluetooth package. This appears to be due to two
- issues:
+ [Impact]
+
+ Without these patches, Bluetooth is
** Patch added: "Groovy SRU"
https://bugs.launchpad.net/ubuntu/+source/pi-bluetooth/+bug/1921915/+attachment/5492486/+files/lp1921915_groovy.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Patch added: "Focal SRU"
https://bugs.launchpad.net/ubuntu/+source/pi-bluetooth/+bug/1921915/+attachment/5492485/+files/lp1921915_focal.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I've uploaded packages to https://launchpad.net/~jawn-
smith/+archive/ubuntu/raspackages for both focal and groovy. They
include changes to binary files so a normal debdiff wouldn't have
worked.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
Hirsute has some patches that address CVEs and enable bluetooth/wifi on
the CM4 and 400. They need to be SRU'd to focal and groovy.
** Affects: linux-firmware-raspi2 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you
** Changed in: pi-bluetooth (Ubuntu Focal)
Status: New => In Progress
** Changed in: pi-bluetooth (Ubuntu Groovy)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: request-tracker5 (Ubuntu)
Status: New => In Progress
** Changed in: request-tracker5 (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: monero (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1923684
Title:
Parallel builds for monero are running out of memory
To manage
** Summary changed:
- Parallel builds for monero are running our of memory
+ Parallel builds for monero are running out of memory
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1923684
Title:
The attached debdiff adds the "--no-parallel" flag to the build. It
successfully built in my ppa.
** Patch added: "monero.debdiff"
https://bugs.launchpad.net/ubuntu/+source/monero/+bug/1923684/+attachment/5487502/+files/monero.debdiff
--
You received this bug notification because you are a
** Changed in: request-tracker5 (Ubuntu)
Assignee: (unassigned) => William Wilson (jawn-smith)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1923659
Title:
Builds are failing due to harml
Public bug reported:
The failed builds have errors like "memory exhausted" and "out of
memory". Removing the parallelization from the build should help with
this.
** Affects: monero (Ubuntu)
Importance: Undecided
Assignee: William Wilson (jawn-smith)
Sta
This patch adds the harmless "No name" warning to the regex. It is not
necessary to forward upstream as the upstream is not a writable
repository.
** Patch added: "request_tracker5.debdiff"
Public bug reported:
The builds have some tests that are failing due to harmless warnings.
The warning "no name" for a missing key is valid behavior, so we will
add it to the regex for acceptable crypt-gnupg warnings.
** Affects: request-tracker5 (Ubuntu)
Importance: Undecided
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986836
Apparently I had not created the bug report correctly the first time.
** Bug watch added: Debian Bug tracker #986836
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986836
--
You received this bug notification because you are a
I have submitted a Debian bug report with the patch suggested, and
updated the bug description.
bluez is pre-installed on the desktop images, but not the server images.
This warning would be very useful for server users that want to install
bluez for the first time.
--
You received this bug
** Description changed:
- In the case of upgrading bluez on certain raspberry pi devices, a reboot
- may be required to apply the changes. We should add a check for this
- scenario in the postinst script.
+ In the case of upgrading or installing bluez for the first time on
+ certain raspberry pi
** Changed in: pi-bluetooth (Ubuntu Groovy)
Assignee: (unassigned) => William Wilson (jawn-smith)
** Changed in: pi-bluetooth (Ubuntu Focal)
Assignee: (unassigned) => William Wilson (jawn-smith)
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Seb, I have made a PR in the github repo. This PR also pulls in the
changes in version 1.6.3, which were previously not present.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922712
Title:
add
The verification passed for focal:
jawn-smith@focal-vm:~$ apt-cache policy procps
procps:
Installed: 2:3.3.16-1ubuntu2
Candidate: 2:3.3.16-1ubuntu2.1
Version table:
2:3.3.16-1ubuntu2.1 500
500 http://us.archive.ubuntu.com/ubuntu focal-proposed/main amd64
Packages
***
Seb,
A reboot is needed in this case because the bluetooth device on the
raspberry pi has to be initialized at boot time. Restarting the service
will not cause the device to be brought up.
The hardcoded addresses are the approach used in the pi-bluetooth
package, and recommended by waveform.
As
Attached is a patch to add the hwcap metric to ubuntu-report.
** Patch added: "lp1922712.debdiff"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-report/+bug/1922712/+attachment/5485728/+files/lp1922712.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Changed in: ubuntu-report (Ubuntu)
Assignee: (unassigned) => William Wilson (jawn-smith)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922712
Title:
add metric for new glibc hwc
Attached is a patch for Hirsute. If this is accepted I will SRU to focal
and groovy.
** Changed in: bluez (Ubuntu)
Assignee: (unassigned) => William Wilson (jawn-smith)
** Patch added: "Hirsute Patch"
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1922792/+attac
Robie,
pgrep and pkill are sharing the same code. Essentially pkill runs pgrep
and then issues a kill signal to the resulting pid. Therefore this fix
applies to both pkill and pgrep. Additionally, the source of the problem
comes from the behavior of `sysconf(_SC_ARG_MAX)` changing in newer
Public bug reported:
In the case of upgrading bluez on certain raspberry pi devices, a reboot
may be required to apply the changes. We should add a check for this
scenario in the postinst script.
** Affects: bluez (Ubuntu)
Importance: Undecided
Status: New
--
You received this
** Patch added: "Groovy SRU"
https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1874824/+attachment/5484328/+files/lp1874824_groovy.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874824
** Patch added: "Focal SRU"
https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1874824/+attachment/5484329/+files/lp1874824_focal.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874824
** Patch added: "Fix RFKILL_EVENT_SIZE_V1 check"
https://bugs.launchpad.net/ubuntu/+source/urfkill/+bug/1922117/+attachment/5482869/+files/lp1922117.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
The kernel has added a byte to the rfkill event struct to account for a
possible reason field. See:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=14486c82612a177cb910980c70ba900827ca0894
urfkill is checking to make sure the rfkill event is
** Attachment added: "Patch to increase sleep"
https://bugs.launchpad.net/ubuntu/+source/golang-github-bugsnag-bugsnag-go/+bug/1921952/+attachment/5482453/+files/lp1921952
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
The test sessions/integration_test.go is consistently failing
autopkgtests and therefore this package cannot migrate.
** Affects: golang-github-bugsnag-bugsnag-go (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are
** Patch added: "Patch with corrected LP reference"
https://bugs.launchpad.net/ubuntu/+source/urfkill/+bug/1921919/+attachment/5482409/+files/lp1921919.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
The version of urfkill in -proposed has a possible segmentation fault if
the call to get_dmi_info fails. After this there is an attempt to free
an uninitialized variable. This was blocking the migration from
-proposed.
kernel: urfkilld[46754]: segfault (11) at 0 nip
** Patch added: "segfault patch"
https://bugs.launchpad.net/ubuntu/+source/urfkill/+bug/1921919/+attachment/5482408/+files/lp1921919.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1921919
** Description changed:
+ [Impact]
+
+ - Users who have ulimit set high would see either slow
+ or failed pgrep and pkill commands
+ - Users who have ulimit set to unlimited would see
+ failed pgrep and pkill commands
+ - This bug occurs because the behavior of sysconf(_SC_ARG_MAX)
Attached is a patch to fix the issue in hirsute. Assuming this is
approved, I have also prepared the SRUs for focal and groovy.
** Patch added: "Hirsute debdiff"
https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1874824/+attachment/5480543/+files/lp1874824_hirsute.debdiff
--
You
** Changed in: procps (Ubuntu Focal)
Assignee: (unassigned) => William Wilson (jawn-smith)
** Changed in: procps (Ubuntu Groovy)
Assignee: (unassigned) => William Wilson (jawn-smith)
** Changed in: procps (Ubuntu Hirsute)
Assignee: (unassigned) => William Wilson (j
@seb128 it turns out Dave had already forwarded the patches, so I
included the URLs in this new debdiff
@vanvugt I set the version to ubuntu3.1 rather than ubuntu4
** Patch added: "Focal SRU"
Attached is a patch to SRU for focal.
** Patch added: "Focal SRU"
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1903048/+attachment/5477287/+files/lp1903048_focal.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I have reviewed flashrom along with fwupd and I don't see anything that
looks like it will cause problems. The flashrom documentation recommends
using vendors' flashing utilities when possible for laptops, and there
is a link to that page of the documentation in the manpage.
I have attached a
The SRU verification passed for focal. The attached screenshot shows
firmware staged in /lib/firmware/updates that is not included in the
initramfs with version 0.136ubuntu6.3 of initramfs-tools, and then
correctly included in the initramfs with version 0.136ubuntu6.4 of
initramfs-tools.
**
[Summary]
This package is safe to include in main.
This does need a security review, so I'll assign ubuntu-security
List of specific binary packages to be promoted to main:
* ftdi-eeprom
* libftdi1-2
* libftdi1-dev
* libftdi1-doc
* libftdipp1-3
* libftdipp1-dev
* python3-ftdi1
Confirmed it is working as expected in the focal daily build image.
Thanks for letting me know they were built using -proposed!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1901043
Title:
No sound
> without a SRU template? ;-)
Thanks for the reminder!
** Description changed:
+ [Impact]
+
+ * Firmware files under /lib/firmware/updates would not be
+processed when running update-initramfs
+
+ * The kernel org specifies that this is a location where
+firmware can be stored, so
This fix already exists in groovy and hirsute. It was applied when
pulling in version 0.137 from upstream. The attached patch is to SRU the
fix into focal.
** Patch added: "Focal SRU"
** Changed in: initramfs-tools (Ubuntu Focal)
Assignee: (unassigned) => William Wilson (jawn-smith)
** Changed in: initramfs-tools (Ubuntu Groovy)
Assignee: (unassigned) => William Wilson (jawn-smith)
** Changed in: initramfs-tools (Ubuntu Hirsute)
Assignee: Dave Jones (wa
** Changed in: update-manager (Ubuntu Focal)
Assignee: (unassigned) => William Wilson (jawn-smith)
** Changed in: update-manager (Ubuntu Groovy)
Assignee: (unassigned) => William Wilson (jawn-smith)
** Changed in: update-manager (Ubuntu Hirsute)
Assignee: (unassigned) =>
** Changed in: update-manager (Ubuntu)
Assignee: (unassigned) => William Wilson (jawn-smith)
** Changed in: update-manager (Ubuntu Focal)
Assignee: (unassigned) => William Wilson (jawn-smith)
** Changed in: update-manager (Ubuntu Groovy)
Assignee: (unassigned) => Willi
The verification passed for groovy. The attached image shows that the
check boxes are working for kernel packages staged for autoremoval.
** Attachment added: "Groovy Verification"
The verification passed for focal. The portion of the image highlighted
in green shows that the check boxes are working for kernel packages
staged for autoremoval.
** Attachment added: "Focal Verification"
The verification passed for Groovy. The attached image shows update-
manager has staged many packages for upgrade without crashing.
** Attachment added: "Groovy Verification"
The verification passed for focal. The attached image shows the latest
version has staged many packages for upgrade without crashing.
** Attachment added: "Focal Verification"
** Changed in: ubuntu-release-upgrader (Ubuntu Hirsute)
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/1907713
Title:
aufs support is deprecated and should be
The verification passed for focal. The following steps were taken for
verification:
1)boot to safe graphics mode
a) observe that no startup sound is played
b) `watch -n 1 'systemctl status sound.target'`
1) wait for sound.target to become active
2) observe that no startup
Per Tianon's suggestion, I have created a NEWS file for aufs-tools to
warn users of the deprecation of AUFS.
** Patch added: "aufs-tools NEWS debdiff"
https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1907713/+attachment/5466772/+files/news.debdiff
--
You received this bug
https://github.com/tianon/debian-docker/pull/4
This PR removes the check for the snap aufs dir.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1907713
Title:
aufs support is deprecated and should
The verification passed for groovy. The attached image shows linux
kernel packages not grouped under Ubuntu base with version 1:20.10.4,
and the packages correctly grouped with version 1:20.10.5.
** Attachment added: "Groovy Verification"
The verification passed for focal. The attached image shows linux kernel
packages not grouped under Ubuntu base with version 1:20.04.10.5, and
the packages correctly grouped with version 1:20.04.10.6. The section
highlighted in green shows that the kernel packages are not grouped
under "Unused
Attached is a debdiff to add a preinst file to docker.io that will stop
it from upgrading if containers are using aufs.
** Patch added: "lp1907713.debdiff"
https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1907713/+attachment/5466341/+files/lp1907713.debdiff
--
You received this bug
** Changed in: docker.io (Ubuntu Hirsute)
Assignee: (unassigned) => William Wilson (jawn-smith)
** Changed in: ubuntu-release-upgrader (Ubuntu Hirsute)
Assignee: (unassigned) => William Wilson (jawn-smith)
--
You received this bug notification because you are a member of Ubunt
Attached is an SRU for focal. It groups all kernel packages under Ubuntu
base while safely avoiding the issues in LP: #1912718 and LP: #1913476.
It also introduces a new test for the scenario in LP: #1912718 and
cleans up binary files left behind by tests.
** Patch added: "Focal SRU"
This new diff from debian drops the whitespace changes and adds the
dropped CVE patches to the changelog
** Patch added: "Diff from Debian take two"
https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1915307/+attachment/5463220/+files/debian-ubuntu.debdiff
--
You received this bug
** Changed in: bluez (Ubuntu Groovy)
Assignee: Dave Jones (waveform) => William Wilson (jawn-smith)
** Changed in: bluez (Ubuntu Hirsute)
Assignee: Dave Jones (waveform) => William Wilson (jawn-smith)
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Patch added: "Diff from latest Ubuntu version"
https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1915307/+attachment/5462731/+files/ubuntu-ubuntu.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Patch added: "Diff from Debian"
https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1915307/+attachment/5462721/+files/debian-ubuntu.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Attached is an SRU for groovy. It groups all kernel packages under
Ubuntu base while safely avoiding the issues in LP: #1912718 and LP:
#1913476. It also introduces a new test for the scenario in LP: #1912718
and cleans up binary files left behind by tests.
** Patch added:
** Description changed:
This requires a merge because there are changes in the Ubuntu version
not present in the Debian version.
+
+ -- Justification of patches removed from debian/patches/series --
+ * typo-in-classic-insults.diff
+ * This exact patch is present in upstream
Public bug reported:
This requires a merge because there are changes in the Ubuntu version
not present in the Debian version.
** Affects: sudo (Ubuntu)
Importance: Undecided
Assignee: William Wilson (jawn-smith)
Status: In Progress
** Changed in: sudo (Ubuntu)
Assignee
I do see now that there are built in tests, so I will update the
description. There is no debian/tests file so I will leave that part in.
Thanks for the input!
** Description changed:
[Summary]
- There are a few issues before we can MIR this package. The package does not
have a test suite
Verification passed for focal.
The attached image verifies the fix in focal. The first half of the
image shows the installed versions of friendly-recovery, systemd, and
resolvconf, the failed result from "dig www.google.com", and the empty
/etc/resolv.conf. The second half of the image shows an
The attached image verifies the fix in bionic. The first half of the
image shows the installed versions of friendly-recovery, systemd, and
resolvconf, the failed result from "dig www.google.com", and the empty
/etc/resolv.conf. The second half of the image shows an updated
installed version of
301 - 400 of 450 matches
Mail list logo
