** Changed in: vim (Ubuntu Lunar)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to vim in Ubuntu.
https://bugs.launchpad.net/bugs/1996087
Title:
Ensure supported codenames are
fects: vim (Ubuntu)
Importance: Wishlist
Assignee: Simon Quigley (tsimonq2)
Status: In Progress
** Affects: vim (Ubuntu Focal)
Importance: Wishlist
Assignee: Simon Quigley (tsimonq2)
Status: In Progress
** Affects: vim (Ubuntu Jammy)
Importance: Wishlist
https://git.launchpad.net/ubuntu/+source/lxc/tree/debian/patches/0003-meson-
Set-DEVEL-flag-post-release.patch is the patch that should be dropped by
the SRU.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
Verified in a fresh Lunar VM.
** Tags removed: verification-needed verification-needed-lunar
** Tags added: verification-done verification-done-lunar
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
resh install)
** Changed in: apport (Ubuntu Lunar)
Assignee: Benjamin Drung (bdrung) => Simon Chopin (schopin)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/2038650
Looking at the code it seems to be affecting Lunar as well. I'm spinning
up a VM to confirm it (LXD containers are being difficult for this)
** Changed in: apport (Ubuntu)
Status: In Progress => Fix Committed
** Also affects: apport (Ubuntu Mantic)
Importance: High
Assignee: Si
This was caused by the addition of this feature:
https://github.com/canonical/apport/pull/131
It broke an assumption that Dependencies was only added by the late
stage info collection, and said collection also had some other side-
effects that were relied upon to trigger the upload.
I'll create
** Also affects: pastedeploy (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dh-python in Ubuntu.
https://bugs.launchpad.net/bugs/2035337
Title:
dh-python: Cannot
Public bug reported:
My home network comprises many VLANs managed by `systemd-
networkd`/`netplan`. Those VLANs are then used as parent interfaces for
LXD networks. Whenever `systemd-networkd` is restarted (i.e: post-
update), my whole network breaks because all the unmanaged bridges lose
their
Public bug reported:
Imported from Debian bug http://bugs.debian.org/1051837:
Source: dh-python
Version: 6.20230825
Severity: normal
X-Debbugs-Cc: scho...@ubuntu.com
We have a FTBFS on src:pastescript because its test suite embeds a
FakePlugin Python package, including its .egg-info, and the
This was fixed in ca-certificates version 20211016 which is what Jammy
released with. As of today, all Ubuntu releases from Bionic onward ship
20230311 so marking as fix released.
** Changed in: ca-certificates (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug
libgl1-mesa-dri:amd64 23.0.4-0ubuntu1~22.04.1
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1989964
Title:
Segmentation fault crocus_dri.so (X server dies)
Status in Mesa:
The problem still exists:
Aug 29 18:35:21 titan /usr/libexec/gdm-x-session[582536]: (EE)
Aug 29 18:35:21 titan /usr/libexec/gdm-x-session[582536]: (EE) Backtrace:
Aug 29 18:35:21 titan /usr/libexec/gdm-x-session[582536]: (EE) 0:
/usr/lib/xorg/Xorg (?+0x0) [0x5614c77b0939]
Aug 29 18:35:21
@oibaf, read your request. unfort i just started rebuilding my profile
from scratch. i'm in the process of re-adding all the applets, and other
X stuff. will keep you posted.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Ah, right. Debootstrap is more low-level, thanks.
--
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/2028769
Title:
[SRU] missing riscv64 packages ubuntu-desktop,
I'm just generally curious, does debootstrap function differently
with/without this patch?
I'd imagine it either goes off the task, or a level lower than the
metapackages.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Hi,
I'm sorry, I'm not entirely sure I understood that correctly, but if
you're looking for the apport sources, you can find them there:
https://github.com/canonical/apport
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Hi,
Thanks for the patch. I took care of the LP metadata for the bug
(targetting the proper series), and unsubscribe ubuntu-sponsors since
it's not ready for upload yet. Please resubscribe ubuntu-sponsors once
you feel it's ready for upload.
@enr0n can you chime in on this, do we have things
I'll reiterate my point: the issue being discussed is a Green Linux
issue, this should be discussed wherever that distribution does its
development, and investigated by its developers. For the `apport` Ubuntu
package this is completely out of scope.
I'll also clarify our position as upstream
Hi,
Thanks for taking the time to report the issue. I've tried to reproduce
the issue in Ubuntu in a fresh Jammy VM, without success, and the
provided logs don't really help us out.
However, it appears you're not using Ubuntu, but rather a derivative.
While we'd probably welcome patches in the
This has been re-broken in the glibc package when upstream changed the
name of the actual ld.so binary, thus escaping the stripping exception.
I've fixed this in the git tree in preparation of the mantic upload.
There's currently a Jammy SRU in -proposed, I won't supersede it for
this fix since
Nowadays, btrfs snapshots can only be taken by the owner of the source
subvol. https://btrfs.readthedocs.io/en/latest/ch-mount-
options.html#btrfs-specific-mount-options:
> Historically, any user could create a snapshot even if he was not
owner of the source subvolume, the subvolume deletion has
Hi,
Thanks for adressing Steve's comments, I uploaded the Jammy debdiff,
it's now in the SRU queue. I also unsubscribe ubuntu-sponsors, so if by
any chance there's a need to revisit this upload do remember to
subscribe it again :)
--
You received this bug notification because you are a member
** Changed in: initramfs-tools (Ubuntu Jammy)
Status: Confirmed => In Progress
--
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/1983359
Title:
[SRU] hwrng
oblematic function.
> @Simon: I also removed "cryptography" via pip because it was installed from
> the Repo and by pip.
> Not sure which program caused it, but everything is fine now.
>
> Thank you very much for your quick help!
> Much appreciated!
You're welcome :)
-
Hi,
In addition to what Adrien asks, could you show us the version of
python3-cryptography you're using? The bindings used by pyOpenSSL are
actually provided by the cryptography package. Also, could you make sure
you don't have a local version of said code in /usr/local, similar to
your PyOpenSSL
Is this going to happen in 23.10? It seems to have been stalled in
-proposed since May.
After the imminent Debian 12 release (which includes polkit 122), I
intend to start removing legacy polkit 0.105 support, with my goal being
polkitd-pkla no longer existing in Debian 13, and packages no longer
@slyon I saw that https://git.launchpad.net/network-
manager/commit/?h=netplan/lunar-
gu=900b2e15bce37363b263a224e60674f804114693 requires the `file`
package to be available. Some systems don't have installed, albeit
probably not common on desktops but I though I'd mention just in case.
That same
The latest Ubuntu 22.04.2 desktop live image (ubuntu-22.04.2-desktop-
amd64.iso, sha256
b98dac940a82b110e6265ca78d1320f1f7103861e922aa1a54e4202686e9bbd3)
exhibits what appears to be the same problem, which should make this
very easy for a developer to reproduce.
--
You received this bug
I can reproduce what I think is the same problem on the original Ubuntu
22.04 live image ubuntu-22.04-desktop-amd64.iso (sha256:
b85286d9855f549ed9895763519f6a295a7698fb9c5c5345811b3eefadfb6f07):
* boot a virtual machine with the live image in the virtual CD-ROM drive, and
no hard drive
* wait
Public bug reported:
evince does not store setting "Select page size using document page
size".
the setting is overwritten by the setting "Draw border around pages"
fix:
diff -r evince-42.3/libview/ev-print-operation.c
evince-42.3-patched/libview/ev-print-operation.c
2778c2778
<
Quoting Steven R. Loomis (2023-04-12 17:30:25)
> What ICU is this? I can't tell which version from here. Your analysis
That'd be 72.1-3ubuntu1, now ubuntu2 with this patch. This bug was
mostly for reference for the folks in the Ubuntu release team since
we're in feature freeze, almost at final
Public bug reported:
During the last test rebuild, it was noticed that icu failed to build
from source, with the following failures in the test suite:
-
| *** FAILING TEST SUMMARY FOR: intltest
TestAliasedNames
TestCanonicalID
TimeZoneTest
Another affected user. Here using VNC through Apache Guacamole with
XFCE4 as a desktop manager. Similar errors to others:
$ firefox
2023/03/30 14:56:04.261227 cmd_run.go:1055: WARNING: cannot start document
portal: Can't mount path /home/student/.cache/doc
Public bug reported:
There's been a bunch of security patches to the Kinetic version of vim,
those need to be applied to Lunar as well:
* CVE-2033-0433
* CVE-2023-1170
* CVE-2023-1175
* CVE-2023-1264
In addition, the following only affect the version in Lunar:
* CVE-2023-0512
* CVE-2023-1127
Did I mentioned it was not convenient? :P
$ d="$(mktemp -d)"
$ lxc manpage "$d"
$ ls -1 "$d"
lxc.1
lxc.alias.1
lxc.alias.add.1
lxc.alias.list.1
lxc.alias.remove.1
lxc.alias.rename.1
lxc.cluster.1
lxc.cluster.add.1
...
$ ls -1 "$d" | wc -l
293
--
You received this bug notification because you
I've been told that snaps can't ship man pages unfortunately:
https://forum.snapcraft.io/t/support-for-man-pages/2299/24
https://bugs.launchpad.net/snapd/+bug/1575593
You can get something with `lxc manpage` which is basically the builtin
--help formatted for man. However, that's not
Interesting! If your recollection is accurate then I unfortunately don't
see how rsync could workaround that FAT32 limitation :/
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsync in Ubuntu.
Jammy's rsync (3.2.7) has --trust-sender that's described as: "trust the remote
sender's file list"
However that won't be of much help as that's not available in older releases :/
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
Hey Mauricio,
> Could you please confirm if from the Anbox perspective, for a
> workaround, is it OK to temporatily unmask/start the unit
> (due to restart), then upgrade the package, and stop/mask again?
It's not that simple. We have prebuilt images we ship to users which run
through an
** Description changed:
The Anbox Cloud LXD images are based of the standard Ubuntu cloud images
- for LXD but have the systemd-udev.service unit masked (`systemctl mask
- systemd-udev.service`) as we do not need udev.
+ for LXD but have the systemd-udevd.service unit masked (`systemctl mask
+
Public bug reported:
The Anbox Cloud LXD images are based of the standard Ubuntu cloud images
for LXD but have the systemd-udev.service unit masked (`systemctl mask
systemd-udev.service`) as we do not need udev.
With the latest security patch on Ubuntu 22.04 upgrading the udev
package fails:
The rsync versions mentioned in the bug are very old and the distro
version they came with, long out of support. As such, I'll mark the
issue as incomplete until this can be reproduced/confirmed with a
recent/supported version. Thanks!
** Changed in: rsync (Ubuntu)
Status: Confirmed =>
I'll mark this old bug as fix released because I can't reproduce it on
20.04 (3.1.3) nor 22.04 (rsync 3.2.7). Here's how I tested it on 20.04:
# rsync --version
rsync version 3.1.3 protocol version 31
...
# mkdir -p "src/a " dst
# rsync -aiv src/ dst/
sending incremental file list
.d..t..
I /think/ there is work being done by security to land a MRE for rsync,
you might want to sync with @mdeslaur.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsync in Ubuntu.
https://bugs.launchpad.net/bugs/2007837
Title:
Sponsored, thank you!
** Changed in: grilo-plugins (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to grilo-plugins in Ubuntu.
https://bugs.launchpad.net/bugs/2007623
Title:
Merge
** Changed in: sudo (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sudo in Ubuntu.
https://bugs.launchpad.net/bugs/2007698
Title:
Please merge 1.9.13p1-1 into lunar
Status in
** Changed in: curl (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to curl in Ubuntu.
https://bugs.launchpad.net/bugs/2008123
Title:
Please merge 7.88.1-1 into lunar
Status in
It looks like this upload has already been sponsored, thanks.
** Changed in: sysvinit (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sysvinit in Ubuntu.
Uploaded, thanks!
** Changed in: openssl (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/2006954
Title:
openssl: merge
also on libgl1-mesa-dri:amd64 22.2.5-0ubuntu0.1~22.04.1
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1989964
Title:
Segmentation fault crocus_dri.so (X server dies)
Please remember to mention the bug number in the changelog entry.
Additionally, for stylistic purposes, I changed this:
* Merge from Debian unstable. The remaining difference is the change
for ignoring test results on i386 to avoir failure.
To this:
* Merge from Debian Unstable (LP:
@georgiag, the behaviour changes when you tell tcpdump to do line
buffering (`-l`).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1641236
Title:
Confined processes
> the next casper upload will regress the current version of the fix
I'm all in favor of a better longer-term fix replacing this one being
tracked in systemd, but an unrelated casper upload regressing this
change prior to a longer-term solution being in place will cause issues
with all amd64 live
The issue has been fixed upstream just before the final 2.37 release,
thus closing this.
** Changed in: libunistring (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libunistring in
LGTM, sponsored, thank you!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libunwind in Ubuntu.
https://bugs.launchpad.net/bugs/2004039
Title:
libunwind 1.6.2-0 assumes 4k page sizes and crashes on systems with
bigger
** Tags removed: update-excuse
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python3-defaults in
Ubuntu.
https://bugs.launchpad.net/bugs/2002660
Title:
networkx incompatible with numpy 1.24
Status in networkx package in
The failure is in a gnulib test. I've bisected it to the following glibc
upstream commit:
https://sourceware.org/git/?p=glibc.git;a=commit;h=642933158e7cf072d873231b1a9bb03291f2b989
The issue has been reported upstream.
** Bug watch added: Sourceware.org Bugzilla #30065
Public bug reported:
Hi,
During a mass rebuild of Lunar, the package libunistring failed to build
against a snapshot of the upcoming glibc 2.37, while building fine using
2.36 as present in the archive.
** Bug watch added: Debian Bug tracker #1029785
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029785
** Also affects: systemd (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029785
Importance: Unknown
Status: Unknown
--
You received this bug notification
Just to catch the bug report up with the IRC discussion:
we got away with it in casper because we knew there weren't going to
be 899 IDs allocated in this range in the installer context, and the casper
user goes away post-install
systemd doesn't statically set them, it allocates them using
Hi Tobias, thanks for your interest in this bug!
While I did not do a code review of the patch itself, I have some general
feedback on the diff and the bug report itself that I hope you find helpful:
- The version should be 1.6.2-0ubuntu1.1 instead of 1.6.2-0ubuntu2, following
Stable Release
> It's not clear to me that changing the casper user to use this uid
won't badly confuse the installer when it comes time to create the
actual user account, or at least cause gid 1000 to be skipped.
After some testing with the newly-uploaded casper, I can confirm this is not
the case. I tested
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
** Changed in: systemd (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
> It's not clear to me that changing the casper user to use this uid
won't badly confuse the installer when it comes time to create the
actual user account, or at least cause gid 1000 to be skipped.
It's not clear to me that it will. Casper doesn't touch the squashfs
that ends up on the installed
Uploaded, thanks :)
** Changed in: p11-kit (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to p11-kit in Ubuntu.
https://bugs.launchpad.net/bugs/2003548
Title:
Merge Debian
Hi Nathan!
I have no problem with the patch, given the author. That being said, it
would be useful to send this delta up to Debian if at all possible.
Please consider it. :)
Also, it's best not to modify changelog entries that exist in Debian.
I'm dropping this before uploading:
wpa (2:2.10-9)
Yeah, I figured it was likely the outcome when I replied to a bug that
was last touched 10 years ago ;) The bug will close itself in ~60 days
if nothing happen so I think that's OK. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Looks like this was sponsored (thanks William!), unsubscribing the
sponsors team.
** Changed in: coreutils (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to coreutils in Ubuntu.
I tested a rsyslog client talking to a rsyslog server both using
`rsyslog-gnutls 8.2112.0-2ubuntu2.2` on Ubuntu 22.04 and it worked fine.
There, there is no error loading "/usr/lib/x86_64-linux-
gnu/rsyslog/lmnsd_gtls.so" as long as the `-gnutls` package is
installed. I used only a cert (from
Public bug reported:
Imported from Debian bug http://bugs.debian.org/1028603:
Package: dh-python
Version: 5.20221001
Severity: normal
X-Debbugs-Cc: scho...@ubuntu.com
For instance, pylint has "tomli>=1.1.0;python_version<'3.11'" in its
pyproject.toml, which is translated as "python3-tomli (>=
Public bug reported:
The nipype autopkgtests have started failing with the following stack
trace:
ERROR collecting pipeline/plugins/tests/test_tools.py _
/usr/lib/python3.10/importlib/__init__.py:126: in import_module
return _bootstrap._gcd_import(name[level:],
Hi!
Seeing this line:
Unpacking libssl-dev:i386 (3.0.2-0ubuntu1.7) over (1.0.1f-1ubuntu2.27)
makes me think you either are trying to upgrade directly from Trusty
(which would be weird given your install medium is Jammy), or have
third-party packages on your system, most likely installed through
** Changed in: vim (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to vim in Ubuntu.
https://bugs.launchpad.net/bugs/1864424
Title:
new vim version in 20.04 sets mouse=a
Looks like this was already sponsored:
https://launchpad.net/ubuntu/+source/dbus/1.14.4-1ubuntu1
Please re-subscribe ~ubuntu-sponsors if further action is required.
Thank you!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Looking at the logs, this bug seems rather to be in
/usr/share/perl5/Debconf/Db.pm, which is in debconf. Reassigning it
there.
** Also affects: debconf (Ubuntu)
Importance: Undecided
Status: New
** Changed in: glibc (Ubuntu)
Status: New => Invalid
--
You received this bug
** Description changed:
In several stable releases of Ubuntu, Vim has information regarding
releases that are outdated. It would be optimal for Vim to grab this
data from distro-info-data (or similar), but unfortunately that is not
the case. Therefore, the list needs to be updated.
this update is to download a package from the Lunar
archive, and open the changelog with Vim. Instead of the changelog
release (e.g. "lunar") showing as red, it should show as blue.
** Affects: vim (Ubuntu)
Importance: Undecided
Assignee: Simon Quigley (tsimonq2)
S
** Tags added: fr-2936
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tzdata in Ubuntu.
https://bugs.launchpad.net/bugs/1995601
Title:
tzdata 2022f ICU data update
Status in tzdata package in Ubuntu:
Triaged
Status in
reported upstream:
https://gitlab.freedesktop.org/mesa/mesa/-/issues/7626
** Bug watch added: gitlab.freedesktop.org/mesa/mesa/-/issues #7626
https://gitlab.freedesktop.org/mesa/mesa/-/issues/7626
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
Public bug reported:
The ICU data we embed in tzdata was out of sync on the 2022f-0ubuntu1
upload, still matching the 2022e data instead. It's been updated
upstream, so we need to do another round of SRUs for it:
https://github.com/unicode-org/icu-
All verifications done (except for ICU data which wasn't ready) on
bionic, focal, jammy and kinetic using fresh LXC containers and the
instructions from
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1986984 adjusted
for the new data updates.
** Tags removed: verification-needed
Folded into the LP #1990379 uploads to Jammy, Kinetic and Lunar.
** Also affects: zlib (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: zlib (Ubuntu Kinetic)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of
Uploaded to Lunar, Kinetic, Jammy and Focal
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to zlib in Ubuntu.
https://bugs.launchpad.net/bugs/1990379
Title:
[UBUNTU 20.04] zlib: inflate() does not update strm.adler if DFLTCC
is this read/followed by upstream? or should i find upstream myself to
report it?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1989964
Title:
Segmentation fault
As for verification, I verified this using the following command in LXC
containers:
❯ LANG=C timedatectl list-timezones | grep Kyiv
Europe/Kyiv
This worked in all containers.
** Tags removed: verification-needed verification-needed-bionic
verification-needed-focal verification-needed-jammy
** Changed in: console-setup (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to console-setup in Ubuntu.
https://bugs.launchpad.net/bugs/1733346
Title:
package
I retried chrony and it passed :)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tzdata in Ubuntu.
https://bugs.launchpad.net/bugs/1969671
Title:
Misspelled Ukrainian cities in tzdata
Status in tzdata package in Ubuntu:
Both regressions were retried and succeeded.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tzdata in Ubuntu.
https://bugs.launchpad.net/bugs/1992692
Title:
tzdata 2022e release
Status in tzdata package in Ubuntu:
Fix
** Changed in: dbus (Ubuntu)
Status: Invalid => Triaged
--
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/1968845
Title:
Upgrade to 22.04 from 20.04 ends with dbus
Hi,
Looking into the Df.txt logs, I see this:
/dev/sdb6 210872 170420 23468 88% /boot
You probably don't have enough space on your /boot for the new kernel.
Could you try freeing some space on it or resizing it?
** Changed in: initramfs-tools (Ubuntu)
Status: New =>
Hi, I verified the 2022e-0ubuntu0.XX.04.0 packages on jammy, focal and
bionic using fresh LXC containers. I'll look into the autopkgtest
regressions as well.
** Tags removed: verification-needed verification-needed-bionic
verification-needed-focal verification-needed-jammy
** Tags added:
@paride, I know it's a low priority item but I was wondering what's next
to do for the SRU? Thanks!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsync in Ubuntu.
https://bugs.launchpad.net/bugs/1965076
Title:
rsync
** Description changed:
New timezone data, with the following timezones impacted:
- Palestine transitions are now Saturdays at 02:00. This means 2022 falls
back 10-29 at 02:00, not 10-28 at 01:00.
- Simplify three Ukraine zones into one.
- Jordan and Syria switch from +02/+03 with DST
Thanks Paride for the feedback, here's a refreshed debdiff!
** Patch removed: "rsync_3.2.3-8ubuntu4.debdiff"
https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1965076/+attachment/5623548/+files/rsync_3.2.3-8ubuntu4.debdiff
** Patch added: "rsync_3.2.3-8ubuntu3.1.debdiff"
I packaged the upstream fix (minus the changes to NEWS.md) and created
the debdiff attached.
** Description changed:
+ [Impact]
+
+ This bug causes rsync 3.2.3 to wrongly report files with an exact same mtime
as being "newer"
+ implying they would need to be transfered/sync'ed where in fact
** Also affects: rsync via
https://github.com/WayneD/rsync/issues/98
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsync in Ubuntu.
https://bugs.launchpad.net/bugs/1965076
If you can fill out the SRU template, that'd be great! I see that you
worked with upstream to ID which commit corrected the problem, that will
be useful to whoever creates a debdiff! If you need a hand with the
debdiff, please let me know and I'll set some time aside. Thanks!
--
You received
@Ian, the back and forth on status was apparently due to a simple
mistake on which distro version was affected. The good news is that
thanks to comment #7, we now know that Kinetic is fixed which is one of
the required step to do a SRU
(https://wiki.ubuntu.com/StableReleaseUpdates) to have the fix
I can confirm the problem affects rsync 3.2.3-8ubuntu3 as shipped in
22.04.
** Changed in: rsync (Ubuntu)
Status: Invalid => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsync in Ubuntu.
101 - 200 of 1674 matches
Mail list logo
