Patch updated.
** Patch removed: "disable-phone-home.patch"
https://bugs.launchpad.net/ubuntu/+source/rclone-browser/+bug/2059246/+attachment/5870479/+files/disable-phone-home.patch
** Patch added: "disable-phone-home.patch"
https://bugs.launchpad.net/ubuntu/+source/rclone-browser/+bug/20
I filed a bug against the package in Debian:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1102487
** Bug watch added: Debian Bug tracker #1102487
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1102487
** Also affects: rclone-browser (Debian) via
https://bugs.debian.org/cgi-bin/bugre
I didn't specify that the patch is against Plucky. I agree that this
should be SRU'd to Noble, but that needs to come later.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059246
Title:
packaged ver
It looks like the phone home behaviour is configurable, and defaults to
"true" in src/preferences_dialog.cpp:
ui.checkRcloneBrowserUpdates->setChecked(
settings->value("Settings/checkRcloneBrowserUpdates", true).toBool());
ui.checkRcloneUpdates->setChecked(
settings->value("Settings/ch
I posted this in Matrix yesterday (didn't have my Launchpad login
handy):
Thank you for doing this and I completely agree - I’ve sought fixes for
similar issues myself. It looks like this will drop the notice but
presumably there’s still an issue with a privacy leak while the tool
“phones home” th
The verification of the Stable Release Update for geeqie 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
Also I think this needs removing from jammy-proposed?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2089830
Title:
[SRU] Make add-nvidia-repositories available in jammy and noble
To manage notifica
I filed removal bug 2103602.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2089830
Title:
[SRU] Make add-nvidia-repositories available in jammy and noble
To manage notifications about this bug go t
> for example, where api.snapcraft.io might currently time out
Oh, and there's another case to check timeout lengths - where DNS times
out before a connection is attempted.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.
This is a very well written up SRU. Thank you! I have three review
points:
1. Since this involves impact to a specific Internet service, please
document sign-off from the operators of api.snapcraft.io that they are
happy with this change. I guess it may triple service load but
specifically at the
Hello appe, or anyone else affected,
Accepted apparmor into noble-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/apparmor/4.0.1really4.0.1-0ubuntu0.24.04.4
in a few hours, and then in the -proposed repository.
Please help us by testing this new packa
This seems like an appropriate fix for future releases. However, is it
appropriate for SRU? Won't it change existing behaviour for existing
users?
> We happened to have some devices having Mic Mute key untranslated by
hwdb, typically we just add entries in hwdb to fix the issue
This seems like a
Hello Marcus, or anyone else affected,
Accepted nautilus into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/nautilus/1:42.6-0ubuntu2 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https:/
Hello Dirk, or anyone else affected,
Accepted libfprint into oracular-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/libfprint/1:1.94.8+tod1-0ubuntu2~24.10.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new pac
Hello Dirk, or anyone else affected,
Accepted libfprint into noble-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/libfprint/1:1.94.7+tod1-0ubuntu5~24.04.3
in a few hours, and then in the -proposed repository.
Please help us by testing this new packag
> ...if I fix all the reported bugs and maintaining and verify
checksums, it'd be worthwhile to have it in the archive
But why isn't this going to be inside add-apt-repository instead, then,
which is bug 2100496?
--
You received this bug notification because you are a member of Ubuntu
Bugs, whic
Public bug reported:
Due to:
Misuse of /tmp could result in root privilege escalation: bug 2100494
Poor guarantees of authenticity and origin: bug 2100495
Duplicates functionality of add-apt-repository: bug 2100496
Please remove src:add-nvidia-repositories from Plucky, as agreed in bug
2089830.
Next steps: I think the private test suite question is still
hypothetical at the moment, since there are so many other open issues
that currently sound like they invalidate this SRU. Please revise the
analysis in this bug to cover all other issues, so that the only review
point remaining is that a
PS. my previous comment is me reviewing this upload as an individual
member of the SRU team. It is not an opinion of the entire SRU team or
the Technical Board.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
> as the mofed dkms is "hard" to test and can only be done in an LTS
Why is this the case, please?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/213
Title:
backport mofed-modules-24.10 24.10.1.
> given that this also could qualify as an HWE upload as explained?
On your "HWE exception" claims, let me be clear. If an SRU upload
*contains* a hardware enablement as part of other changes, that does not
automatically give the other changes a free pass. The other changes
would require SRU justi
> What should we do with the package in Plucky though?
Seems to me it should be removed unless there is a good reason to keep
it. That will save the burden of maintaining a tool in a stable release
if there is no long term intention to keep this specific mechanism (as
opposed to a better integrate
"Remove apt-xapian-index" from where? The Ubuntu archive entirely? Or
just seeds? I see that it exists in Debian and while orphaned it doesn't
have an RM bug filed against it. So it'll just autosync back, no? Or are
you proposing to sync blocklist it as well? What's the justification for
diverging
Ping. Any plans to address the above, please, or should I reject this
from the queue if nobody is driving this any more?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2087832
Title:
qatengine - fix
Here are my comments - sorry I think this got double-reviewed since
Frank asked through multiple channels:
> QEMU part of this enablement work is tracked in bug #2049698
It'd be better to track these items together in one bug with multiple
bug tasks. But either way, if this part is dependent on t
An upload of libfprint to noble-proposed has been rejected from the
upload queue for the following reason: "Not a minimal cherry-pick; see
https://bugs.launchpad.net/ubuntu/+source/libfprint/+bug/2097831/comments/9";.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Note that this wasn't a complete review - I'm struggling to do that
without the context I would get from understanding the problem that
you're wanting to fix.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/b
I'm sorry, I still do not understand your Test Plan well enough that I'd
be able to execute it and understand which specific kernels and out-of-
tree drivers in Noble this means, and which combinations you intend to
test.
--
You received this bug notification because you are a member of Ubuntu
Bu
> Also all that list is fully tested by libfprint test suite, so that if
one string is missing the build will fail, reason why reordering them is
completely fine.
And in that case, why isn't the patch adjusting the test suite?
Apparently you can add these IDs without the test suite needing
adjusti
An upload of magnum to jammy-proposed has been rejected from the upload
queue for the following reason: "No response to
https://bugs.launchpad.net/ubuntu/+source/magnum/+bug/2038109/comments/25";.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
An upload of magnum to focal-proposed has been rejected from the upload
queue for the following reason: "No response to
https://bugs.launchpad.net/ubuntu/+source/magnum/+bug/2038109/comments/25";.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
> not doing it now it implies that all next cherry-picks will be more
annoying to do and more risky
Oh come on. You're adding some device IDs, that's all. Fixing a merge
conflict will take all of one minute, and the result will be easily
reviewable. I *think* you're just adding two, since that's w
An upload of libfprint to oracular-proposed has been rejected from the
upload queue for the following reason: "Not a minimal cherry-pick; see
https://bugs.launchpad.net/ubuntu/+source/libfprint/+bug/2097831/comments/9";.
--
You received this bug notification because you are a member of Ubuntu
Bug
I see a technical analysis of the change that you're wanting to make
under "Impact", but no actual explanation of an issue with an impact to
users.
For example, why is it that watcher's use of the deprecated ceilometer
metric, cpu_util, which reported cpu utilization as a percentage, is a
problem
(I've spent a few minutes trying to interpret it to infer this
information, and I couldn't)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2092139
Title:
Rename media device as ipu6-downstream in Nob
> A new 24.10 minor version has been released from upstream, and should
be backported under the HWE exception.
No, those are two different exceptions. If you're doing hardware
enablement, then this bug should be titled something like "hardware X
not supported", and then the impact to users would b
> If you're fixing bugs
If you're fixing bugs by choosing to take a new upstream bugfix release,
that is, rather than cherry-picking, then
https://documentation.ubuntu.com/sru/en/latest/reference/requirements/#new-
upstream-microreleases applies, and you should document how it is that
upstream mee
> The patch is now in plucky but needs to be backported to noble and
oracular (TPM backed desktop systems could be affected).
There doesn't seem to be an upload for Oracular? See:
https://documentation.ubuntu.com/sru/en/latest/reference/requirements/#reference-
general-requirements "Any fix or fea
Is this fixed in Plucky? I can't tell from this bug. See:
https://documentation.ubuntu.com/sru/en/latest/reference/requirements/#reference-
general-requirements
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
regression-update not regression-updates. See
https://wiki.ubuntu.com/Bugs/Tags. Otherwise people do not get emailed!
** Tags removed: regression-updates
** Tags added: regression-update
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hello Skia, or anyone else affected,
Accepted libapache2-mod-python into jammy-proposed. The package will
build now and be available at
https://launchpad.net/ubuntu/+source/libapache2-mod-
python/3.5.0+git20211031-0ubuntu3 in a few hours, and then in the
-proposed repository.
Please help us by te
FTR, 3.5.0+git20211031-0ubuntu2 was staged with an autopkgtest fix. This
upload incorporates that, and there's no need for a re-mention in the
changes file since they are two distinct accepted uploads.
** Changed in: libapache2-mod-python (Ubuntu Jammy)
Status: Confirmed => Fix Committed
*
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
FTR, I got OOPS-19e1f6d2b782c10bafdc13447cecb2bd, so I "re-released"
both Oracular and Noble since it didn't tell me which the OOPS was for.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2097546
Title
Thank you to those who have already tested the patch for Noble
independently of Ubuntu's build of it. That gives us confidence that the
patch is what we need.
Please note though that we also need to test the final proposed binary
build of the fix, which will be available soon. Your further testing
Hello Sitsofe, or anyone else affected,
Accepted bluez into noble-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/bluez/5.72-0ubuntu5.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki
The SRU team was asked to consider this. We have discussed this amongst
the SRU team.
It is a longstanding policy position of the Ubuntu project that hardware
enablements are only permitted in stable releases if newer releases are
also enabled, to avoid breaking users in hardware support on upgrad
From bug 2089830, "The tool is currently included in non-packaged form
in some cloud images produced by https://launchpad.net/~cloud-images
team", so this bug also applies to cloud images in their own right and
will also need fixing independently in the duplicated code present
there.
** Also affec
From bug 2089830, "The tool is currently included in non-packaged form
in some cloud images produced by https://launchpad.net/~cloud-images
team", so this bug also applies to cloud images in their own right and
will also need fixing independently in the duplicated code present
there.
** Also affec
Thank you for the feedback! This bug is rapidly getting overloaded so
I've filed separate bugs to track these:
Misuse of /tmp could result in root privilege escalation: bug 2100494
Poor guarantees of authenticity and origin: bug 2100495
Duplicates functionality of add-apt-repository: bug 2100496
From bug 2089830, "The tool is currently included in non-packaged form
in some cloud images produced by https://launchpad.net/~cloud-images
team", so this bug also applies to cloud images in their own right and
will also need fixing independently in the duplicated code present
there.
** Also affec
*** This bug is a security vulnerability ***
Public security bug reported:
From https://bugs.launchpad.net/ubuntu/+source/add-nvidia-
repositories/+bug/2089830/comments/5:
> wget "$keyring_url" -O /tmp/cuda-keyring.deb
> dpkg -i /tmp/cuda-keyring.deb
> rm /tmp/cuda-keyring.deb
>
> That's a c
*** This bug is a security vulnerability ***
Public security bug reported:
From https://bugs.launchpad.net/ubuntu/+source/add-nvidia-
repositories/+bug/2089830/comments/8 by Seth Arnold:
> I strongly dislike this mechanism. We should strive to provide better
> guarantees of authenticity and ori
Public bug reported:
From https://bugs.launchpad.net/ubuntu/+source/add-nvidia-
repositories/+bug/2089830/comments/6
Can this functionality not be added to software-properties-common using
add-apt-repository, instead of adding yet another package? We already
have some "third party" repositories s
Can this functionality not be added to software-properties-common using
add-apt-repository, instead of adding yet another package? We already
have some "third party" repositories supported that way, for example the
Canonical Cloud Archive.
Please do not SRU this until that question is resolved, si
The bug title is much better - thanks. The test plan you describe in
comment 15 is much better, but I think there are a couple of things
still needed, please. Since this is hardware specific, what matrix of
hardware are you intending to test? For example, if using ffmpeg, then
are you testing both
An upload of nspr to noble-proposed has been rejected from the upload
queue for the following reason: "No response to
https://bugs.launchpad.net/ubuntu/+source/nspr/+bug/2084460/comments/4
in months".
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
More here: https://documentation.ubuntu.com/sru/en/latest/howto/common-
issues/#upload
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2097831
Title:
Support Synaptics fingerprint device with ID 06cb:
An upload of backport-iwlwifi-dkms to noble-proposed has been rejected
from the upload queue for the following reason: "Insufficient
justification for SRU; see
https://bugs.launchpad.net/ubuntu/+source/backport-iwlwifi-
dkms/+bug/2046871/comments/14".
--
You received this bug notification because
> also fine tune PID sequence
Please make this a minimal cherry-pick, or otherwise justify why
changing the sequence is required in an SRU. See:
https://documentation.ubuntu.com/sru/en/latest/reference/requirements/#general-
requirements-for-all-srus "Changes must be minimal" and
https://documenta
** Merge proposal linked:
https://code.launchpad.net/~oded-geek/ubuntu/+source/apt-btrfs-snapshot/+git/apt-btrfs-snapshot/+merge/470734
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064274
Title:
Thank you for your report.
You can find pointers to get help for this sort of problem here:
http://www.ubuntu.com/support/community
If it turns out that your issue is a bug in Ubuntu, then we need a full
bug report please. Until then, we can't make any progress on this
report, and you won't find
What's the justification for SRU here please? What's the actual impact
on users? See:
https://documentation.ubuntu.com/sru/en/latest/explanation/requirements/#real-
world-impact
> The code is only called on termination...
If that's where the fix is, how will it benefit users? Or if there's a
gene
I don't see an upload for Oracular?
"To avoid regressions on upgrade, any such hardware enablement must
first also be added to any newer supported Ubuntu release." from
https://documentation.ubuntu.com/sru/en/latest/reference/requirements/#reference-
criteria-hardware
This SRU is blocked on an Or
> Since the new package isn't in the archive yet, we have to install
these separately.
Please *do not* install these from a PPA for the purposes of SRU
verification. If this is necessary then you're not really testing what
would land in the SRU, and there is no real justification for a hardware
en
Hello Lena, or anyone else affected,
Accepted valkey into noble-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/valkey/7.2.8+dfsg1-0ubuntu0.24.04.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
FTR:
$ sru-review --no-browser --no-diff -s oracular valkey
Accept the package into -proposed? [yN] y
Accepted
Success: task
https://bugs.launchpad.net/ubuntu/oracular/+source/valkey/+bug/2097546
in bug 2097546
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/lazr/restfu
I assume that this should be Fix Released for the development release -
the issues being fixed by this update are already fixed in your recent
merge for Plucky?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
Considering the requirements at
https://documentation.ubuntu.com/sru/en/latest/reference/requirements/#new-
upstream-microreleases, looks like upstream CI is running against the
PRs referenced, you've spoken to upstream test coverage, the tests are
running during the package build, and dep8 coverag
> The userspace framework has to be compatible with all kernels, and
therefore all ipu6 kernel driver revisions, available in Noble.
This sounds correct to me, but could you please expand on which specific
kernels and out-of-tree drivers in Noble this means, please, and then
clarify in the Test Pl
> The Intel media driver needs a version update to fully support
Battlemage in 24.4.4
In that case, please add a test for full support of Battlemage to the
Test Plan. If that's the purpose of the update, then we should be
testing that before release. If it doesn't work, then we'd be creating
churn
See also: https://documentation.ubuntu.com/sru/en/latest/howto/common-
issues/#test-plan and
https://documentation.ubuntu.com/sru/en/latest/explanation/further-
requirements/#detail-in-test-plans
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Does the current Jammy upload also need rejecting from Unapproved, then?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2096327
Title:
apport cannot upload blobs to launchpad - X-Launchpad-Blob-Token
Tag FTR.
** 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/2097317
Title:
bpftrace: error while loading shared libraries: libLLVM-18.so.18.1:
cannot open shared objec
** Description changed:
[Impact]
In 24.04, we shipped sysstat by default as part of a wider performance
engineering effort. The idea is that relevant performance engineering
tooling is already present and available when a user finds themselves
needing to solve a performance engineerin
** Description changed:
[Impact]
In 24.04, we shipped sysstat by default as part of a wider performance
engineering effort. The idea is that relevant performance engineering
tooling is already present and available when a user finds themselves
needing to solve a performance engineerin
** Description changed:
[Impact]
When the sysstat package is pre-installed, for example on a fresh Ubuntu
24.04 installation in any cloud image, systemd presets activate the
various sysstat systemd services, even when /etc/default/sysstat sets
ENABLED="false".
This causes a diver
A couple of thoughts, though maybe too late to be worth amending now:
1) I'd treat `systemctl is-system-running --wait` as the default, and
make all older methods as conditional exceptions for releases that
require it.
2) Checking VERSION_ID is invalid unless ID is validated to be "ubuntu".
I don
FWIW I think this is a fair question.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2091859
Title:
RM: remove git-ubuntu [source, binaries]
To manage notifications about this bug go to:
https://bug
> I introduced the Debian package after talking with Robie and he had
nothing against it.
IMHO, if someone wants to maintain any package, whether in Debian or
Ubuntu, they should be welcome to do so provided that they do maintain
it according to our usual standards. That's my opinion generally but
This is in sync with Debian now, at 0.27.0-1.
** Changed in: python-trio (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2076530
Title:
Please merge 0.25.0
The bug title is "Ubuntu apt repos are not available via HTTPS", the
description says "it does not seem to be possible to retrieve core
Ubuntu packages or security updates via TLS", and as far as I can see,
that hasn't changed since the bug was filed, and as written, precisely
that is what is now r
Release of this update is blocked on someone doing the QA for bug
2076152, with which this fix is bundled.
--
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 regression i
The FTBFS is fixed. No further verification required.
** Tags removed: verification-needed verification-needed-noble
** Tags added: verification-done verification-done-noble
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
Hello Karl-Philipp, or anyone else affected,
Accepted apport into noble-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/apport/2.28.1-0ubuntu3.3 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
htt
I've reviewed the changes from 2.28.1-0ubuntu3.2 to 2.28.1-0ubuntu3.3
and they're fine from an SRU perspective since they only tweak the dep8
test. I see that the upload of 2.28.1-0ubuntu3.3 uses -v as expected, so
I'm accepting it to squash into the in-flight SRU without re-review of
what's alread
Hello Benjamin, or anyone else affected,
Accepted apport into noble-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/apport/2.28.1-0ubuntu3.3 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https:/
Hello Benjamin, or anyone else affected,
Accepted apport into noble-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/apport/2.28.1-0ubuntu3.3 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https:/
Hello Chris, or anyone else affected,
Accepted apport into noble-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/apport/2.28.1-0ubuntu3.3 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wi
Hello Jānis, or anyone else affected,
Accepted apport into noble-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/apport/2.28.1-0ubuntu3.3 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wi
Hello errors.ubuntu.com, or anyone else affected,
Accepted apport into noble-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/apport/2.28.1-0ubuntu3.3 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. Se
SRU review for Noble: in progress.
The upload references 17 bugs and since they all follow the regular SRU
process, there's no "tracking bug" as such where I can comment on the
review as a whole. This is a shortcoming in our current workflow. I
decided to arbitrarily choose the lowest numbered bug
** Tags added: server-todo
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2083986
Title:
Live migration fails because VMX features are missing on target cpu
definition
To manage notifications abou
I was concerned that changing the default KDF for existing Ubuntu 22.04
users for FIPS reasons seemed inappropriate because some users might
object to that if (depending on their security perspective and who they
trust) they consider PBKDF2 to be a KDF downgrade. I appreciate that
upstream changed
This was fixed in 8.0.29 and therefore fixed in all supported Ubuntu
releases.
** Changed in: mysql-8.0 (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/19
An upload of cyrus-sasl2 to noble-proposed has been rejected from the
upload queue for the following reason: "See
https://bugs.launchpad.net/ubuntu/+source/cyrus-
sasl2/+bug/2078851/comments/16".
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I think this is blocked on mailman-hyperkitty which needs a special
SRU+AA review and that is in a review queue that isn't routinely
monitored. I'll add it to a list to mention to somebody who can do the
review.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
I see that 5.3.0-1 in Oracular does contain the fix.
** Changed in: lxml (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2076419
Title:
lxml: Doe
Hello Julian, or anyone else affected,
Accepted lxml into noble-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/lxml/5.2.1-1ubuntu0.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.u
For the Test Plan, I had asked in comment 1:
> ...specify what the output should look like
I've added something suitable for you. I guess this is what you intend?
It's important to be clear in case you're unavailable and someone else
needs to do the SRU verification, or if there's a regression fo
1 - 100 of 1560 matches
Mail list logo
