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
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
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 José, or anyone else affected,
Accepted php-mailparse into noble-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/php-
mailparse/3.1.4+2.1.7~dev20160128-1ubuntu1.1 in a few hours, and then in
the -proposed repository.
Please help us by testing th
Based on https://git.launchpad.net/ubuntu/+source/php-
mailparse/tree/mailparse-3.1.6/mailparse.c?h=applied/ubuntu/devel#n951
it looks like this already fixed in Oracular.
** Changed in: php-mailparse (Ubuntu)
Status: In Progress => Fix Released
** Changed in: php-mailparse (Ubuntu Noble)
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
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
> If the preference in Ubuntu is to keep using mysql with this package,
someone’s going to need to revert the change in the package that’s been
mirrored for to not only depend on mysql and investigate why it’s not
working or work with upstream to understand why they’re choosing to
depend on mariadb
> If the preference in Ubuntu is to keep using mysql with this package,
someone’s going to need to revert the change in the package that’s been
mirrored for to not only depend on mysql and investigate why it’s not
working or work with upstream to understand why they’re choosing to
depend on mariadb
On Thu, Aug 29, 2024 at 04:08:04PM -, Dave Hibberd wrote:
> The application will not start with MySQL.
If it works with MariaDB but not MySQL, that doesn't necessarily mean
that it only supports MariaDB, or that there's not just a bug that needs
fixing to keep it compatible with both.
> Do af
On Thu, Aug 29, 2024 at 04:08:04PM -, Dave Hibberd wrote:
> The application will not start with MySQL.
If it works with MariaDB but not MySQL, that doesn't necessarily mean
that it only supports MariaDB, or that there's not just a bug that needs
fixing to keep it compatible with both.
> Do af
The upstream website at https://www.cqrlog.com/ says:
> CQRLOG is an advanced ham radio logger based on MySQL database.
In Ubuntu, we default to MySQL. I think switching to MariaDB by default
requires exceptional justification, such as the upstream and codebase
very clearly not being able to func
The upstream website at https://www.cqrlog.com/ says:
> CQRLOG is an advanced ham radio logger based on MySQL database.
In Ubuntu, we default to MySQL. I think switching to MariaDB by default
requires exceptional justification, such as the upstream and codebase
very clearly not being able to func
OK, but how does this relate to the upload in Jammy unapproved that
disables the test outright?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/2077654
Title:
Race condit
OK, but how does this relate to the upload in Jammy unapproved that
disables the test outright?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2077654
Title:
Race condition on builders result in 100%
Steve has been unavailable unfortunately. In his absence, I'm inclined
to follow my opinion in the previous comment. Third party software is
expected to be rebuilt against the soname used in 24.04, since we do not
provide ABI compatibility across releases.
If the soname does actually go back upstr
** 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
** Tags added: regression-release
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2003027
Title:
fq_codel qdisc compiled but not enabled on 22.10
To manage notifications about this bug go to:
https:/
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
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
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
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
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
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
I'm rejecting two uploads for Noble because they collide between bug
2077746 and bug 2025006 (amongst others). Please coordinate and re-
upload just one SRU at once (possibly squashing multiple fixes together
as you wish).
** Changed in: mutter (Ubuntu Noble)
Status: In Progress => Triaged
I'm rejecting two uploads for Noble because they collide between bug
2077746 and bug 2025006 (amongst others). Please coordinate and re-
upload just one SRU at once (possibly squashing multiple fixes together
as you wish).
** Changed in: mutter (Ubuntu Noble)
Status: In Progress => Triaged
I'm rejecting two uploads for Noble because they collide between bug
2077746 and bug 2025006 (amongst others). Please coordinate and re-
upload just one SRU at once (possibly squashing multiple fixes together
as you wish).
** Changed in: mutter (Ubuntu Noble)
Status: In Progress => Triaged
I'm rejecting two uploads for Noble because they collide between bug
2077746 and bug 2025006 (amongst others). Please coordinate and re-
upload just one SRU at once (possibly squashing multiple fixes together
as you wish).
** Changed in: mutter (Ubuntu Noble)
Status: In Progress => Triaged
I'm rejecting two uploads for Noble because they collide between bug
2077746 and bug 2025006 (amongst others). Please coordinate and re-
upload just one SRU at once (possibly squashing multiple fixes together
as you wish).
** Changed in: mutter (Ubuntu Noble)
Status: In Progress => Triaged
I'm rejecting two uploads for Noble because they collide between bug
2077746 and bug 2025006 (amongst others). Please coordinate and re-
upload just one SRU at once (possibly squashing multiple fixes together
as you wish).
** Changed in: mutter (Ubuntu Noble)
Status: In Progress => Triaged
An upload of libmbim to noble-proposed has been rejected from the upload
queue for the following reason: "Rejecting as agreed with @kchsieh,
pending the full SRU.".
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libmbim in Ubuntu.
https:
An upload of libmbim to noble-proposed has been rejected from the upload
queue for the following reason: "Rejecting as agreed with @kchsieh,
pending the full SRU.".
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
An upload of libcrypto++ to focal-proposed has been rejected from the
upload queue for the following reason: "Blocked on
https://bugs.launchpad.net/ubuntu/+source/libcrypto++/+bug/2064751/comments/7
for over a month".
--
You received this bug notification because you are a member of Ubuntu
Bugs,
From IRC (#ubuntu-release):
13:14 tjaalton: for bug 2060268, are there any cases where the
udev rule would be triggered but is the wrong thing to do? How certain
are we on that point?
13:14 tjaalton: presumably the Test Plan should specify testing
on particular hardware? That needs adjusting. B
From IRC (#ubuntu-release):
13:14 tjaalton: for bug 2060268, are there any cases where the
udev rule would be triggered but is the wrong thing to do? How certain
are we on that point?
13:14 tjaalton: presumably the Test Plan should specify testing
on particular hardware? That needs adjusting. B
SRU review: it looks like the test being disabled was first introduced
in 1:0.9.5.1 and was related to an FTBFS fix. However, it doesn't seem
to be testing the actual payload, but its own test setup. I don't see a
way that disabling this test would cause a false negative, so it appears
to be a no-o
From IRC (#ubuntu-release):
13:14 tjaalton: for bug 2060268, are there any cases where the
udev rule would be triggered but is the wrong thing to do? How certain
are we on that point?
13:14 tjaalton: presumably the Test Plan should specify testing
on particular hardware? That needs adjusting. B
SRU review: it looks like the test being disabled was first introduced
in 1:0.9.5.1 and was related to an FTBFS fix. However, it doesn't seem
to be testing the actual payload, but its own test setup. I don't see a
way that disabling this test would cause a false negative, so it appears
to be a no-o
> +# Race condition may happen and the test fails. This only happens in
> Jammy containers.
> +# Disable the test for now.
> +return
I don't think it's appropriate to disable a test without an analysis
that considers what it was testing, how to mitigate the gap created by
> +# Race condition may happen and the test fails. This only happens in
> Jammy containers.
> +# Disable the test for now.
> +return
I don't think it's appropriate to disable a test without an analysis
that considers what it was testing, how to mitigate the gap created by
On Thu, Aug 01, 2024 at 11:06:34AM +0100, Robie Basak wrote:
> When this was raised to the Technical Board, we formed a view that we
> should have some written policy that defines what users can expect from
> snaps that are installed in this way, together with a process for
> grantin
On Thu, Aug 01, 2024 at 11:06:34AM +0100, Robie Basak wrote:
> When this was raised to the Technical Board, we formed a view that we
> should have some written policy that defines what users can expect from
> snaps that are installed in this way, together with a process for
> grantin
We've long acknowledged that the SRU documentation has outgrown its
(mostly) single wiki page, and that one of the reasons uploads are
mismatching SRU team expectations more frequently than they should is
that the documentation is lacking.
I've been driving a significant evolution into more detail
** Tags added: server-todo
** Also affects: sysstat (Ubuntu Noble)
Importance: Undecided
Status: New
** Changed in: sysstat (Ubuntu Noble)
Assignee: (unassigned) => Robie Basak (racb)
** Changed in: sysstat (Ubuntu Noble)
Status: New => Triaged
--
You received th
** Tags added: server-todo
** Also affects: sysstat (Ubuntu Noble)
Importance: Undecided
Status: New
** Changed in: sysstat (Ubuntu Noble)
Assignee: (unassigned) => Robie Basak (racb)
** Changed in: sysstat (Ubuntu Noble)
Status: New => Triaged
--
You received th
The following subscriptions are superfluous:
ruby3.3
Superfluous subscriptions removed
--
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam
# Performance Impact Analysis
Summary: CPU, memory, storage and power management behaviour changes are
negligible.
All analysis was done on Noble, but there's no reason to believe that
the behaviour will be different on Oracular.
## CPU and direct storage
Robie did the following:
* `time -p sh
1 - 100 of 1247 matches
Mail list logo
