The issue was introduced with https://github.com/shadow-
maint/shadow/pull/237
Basically, the previous group validation was done using glibc's getgrid
directly, which was presumably coping well with the RO status of
/etc/group, but that poses consistency problems because you could add a
local
** 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/2063200
Title:
useradd --extrausers --groups tries to lock /etc/group
To manage notifications about this bug go to:
Quick repro steps:
❯ lxc launch ubuntu-daily:noble shadow
Creating shadow
Starting shadow
❯ lxc exec shadow bash
root@shadow:~# mv /etc /etc_write
root@shadow:~# mkdir /etc
root@shadow:~# mount -o bind,ro /etc_write /etc
root@shadow:~# useradd --extrausers --groups somegroup somenewuser
useradd:
** Changed in: shadow (Ubuntu)
Assignee: (unassigned) => Simon Chopin (schopin)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2063200
Title:
useradd --extrausers --groups tries to lock /
Public bug reported:
perf_indicators.c: In function ‘getTicksPerMicrosec’:
perf_indicators.c:37:30: error: implicit declaration of function
‘get_ticks_per_usec’ [-Werror=implicit-function-declaration]
37 | ticks_per_microsec = get_ticks_per_usec();
|
* Define _DISTRO_EVADE_TIME_BITS for the build, not setting _TIME_BITS
+ and _FILE_OFFSET_BITS in the compiler by default.
+ See https://sourceware.org/bugzilla/show_bug.cgi?id=31624.
+ -> build fix, mostly useful for c-t-b(-p)
+
+ [ Simon Chopin ]
+ * debian/patches/git-updates.diff
Public bug reported:
Details to follow.
** Affects: glibc (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/2062228
Title:
[FFe] late glibc
(and of course not include the system headers in its include paths)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2032624
Title:
mumax3 test suite fails against glibc 2.38
To manage notifications
I'm much more OK with removing the binary than uploading that patch to
glibc.
System headers are just that: headers that reflect the system they're
installed in. The fact that you can sometimes get away with using system
headers when cross-compiling to a different environment is just an
accident,
** Also affects: apport-symptoms (Ubuntu)
Importance: Undecided
Status: New
** Changed in: apport (Ubuntu)
Status: New => Invalid
** Description changed:
Apport version: 2.28.0-0ubuntu1
Ubuntu-Server 24.04 Beta amd64 (20240410.1)
- See attached screenshot for error.
+
** Changed in: libelfin (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/2060786
Title:
libelfin autopkgtests fail against newer clang
To manage
Public bug reported:
The autopkgtests are failing due to clang warnings:
101s autopkgtest [09:01:23]: test test-build-libdwarf++:
[---
101s Output from pkg-config --cflags libdwarf++:
101s -I/usr/include/libelfin
101s success: pkg-config call succeeded
101s success:
I had a look at the Debian tracker for this package, and I'm guessing
it's entangled in a similar transition, so I'd suggest upstreaming the
patch there as well.
I removed the ubuntu-sponsors tag, please add it back when you feel
you've addressed my question :)
--
You received this bug
Why does it have an explicit dependency on the library package? Using
the -dev instead should be enough and would avoid similar problem next
time libtins changes ABI.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Newly added autopkgests for tree are failing.
431s autopkgtest [13:00:47]: test command1: [---
431s #1 tree debian
431s
431s [FAILED #1, line 7] tree debian
431s @@ -4,6
For Noble the conflicting manpages should probably be removed from
src:manpages, because I'd rather not spin a new glibc just for this.
That delta should however be dropped in subsequent releases as we sync
back with Debian where they're seemingly going in the opposite direction
(which is probably
That's not time-t. Some scripts in /usr/libexec/installed-
tests/gtk-4.0/tools used to be executable and now are not:
noble-dev ❯ ls -lh /usr/libexec/installed-tests/gtk-4.0/tools/simplify
.rwxr-xr-x root root 1.0 KB Fri Jan 26 20:26:45 2024
/usr/libexec/installed-tests/gtk-4.0/tools/simplify
This should be fixed in 24.04.23 (but I forgot to add the bug stanza)
** Changed in: calamares-settings-ubuntu (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I would have submitted the fix in the Gitea instance but it seems
account creations are disabled? Anyway, I'm attaching the patch here.
** Patch added: "0001-Set-GOCACHE-to-stay-within-the-build-directory.patch"
Public bug reported:
make[2]: Leaving directory '/<>/common/modules/pkgselect/build'
(cd common/snap-seed-glue && go build -gcflags="all=-N -l"
-ldflags="-compressdwarf=false" -o snap-seed-glue main.go)
failed to initialize build cache at /sbuild-nonexistent/.cache/go-build: mkdir
What now remains to be done is to heavily patch faketime to, when on
armhf:
1/ use the proper symbols from glibc (e.g. __clock_gettime64 instead of
__clock_gettime)
2/ expose those symbols instead of the legacy 32-bit ones.
--
You received this bug notification because you are a member of
** Tags removed: 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/2059278
Title:
glibc: apparmor userns mitigation breaks test suite (again)
To manage notifications about this bug go
** Changed in: glibc (Ubuntu Noble)
Status: Triaged => 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/2055175
Title:
[UBUNTU 23.10] s390x: clone clobbers r7
To manage
** Changed in: glibc (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/2059278
Title:
glibc: apparmor userns mitigation breaks test suite (again)
** Changed in: glibc (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/2058466
Title:
glibc 2.39 test failure on ppc64el: elf/tst-decorate-maps
To manage
** Changed in: glibc (Ubuntu)
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2052929
Title:
failed autopkgtests for evolver vs glibc 2.39 on amd64
To manage
** Tags removed: rls-nn-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054343
Title:
arm64 build of gcc-10 10.5.0-3ubuntu1 still broken (CVE-2023-4039
still open)
To manage
Hi,
This is only temporary, see https://lists.ubuntu.com/archives/ubuntu-
devel/2024-March/042954.html for more details.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059498
Title:
Fatally broken
I'm assuming you're running Noble?
** Changed in: ubuntu
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059498
Title:
Fatally broken update
To manage notifications
Public bug reported:
The test sometimes fail, I don't know why.
I'm xfailing it for now but it'd be good to understand exactly what's
going on.
--
--
FAIL: elf/tst-shstk-legacy-1g
original exit status 1
--
** Affects: glibc (Ubuntu)
Importance: Undecided
main;
> status=New; importance=Unknown; assignee=None;
> Launchpad-Bug-Tags: time-t update-excuse
> Launchpad-Bug-Information-Type: Public
> Launchpad-Bug-Private: no
> Launchpad-Bug-Security-Vulnerability: no
> Launchpad-Bug-Commenters: schopin
> Launchpad-Bug-Reporter: S
Public bug reported:
The autopkgtests fail on i386 for version 2:1.0.27-1. In the previous
version the test name was "stress" while the failing one is "testsuite",
so presumably this isn't a regression so much as the new testsuite
failing due to i386 being a partial arch.
Relevant parts of the
Public bug reported:
tmux-server crashes with this assertion:
1711556753.777994 event.c:3172: Assertion tv->tv_usec >= 0 failed in
timeout_next
Something somewhere doesn't speak 64bit time_t, it seems.
** Affects: tmux (Ubuntu)
Importance: Undecided
Status: Confirmed
** Tags:
Public bug reported:
The latest policy on apparmor vs userns isn't to reject the namespace
creation outright but rather to deny all capabilities within that
namespace.
That breaks the glibc testsuite, again, because our patch only takes the
former policy into account, and so all tests that use
Public bug reported:
368s src/github.com/google/gopacket/pcap/pcap_unix.go:344:18: cannot use
_Ctype_gopacket_time_secs_t(ci.Timestamp.Unix()) (value of type _Ctype_long) as
_Ctype_longlong value in assignment
368s src/github.com/google/gopacket/pcap/pcap_unix.go:345:19: cannot use
** Also affects: glib2.0 (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
- click 0.5.2-2 is stuck in -proposed. autopkgtest now fails on armhf,
- and possibly on all archs.
+ click 0.5.2-2 is stuck in -proposed. autopkgtest now fails on ppc64el,
+ s390x.
- armhf
Oh, hang on. The bash build has apparently been uploaded just a day
after the t64 gcc, which means gcc was presumably still building when
the bash build started:
gcc-13 armhf 13.2.0-13ubuntu1 (from the bash build logs)
A bash rebuild should "fix" this somewhat. Well, at least a little bit.
**
The failure is because bash, for some reason, still links against
gettimeofday rather than __gettimeofday64, and calls that to seed its
internal random number generator. I still can't figure out why it's
using the old version, though.
ubuntu@noble-armhf:~$ readelf -W -s a.out | grep timeof # a
Thanks Andreas for pointing me to the page size.
There's an assumption made in the test that the early allocation code
will need to grow beyond the initial data page, as those extra pages
would be the ones marked "[anon: glibc: loader malloc]". However, if the
page size is large enough, I guess
** Changed in: interimap (Ubuntu)
Status: New => Fix Committed
** Tags added: time-t
** 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/2059120
Title:
interimap
Public bug reported:
interimap packs a timeval to pass as a socket timeout, but it uses
'l!l!' as a template. That's broken when time_t != long.
** Affects: interimap (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of
@Paolo thanks for probing this. I finally managed to get my hands on a
suitable power system with recent enough kernel to reproduce this and
file an upstream bug report, and the conversation there led me to
conclude that it's just a faulty assumption in the test (namely that the
initial allocation
Public bug reported:
Please remove src:hkl and src:sardana from noble
hkl is FTBFS and blocks the t64 glib2.0 transition. sardana is its only hard
rdep.
It has been removed from Debian testing:
https://tracker.debian.org/news/1513984/hkl-removed-from-testing/
❯ check-removal sardana
### Source
** Bug watch added: Sourceware.org Bugzilla #31553
https://sourceware.org/bugzilla/show_bug.cgi?id=31553
** Also affects: glibc via
https://sourceware.org/bugzilla/show_bug.cgi?id=31553
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a
Public bug reported:
It's FTBFS on armhf: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065993
Binaries:
xwiimote
libxwiimote2
libxwiimote-dev
xserver-xorg-input-xwiimote
❯ SOURCE=xwiimote; reverse-depends -a source src:$SOURCE; echo binaries:;
reverse-depends src:$SOURCE; echo seeded:;
Uploaded along with a quick fix for https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=1067075
Could you please open a bug in Debian/upstream to see if they'd be open
to adopt your patch? It'd be nice to be able to remove the delta
altogether :)
** Bug watch added: Debian Bug tracker #1067075
Public bug reported:
Please remove the armhf binaries for src:libosmo-netif and its reverse-
dependencies:
* libosmo-netif
* libosmo-sccp
* osmo-bsc
* osmo-hlr
* osmo-iuh
* osmo-mgw
* osmo-msc
* osmo-sgsn
libosmo-netif is non-trivially broken on armhf due to the time_t
transition, see
** Changed in: socat (Ubuntu)
Status: Invalid => 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/2056485
Title:
Behaviour of socat in Ubuntu 20.04 unexpected
To manage
FWIW, we've actually seen at least one package seemingly failing to build
because of this issue:
https://launchpadlibrarian.net/720254657/buildlog_ubuntu-noble-armhf.libflorist_2022.0.1~20220616-5_BUILDING.txt.gz
> posix-c.ads:876:07: error: size for "suseconds_t" too small, minimum
allowed is
Public bug reported:
This test fails on Noble/ppc64el
3775s FAIL: elf/tst-decorate-maps
3775s original exit status 1
3775s error: tst-decorate-maps.c:152: not true: r.n_loader_malloc_mmap >= 1
3775s error: tst-decorate-maps.c:167: not true: r.n_loader_malloc_mmap >= 1
3775s error:
** Bug watch added: Sourceware.org Bugzilla #31510
https://sourceware.org/bugzilla/show_bug.cgi?id=31510
** Also affects: glibc via
https://sourceware.org/bugzilla/show_bug.cgi?id=31510
Importance: Unknown
Status: Unknown
** Summary changed:
- understand conform test failures on
Using the PPA's libquadmath makes the tests pass, so I sent the patch
upstream:
https://gcc.gnu.org/pipermail/gcc-patches/2024-March/647635.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2052929
** Changed in: glibc (Ubuntu)
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2052930
Title:
liblocale-gettext-perl autopkgtests fail against glibc 2.39
To manage
This ended up being fixed in the upstream libdfp, I pushed a patched
version in the archive, currently in -proposed.
** Changed in: libdfp (Ubuntu)
Status: New => Fix Committed
** Changed in: glibc (Ubuntu)
Status: In Progress => Invalid
--
You received this bug notification
As mentioned, I'm fuzzy on the detailed steps that led to this problem,
and have thus far been unable to observe it.
** Changed in: glibc (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This will be fixed in Noble in an upcoming bugfix upload of glibc (a
couple of weeks), however we aren't planning on doing a Mantic SRU
unless something critical comes up.
** Changed in: glibc (Ubuntu Mantic)
Status: New => Won't Fix
** Changed in: glibc (Ubuntu Noble)
Status: New
Hi, thanks for taking the time to report this.
According to the upstream bug, the fix is present from 2.37 onward, and
has been backported to the release branches down to 2.34, while Focal
has 2.31. Given the sheer size of the diff, I'm wary of backporting it
that far. Jammy should be possible,
** Changed in: glibc (Ubuntu)
Importance: Undecided => Medium
** Changed in: glibc (Ubuntu)
Status: New => Triaged
** Also affects: glibc (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: glibc (Ubuntu Jammy)
Importance: Undecided
Status: New
**
To be more precise: I can't reproduce it using gcc or clang, no matter
the fortify level, and the upstream fix
https://sourceware.org/git/?p=glibc.git;a=commit;h=5a5f94af0542f9a35aaa7992c18eb4e2403a29b9
mentions that you can only trigger it on older releases that aren't
available in Jammy.
As a
Hi, thanks for reporting the issue.
could you provide us with a reproducer for this?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056751
Title:
Error compiling with glibc2.35 in Ubuntu22.04.3
This bug is actually in gcc-14, more specifically libquadmath, as they
do a misaligned read from args to a float128, which produces the
segfault.
It was hidden so far because args was allocated using alloca() which I
guess must be naturally aligned, but in 2.39 they removed that in favor
of
** Tags added: foundations-todo
** Changed in: glibc (Ubuntu)
Assignee: (unassigned) => Simon Chopin (schopin)
** Changed in: glibc (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
It turns out the fix was already in the upstream repo as a PR for a
while (couple of years?). I've submitted a Salsa MR to proactively
address the issue before it shows up there:
https://salsa.debian.org/perl-team/modules/packages/liblocale-gettext-
perl/-/merge_requests/1
and I've uploaded the
Unless I'm missing something, the issue you're linking is about glib,
not glibc. Reassigning the bug accordingly.
** Also affects: glib2.0 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: glibc (Ubuntu)
Status: New => Invalid
--
You received this bug notification
After a bit more reflexion, I'd even argue that this 'built tree'
exception shouldn't exist in the first place as it seems like a nice
footgun, but I'm guessing it's not that simple, so in the mean time I'll
just go and amend my wrapper script to not use `autopkgtest .` but
rather
I'll be damned. That's the issue, indeed. I tried to reproduce with a
fresh `hello` but couldn't so I wrongly concluded that it was because it
wasn't on the image.
I'd argue it's still a bug, as in *this should be documented*! I'd never
consider that an unpackage source package would be in a
Confirmed on salsa, and yes I'm using noble, 5.32ubuntu3, sorry about
that.
One solution I could think of is to go through the list of dependencies
and add a strict version if it's a binary generated by the tested source
package (lib/adt_testbed.py, install_apt)
--
You received this bug
Public bug reported:
While working on needrestart autopkgtests, I've run into issues testing
it using my standard invocation:
autopkgtest . -U -- lxd autopkgtest/ubuntu/noble/amd64
The runner wouldn't install the built package but would just keep
whichever version is in the archive, while still
Public bug reported:
Release of Ubuntu: Noble
Package Version: 5.72-0ubuntu1
My headset changed profile from A2DP to HSP as I received a phone call on my
phone (the headset can connect to multiple BT devices).
I'd expect the system to adapt to the new profile (add a new source, change the
To be clear, this appeared right after you selected the english
keyboard?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054193
Title:
locale-gen crashed with SIGABRT in __GI___wait4()
To manage
Public bug reported:
As a header to all .conf files in systemd there's a comment saying
# Entries in this file show the compile time defaults. Local configuration
# should be created by either modifying this file (or a copy of it placed in
# /etc/ if the original file is shipped in /usr/), or by
** Summary changed:
- needrestart should integrate with /run/reboot-required
+ needrestart should integrate with /run/reboot-needed
** Description changed:
We have a standard mechanism to notify users that their machine should
- be rebooted through /run/reboot-required, needrestart should use
Public bug reported:
To quote vorlon in bug 2049208
> The debconf frontend is always non interactive when running under
unattended-upgrades; failing to restart affected services when auto
applying security updates is critically BROKEN BY DESIGN
While a bit hyperbolic, the point still stands.
Public bug reported:
We have a standard mechanism to notify users that their machine should
be rebooted through /run/reboot-required, needrestart should use that
instead of debconf prompts.
** Affects: needrestart (Ubuntu)
Importance: Undecided
Status: New
--
You received this
Hi, thanks for reporting this issue.
Could you please specify which version of Ubuntu you're using?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2051766
Title:
needrestart should priorize and
We had a mitigation for this in glibc but the latest change from simply
denying the unshare() call to allowing it but then denying anything
requiring capabilities *presumably* broke the glibc test suite again.
I'm only basing this from looking at the test logs, as I'm temporarily
unable to run
Uploaded, thanks for the debdiff, and thanks Frank for the review.
For the record, `update-maintainer` is usually not mentioned in the
changelog, we sort of consider it par for the course.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Tags removed: foundations-triage-discuss
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1968334
Title:
Fix CVE-2019-13115
To manage notifications about this bug go to:
** Also affects: libssh2 (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: libssh2 (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: libssh2 (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you
** Summary changed:
- libssh2 upgrade
+ Fix CVE-2019-13115 in Focal
** Changed in: libssh2 (Ubuntu)
Status: New => Triaged
** Changed in: libssh2 (Ubuntu)
Status: Triaged => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
The chain is rustc -> llvm-13 -> llvm-13-dev -> z3, so that's still an
issue with Jammy, I think. Reopening :)
** Changed in: rustc (Ubuntu Jammy)
Status: Invalid => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Imported from Debian bug http://bugs.debian.org/1012262:
Source: libisal
Version: 2.30.0-4
Severity: normal
X-Debbugs-Cc: scho...@ubuntu.com
This package fails to build on big-endian architectures, notably s390x.
There's a fix available upstream:
Adding fastp to the affected packages as this blocks its transition from
-proposed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1976622
Title:
libisal: FTBFS on big-endian architectures
To
Public bug reported:
Imported from Debian bug http://bugs.debian.org/996235:
[,
]
** Affects: ruby-gitlab-fog-azure-rm (Ubuntu)
Importance: Undecided
Status: New
** Affects: ruby-gitlab-fog-azure-rm (Debian)
Importance: Undecided
Status: New
** Tags: update-excuse
*** This bug is a duplicate of bug 1968831 ***
https://bugs.launchpad.net/bugs/1968831
** This bug has been marked a duplicate of bug 1968831
ruby-tty-screen: endianness bug detected by autopkgtest
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
Imported from Debian bug http://bugs.debian.org/1012204:
Source: ruby-tty-screen
Version: 0.7.1-2
Severity: normal
X-Debbugs-Cc: scho...@ubuntu.com
Hi,
The autopkgtests for this package fail on s390x, apparently due to an
endianness issue. See
** Tags added: transition-openssl3-jj
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1976299
Title:
hashlib.algorithms_available lists algorithms that cannot be used
To manage notifications about
Public bug reported:
Imported from Debian bug http://bugs.debian.org/1012125:
Source: astroquery
Version: 0.4.6+dfsg-2
Severity: serious
Justification: RT
X-Debbugs-Cc: simon.cho...@canonical.com
Hi,
The autopkgtests for 0.4.6+dfsg-2 fail with attempts to write to
locations in /usr/lib,
** Description changed:
+ [Impact]
+
+ The TLS test server `openssl s_server` can very easily be led into an
+ infinite loop if configured with incompatible settings and used via
+ DTLS. This makes it harder to test one's TLS configuration.
+
+ [Test plan]
+
+ In one session:
+ $ openssl
** Patch added: "rustc.debdiff"
https://bugs.launchpad.net/ubuntu/+source/rustc/+bug/1971128/+attachment/5593815/+files/rustc.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971128
Title:
** Description changed:
- openssl.cnf as provided misses some directive, which make it a bit
- difficult to change security level, which since openssl 3 disables SHA1
- signatures.
+ [Impact]
+
+ The OpenSSL 3.0 lead to a lot of broken setups. Some of them are
+ regressions, but others are
(Ubuntu Kinetic)
Status: Incomplete => Invalid
** Changed in: rustc (Ubuntu Jammy)
Status: New => Confirmed
** Changed in: rustc (Ubuntu Kinetic)
Status: New => Confirmed
** Changed in: rustc (Ubuntu Jammy)
Assignee: (unassigned) => Simon Chopin (schopin)
--
You rec
** Summary changed:
- [MIR] z3
+ z3 is incorrectly marked as a MIR candidate
** Description changed:
- TDB by foundations.
+ rustc pulls llvm-13 into main (the llvm-toolchain-13 being already
+ partially seeded, it doesn't raise any issue), and z3 is a dependency of
+ it.
** Also affects:
Refreshed version of the same thing, with the merge fixed, adding
Replaces/Breaks fields due to the Ubuntu/Debian divergence on which
package ships the new static libraries.
I used the dh-exec mechanism for the i386 exception as it is what is
used in the current Salsa 13 branch for their
** Description changed:
- Imported from Debian bug http://bugs.debian.org/1010958:
+ [Impact]
+
+ The fix for
+ https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1968997 has
+ broken some code paths as the new string comparison functions now need
+ initialization, triggering segafults.
+
+
Attached is a debdiff for the Jammy changes. I'm still working on
Kinetic as this will be folded into the merge, but I still need to do
some more work as some new patches have surfaced upstream since then, as
well as a new Debian revision. I feel the Jammy SRU should still move
forward.
Note that
** Changed in: openssl (Ubuntu Kinetic)
Status: Confirmed => 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/1974037
Title:
openssl: EVP_EC_gen() segfault without init
To manage
Here's a merge of llvm-toolchain-13 that includes this patch, along with
another one for https://bugs.launchpad.net/ubuntu/+source/llvm-
toolchain-13/+bug/1973041
Build in progress there:
https://launchpad.net/~schopin/+archive/ubuntu/rustc-1.59/+sourcepub/13636485/+listing-
archive-extra
**
** Merge proposal linked:
https://code.launchpad.net/~schopin/ubuntu/+source/openssl/+git/openssl/+merge/423153
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1974037
Title:
openssl:
Here's a MP using git-ubuntu (well, with a lot of manual fiddling):
https://code.launchpad.net/~schopin/ubuntu/+source/openssl/+git/openssl/+merge/423153
I'd appreciate it the upload would be using rich history support:
https://lists.ubuntu.com/archives/ubuntu-devel/2021-October/041649.html
as
1 - 100 of 626 matches
Mail list logo
