Also encountered this when upgrading a server from 12.04 to 14.04 (for
reference, wound up filing duplicate bug #1579566). Managed to get slapd
restored happily by creating the accesslog directory (then slapadd to
restore).
Unfortunately as I restored the database, rather than apt handling it,
Ah, no worries - finally figured it out. Needed to apply the patch to
/var/lib/dpkg/info/slapd.postinst (rather than slapd.config - was
confused over package's half-configured state) and restore the old-
version backup prior to retrying "dpkg --configure -a". All good now!
--
You received this
** Attachment added: "apt log from server upgrade"
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1579566/+attachment/4658826/+files/apt.log
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openldap in Ubuntu.
Public bug reported:
While attempting to perform an upgrade of my home server from Ubuntu
12.04 to Ubuntu 14.04, I received the following error:
===
Error in function:
A fatal error occurred
Please report this
After a bit of playing around, it appears the root cause was that I'm
using the accesslog overlay which necessitates having another database
under /var/lib/ldap/accesslog. The migration process backed up
everything under /var/lib/ldap to /var/backups then re-created
/var/lib/ldap - but didn't
I should add: I think the accesslog overlay is implicit in replicated
setups (yes, I know, weird enough that a home server's using LDAP, but
replication too?! I originally set it up to learn about LDAP replication
in order to use it at work :). It seems to be used to ease the burden of
change
*** This bug is a duplicate of bug 1003854 ***
https://bugs.launchpad.net/bugs/1003854
Ah, you're absolutely right - that looks like it. Sorry for the
duplicate (don't know why I didn't find that report first)!
--
You received this bug notification because you are a member of Ubuntu
Touch
My backup was indeed slapcat / slapadd (for both the main directory and
the cn=config stuff). I'd *guess* that if the package state is "ii" you
may not need the patch (incidentally the patch is in bug description at
the top), particularly if the server's starting fine and everything
queries
Hi Andre - I did take a backup of the LDAP directory prior to "do-
release-upgrade" (actually I had nightly backups running so I just
grabbed a copy of the last one of those). That's what I was referring to
when I stated "restore the old-version backup...". It's been a few
months now but I vaguely
approach to me, and hence is what is in the PR
(https://github.com/CanonicalLtd/landscape-client/pull/55).
** Changed in: landscape-client (Ubuntu)
Assignee: (unassigned) => Dave Jones (waveform)
** Changed in: landscape-client (Ubuntu)
Status: Confirmed => In Progress
--
You re
Seems like there's two issues here which I'll address in separate PRs to
the landscape-client:
First is the issue that the landscape-client fails to report the
completion (or failure) of the release upgrade process. This turns out
to be due to a delayed import in the version of twisted
> /sbin/shutdown, post upgrade not working, imho is a severe bug
I suspect no-one's bothered to report it because as soon as the machine
is (somehow) rebooted, the issue goes away (and reproduction then
involves the pain of going through a trusty install + xenial upgrade
cycle). Still, I'm not
** Changed in: landscape-client (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1670291
Title:
Landscape: Upgrade
@xnox Scheduling with /sbin/shutdown normally does work ... however,
what we're dealing with here is the anomalous situation of an instance
which starts off as trusty and is upgraded to xenial. During the upgrade
process, the /sbin/shutdown implementation is changed from the upstart
one to the
For anyone else that encounters this, running "cancel -x -a" to delete
everything from the queue (including historical control files) seems to
have cured the problem. Sorry for not keeping the evidence around, but
I'm afraid after it generated 70Mb of logs in two days I needed to fix
it :)
--
Public bug reported:
Since my server (running xenial) updated to cups 2.1.3-4ubuntu0.9 last
night the CUPS logs have had a considerable number of messages from
cupsd stating "Removing document files" - about 3 or 4 a second
constantly. Stopping the cups service stops the log-spam, and starting
it
I have an updated patch available from the following branch for focal:
https://code.launchpad.net/~waveform/ubuntu/+source/python-apt/+git
/python-apt/+ref/fix-dupe-ppa
Currently building a test package in the following PPA:
** Changed in: python-apt (Ubuntu)
Assignee: (unassigned) => Dave Jones (waveform)
** Changed in: python-apt (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pyth
Updated python-apt package available in the following PPA:
https://launchpad.net/~waveform/+archive/ubuntu/pkg
Branch from which the package was built:
https://code.launchpad.net/~waveform/ubuntu/+source/python-apt/+git
/python-apt/+ref/focal-entry
--
You received this bug notification
Please note for testing:
add-apt-repository does not operate without the updated package either,
so just download the relevant .debs and install manually with "sudo dpkg
-i" for testing. The package that's really needed is python-apt-common
(which contains the updated template output), but you
@jblainemitre indeed - but presumably one can pick any directory? I'm
assuming there's no particular requirement that the selected dir is
world-writeable like /tmp and /var/tmp (or at least there doesn't seem
to be in my setup?)
--
You received this bug notification because you are a member of
** Description changed:
Impact
==
Under most circumstances, the impact is minimal (a few extra redundant
comment lines in apt sources. However, if users are automating source
removal / addition on a machine (as in comment 11), there is the
potential to wind up with an
** Description changed:
+ Impact
+ ==
+
+ Under most circumstances, the impact is minimal (a few extra redundant
+ comment lines in apt sources. However, if users are automating source
+ removal / addition on a machine (as in comment 11), there is the
+ potential to wind up with an
> Do you have the new python3.7 installed from focal-proposed?
> note, i was running everything from proposed. Since libffi6 & 7 might
> be used by python3.7.
Ah, no I didn't. However, doesn't seem like it makes much difference:
ubuntu@ubuntu:~$ sudo apt install -t focal-proposed python3.7
> so this is not completely updated to focal-proposed?
No, that was just certain focal-proposed packages on a focal image (on a
pi4). Have now re-run with a full focal-proposed chroot (under the same
focal image), and that doesn't reproduce the issue:
(focal-arm64)root@ubuntu:~# cat
Reproduced on a Pi4 running the current focal daily:
ubuntu@ubuntu:~$ python3 -c "import goocalendar;
print(goocalendar.__version__)"
Unable to init server: Could not
I can confirm the behaviour Brian's seeing on the Pi 3B on armhf and
arm64 with systemd 245.4-2 from the PPA Balint mentioned (and the same
error message which appears to be from a chunk of code slightly beyond
where we were last time - so we're moving forward at least :).
As before, wifi is
Also tested under armhf and arm64 on Raspberry Pi models 3B, 3A+, and
3B+. Results are the same as for bdmurray's tests with armhf on the 3B
above.
My initial suspicion was that this was related to the wifi chipset used
on the 3B (the BCM43430) to the 4B (the BCM43455). However, given the
3A+ and
** Changed in: python-apt (Ubuntu Eoan)
Assignee: (unassigned) => Dave Jones (waveform)
** Changed in: python-apt (Ubuntu Xenial)
Assignee: (unassigned) => Dave Jones (waveform)
** Changed in: python-apt (Ubuntu Bionic)
Assignee: (unassigned) => Dave Jones (waveform)
Confirmed test build in the PPA in comment 13 (245.4-4ubuntu3) fixes the
issue on both archs (armhf and arm64) on the Pi 3B, 3A+, and 3B+ (re-
tested 4B as well to ensure nothing broken, and it's still working).
--
You received this bug notification because you are a member of Ubuntu
Touch
Public bug reported:
Attempting to play audio (e.g. from rhythmbox) on the raspberry pi
desktop image, results in broken up / crackling audio. The "tsched=0"
workaround noted in
https://wiki.ubuntu.com/Audio/PositionReporting#Turning_off_PulseAudio_timer_scheduling
successfully avoids the issue.
Public bug reported:
On each boot, an incorrect audio output device is selected, at least
when HDMI audio output is in use (still need to test the TV/aux output;
will update the bug when done).
Specifically, the settings application lists "Multichannel Output -
Built-in Audio" as the selected
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-apt in Ubuntu.
https://bugs.launchpad.net/bugs/1311056
Title:
[SRU]
Successfully verified fixes on xenial, bionic, and eoan. The autopkgtest
regressions on xenial were due to flaky tests on i386 and armhf; these
have been re-run successfully. The regressions on bionic look like a
transient network failure (would be grateful if someone could attempt a
re-run on
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
** Tags removed: verification-needed-eoan
** Tags added: verification-done-eoan
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-apt
Hmm, this looks like someone reported exactly this about a year ago:
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/762
Unfortunately it's closed with "approach the driver maintainer".
** Bug watch added: gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues #762
Public bug reported:
Under gcc-10's linker an error occurs wherein "progname" appears to be
included from multiple locations (as it's defined in version.h rather
than merely declared).
** Affects: kbd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug
** Description changed:
Under gcc-10's linker an error occurs wherein "progname" appears to be
included from multiple locations (as it's defined in version.h rather
than merely declared).
+
+ A trivial patch is available from the following branch:
+
+
All regressions now cleared after a re-run (thanks!), and verifications
done.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-apt in Ubuntu.
https://bugs.launchpad.net/bugs/1311056
Title:
[SRU] apt-add-repository
@hujq is there anything unusual about your bluetooth setup? miniuart-bt
overlay or anything like that? I'm unable to replicate the failure here
on a Pi 4 8GB
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
Ooops - left a redundant file in the diff; revised patch attached below
** Patch added: "2-2.3.0-3ubuntu1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/kbd/+bug/1903614/+attachment/5432819/+files/2-2.3.0-3ubuntu1.debdiff
--
You received this bug notification because you are a member of
Public bug reported:
Please merge kbd 2.3.0-3 from Debian unstable.
Updated changelog and diff against Debian unstable is attached below.
Test build available from
https://launchpad.net/~waveform/+archive/ubuntu/kbd/+packages
** Affects: kbd (Ubuntu)
Importance: Undecided
Status:
** Summary changed:
- Bluetooth won't activate on the pi 400
+ [SRU] Bluetooth won't activate on the pi 400
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1903048
Title:
** Description changed:
+ [Impact]
+
+ Without these patches, Bluetooth is inoperable on the recently released
+ Raspberry Pi 400.
+
+ [Test Case]
+
+ * Boot the Ubuntu Desktop for Pi image on a Pi 400.
+ * Start the Settings application and switch to the Bluetooth tab
+ * Verify that
On Thu, Nov 12, 2020 at 11:11:23AM -, Sebastien Bacher wrote:
>Sorry but I'm reverting that upload for now until the patches are
>properly upstreamed. We have been bitten too often by unforwarded
>changes that create issues or create maintainance burden over the years
>and we currently don't
On Tue, Nov 10, 2020 at 03:12:30PM -, Sebastien Bacher wrote:
>Thanks for the work but it there any work to upstream those changes? I'm
>not happy to carry a sleep(1) hack in our package unless there is a
>strong reason and we are working on a way to replace it by a better
>solution
The
On Fri, Nov 13, 2020 at 09:37:34AM -, Sebastien Bacher wrote:
>@Matthieu, @Dave, thanks for the comments and details.
>
>I'm not blocking work to land, the 20.10 SRU could be accepted now and I
>didn't revert in that serie.
>The SRU team tries to ensure the fix is in the new serie so it
@Daniel could you try out the bluez package from the following PPA:
https://launchpad.net/~waveform/+archive/ubuntu/pi-bluetooth/+packages ?
Should be as simple as doing:
sudo add-apt-repository ppa:waveform/pi-bluetooth
sudo apt update
sudo apt upgrade
The version in that PPA contains
This was fixed by the merge from debian back in yakkety
** Changed in: kbd (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to kbd in Ubuntu.
AC address.
** Affects: bluez (Ubuntu)
Importance: Undecided
Assignee: Dave Jones (waveform)
Status: New
** Changed in: bluez (Ubuntu)
Assignee: (unassigned) => Dave Jones (waveform)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded pa
@henry-sprog yup, that looks like the same
Attached a patch to fix this in hirsute; once landed will SRU this to
groovy and earlier.
** Patch added: "lp1903048.debdiff"
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1903048/+attachment/5431962/+files/lp1903048.debdiff
--
You received
There's a version of bluez with the patches that I've submitted upstream
built in the following PPA against the hirsute branch (the patch changes
are pretty minimal; basically amounts to removal of the arbitrary
sleep(1) as during December's tests I couldn't find a single platform
that actually
Public bug reported:
Please merge db5.3 5.3.28+dfsg1-0.8 from Debian unstable.
Updated changelog and diff against Debian unstable to be attached below.
** Affects: db5.3 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of
Attaching patch against Debian unstable. Test builds available from the
following PPA:
https://launchpad.net/~waveform/+archive/ubuntu/db/+packages
** Patch added: "1-1927978.debdiff"
https://bugs.launchpad.net/ubuntu/+source/db5.3/+bug/1927978/+attachment/5496169/+files/1-1927978.debdiff
Public bug reported:
Please merge lvm2 2.03.11-2.1 from Debian unstable.
Updated changelog and diff against Debian unstable to be attached below.
** Affects: lvm2 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Attaching patch against Debian unstable. For ease of review, I've also
pushed relevant commits and tags to the following repository:
https://code.launchpad.net/~waveform/ubuntu/+source/lvm2/+git/lvm2
Specifically:
* logical/2.03.11-2ubuntu4 represents our split-out delta on top of old/debian
> Thanks for the details. You did address the part about upstreaming the
change to Debian. How important is that notification in practice? If
feels like we should have bluez preinstall on the raspi images if that's
not the case, and if it's pre-install is that really worth the packaging
overhead
Attaching patch against Debian unstable.
** Patch added: "1-1915005.debdiff"
https://bugs.launchpad.net/ubuntu/+source/findutils/+bug/1915005/+attachment/5461235/+files/1-1915005.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Public bug reported:
Please merge findutils 4.8.0-1 from Debian unstable.
Updated changelog and diff against Debian unstable to be attached
shortly.
** Affects: findutils (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of
** Changed in: initramfs-tools (Ubuntu Hirsute)
Assignee: (unassigned) => Dave Jones (waveform)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1571506
Ti
Public bug reported:
The netplan configuration in ubuntu-raspi-settings (and more widely, the
network-config in the gadget used on the server images) fails to rename
the internal ethernet interface on Pi 3B and 3B+ models from "en" to "eth0". In the netplan case this is because the driver
The most reliable means I know of at the moment for detecting Raspberry
Pi hardware at runtime is to query the device-tree.
For example, flash-kernel determines the type of board it is running on,
by matching the content of /proc/device-tree/model (e.g. "Raspberry Pi
400 Rev 1.0") against a
Attaching revised patch with needs-root added to the new qemu-related
tests (to work around build failure:
https://launchpad.net/ubuntu/+source/initramfs-
tools/0.139ubuntu1/+build/21138158)
** Patch added: "2-1915966.debdiff"
Attaching debdiff; test builds are available from the following PPA:
https://launchpad.net/~waveform/+archive/ubuntu/ubuntu-
settings/+packages
** Patch added: "1-1922266.debdiff"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1922266/+attachment/5488517/+files/1-1922266.debdiff
Public bug reported:
At present, access to the GPIO pins is provided to the dialout group by
the udev rules from the rpi.gpio-common package. However, rpi.gpio is a
single GPIO library, and the device(s) it provides access to are not
specific to it. Moreover, the interface used is deprecated and
Seeds have now been updated:
https://code.launchpad.net/~waveform/ubuntu-seeds/+git/ubuntu-seeds/+merge/400932
https://code.launchpad.net/~waveform/ubuntu-seeds/+git/ubuntu-seeds/+merge/400933
And the meta package has been updated to incorporate these changes in
1.467
** Also affects:
It's still necessary; I've got the changes ready but was holding off as
there's possibly another fix that may need to go into this package too
(LP: #1900904). But it's getting close to release so I'll push it anyway
and deal with the other ticket separately.
--
You received this bug notification
Public bug reported:
Please merge initramfs-tools 0.139 from Debian unstable.
Updated changelog and diff against Debian unstable to be attached
shortly.
** Affects: initramfs-tools (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a
Attaching patch against Debian unstable. For ease of review, I've also
pushed relevant commits and tags to the following repository:
https://code.launchpad.net/~waveform/ubuntu/+source/initramfs-
tools/+git/initramfs-tools
Specifically:
* The logical/0.137ubuntu12 tag represents our split-out
Worth noting that this issue only appears to occur when the fkms ("fake"
KMS) overlay is in use on the Ubuntu Desktop for Raspberry Pi images.
Under the kms ("full" KMS) overlay, the audio is fine. While kms is
indeed the default overlay, it is likely (due to LP: #1946368 on impish)
that many may
Public bug reported:
Please merge netcat-openbsd 1.218-2 from Debian unstable.
Updated changelog and diff against Debian unstable is attached below.
** Affects: netcat-openbsd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a
netcat-openbsd (1.218-2ubuntu1) jammy; urgency=low
* Merge from Debian unstable. Remaining changes:
- Move the netcat transitional package here and have it depend on the
peferred netcat-openbsd implementation of netcat, not
netcat-traditional.
-- Dave Jones Sun, 14 Nov 2021
** Also affects: initramfs-tools (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: linux-firmware (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
This is down to initramfs-tools switching to zstd by default, which has
such huge memory requirements that it gets killed by OOM on the Zero 2
(and presumably the 3A+?) which only has 512MB of RAM. The default
should be switched back to lz4, at least on the Pi images.
Note to self: add a test for
Targetting to Impish and Jammy as apparently ubuntu-settings lost the
21.04.3 changes in 21.10.1 (which was based on 21.04.2).
** Also affects: ubuntu-settings (Ubuntu Jammy)
Importance: Undecided
Status: Fix Released
** Also affects: ubuntu-settings (Ubuntu Impish)
Importance:
Adding ubuntu-settings as that's where the override for the raspi will
be added
** Also affects: ubuntu-settings (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Targetting to Impish and Jammy as apparently ubuntu-settings lost the
21.04.3 changes in 21.10.1 (which was based on 21.04.2).
** Also affects: ubuntu-meta (Ubuntu Impish)
Importance: Undecided
Status: New
** Also affects: ubuntu-settings (Ubuntu Impish)
Importance: Undecided
Public bug reported:
The sed 4.8-1 package currently in proposed is failing to migrate due to
a failing test on armhf. The patch added in 4.7-1ubuntu1 is still
required to work around this, and the attached debdiff restores this.
The patch has been applied upstream to gnulib
** Changed in: ubuntu-settings (Ubuntu Jammy)
Status: New => Confirmed
** Changed in: ubuntu-settings (Ubuntu Impish)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-settings in
The attached debdiff fixes the issue.
** Patch added: "1-1953521.debdiff"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1953521/+attachment/5546054/+files/1-1953521.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
Public bug reported:
The premount script for fixrtc produces a couple of lines of extraneous
(and slightly confusing) output. While this is irrelevant for most
platforms, on the pi images (which use fixrtc owing to the lack of an
RTC on the board), it means that "ext4" and "Thu Jan 1 00:00:10
The attached debdiff fixes this issue in ubuntu-settings (and restores
the 21.04.3 changes that were previously missing). Packages have been
built and tested in the following PPA:
https://launchpad.net/~waveform/+archive/ubuntu/ubuntu-settings
** Patch added: "1-1950214.debdiff"
Just to clarify, while gzip may be preferable this shouldn't prevent the
lz4 fix from landing. It's a "good enough" workaround for a bug that
prevents people from running apt-upgrade (which is far more important
than "choice of compression algorithm").
--
You received this bug notification
Some further research on this [1] suggests gzip may be a preferable
choice on the smaller platforms (lower memory usage, and better
compression anyway), plus this would alleviate the need for including
lz4 in the images.
I need to do some further analysis of the decompression to see if it is
** Also affects: initramfs-tools (Ubuntu Jammy)
Importance: Undecided
Status: Confirmed
** Also affects: initramfs-tools (Ubuntu Impish)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Yes, managed an sbuild of source and binary packages in a jammy chroot
(build log: https://paste.ubuntu.com/p/ySB3mm6xMG/) -- what was the
build failure you encountered?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
** Tags removed: rls-jj-incoming
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/574287
Title:
tasksel: forcefully removes packages when tasks overlap
Status in apt package
Closing as we're now using "full" KMS on all supported desktops
** Changed in: linux-raspi2 (Ubuntu)
Status: Confirmed => Won't Fix
** Changed in: linux-raspi (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch
nf/debconf/-/blob/master/dpkg-
reconfigure#L196-198
** Also affects: debconf (Ubuntu)
Importance: Undecided
Status: New
** Changed in: debconf (Ubuntu Jammy)
Assignee: (unassigned) => Dave Jones (waveform)
--
You received this bug notification because you are a member of Ubuntu
@ahasenack Could you try the debconf version from [1]? I've patched that
with the same fix that I've proposed upstream [2]. I'll add the relevant
debian bug here too. I realize this is *technically* a separate issue,
but it's all so interconnected and related that I'd prefer to keep it
all in one
** Changed in: dbus (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
https://bugs.launchpad.net/bugs/1959211
Title:
Please merge dbus 1.12.20-3 from Debian unstable
1/+files/1-1959054.debdiff
** Changed in: debconf (Ubuntu Jammy)
Status: New => Confirmed
** Changed in: debconf (Ubuntu Jammy)
Assignee: Dave Jones (waveform) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, whi
** Changed in: debhelper (Ubuntu Jammy)
Assignee: Dave Jones (waveform) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to debconf in Ubuntu.
https://bugs.launchpad.net/bugs/1959054
Title:
debhel
sktop
seed specifically instead of the raspi-common seed.
** Also affects: ubuntu-meta (Ubuntu)
Importance: Undecided
Status: New
** Changed in: ubuntu-meta (Ubuntu)
Assignee: (unassigned) => Dave Jones (waveform)
** Changed in: cloud-init (Ubuntu)
Assignee: Dave Jones (waveform) =
Public bug reported:
The eth0 rename fix introduced in 20.10.1, and removed in 22.04.1
unfortunately causes problems on upgrade from impish to jammy as the
file (/etc/netplan/10-rpi-ethernet-eth0.yaml) still remains in place,
and the new netplan version on jammy chokes on the space-separated
** Patch added: "1-1961618.debdiff"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1961618/+attachment/5562552/+files/1-1961618.debdiff
** Changed in: ubuntu-settings (Ubuntu)
Status: New => Confirmed
** Tags added: raspi-image rls-jj-incoming
--
You received this
Oh, and apparently ubuntu-settings FTBFS with the version of meson in
jammy (0.61.2-1); will add a patch for that too.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu.
@xnox Ah, that makes sense, thanks. I'll propose some seed updates in a
bit.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1947311
Title:
Unexpected partition growth
** Description changed:
+ NOTE: Resetting to new; do NOT merge (the current state of the merge
+ would also produce LP: #1962036 -- will update this merge once that is
+ fixed)
+
Please merge dbus 1.12.20-3 from Debian unstable.
Updated changelog and diff against Debian unstable to be
Attaching debdiff which I believe should prevent the service from being
stopped on upgrade. Test packages are currently building in
ppa:waveform/dbus (https://launchpad.net/~waveform/+archive/ubuntu/dbus)
but I've already built locally and verified that the offending portion
of the preinst
1 - 100 of 270 matches
Mail list logo
