Thank you for preparing the SRU and for testing!
The Test Plan agreed in the bug description included two cases but it
looks like you only did the first one? Given that a different SRU team
member did the review and agreed the fully stated plan, I don't feel
that I'm in a position to then release
The verification of the Stable Release Update for dnsmasq has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
The verification of the Stable Release Update for dnsmasq has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
I'm retrying these failing autopkgtests with migration-reference/0 since
if they fail anyway they shouldn't hold things up.
In the meantime, could you please also verify that behaviour on 4K page
size hasn't regressed? It looks like this was implied in the Test Plan
but hasn't been verified. Thank
Hello Andy, or anyone else affected,
Accepted apt into jammy-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/apt/2.4.12 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Test
Hello Andy, or anyone else affected,
Accepted apt into mantic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/apt/2.7.3ubuntu0.1 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu
Hello Mekaniserad, or anyone else affected,
Accepted apt into mantic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/apt/2.7.3ubuntu0.1 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki
Hello Mekaniserad, or anyone else affected,
Accepted apt into jammy-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/apt/2.4.12 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.c
I'm flagging this as Critical. It sounds like everyone agrees that the
distro patch we're carrying is bad. I think it's possible that it's bad
in quite a serious way, so we should investigate immediately without
delay until we've understood the severity of this, especially because by
carrying the d
** Changed in: openssh (Ubuntu)
Status: New => Triaged
** Changed in: openssh (Ubuntu)
Importance: Undecided => Medium
** Tags added: server-todo
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
h
This sounds like exactly the behaviour that I explained in 2013 here:
https://askubuntu.com/a/332421/7808
ifconfig still exists but is deprecated and no longer shipped by
default. Users should use its replacement "ip" instead.
However it is true that ifconfig does not display the additional alias
** Tags added: regression-update
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/2055776
Title:
After updating ubuntu, the network to which the subnet address is
assigned
** Tags added: reboot-required
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1747499
Title:
98-reboot-required and Interaction with livepatch
Status in unatt
** Tags added: reboot-required
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/2017401
Title:
Unexpected / unwanted unattended-upgrades behaviour after kernel
It's not clear to me if a simple "ssh -Snone localhost" is covered by
the autopkgtests, so I did that manually, testing without -proposed
first, and ensuring to run "sudo systemctl restart ssh" after upgrading
to -proposed to ensure that I'm definitely hitting the daemon from
-proposed.
Success on
The verification of the Stable Release Update for openssh has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
+libnotify (0.7.7-3ubuntu0.20.04.1) bionic; urgency=medium
Shouldn't this be ...0.18.04.1? The version number used will work, but
is confusing.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libnotify in Ubuntu.
https://bugs
Apart from that the Bionic upload looks fine. I note that notification-
Handle-snap-applications.patch is added over the SRU for Focal, but that
makes sense as that functionality is required for the other patches.
--
You received this bug notification because you are a member of Ubuntu
Touch seed
Sorry I missed your reply, but to make progress I just tweaked the
version string in a new upload that I signed. It's otherwise identical.
So I'll just accept that.
** Changed in: libnotify (Ubuntu Bionic)
Status: In Progress => Fix Committed
** Tags added: verification-needed-bionic
--
Hello Marco, or anyone else affected,
Accepted libnotify into bionic-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/libnotify/0.7.7-3ubuntu0.18.04.1 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. Se
Hello Utkarsh, or anyone else affected,
Accepted keyutils into impish-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/keyutils/1.6.1-2ubuntu2.1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
http
Hello Utkarsh, or anyone else affected,
Accepted keyutils into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/keyutils/1.6-6ubuntu1.1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https:/
An upload of cups to focal-proposed has been rejected from the upload
queue for the following reason: "As requested in
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1973733/comments/4";.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Hello Scott, or anyone else affected,
Accepted lvm2 into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/lvm2/2.03.07-1ubuntu1.1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.
Hello Shih-Yuan, or anyone else affected,
Accepted software-properties into jammy-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/software-
properties/0.99.22.2 in a few hours, and then in the -proposed
repository.
Please help us by testing this new p
> The exact conditions for reproducing this bug on mixed IPv4/IPv6
networks are not known
Looking at the upstream commit description, isn't it just that a DHCPv6
lease expires and the server NAKs a request for the same IP again? Or is
that not sufficient to trigger the problem.
In any case, I app
What's the current status of this please?
Julian's last comment suggests that there's a problem?
I see an upload in the queue for Bionic, but not for Focal. What's the
status in Focal?
Is this something that can be staged in proposed, or do you need it in
the updates pockets, and if so, why?
**
Thank you for the comments. These seem like good ideas, but need details
before they are actionable.
I think this update is still blocked on having a specific, step-by-step
test plan please.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Accepting this into Bionic blocked on bug 1940141, and it's further
noted there that there's an openssl security update expected on 21 June,
so it's probably best to rebase on that when it arrives.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, whi
Thank you for working on this!
The proposed SRU carries quite a bit of regression risk I think, since
there are many packages both in and out of the archive that may parse
this file under various different circumstances. A regression that leads
to a TLS failure, possibly across multiple packages a
> openssl 3.0.3-7 needs port from sid to jammy
This is presuming the solution, rather than describing the problem, so
I'll amend this.
** Summary changed:
- openssl 3.0.3-7 needs port from sid to jammy
+ Apps expecting an OpenSSL 1.1 -formatted openssl.cnf fail
--
You received this bug notific
On Thu, Jul 14, 2022 at 03:56:04PM -, David Zuelke wrote:
> So I think a big class of programs to consider that are affected by this
> potentially are those that use a statically linked OpenSSL v1, not just
> Node.js or any leftover programs that dynamically link against
> libssl1.1.
>
> And t
> ...it has basically no impact on our own applications...
Just because you and I can't find a case that would break doesn't mean
there isn't one. So there's risk. And I think the consequences, because
of the nature of this package, could be quite large.
> I'm not particularly keen on doing this
What's the user impact here please? Just noisy logs, or are users
impacted in a more meaningful way? The downside here is that a rebuild
of apparmor is going to result in virtually every Ubuntu Bionic user
having to download and install an update. The vast majority of whom
aren't using dovecot, or
>From an SRU perspective bug 1703821 is similar to this, except for
dovecot in Bionic. In both cases, a workaround is trivially available
since a user can safely modify the profile directly in /etc.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, wh
Please also fix the bug status for the Ubuntu development release
apparmor package task.
--
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/1703821
Title:
Dovecot and Apparmo
Bug 1979879 is similar to this, except for samba in Jammy. In both
cases, a workaround is trivially available since a user can safely
modify the profile directly in /etc.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmo
OK, rejecting from Bionic then and setting Won't Fix. This can be
reconsidered if something new comes up.
** Changed in: apparmor (Ubuntu Bionic)
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscr
Public bug reported:
Hi,
https://discourse.ubuntu.com/t/phased-updates-in-apt-in-21-04/20345
describes Dir::Etc::machine-id, APT::Get::Always-Include-Phased-Updates
and APT::Get::Never-Include-Phased-Updates. I expected these to be
documented in apt.conf(5) which I treat as a definitive reference
That's not really discoverable as a reference though. I wouldn't expect
"examples" to contain a definitive reference, and nor a Discourse post
about a feature that as far as I know isn't pointed to from any
definitive documentation. Same with apt_preferences - I do expect to
find information about
Looking at apt.conf(5), it does read as if it's the definitive
reference, too, and the examples file is just an example.
--
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/1986660
T
> Fixing this is nice for the users, but OTOH very low severity and
would cause a package download and update on almost every Ubuntu in the
world. Therefore we will mark this as block-proposed and keep it in
focal-proposed so that a later real update (security or functional) will
pick this up from
There's further discussion in the ubuntu-devel ML thread.
In addition to that though, I notice that mkosi in Jammy does refer to
/usr/bin/systemd-repart. Will the Jammy packaged mkosi therefore change
behaviour if you start shipping it in Ubuntu?
--
You received this bug notification because you
Hello Jason, or anyone else affected,
Accepted tzdata into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/tzdata/2022c-0ubuntu0.20.04.0 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https
Hello Jason, or anyone else affected,
Accepted tzdata into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/tzdata/2022c-0ubuntu0.18.04.0 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
http
Hello Jason, or anyone else affected,
Accepted tzdata into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/tzdata/2022c-0ubuntu0.22.04.0 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https
https://wiki.ubuntu.com/StableReleaseUpdates#tzdata says "Uploads should
also be made to any releases supported via ESM". I see a bug task but
nothing in the queue. What are your plans on this, please?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
** Changed in: cyrus-sasl2 (Ubuntu Jammy)
Assignee: Andreas Hasenack (ahasenack) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openldap in Ubuntu.
https://bugs.launchpad.net/bugs/1912256
Title:
Missin
The verification of the Stable Release Update for openldap has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
Progress to fix this in Jammy is still blocked on a test plan.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1937110
Title:
dhcp option 121 & 249
Status in subiquity:
An upload of sudo to jammy-proposed has been rejected from the upload
queue for the following reason: "The mode of debian/source_sudo.py is
changed but this is not explained in the changelog or SRU information".
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Is there any possibility that passing through this environment variable
when we previously did not will change behaviour in such a way that a
user treats that as a regression? For example, if some user has a
setting that causes some app to now break, when it didn't before?
Your upload changes the
In #ubuntu-security just now:
14:44 sarnold: please could we have a definitive nack if you
don't want bug 1981807 in the security pocket? Looking at the previous
IRC conversation, it looks like it was a "decision pending review".
--
You received this bug notification because you are a member of
Thanks everyone for the discussion. As there have been no further
comments, I think it's appropriate to make a decision. I'll reject the
openssl upload from Jammy, and mark that task Won't Fix. We won't update
the default configuration in Jammy. Third parties who ship software
intended for Jammy ne
An upload of openssl to jammy-proposed has been rejected from the upload
queue for the following reason: "See discussion in LP: #1979639".
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchp
That's a good question. I think it's up to Simon and the Foundations
team what they want to do there. There is far less of a risk to users
either way in Kinetic, because it hasn't been released yet. So I have no
preference for Kinetic, though it does make sense to revert to me.
--
You received th
** Information type changed from Public to Public Security
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to policykit-1 in Ubuntu.
https://bugs.launchpad.net/bugs/1535768
Title:
pkexec tty hijacking via TIOCSTI ioctl
Status
> * run update-maintainer script
FWIW, it's not necessary to mention this directly. It is correct to do
it, but convention is to skip mentioning it in the changelog because
otherwise we'd have to unnecessarily mention it on nearly every Ubuntu
upload.
--
You received this bug notification becaus
I wondered if ucf is expected to handle dpkg-divert -ed files in the
first place, since that seemed odd to me. It does seem like that's a
feature the code was intended to support, although it's unclear to me if
it ever worked, and it's not really documented anywhere I can find
except that is implie
Any suggestions on how to identify SRUs that are affected so that we can
ensure that the necessary Breaks are in there?
(also, do we know that Breaks will work as needed for an issue in the
prerm?)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, wh
Here's the buggy code that assumes UTF-8:
https://git.launchpad.net/ubuntu/+source/python3-defaults/tree/debpython/files.py#n54
--
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.launchpa
Setting C.UTF-8 would work internally I agree. But what does this mean
for SRUs? Does every affected SRU now have to declare Breaks:
python3-minimal (<< whatever)?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python3-defaul
I think it's fair to call this Critical since SRU releases generally are
currently blocked by this. Looking at the definition, "Severely affects
applications beyond the package responsible for the root cause" also
applies.
** Changed in: python3-defaults (Ubuntu)
Importance: High => Critical
-
Thanks all for working on this!
Do we know if releases prior to Noble are affected?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dh-python in Ubuntu.
https://bugs.launchpad.net/bugs/2075337
Title:
py3clean fails when us
Ghadi is working on a replacement upload, so I'm rejecting the current
one as agreed with him.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tar in Ubuntu.
https://bugs.launchpad.net/bugs/2059734
Title:
Tar fails to extra
** Also affects: python3-defaults (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: dh-python (Ubuntu Jammy)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed t
From #ubuntu-release, Jeremy suggested that this needs doing before the
language packs are generated for 24.04.1.
** Changed in: gsettings-desktop-schemas (Ubuntu Noble)
Milestone: None => ubuntu-24.04.1
--
You received this bug notification because you are a member of Ubuntu
Touch seeded pa
Hello Julian, or anyone else affected,
Accepted apt into noble-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/apt/2.8.2 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Tes
Hello Julian, or anyone else affected,
Accepted apt into noble-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/apt/2.8.2 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Tes
I discussed the plan for noble-updates and for 24.04.1 with Julian in
detail yesterday. I think the plan is likely to be accepted by the SRU
team. We're behind with the documentation, but I'm accepting the newest
upload to noble-proposed now since time is tight. Julian will make sure
that the full
I see the Test Plan has been copied over from previous bugs. I think we
should also test that apt seems the cloud archive correctly. That was
already being done, so I'll just add to the Test Plan what was actually
being already done.
** Description changed:
Please add support for:
-cloud
This is missing the previous changelog entry, but also should just be
squashed together. I pinged juliank and jamespage in #ubuntu-devel.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://b
This is missing the previous changelog entry, but also should just be
squashed together. I pinged juliank and jamespage in #ubuntu-devel.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://b
OK I'm releasing this on the basis of Julian's justification above.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/2061214
Title:
[SRU] Software Sources is not
Actually, no need to actually release, since it's identical to the
special binary package, right? So I can just accept the next SRU for
this package into noble-proposed and treat this bug as completed. When
that SRU lands, this no-binary-change one will, too.
--
You received this bug notification
Accepting, but my request to amend the Test Plan from comment 2 still
stands, and needs adjusting (and SRU verification accordingly) prior to
SRU release.
** Changed in: software-properties (Ubuntu Noble)
Status: Incomplete => Fix Committed
** Tags added: verification-needed verification-n
Hello Julian, or anyone else affected,
Accepted software-properties into noble-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/software-
properties/0.99.49.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new pack
Hello James, or anyone else affected,
Accepted software-properties into noble-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/software-
properties/0.99.49.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new packa
Public bug reported:
In bug 2003027, Ubuntu's procps regressed the default qdisc from
fq_codel to pfifo_fast. Given that this was considered important enough
to justify changing behaviour in a stable release, we should have an
autopkgtest that verifies our intended delta against upstream, but we d
Accepting for 24.04. It is unfortunate to have to change behaviour in
this way, but this seems preferable than to switch to the reported-worse
qdisc just for 24.04, and also preferable to do sooner rather than later
in 24.04's lifetime, given that the .1 release is due this week.
However, if this
Hello Dave, or anyone else affected,
Accepted procps into noble-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/procps/2:4.0.4-4ubuntu3.1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wi
This missed making it into 24.04.1, but it'd be nice to get this
released immediately after the images for 24.04.1 are finalised, so that
users get the new behaviour from day one of using 24.04.1. I asked about
this in #ubuntu-release. It'd be a great help if this could be SRU-
verified *immediatel
** Tags added: regression-release
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to procps in Ubuntu.
https://bugs.launchpad.net/bugs/2003027
Title:
fq_codel qdisc compiled but not enabled on 22.10
Status in Ubuntu:
Fix Re
Thank you for working on this!
SRU review
> Currently there is an issue with the ac_on_power script where it
thinks that USB-c ports with devices plugged in to them are plugged in
to power.
This isn't a statement of user impact, making it difficult to understand
how changing the stable releases
This seems like quite an invasive change. It has not yet been accepted
upstream. It touches PAM, and it looks to me like it might affect
behaviour before authentication is complete. It affects escaping.
Injection of malicious data into a stream to be parsed by the terminal
has security implications
Hello Matthew, or anyone else affected,
Accepted ubuntu-settings into noble-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/ubuntu-
settings/24.04.5 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Accepting. I see that the change is scoped to
"[org.gnome.desktop.background:GNOME-Greeter]" so I guess there's low
likelyhood of impact outside that, but for testing, to what extent do we
need to consider other flavours that use gnome-greeter?
** Tags added: verification-needed verification-neede
Nice find!
So that's *a* bug, but is it *this* bug?
@mcecs do you have $errors set in your environment?
--
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/2078356
Tit
Looking at
https://launchpad.net/ubuntu/+source/python3.10/3.10.12-1~22.04.6, it
sounds like this was caused by a security update?
** Information type changed from Public to Public Security
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is s
Thank you for your report.
I was unable to reproduce this on Ubuntu. Installing libudev-dev
249.11-0ubuntu3.6 seems to work just fine. I tried both an Ubuntu cloud
image in a container, and a fresh desktop image in a VM. Log attached.
Your "Proof that is not Mint's fault" doesn't demonstrate that
** Tags removed: server-next
** Tags added: server-todo
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openldap in Ubuntu.
https://bugs.launchpad.net/bugs/2000817
Title:
Wrong SHA256-value computed on kinetic
Status in op
The verification of the Stable Release Update for cyrus-sasl2 has
completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encount
The verification of the Stable Release Update for cyrus-sasl2 has
completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encount
Hello Julian, or anyone else affected,
Accepted apt into jammy-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/apt/2.4.9 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Tes
Thank you for working on this!
What's the plan for Kinetic? Please see:
https://wiki.ubuntu.com/StableReleaseUpdates#Newer_Releases
If the goal is to make Sinhala text more readable on Ubuntu, please
could you make that an additional part of the Test Plan, instead of only
checking the order of ou
Thank you for the updates! It looks like you responded appropriately to
all of my points, but I'd like to clarify one thing about version
numbers and Kinetic.
> If a user with an updated jammy (including this fix) upgrades to
kinetic, they will still have version 0.219.1 of the language-selector-*
Hello Aurora, or anyone else affected,
Accepted language-selector into jammy-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/language-
selector/0.219.1 in a few hours, and then in the -proposed repository.
Please help us by testing this new package.
Hello Aurora, or anyone else affected,
Accepted language-selector into kinetic-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/language-
selector/0.219.22.10.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new pa
The verification of the Stable Release Update for python-apt has
completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounte
Since the SRU team -approved Test Plan was to rely on autopkgtest, and
autopkgtests are showing all passed, we can consider this bug verified
for those releases.
** Tags removed: verification-needed verification-needed-jammy
verification-needed-kinetic
** Tags added: verification-done verificatio
1 - 100 of 1261 matches
Mail list logo
