Thanks for the update. I've looked more at the logs and I'm very
surprised to see the following:
libgit2: 1.8.1 (sys:0.19.0 vendored)
libcurl: 8.9.0-DEV (sys:0.4.74+curl-8.9.0 vendored ssl:OpenSSL/1.1.1w)
ssl: OpenSSL 1.1.1w 11 Sep 2023
I guess that's from some binary install of rust
My point is that you linked to six different bug reports on github
which, when taken together, point to an issue being elsewhere. If there
are unrelated reports in that list, can you remove them? It's difficult
for me to read through so much stuff if it's only loosely correlated.
Also, if the issu
Hi and thanks for your report.
I can't find a direct link between all these reports, or at least not
one that points towards openssl. In particular, GCC does not use openssl
which means that crashes in GCC cannot be explained by problems in
openssl.
Since it looks like there may be a single issue
** Changed in: openssl (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2096810
Title:
[25.04 FEAT] openSSL MSA 10 XTS support
To manage notifications ab
Public bug reported:
Please sync m2crypto 0.42.0-2.1 (universe) from Debian unstable (main)
Explanation of the Ubuntu delta and why it can be dropped:
* d/p/openssl-3.4-ftbfs.patch:
Remove as this was leading to a whack-a-mole game trying to have
SWIG parse properly all system headers
I
Public bug reported:
There is a new version in Debian (1.8.11-2) and merging it fixes tests
failures for the new libnftnl.
** Affects: iptables (Ubuntu)
Importance: High
Assignee: Adrien Nader (adrien)
Status: In Progress
** Tags: update-excuse
--
You received this bug
Public bug reported:
libunwind 1.7.2 fails to build from source on arm64 and i386 and
introduces bugs in some programs. Version 1.8.1 fixes these issues but
hasn't been uploaded in Debian yet.
I don't think we need the update so I would simply wait for a change in
Debian rather than introduce a d
** Changed in: openssl (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059101
Title:
Automatic EST certificate retrieval does not work on Ubuntu 22.04
To ma
I'm going to switch this to Won't fix since only on person seems to be
affected and they had a solution for them. I never found out who is the
other user affected on 2024-05-17. We can re-consider if I get
information from that user (it's really unfortunate that LP didn't
provide more insights)
**
Glad that you found a solution for your issue and thanks for the update.
** Summary changed:
- Openssl can't find libs and finally crashes on "missing shared library
libssl.so.1.0.0"
+ With splunk, openssl can't find libs and finally crashes on "missing shared
library libssl.so.1.0.0"
--
You
Hmm, I was perplexed with breezy and took another look at the report
above. I may have to re-open it but I'll see later on (maybe a few
days).
The issue in the logs is still maybe present but there are also fixes
for two FTBFS on python 3.13 waiting I think the effect of the new
openssl version sh
Breezy is not compatible with python 3.13; this is not related to
openssl 3.4. I'm preparing a PR for breezy on github right now.
** Changed in: breezy (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
* Changed in: python3.12 (Ubuntu)
Assignee: (unassigned) => Adrien Nader (adrien)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2092298
Title:
python3.12/3.13: incompatibility with openssl
I believe it has been fixed for python3.13 by 3.13.1-3 .
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2092298
Title:
python3.12/3.13: incompatibility with openssl 3.4
To manage notifications about
I've added specific affects entries for noble and oracular so that I
could mark
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2092609 as
duplicate.
Fixing this for Noble would require an SRU obviously, which would have
to be staged to be picked up with some security update when that
happe
lar)
Assignee: (unassigned) => Adrien Nader (adrien)
** Changed in: openssl (Ubuntu Oracular)
Importance: Undecided => Medium
** Changed in: openssl (Ubuntu Noble)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
*** This bug is a duplicate of bug 1297025 ***
https://bugs.launchpad.net/bugs/1297025
** This bug has been marked a duplicate of bug 1297025
Either the changelog.gz is missing or there is an erroneous link in the
libssl1.0.0 package
--
You received this bug notification because you are
** Tags added: foundations-todo
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2092298
Title:
python3.12/3.13: incompatibility with openssl 3.4
To manage notifications about this bug go to:
https://
** Also affects: python3.13 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2092298
Title:
python3.12/3.13: incompatibility with openssl 3.4
To ma
Public bug reported:
Python3.12 (and 3.13?) probably need to include the patches given through
https://github.com/python/cpython/pull/127361:
- python3.12: https://github.com/python/cpython/pull/127905
- python3.13: https://github.com/python/cpython/pull/127812
The upstream changes address repor
freedombox 24.25 has been uploaded with the fix that Julian linked to
but it currently FTBFS probably due to python-django.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2074186
Title:
pyopenssl: re
Public bug reported:
Changed exception.
** Affects: m2crypto (Ubuntu)
Importance: High
Assignee: Adrien Nader (adrien)
Status: In Progress
** Changed in: m2crypto (Ubuntu)
Status: New => Incomplete
** Changed in: m2crypto (Ubuntu)
Status: Incomplete =&
** Summary changed:
- m2crypto: FTBFS with openssl 3.4
+ m2crypto: FTBFS with openssl 3.4 as swig and gcc use different feature flags
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2091883
Title:
m2
** Description changed:
- Testsuite fails with openssl 3.4.
+ Openssl 3.4 has started returning an error for when calling
+ X509_REQ_set_version() with "1" which is not specified. However,
+ m2crypto was using that in its testsuite which now fails due to that.
** Summary changed:
- Testsuite fai
High
Assignee: Adrien Nader (adrien)
Status: In Progress
** Tags: update-excuse
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2091883
Title:
m2crypto: FTBFS with openssl 3.4
To m
Public bug reported:
Testsuite fails with openssl 3.4.
** Affects: m2crypto (Ubuntu)
Importance: High
Assignee: Adrien Nader (adrien)
Status: In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
AFAIU the API issues for freedombox and python-oauth2client were not the
same. I can imagine having a single bug for these API removals in
pyopenssl since it looks like they're going to be pretty common but we
should have a separate diary entry in the bug description for each
removal that's problem
** Tags added: update-excuse
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2089065
Title:
rust-cargo-c: FTBFS on Plucky
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubun
I've prepared an MR+debdiff for rust-libgit2-sys :
https://code.launchpad.net/~adrien/ubuntu/+source/rust-
libgit2-sys/+git/rust-libgit2-sys/+merge/477805
Note that I've tested the build in a PPA to ensure there isn't an FTBFS.
--
You received this bug notification because you
*** This bug is a duplicate of bug 2091023 ***
https://bugs.launchpad.net/bugs/2091023
** This bug has been marked a duplicate of bug 2091023
Please remove ruby3.1 and add to blocklist
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
** Changed in: plr (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/2087739
Title:
plr: Please RM armhf binaries
To manage notifications about this bug go t
** Changed in: openssl (Ubuntu)
Status: Confirmed => In Progress
** Changed in: openssl (Ubuntu)
Milestone: None => ubuntu-25.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2066990
Title
** Changed in: openssl (Ubuntu)
Status: In Progress => 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/2087955
Title:
openssl: merge 3.4.0-1 from Debian unstable
To manage notifi
** Changed in: pgauditlogtofile (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2088006
Title:
Remove NBS 32-bit postgresql extension packages, part 4
To man
I guess that splunk is shipping its own libraries somewhere in
/opt/splunk but somehow they're not being used. I'm not familiar with
splunk at all and I don't know how they integrate with the system:
LD_LIBRARY_PATH, some other ld.so config, or maybe there's a special
environment to run? I can only
Hi,
libssl.so.1.0.0 points towards openssl 1 while Ubuntu has been shipping
openssl 3 and libssl.so.3 for several years now.
It seems you're using splunk as can be seen in the output of strace:
/opt/splunk/bin/openssl . I think the issue is that your splunk
installation is either out-of-date, or
I had a look at the packages.
I addressed pgl-ddl-deploy and pglogical-ticker in
https://bugs.launchpad.net/ubuntu/+source/pgrouting/+bug/2089236/comments/8
.
I checked the reverse runtime and build dependencies of all other
packages.
- pgsphere has a reverse depend from gavodachs2-server which
Note that pglogical-ticker and pgl-ddl-deploy are listed in
https://bugs.launchpad.net/ubuntu/+source/pgrouting/+bug/2088006 so I'm
not touching the bug here.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/b
Hmm, duh, thanks for pointing out the bad -a and -b combination. I need
to get the habit of avoiding -b completely.
I checked the packages which depend upon pglogical:
- pglogical-ticker: source, restricted to 64-bit arches
- postgresql-17-pglogical-ticker: binary missing in proposed, sole pack
For reference, during a build, the testsuite now says the following:
# Subtest: ../../test/fips_auto_enable_test
1..1
While loading "fips" provider: error:07880025:common libcrypto
routines::reason(37)
While loading "fips" provider: error:07880025:common libcrypto
routines::reaso
My plan is to make the library write the following error message when
failing to load a provider (it will apply to any provider):
While loading "fips" provider: error:07880025:common libcrypto
routines::reason(37)
There was already an error but it was silent until it reached the
application w
I and others have re-triggered the tests on focal but there are
infrastructure issues. Considering the number of retries so far, it
seems unlikely that further attempt will help.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
** Tags added: ftbfs plucky update-excuse
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2089286
Title:
mayavi2: remove from armhf due to Build-Depends: architecture-
is-64-bit
To manage notificat
** Tags added: ftbfs plucky update-excuse
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2089285
Title:
Remove from armhf due to Build-Depends: architecture-is-64-bit
To manage notifications about t
** Tags added: ftbfs plucky update-excuse
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2089236
Title:
Remove NBS 32-bit postgresql extension packages, part 5
To manage notifications about this bu
Public bug reported:
mayavi2 now Build-Depends on architecture-is-64-bit
The following returned only python3-surfer which is an "all" package.
reverse-depends -a armhf -r plucky -R -l src:mayavi2
reverse-depends -a armhf -r plucky -R -l -b src:mayavi2
** Affects: ubuntu
Importance: Und
Public bug reported:
Adios2 does not support 32-bit builds and Build-Depends on architecture-
is-64-bit.
The package currently FTBFS but that doesn't change the need to remove
it.
I recursively ran the following, stopping at branches with no "armhf"
binary package (I did not do the same check fo
Public bug reported:
This is a follow-up to #208800{3,4,5,6} as I've identified a few more
affected packages.
I'm copying Jeremy's original description at the end of this
description.
The affected packages are:
- pgpointcloud
- pgnodemx
- pgmemcache
- pglogical
- pgfincore
- pgextwlist
- mobili
I had actually re-tried them but they failed the same way (which I don't
believe was related to the upload). I've triggered them again, and
hopefully the runners will behave better this time.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
I've found more packages which are affected:
pgpointcloud
pgnodemx
pgmemcache
pglogical
pgfincore
pgextwlist
mobilitydb
I've also noticed the following non-postgres packages which B-D on
architecture-is-64-bit
r-bioc-alabaster.base
adios2
mayavi2
pmix
purify
icu-ext
rocr-runtime (but there are o
I've retriggered the tests on oracular and they all passed. Britney has
also updated.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2083490
Title:
[SRU] 2.66.1
To manage notifications about this bu
I hadn't re-triggered the tests on jammy and focal though (they had
already passed on noble) and I've done so now. The infra issues are
still present however so the tests may need an unknown number of
retriggers to pass.
--
You received this bug notification because you are a member of Ubuntu
Bug
** Merge proposal unlinked:
https://code.launchpad.net/~adrien/ubuntu/+source/openssl/+git/openssl/+merge/476328
** Changed in: openssl (Ubuntu)
Status: New => In Progress
** Changed in: openssl (Ubuntu)
Importance: Undecided => High
** Changed in: openssl (Ubuntu)
Mil
Public bug reported:
Openssl 3.4.0-1 has been uploaded to unstable and it's now possible to
merge it.
I'm creating a bug report too because I encountered an issue while
preparing the merge and it actually landed with 3.3 but somehow wasn't
triggered which is odd.
This was caused by the addition
I've marked https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2084802
as duplicate of this issue because it is solved the same way and I also
edited the title here to make it more generic (don't hesitate to change
it further).
The issue in that other bug report has a different setup however.
Qu
*** This bug is a duplicate of bug 2084251 ***
https://bugs.launchpad.net/bugs/2084251
** This bug has been marked a duplicate of bug 2084251
LUKS not detected or prompted for on boot
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
I ended up installing the package because systemctl status indicated my
system was in "maintenance" and that was probably the start of a chain
of issues (e.g. no audio). It fixed the issue for me too.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
It looks like I'm facing the issue too on an upgrade from Noble to
Oracular. I haven't changed anything yet on purpose. Let me know if you
want me to try something. (meanwhile I'm going to debug pcscd's new use
of polkit to get my yubikey working again...)
--
You received this bug notification be
The SRU process is dedicated work that is specific to non-security
updates to a package in a released Ubuntu version: no such thing has
been done for libssh2 in 22.04. It has to be done for every change
anyway as the goal is to avoid behavior differences from the
corresponding changes.
But I was w
** Changed in: openssl (Ubuntu)
Importance: Undecided => High
** Changed in: ca-certificates (Ubuntu)
Status: Confirmed => Invalid
** Changed in: openssl (Ubuntu)
Assignee: (unassigned) => Adrien Nader (adrien)
--
You received this bug notification because you are a
NB: we can only SRU that to Noble if it first goes in a development
version of Ubuntu which will only be possible when development for 25.04
begins.
** Summary changed:
- high memory consumption in Ubuntu Noble
+ openssl fails with out of memory messages while trying to load the FIPS
provider in
Steps to reproduce on any machine on Noble or later:
cp -r /usr/lib/ssl/certs/ .
OPENSSL_FORCE_FIPS_MODE=1 openssl rehash certs
** Changed in: openssl (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
** Also affects: openssl (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2066990
Title:
high memory consumption in Ubuntu Noble
To manage notifica
I'm wary of version upgrades for packages I'm not sure we've done SRUs
before.
Have you considered using ssh-audit? It can tell you which host-key
algorithms are offered and I think it implements just enough of the SSH
protocol so that it can tell you such information.
I see it's also available a
I've opened https://bugzilla.kernel.org/show_bug.cgi?id=219358 upstream.
** Bug watch added: Linux Kernel Bug Tracker #219358
https://bugzilla.kernel.org/show_bug.cgi?id=219358
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:
Public bug reported:
Please sync gcalcli 4.5.0-1 (universe) from Debian unstable (main)
Explanation of the Ubuntu delta and why it can be dropped:
* Switch to google-auth-oauthlib from oauth2client (patches included in 4.4)
(LP: #2078793):
- 22dbc71c5dc17dace62e87b3f31b8cdb3eb37996.patc
Public bug reported:
I've recently noticed that two subtests of gsasl have started failing a
few months ago on armhf. This also happens in Debian.
Unfortunately this coincided with infrastructure issues for Ubuntu and
it's not clear which package has been causing the issue. Debian side,
logs are
I haven't opened a report yet. I need direct access to an s390x machine
and not only to the builders, which I didn't have at hand yet.
I shall try to do that this week.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.laun
e the SHA3 acceleration for that.
The patch is limited to s390x, simple, already upstream and merged:
https://git.gnupg.org/cgi-
bin/gitweb.cgi?p=libgcrypt.git;a=commit;h=2486d9b5ae015c1786cb84466a751da4bc0d7122
** Affects: libgcrypt20 (Ubuntu)
Importance: High
Assignee: Adrien Nader (adrien)
ns itself. This will be the
only delta from Debian so we'll certainly revisit the issue.
** Affects: gsasl (Ubuntu)
Importance: Undecided
Assignee: Adrien Nader (adrien)
Status: In Progress
** Changed in: gsasl (Ubuntu)
Assignee: (unassigned) => Adrien Nader (adrien
Thanks for letting me know about it. I've taken a look at 4.5.0 and it
seems too big for an upload this late in the Ubuntu cycle unfortunately;
even the few patches for the files location are probably too much even
though they're definitely welcome.
--
You received this bug notification because y
Changing the target for 25.04 because it's late in the cycle and there
are still a few packages to handle (certbot and pydrive2 iirc).
** Changed in: python-oauth2client (Ubuntu)
Milestone: ubuntu-24.10 => None
--
You received this bug notification because you are a member of Ubuntu
Bugs, wh
That's a good point. It seems the only thing to do in that case is to
drop the dependency on architecture-is-64-bit .
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2081090
Title:
gutenprint FTBFS du
** Changed in: openssl (Ubuntu)
Status: New => Invalid
** Changed in: htpdate (Ubuntu)
Milestone: None => ubuntu-24.10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2071779
Title:
htpdat
I tried building it too on armhf and encountered no issue.
Looking at my analysis results, libgutenprint-dev did not build and was
therefore not analyzed and libgutenprintui2-dev did not have an ABI
incompatibility.
This means that the library should go through the t64 transition.
If you conside
Alright, 0046-signature-Clamp-PSS-salt-len-to-MD-len.patch has been
merged upstream for openssl 3.1:
https://github.com/openssl/openssl/commit/6c73ca4a2f4ea71f4a880670624e7b2fdb6f32da
No concern for OSSL_PKEY_RSA_PSS_SALT_LEN_AUTO_DIGEST_MAX and
RSA_PSS_SALTLEN_AUTO_DIGEST_MAX in openssl >= 3.1 an
I've been preparing a build that includes these changes.
These are fine:
UBUNTU_OSSL_PROV_FIPS_PARAM_UNAPPROVED_USAGE
UBUNTU_OSSL_SELF_TEST_DESC_PCT_DH
These don't seem fine:
OSSL_PKEY_RSA_PSS_SALT_LEN_AUTO_DIGEST_MAX
RSA_PSS_SALTLEN_AUTO_DIGEST_MAX
Defining them would change the behavior of t
Tobias, I think the files are available now.
Package: libssl3-dbgsym
Package-Type: ddeb
Architecture: amd64
Version: 3.0.2-0ubuntu1.18
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2079970
Title:
The MR at
https://code.launchpad.net/~adrien/ubuntu/+source/gcalcli/+git/gcalcli/+merge/472464
is now ready for review.
** Description changed:
gcalcli is another application that had been using oauth2client and I
had unfortunately missed it.
Luckily, upstream patched that mid-August
I've opened a PR upstream for a better error message:
https://github.com/insanum/gcalcli/pull/733 . The log message appears
above the backtrace but there is a delay between the message and the
backtrace and the message is colored in red. It's quite visible.
I'm currently building a version with th
sl (Ubuntu)
Assignee: (unassigned) => Adrien Nader (adrien)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2073991
Title:
Add FIPS defines to Noble OpenSSL header files
To manage notifications
Hi,
That's an interesting aspect that I had overlooked and I see how it can
be annoying.
Looking at the code, I'm not sure there can be a way to move the data
from oauth2client storage to google-auth without spending a lot of time
doing so. The two are quite different.
A related issue is that th
sanum/gcalcli/commit/1260a41410e1a8e11438ac41156f8dfe00c8791e
- Remove deprecated oauth arguments.
https://github.com/insanum/gcalcli/commit/646314e6eaae630b90cc2bde51c8952295a452d7
There is a PPA at
https://launchpad.net/~adrien/+archive/ubuntu/oracular-gcalcli-drop-
oauth2client .
The WIP MR is at
https:
There is an argument for removing it though: we don't know if it's still
working. But what's worse: a non-working package, or a removed package
one? I'm not sure they're very different in this situation.
The main reason for removing packages was that they hold back other
changes due to autopkgtest
I can confirm the issue:
BIOS Model name: AMD Ryzen 7 7840HS w/ Radeon 780M Graphics
Unknown CPU @ 3.8GHz
It looks very minor however. As far as I'm concerned, it doesn't look
like it would be worth SRU'ing it, and considering we're past feature-
freeze for oracular, I'm not sure it woul
** Tags added: foundations-todo
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2074069
Title:
python-oauth2client is deprecated
To manage notifications about this bug go to:
https://bugs.launchpad.n
** Description changed:
python-oauth2client uses deprecated pyopenssl APIs and now they've been
removed.
+
+ See the actual issue in python-oauth2client :
+ https://bugs.launchpad.net/bugs/2074069
+
+ I'm removing the "duplicate" status because I think this prevents this
+ issue from showing
Hi Eric and thanks for the report.
The SRU process necessarily takes time and openssl is a library that is
installed everywhere and is therefore more difficult to get through the SRU
process.
Time-wise (including due to my own availability), I don't think there will be a
patched openssl version
** Changed in: openssl (Ubuntu)
Milestone: None => ubuntu-24.10
** Also affects: openssl (Ubuntu Oracular)
Importance: Undecided
Status: New
** Also affects: openssl (Ubuntu Noble)
Importance: Undecided
Status: New
** Changed in: openssl (Ubuntu Noble)
Milestone: None
*** This bug is a duplicate of bug 2074069 ***
https://bugs.launchpad.net/bugs/2074069
Public bug reported:
python-oauth2client uses deprecated pyopenssl APIs and now they've been
removed.
** Affects: pyopenssl (Ubuntu)
Importance: Undecided
Status: New
** Tags: update-excuse
** Tags added: update-excuse
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2074069
Title:
python-oauth2client is deprecated
To manage notifications about this bug go to:
https://bugs.launchpad.net/
With everything happening with the Noble release, I didn't handle that
back in March and then I forgot about it. Sorry about that.
Is this still relevant?
And is there a reproducer that I can run? I'm asking for a reproducer
because having to rely on a reporter or an environement I don't have
acc
** Changed in: python-oauth2client (Ubuntu)
Status: New => Confirmed
** Changed in: python-oauth2client (Ubuntu)
Importance: Undecided => High
** Changed in: python-oauth2client (Ubuntu)
Milestone: None => ubuntu-24.10
--
You received this bug notification because you are a member
that vendoring the library will be required (if it can
still be made to work!)
There are also in-review changes:
- beancount:
https://code.launchpad.net/~adrien/ubuntu/+source/beancount/+git/beancount/+merge/469654
- cinder:
https://code.launchpad.net/~adrien/ubuntu/+source/cinder/+git/cinde
I'm going to close this as GCS uploaded a new python3-googleapi version
to Debian that is new enough for our needs and depends on
python3-google-api-core (which I packaged and Julian sponsored in
Debian). I've requested a sync that Benjamin did soon after; the package
is currently in -proposed.
**
Public bug reported:
python3-oauth2client has been deprecated and unmaintained for several
years. It's not compatible anymore with new version of pyopenssl. It has
also been replaced with google-auth: https://google-
auth.readthedocs.io/en/latest/oauth2client-deprecation.html
fence-agents makes t
: Adrien Nader (adrien)
Status: In Progress
** Changed in: python-googleapi (Ubuntu)
Milestone: None => ubuntu-24.10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2073850
Title:
pyth
** Also affects: cinder (Ubuntu)
Importance: Undecided
Status: New
** Changed in: cinder (Ubuntu)
Status: New => In Progress
** Changed in: cinder (Ubuntu)
Assignee: (unassigned) => Adrien Nader (adrien)
** Changed in: cinder (Ubuntu)
Importance: Undecided =
Removing the foundations-todo tag as I don't see a plan to work on this
in the near future considering the current state and infos available.
** Tags removed: foundations-todo
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bu
Is there still a wish for this on Jammy?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1988398
Title:
crash due to incomplete AVX check
To manage notifications about this bug go to:
https://bugs.la
1 - 100 of 1942 matches
Mail list logo
