Uploaded.
** Changed in: ubuntu-advantage-tools (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/2083665
Title:
ubuntu-pro-client has an unnecessary depend
On Tue, Aug 27, 2024 at 04:35:45PM +0100, Robie Basak wrote:
> Since there's no further feedback, I’ll ask the Technical Board to make
> the draft policy above final at their (our) next meeting, which is later
> today at 1900 UTC. See the agenda[1] for details (which I’ll update
&g
On Tue, Aug 27, 2024 at 04:35:45PM +0100, Robie Basak wrote:
> Since there's no further feedback, I’ll ask the Technical Board to make
> the draft policy above final at their (our) next meeting, which is later
> today at 1900 UTC. See the agenda[1] for details (which I’ll update
&g
I had a thought so leaving a note here. I'm not sure how valid this is.
src:ubuntu-advantage-tools has a strong aversion to adding new
dependencies due to the difficulties in backporting that. So if this is
removed now, it is very difficult to re-add later should it be needed.
So a question for th
> 1. > There are spurious development artifacts being added
> I have looked through the debdiffs and couldn't find such, are you
referring to the "Maintainer" and "XSBC-Original-Maintainer" section
maybe?
Not the debdiffs, the actual upload. For example, from the Rejected
queue, http://launchpadl
> 1. > There are spurious development artifacts being added
> I have looked through the debdiffs and couldn't find such, are you
referring to the "Maintainer" and "XSBC-Original-Maintainer" section
maybe?
Not the debdiffs, the actual upload. For example, from the Rejected
queue, http://launchpadl
On Fri, Oct 04, 2024 at 11:08:32AM +0100, Robie Basak wrote:
> I accepted openvpn updates to Focal, Jammy and Noble. The Focal and
Correction: just Jammy and Noble. But my example works for the Jammy
case below:
> openvpn | 2.4.7-1ubuntu2 | focal | source
> openvpn
On Fri, Oct 04, 2024 at 11:49:32AM +0200, Matthias Klose wrote:
> I don't think this is necessary when the .orig tarball already is in the
> archive for a newer release. Which extra checks do you want to perform?
I think there is still some benefit when the stable updates are arriving
very closel
See comment 5 above. Progress is blocked on someone doing the
appropriate testing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1992108
Title:
[SRU] python3-build cannot create venv virtual environ
Hello Bryce, or anyone else affected,
Accepted openvpn into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/openvpn/2.5.11-0ubuntu0.22.04.1 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
ht
Hello Bryce, or anyone else affected,
Accepted openvpn into noble-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/openvpn/2.6.12-0ubuntu0.24.04.1 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
ht
Hello Dave, or anyone else affected,
Accepted mesa into noble-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/mesa/24.0.9-0ubuntu0.2
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ub
Hello Dave, or anyone else affected,
Accepted mesa into noble-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/mesa/24.0.9-0ubuntu0.2
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ub
Hello Dave, or anyone else affected,
Accepted mesa into noble-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/mesa/24.0.9-0ubuntu0.2
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ub
Hello Dave, or anyone else affected,
Accepted mesa into noble-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/mesa/24.0.9-0ubuntu0.2
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ub
Leaving my draft here both so you can read it and so I don't lose it:
> Indeed, the reason for this is that in authd we are presenting a
qrcode to perform weblogin and that doesn't work.
This seems a reasonable justification for an SRU in principle then, now
that it's documented. Thank you for th
Leaving my draft here both so you can read it and so I don't lose it:
> Indeed, the reason for this is that in authd we are presenting a
qrcode to perform weblogin and that doesn't work.
This seems a reasonable justification for an SRU in principle then, now
that it's documented. Thank you for th
The final upload to Noble unapproved cherry-picks the required fixes
rather than bumping to 24.2, right? So this bug is presumably better
described for the actual problem being solved rather than one presumed
solution that is no longer the plan?
** Summary changed:
- [SRU] Mesa bump to 24.2 requi
The final upload to Noble unapproved cherry-picks the required fixes
rather than bumping to 24.2, right? So this bug is presumably better
described for the actual problem being solved rather than one presumed
solution that is no longer the plan?
** Summary changed:
- [SRU] Mesa bump to 24.2 requi
The final upload to Noble unapproved cherry-picks the required fixes
rather than bumping to 24.2, right? So this bug is presumably better
described for the actual problem being solved rather than one presumed
solution that is no longer the plan?
** Summary changed:
- [SRU] Mesa bump to 24.2 requi
The final upload to Noble unapproved cherry-picks the required fixes
rather than bumping to 24.2, right? So this bug is presumably better
described for the actual problem being solved rather than one presumed
solution that is no longer the plan?
** Summary changed:
- [SRU] Mesa bump to 24.2 requi
Hello errors.ubuntu.com, or anyone else affected,
Accepted update-manager into noble-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/update-
manager/1:24.04.9 in a few hours, and then in the -proposed repository.
Please help us by testing this new pac
(this is "Test Plan only covers the fix, and not general use of the
package to make sure that it still works after the update. A smoke test
will suffice. If that’s implied by verifying the bug is fixed then it’s
not needed as a separate step" from https://canonical-sru-
docs.readthedocs-hosted.com/
This looks fine, but please also add to the Test Plan a test to ensure
that update-manager still basically works (ie. can update packages in
the default scenario). If this is already covered by automation, then
please point to the appropriate test.
--
You received this bug notification because yo
Hello Jon, or anyone else affected,
Accepted shotwell into noble-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/shotwell/0.32.6-1ubuntu2 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wi
Hello Jon, or anyone else affected,
Accepted shotwell into noble-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/shotwell/0.32.6-1ubuntu2 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wi
You could have fixed the test plan as I requested instead of
complaining?
FYI, you can find the upload in the rejected queue. The SRU team can
even accept from the rejected queue. It should be minimal work to do
this.
On the other hand the current SRU workflow requires SRU team members to
continu
SRU review
1. Is this bug that saslauthd doesn't work in Noble at all because the
permissions are wrong? Or only in certain circumstances, and in which
case, which ones?
2. Is it possible that somebody is successfully using saslauthd running
as root, and changing the group of the service to sasl
SRU review
1. Is this bug that saslauthd doesn't work in Noble at all because the
permissions are wrong? Or only in certain circumstances, and in which
case, which ones?
2. Is it possible that somebody is successfully using saslauthd running
as root, and changing the group of the service to sasl
Hello prusswan, or anyone else affected,
Accepted indicator-keyboard into noble-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/indicator-
keyboard/0.0.0+19.10.20220803-0ubuntu3.1 in a few hours, and then in the
-proposed repository.
Please help us by
> Test Plan
Please could you amend this to verify that indicator-keyboard still
works correctly in a basic use case?
** Changed in: indicator-keyboard (Ubuntu Noble)
Status: Confirmed => Fix Committed
** Tags added: verification-needed verification-needed-noble
--
You received this bug
Hello Ian, or anyone else affected,
Accepted neon27 into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/neon27/0.32.2-1ubuntu0.1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki
Thank you for contributing the fix for this!
The changes look good to me and I'll accept these into jammy-proposed
shortly.
I would like a couple of things thought about with regard to testing
though please:
1) It's a hard requirement that a test be performed to ensure that the
package still wor
Hello Ian, or anyone else affected,
Accepted neon27 into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/neon27/0.32.2-1ubuntu0.1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki
Thank you for contributing the fix for this!
The changes look good to me and I'll accept these into jammy-proposed
shortly.
I would like a couple of things thought about with regard to testing
though please:
1) It's a hard requirement that a test be performed to ensure that the
package still wor
Hello Ian, or anyone else affected,
Accepted neon27 into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/neon27/0.32.2-1ubuntu0.1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki
Thank you for contributing the fix for this!
The changes look good to me and I'll accept these into jammy-proposed
shortly.
I would like a couple of things thought about with regard to testing
though please:
1) It's a hard requirement that a test be performed to ensure that the
package still wor
If we take a fresh upstream release directly into a stable release
update, then it seems to me that it's important to validate that the
orig tarball matches what upstream released, or is otherwise
reproducible against what upstream released (eg. if it was repacked for
the usual reasons).
It's not
The verification of the Stable Release Update for valkey 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 r
I suggest cancelling our meeting scheduled on 2024-10-22, since a number
of Canonical staff who are TB members will be occupied at an internal
event.
Or are sufficient TB members not at that event such that it's worth
holding a meeting anyway?
Robie
signature.asc
Description: PGP signature
--
gt; System components.
- Fix Ubuntu Pro item not being a parent group of its corresponding
packages.
- Fix incorrect available version for Ubuntu Pro updates in unattached case
(LP: #2043425).
Date: 2024-06-26 09:15:09.302684+00:00
Changed-By: Nathan Teodosio
Signed-B
The verification of the Stable Release Update for lxd-agent-loader 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 en
Thanks! I think update-manager in xenial-proposed is ready to be
released then, except there was a dep8 tmpfail. I've retried it; just
waiting for that to filter through to the pending-sru report to be sure
it's good.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
The verification of the Stable Release Update for update-manager 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 enco
This bug tracks a problem with the dist-upgrade prompt, and the test
plan says "...if a newer LTS is available, suggest to the user to update
to it". This seems like the most essential thing to verify in order to
check that this bug is fixed, but according to your verification report
you didn't che
** Tags removed: verification-needed verification-needed-noble
** Tags added: verification-failed verification-failed-noble
--
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/
** Tags removed: verification-needed verification-needed-noble
** Tags added: verification-failed verification-failed-noble
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2081334
Title:
further perfo
The fix for this is in oracular-proposed.
** Changed in: mercurial (Ubuntu)
Status: Confirmed => 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/2081117
Title:
Mercurial FTBFS wi
Is this the same as https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=1082373 ? nginx-common and nginx have (I think
incorrectly) a dependency loop, which gets broken by dpkg. If nginx-
common isn't configured first, then the nginx postinst fails. The
solution is to fix the dependency loop which I
The following subscriptions are missing:
valkey
Missing subscriptions added
--
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam
> [SRU Justification]
> [Impact]
> To migrate the a version scheme that is well-known to all parties.
This is the only reason given at the moment, and that's definitely not
sufficient to justify an SRU.
> I couldn't find any SRU exception for backport-iwlwifi-dkms, and I'm
unclear of how it wou
Hello Dave, or anyone else affected,
Accepted mercurial into noble-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/mercurial/6.7.2-1ubuntu2.2 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https:
Hello Gleb, or anyone else affected,
Accepted mercurial into noble-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/mercurial/6.7.2-1ubuntu2.2 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https:
Hello Matthias, or anyone else affected,
Accepted mercurial into noble-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/mercurial/6.7.2-1ubuntu2.2 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
ht
So this failed to build. I know Dave is working on it, but just a note
that the call for testing above is invalid.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2070443
Title:
SRU: Fix critical regr
On Fri, Sep 13, 2024 at 05:20:34PM +0200, Luca Boccassi wrote:
> I think we need to be careful to avoid making our lives unnecessarily
> hard without good reasons.
I agree with this principle. However, I think that given that you're
asking to make changes to a trust root for the purposes of mainta
Hello David, or anyone else affected,
Accepted rally into jammy-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/rally/3.3.0-1ubuntu1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ub
Hello Skia, or anyone else affected,
Accepted retry into jammy-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/retry/1.0.4-3build1 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubun
An upload of lxml to noble-proposed has been rejected from the upload
queue for the following reason: "No response to review feedback in over
a month.".
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/20
Hello Gunnar, or anyone else affected,
Accepted egl-wayland into jammy-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/egl-
wayland/1:1.1.9-1.1ubuntu0.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package.
Unsubscribing ~ubuntu-sponsors as there is nothing left to sponsor.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to egl-wayland in Ubuntu.
https://bugs.launchpad.net/bugs/1965563
Title:
GNOME apps crash with "Protocol error" in NVIDIA Wayland
Hello Gunnar, or anyone else affected,
Accepted egl-wayland into jammy-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/egl-
wayland/1:1.1.9-1.1ubuntu0.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package.
Unsubscribing ~ubuntu-sponsors as there is nothing left to sponsor.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1965563
Title:
GNOME apps crash with "Protocol error" in NVIDIA Wayland sessions
To
Hello Skia, or anyone else affected,
Accepted retry into noble-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/retry/1.0.5-3build1~ubuntu0.24.04.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
h
As discussed in #ubuntu-devel right now, it's probably best to avoid
bumping Noble's package version higher than Oracular, so I'll arrange
some tweaks:
No-change rebuild using 1.0.5-3build1~ubuntu0.24.04.1 for Noble.
No-change rebuild using 1.0.5-3build1 for Oracular.
** Changed in: retry (Ubunt
As discussed in #ubuntu-devel right now, it's probably best to avoid
bumping Noble's package version higher than Oracular, so I'll arrange
some tweaks:
No-change rebuild using 1.0.5-3build1~ubuntu0.24.04.1 for Noble.
No-change rebuild using 1.0.5-3build1 for Oracular.
** Changed in: retry (Ubunt
SRU review:
1) debian/patches/egl-wayland-retrieve-DRM-device-name-before-
acquiring-.patch is being modified for no good reason (at least, it
isn't documented) and the dep3 headers are being dropped. Please explain
or fix.
2) Not essential, but the expected package version string would be
1:1.1.
SRU review:
1) debian/patches/egl-wayland-retrieve-DRM-device-name-before-
acquiring-.patch is being modified for no good reason (at least, it
isn't documented) and the dep3 headers are being dropped. Please explain
or fix.
2) Not essential, but the expected package version string would be
1:1.1.
Hello Gleb, or anyone else affected,
Accepted mercurial into noble-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/mercurial/6.7.2-1ubuntu2.1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https:
Hello Matthias, or anyone else affected,
Accepted mercurial into noble-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/mercurial/6.7.2-1ubuntu2.1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
ht
Based on the upload of mercurial to noble-proposed unapproved, this bug
is intended to cover _all_ bad Mercurial interactions with Python 3.12,
is it? Should it be renamed?
FTR, I found the change to tests/test-profile.t alarming at first, but
then I followed the trail to
https://github.com/python
Alessandro informs me that this was caused by some combination of kernel
6.8.0 and a nvidia-driver-550 update, so tagging regression-update, and
I'll review the proposed fix next.
** Tags added: regression-update
--
You received this bug notification because you are a member of Ubuntu
Bugs, whic
Alessandro informs me that this was caused by some combination of kernel
6.8.0 and a nvidia-driver-550 update, so tagging regression-update, and
I'll review the proposed fix next.
** Tags added: regression-update
--
You received this bug notification because you are a member of Ubuntu-X,
which i
** Tags added: regression-update
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to adsys in Ubuntu.
https://bugs.launchpad.net/bugs/2078245
Title:
DCONF policy manager removes userdb on empty policy
Status in adsys package in Ubuntu:
** Tags added: regression-update
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2078245
Title:
DCONF policy manager removes userdb on empty policy
To manage notifications about this bug go to:
https
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
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
Bugs, which is subscribed to Ubun
Following on from the xz-utils code injection, it's clearly critical to
validate binary blobs, so I tried to do that and am recording what I
found here.
https://lists.mercurial-scm.org/pipermail/mercurial-
packaging/2024-August/000737.html is the best validation I could find
for mercurial-6.8.1.ta
[Splitting into more than one sub-thread so that I can reply to some of
this without holding up my entire reply; this sub-thread is about
validation]
On Wed, Sep 11, 2024 at 04:38:27PM +0200, Luca Boccassi wrote:
> Regarding the request for validation, could you please clarify exactly
> what kind
Hi Otto!
On Wed, Sep 04, 2024 at 11:20:48PM -0700, Otto Kekäläinen wrote:
> > You can find the new documentation here[3]:
> > https://canonical-sru-docs.readthedocs-hosted.com/en/latest/
>
> I read all of this and as a person with plenty of Ubuntu stale
> security update experience, reading the S
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2078356
Title:
python3 preinst failure to run
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
The verification of the Stable Release Update for update-manager 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 enco
This leads to a minor inconsistency but I think that's acceptable. I
understand that the desktop team already has code committed (somewhere)
to get this resolved in the future.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bu
I was asked to review the current upload in jammy-proposed for release,
in order to make 22.04.5. I agree with Seb and Nathan that the benefit
of getting what is currently in jammy-proposed into the point release
outweighs the code quality concern I had identified previously. +1 to
release to jammy
Hi,
On Wed, Sep 04, 2024 at 10:51:30AM +0100, Luca Boccassi wrote:
> For developers like myself who work across distributions, it is very
> valuable to have a secure, simple and transparent way to bootstrap one
> distro from another without relying on external trust anchors that
> have to be verif
The following subscriptions are missing:
ruby3.3
Missing subscriptions added
--
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam
I have a long reply to the ML thread half drafted, but haven't had a
chance to finish it yet. I'd appreciate having at least a week to do so,
please.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/20755
Sorry, I think you misunderstand. My comments were aimed at the Ubuntu
developer who prepared an update that was not acceptable for the reasons
I gave. My involvement was as a reviewer to uphold quality standards
within Ubuntu which apply to any change we make in stable Ubuntu
releases. This is nec
We can bump Mercurial up to 6.7.4 in Ubuntu 24.04. However, this
requires someone to take one of the following three paths. See
https://canonical-sru-docs.readthedocs-
hosted.com/en/latest/reference/requirements/#new-upstream-microreleases
1. If all changes being made are acceptable under normal S
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
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
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
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
To be clear:
MySQL and MariaDB remain broadly compatible. Ubuntu has maintained its
status quo in defaulting to MySQL since before MariaDB existed. Users
expect consistency, and this means that packages in Ubuntu should
default to using MySQL over MariaDB unless the user has explicitly
chosen othe
To be clear:
MySQL and MariaDB remain broadly compatible. Ubuntu has maintained its
status quo in defaulting to MySQL since before MariaDB existed. Users
expect consistency, and this means that packages in Ubuntu should
default to using MySQL over MariaDB unless the user has explicitly
chosen othe
> Create a test fitimage and sign with rsa3072 algorithm.
How?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2078395
Title:
[SRU] Add RSA3072 support to jammy
To manage notifications about this b
> mkimage on jammy doesn't support RSA3072.
This does not explain the impact on users. Please explain why the
regression risk of changing a stable release is justified.
** Changed in: u-boot (Ubuntu Jammy)
Status: Confirmed => Incomplete
--
You received this bug notification because you
1 - 100 of 1295 matches
Mail list logo
