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
vorlon +1'd and reverted as requested in comment 6. But this bug remains
open since some users are still on the regressed 0.107 version.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/208
Title:
> Furthermore, people that already started using 0.107 functionality
(veth,dummy,wpa3,...) would be left stranded with broken network
configuration after reverting to 0.106.
Another thought is that following your suggestion (proceeding in
#ubuntu-release anyway) doesn't actually stop this scenario
Thank you for working on this!
> Furthermore, people that already started using 0.107 functionality
(veth,dummy,wpa3,...) would be left stranded with broken network
configuration after reverting to 0.106.
I think that's the deliberate intention of a revert, and therefore is
acceptable in the gene
This resulted in a regression reported in bug 208. A revert is
currently on the table.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2058031
Title:
[SRU] Backport 0.107.1-3 to Ubuntu 22.04
To m
> In my opinion it should be addressed in Juju. We can't change the
format of the YAML emitted by Netplan or it would be yet another change
in behavior.
Under normal circumstances, this is the opposite of what we would
expect. It looks like this regression landed only 9 days ago. Please
prepare a
** Also affects: git-ubuntu
Importance: Undecided
Status: New
** Changed in: git-ubuntu
Status: New => Triaged
** Tags added: snap
** Changed in: git-ubuntu
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Public bug reported:
Steps to reproduce:
On a Noble system:
sudo apt install python3-pip python3-debianbts
pip check
Expected result:
No broken requirements found.
Actual result:
python-debianbts 4.0.2 requires pysimplesoap, which is not installed
This makes "pip check" less useful. In the gi
> 3. the package is actually maintained by the kernel team,
traditionally by the NVIDIA driver maintainer, and the change has landed
to the jammy git branch
Shouldn't the kernel team be a bug subscriber then? I only see the
desktop team. Who monitors bugs against this package?
--
You received th
I thought of a further edge case:
8. What happens if reimaging from the OEM image, and then upgrading to
the updates pocket all at once, including the update that triggered this
bug together with this for it? Which postinst will run first? If not
deterministic, and this one runs first, will that c
SRU review.
I appreciate the importance of fixing this and the general approach
seems OK to me.
0. I do have some difficulty in understand the exact mechanism involved.
Is it correct that in *all* cases it's now wrong in Jammy for
/etc/default/grub.d/oem-flavour.cfg to point to `oem-
somerville*-
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
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
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
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
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
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
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
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
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
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
> [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
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
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
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
** 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
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
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
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
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
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
> 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
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
> 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
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 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
1 - 100 of 1482 matches
Mail list logo
