Public bug reported:
This package has a t64 transition in proposed which has not migrated...
the reason it has not migrated is that the only interesting binary
package this source builds (android-platform-frameworks-native-headers)
has long since been taken over by a different source package
Uploading to ubuntu (via ftp to upload.ubuntu.com):
Uploading bpfcc_0.29.1+ds-1ubuntu7.dsc: done.
Uploading bpfcc_0.29.1+ds-1ubuntu7.debian.tar.xz: done.
Uploading bpfcc_0.29.1+ds-1ubuntu7_source.buildinfo: done.
Uploading bpfcc_0.29.1+ds-1ubuntu7_source.changes: done.
Successfully
FWIW, as the foundations team member trying to tie up the loose ends of
the time64 transition, I support this work -- the alternative is doing
the t64 transition for ceph, which is more effort.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
This package build depends on 'slib' which was removed from noble on
2024-03-27
(https://launchpad.net/ubuntu/+source/slib/+publishinghistory)
mwhudson@orcrist:~/tmp/bootstrap$ reverse-depends src:gauche
mwhudson@orcrist:~/tmp/bootstrap$ reverse-depends -b src:gauche
No
FWIW there is some discussion upstream in these two issues:
https://gitlab.gnome.org/GNOME/folks/-/issues/140
https://gitlab.gnome.org/GNOME/glib/-/issues/3316
** Bug watch added: gitlab.gnome.org/GNOME/glib/-/issues #3316
https://gitlab.gnome.org/GNOME/glib/-/issues/3316
--
You received
Public bug reported:
https://autopkgtest.ubuntu.com/packages/s/starlette/noble/arm64 ->
https://objectstorage.prodstack5.canonical.com/swift/v1/AUTH_0f9aae918d5b4744bf7b827671c86842/autopkgtest-
noble/noble/armhf/s/starlette/20240326_094833_58e76@/log.gz ->
304s > assert ctxvar.get() ==
Public bug reported:
https://autopkgtest.ubuntu.com/packages/pylint/noble/armhf ->
https://autopkgtest.ubuntu.com/results/autopkgtest-
noble/noble/armhf/p/pylint/20240326_095003_d135e@/log.gz ->
432s === short test summary info
432s FAILED
Public bug reported:
See https://autopkgtest.ubuntu.com/packages/pydantic/noble/armhf, e.g.
https://autopkgtest.ubuntu.com/results/autopkgtest-
noble/noble/armhf/p/pydantic/20240326_094721_eb3d5@/log.gz where we see
292s E assert [{'loc': ('a'...rtion_error'}] == [{'loc':
no, RAOF triggered me into fixing the build instead
** Changed in: threadscope (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2058878
Title:
please remove
Public bug reported:
This package build-depends on libghc-ghc-events-dev << 0.18 but 0.19.0.1
is now in the archive so this is going to need a sourceful change to fix
and it's been removed from testing.
mwhudson@orcrist:~/tmp/bootstrap/indicator-datetime-15.10+21.04.20210304$
reverse-depends
Public bug reported:
It hasn't had a real upload since 2015 and now ftbfs because it uses
debhelper compat 5 and has been removed from testing in Debian.
** Affects: curlftpfs (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a
It's in Jira as well, fwiw.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2038906
Title:
Ubuntu desktop ISOs are around 700MB larger than legacy desktop ISOs
To manage notifications about this bug
Public bug reported:
I xfailed a whole stack of the "conform" tests on armhf, which
presumably fail because of the change in default size of time_t (and
off_t). We should work out what is going on here before release -- maybe
leaving them xfail is appropriate but I'm not confident to say that at
Nothing has changed here. I do have a branch in review that should help
but it broke other vmtests in obscure ways. Now Jenkins is usable again,
I guess I/someone should take a look at it again...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
It's deliberately but sometimes unfortunately hard to map an error
report back to who submitted it, so I can't be sure whether the reports
I'm looking at are from you.
If you do try again and hit a similar failure, the crash file will be
present in /var/crash in the live session. If you can
Sigh, I thought we'd fixed this. Can you attach a crash log? They should
have been saved to the USB stick you were using for the install.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1975391
Title:
Verified that the new version does not generated bogus lines on bionic:
root@lp-1892825-bionic:~# cp /etc/default/locale /tmp/locale
root@lp-1892825-bionic:~# update-locale --locale-file /tmp/locale LANG = C.UTF-8
root@lp-1892825-bionic:~# diff -u /etc/default/locale /tmp/locale
---
Verified that libc6 2.27-3ubuntu1.6 can be installed fine in a bionic
docker container an Amazon Linux 2 system with the problematic kernel
version:
root@eef8e8932f4b:/# apt install libc6
Reading package lists... Done
Building dependency tree
Reading state information... Done
Suggested
All packages in Ubuntu have extra png compression applied by
pkgbinarymangler. We can add NO_PNG_PKG_MANGLE=1 to the rules file to
turn this off I think.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
We have a bunch of bug reports about cloud-init not completing within 10
minutes when the installer media is mounted as a virtual ISO/image and
adding 'fsck.mode=skip' the command line usually helps.
We could instrument casper-md5check to monitor how long it is taking or
Public bug reported:
Given it no longer runs from the initrd.
I guess it's not harmful, but it doesn't do anything now and it clutters
the code.
** Affects: casper (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Marking verification done. I have tested upgrades in containers and vms,
I have tested upgrades on several architectures, I have tested upgrades
specifically on arm64 around lib6-lse and I have tested a core20 snap
with glibc from proposed on amd64, ppc64el and arm64, including a
graphical snap on
Verified on an AL2 instance:
root@19bea50a89e2:/# uname -r
4.14.275-207.503.amzn2.x86_64
root@19bea50a89e2:/# apt install --reinstall libc6=2.31-0ubuntu9.7
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 1
I made a core20 snap with libc6 & libc-bin 2.31-0ubuntu9.9 in it and
uploaded it to
https://people.canonical.com/~mwh/core20_glibc_proposed.snap so
especially brave people could test this if they wanted to.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Hello, could someone affected by this bug test the version of glibc in
focal-proposed? We had to rebuild the package for unrelated reasons.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1962225
Verified:
root@146e5ef6a792:/# dpkg -l libc6
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
** Tags removed: verification-needed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1951032
Title:
AArch64:
Oops, this is my fault, in
https://github.com/canonical/probert/commit/5a37f8821bf6ad1af19babc862a17e148da5ae25
I accidentally changed to code so that it would think that partitions of
an existing RAID are RAID devices.
** Changed in: curtin (Ubuntu)
Status: Confirmed => Triaged
**
https://github.com/canonical/probert/pull/115
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1970116
Title:
Ubuntu 22.04 not installing on md partition
To manage notifications about this bug go to:
I verified that arm64 systems with and without libc6-lse installed
upgrade to the new version of glibc in proposed smoothly.
** Tags removed: verification-needed verification-needed-focal
verification-needed-groovy
** Tags added: verification-done-focal
--
You received this bug notification
** No longer affects: glibc (Ubuntu Focal)
** Also affects: glibc (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: cross-toolchain-base (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: glibc (Ubuntu Focal)
Milestone: None => focal-updates
** Also affects: cross-toolchain-base (Ubuntu)
Importance: Undecided
Status: New
** Changed in: cross-toolchain-base (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I installed debootstrap from impish-proposed and was able to build a
kinetic chroot with mk-sbuild.
** Tags removed: verification-needed-impish
** Tags added: verification-done-impish
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I verified part 3 of the test case, that (an appropriately configured)
unattended-upgrades upgrades an arm64 with libc6-lse without complaints:
new_user@ip-172-31-25-59:~/bench$ sudo unattended-upgrade -v
Could not figure out development release: Distribution data outdated. Please
check for an
I ran the tests on a graviton2 instance and saw the improvement as
expected/desired:
length | before (MiB/s) | after (MiB/s) |delta
--|||--
32768 | 233.19 | 247.61 |6.18%
65536 | 443.44 | 468.68 |
verified:
root@focal-vm:~# dpkg -l libc6-dbg | grep ^ii
ii libc6-dbg:amd64 2.31-0ubuntu9.7 amd64GNU C Library: detached
debugging symbols
root@focal-vm:~# gdb -q /bin/date
Reading symbols from /bin/date...
(No debugging symbols found in /bin/date)
(gdb) starti
Starting program:
(I removed some test cases around handling upgrades from 2.31-0ubuntu9.3
as that version got superseded by a security update)
** Description changed:
[impact]
It is time to update glibc in Focal. This bug is a placeholder for the
overall process and a place to link the individual bugs that
Verified:
root@focal-vm:~# dpkg -l locales | grep ^ii
ii locales2.31-0ubuntu9.7 all GNU C Library: National
Language (locale) data [support]
root@focal-vm:~# cp /etc/default/locale /tmp/locale
root@focal-vm:~# update-locale --locale-file /tmp/locale LANGUAGE = en_US.UTF-8
I've verified this fix, the test case hung fairly quickly (~5 mins) in a
4 core VM and after installing the libc packages from proposed has been
running for so long I no longer have access to the scrollback to paste
here.
** Tags removed: verification-needed verification-needed-focal
** Tags
Thanks for checking!
** Changed in: subiquity (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/1968952
Title:
subiquity crash when install ubuntu server
This looks like a bug we fixed just hours before release. Can you try
again with the final ISO?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1968952
Title:
subiquity crash when install ubuntu
This could be https://bugs.launchpad.net/subiquity/+bug/1968161 perhaps.
Does this happen every time?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1968772
Title:
Installation stuck on Hyper-V 2019
Ugh that sounds bad! Can you extract the files from /var/log/installer
somehow?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1968772
Title:
Installation stuck on Hyper-V 2019
To manage
I guess subiquity's expectation is still that the installation media is
read-only. I wonder how we can detect that this is OK to allow...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1968156
Title:
Oops. This definitely used to work! The cancellation can take a while
but rebooting while it's still happening is certainly not intended! The
state machine around cancellation is a bit complicated, I guess some
refactoring broke it :(
--
You received this bug notification because you are a
At this point I expect jammy glibc to use the clone3 syscall. The only
application I've had complaints about is rstudio and they have a plan
(which is roughly speaking "start using Election").
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Ah yes that would do it. I wonder how that symlink got there -- I'm
pretty sure it was not created by any official part of Ubuntu. (A bit of
googling finds people doing things like this
https://github.com/remap/ndnfs-port/issues/8 but it's not clear to me
where they got the idea from).
We might
The crash on timeout is fixed in main fwiw and I'm just doing the
necessary stuff to make sure it's fixed in jammy. Did anyone try adding
toram to the kernel command line?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: initramfs-tools (Ubuntu)
Importance: Medium => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958148
Title:
mkinitramfs is too slow
To manage notifications about this bug go
I think given that verification is going to be slightly fiddly and the
update is already badly overdue, I will not attempt to fix this bug in
the next focal update. But also I do not want to leave it so long again
until the next update.
--
You received this bug notification because you are a
So the package still fails autopkgtests because there is a test that
downloads the test.pfx file from upstream git and does operations on
that. So I'll disable that I think...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
So for SRU we ideally want a nice, self-contained, ubuntu-based test
case. Is that possible here? It reads to me as if it's a bit non-
deterministic, is that true?
@kjtsanaktsidis, do you think you can write up reproduction
instructions? If not, would you be able to test the proposed glibc in
** Description changed:
[impact]
A simple typo using the update-locale script can render a system inoperable
without booting into single user mode or similar:
$ sudo update-locale LANGUAGE = en_US.UTF-8
$ sudo -s
sudo: pam_open_session: Bad item passed to pam_*_item()
sudo: policy
Dave, if you have time to test 2.31-0ubuntu9.8~ppa4 vs focal-update that
would be interesting -- I think given Dann's results though they will be
pretty neutral though so I wouldn't worry over much about it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I saw an autopkgtest on ppc64el that failed with a similar complaint
too: https://autopkgtest.ubuntu.com/results/autopkgtest-
jammy/jammy/ppc64el/f/faiss/20220306_103918_ed101@/log.gz
I have no idea what is going on though.
--
You received this bug notification because you are a member of
** Changed in: glibc (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/1942113
Title:
systemd unit test regression in autopkgtest (oomd-utils)
To manage
It was pointed out to me that my compare.py script printed the times the
wrong way around, so I fixed that and also changed it to print output in
MiB/s -- always easier to reason about a benchmark when "bigger is
better"!
** Description changed:
[impact]
glibc 2.32 contained a number of
Didier merged a better version of the fix I uploaded so presumably he'll
upload that soon and we can see where things fall.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1962170
Title:
DEP8 failure
This got fixed in https://ubuntu.com/security/notices/USN-5310-1
** Changed in: glibc (Ubuntu Bionic)
Status: New => Fix Released
** Changed in: glibc (Ubuntu Focal)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Description changed:
[impact]
glibc 2.32 contained a number of improvements to the memcpy routines for
server-grade AArch64 implementations (in particular, graviton2 & graviton3).
They should be backported to focal, as the LTS releases are by far the most
used on servers.
[test
Yes indeed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926918
Title:
cannot install libc6-dev, requires old libc6 version
To manage notifications about this bug go to:
> So I would propose to add imgui to the lto-disabled-list and
> recompile open3d afterwards. What do you think?
Sounds plausible. I'll try it in my PPA first though!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
We need to do a better job of surfacing "your mirror is broken" errors to
the user.
On Sat, 5 Mar 2022, 13:50 MercSniper, <1963...@bugs.launchpad.net>
wrote:
> Seems to be it. I've been fighting this all day. Can't believe the
> mirror hadn't synced in the last 6+ hours.
>
> --
> You received
Sponsored, thanks. Could you look into sending this to Debian as well?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1963582
Title:
SystemError: PY_SSIZE_T_CLEAN macro must be defined for '#'
I spent a bit too long on this and I think this valgrind error is the
core of the issue:
==62437== Invalid write of size 4
==62437==at 0x685A6C0: stbrp_pack_rects (stb_rect_pack.h:548)
==62437==by 0x522A2D9: ImFontAtlasBuildWithStbTruetype(ImFontAtlas*) (in
This is the traceback of how it's crashing:
(gdb) bt
#0 0x76f5779f in unlink_chunk (p=p@entry=0x55d7b380,
av=0x770cac80 ) at ./malloc/malloc.c:1628
#1 0x76f5a6ab in _int_malloc (av=av@entry=0x770cac80 ,
bytes=bytes@entry=4584) at ./malloc/malloc.c:4307
#2
** No longer affects: lto-disabled-list (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1963556
Title:
Open3D segfaults when compiled with LTO
To manage notifications about this bug go to:
Turns out open3d is already in lto-disabled-list so something else is
going on.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1963556
Title:
Open3D segfaults when compiled with LTO
To manage
** Also affects: lto-disabled-list (Ubuntu)
Importance: Undecided
Status: New
** Tags added: lto
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1963556
Title:
Open3D segfaults when
Can you post the error report that is generated? It is not impossible
for the install to run out of disk or memory at this point but I can't
tell from what you have posted.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
New ubuntu official images have been published which contain the glibc
update, so this issue should be less impactful now. The plan is still
to fix this quickly though.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This fix will land in glibc in a week or so (hopefully) but before that
we can get new images out with the glibc from the security update in,
which will make your builds work again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Summary changed:
- 3.6.2-1 FTBFS in Jammy on x86/s390x
+ 3.6.2-1 FTBFS in Jammy on s390x
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1961901
Title:
3.6.2-1 FTBFS in Jammy on s390x
To manage
Hm no, if I apply this patch (or something like it)
https://paste.ubuntu.com/p/vVTyzHMqvr/ the build succeeds. Wtf.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1962170
Title:
DEP8 failure with
So fwiw the build failure on ppc64el is hanging on the the call to
io.ReadAll(stderr) in SetupSmb (i.e. here:
https://github.com/ubuntu/adsys/blob/v0.8/internal/testutils/samba.go#L38).
No idea why, but my sense from poking around is that the test has
already failed when the hang occurs so maybe
** Changed in: glibc (Ubuntu Focal)
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/1962225
Title:
preinst check that kernel revision < 255 now does more harm
*** This bug is a duplicate of bug 1962225 ***
https://bugs.launchpad.net/bugs/1962225
** This bug has been marked a duplicate of bug 1962225
preinst check that kernel revision < 255 now does more harm than good
--
You received this bug notification because you are a member of Ubuntu
** Changed in: ntpsec (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/1960905
Title:
ntpsec: FTBFS with OpenSSL 3.0
To manage notifications
"so this is fixed already in f and later" - think you mean "b and later"
here?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1962332
Title:
xenial systemd fails to start if cgroup2 is mounted
To
Verified on bionic:
ubuntu@juju-e14b64-adt-9:~$ mk-sbuild jammy
Specified release (jammy) not known to debootstrap
ubuntu@juju-e14b64-adt-9:~$ sudo apt install -t bionic-proposed debootstrap
Reading package lists... Done
Building dependency tree
Reading state information... Done
Suggested
Public bug reported:
[impact]
Amazon Linux 2 currently has a kernel with version
4.14.262-200.489.amzn2.x86_64. This causes complaints from libc6's preinst that
asserts that the "revision" part of the kernel version is less than 255.
The significance of the check is much less than it used to
Public bug reported:
Evidence:
https://autopkgtest.ubuntu.com/packages/c/cluster-glue/jammy/amd64
https://autopkgtest.ubuntu.com/packages/cluster-glue/jammy/ppc64el
https://autopkgtest.ubuntu.com/packages/cluster-glue/jammy/s390x
(almost all failures I looked at were the logd test failing)
**
** Package changed: curtin (Ubuntu) => subiquity
** Changed in: subiquity
Status: Incomplete => In Progress
** Changed in: subiquity
Assignee: (unassigned) => Michael Hudson-Doyle (mwhudson)
--
You received this bug notification because you are a member of Ubuntu
Bu
You are correct that subiquity does not allow you to put the ESP on a
metadata 1.2 MD RAID device. That's because, to the best of my
knowledge, almost all firmware does not know about MD RAID formats and
so would be unable to boot the system.
The question thus becomes, how can the installer know
** Changed in: subiquity (Ubuntu)
Status: Won't Fix => In Progress
** Package changed: subiquity (Ubuntu) => subiquity
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1907128
Title:
Subiquity
** Also affects: multipath-tools (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/1961136
Title:
Syslog shows "multipathd[3142]: failed to increase
I wrote another script to install the "bad" libc version
(2.31-0ubuntu9.3) on a system:
#!/bin/sh
set -eux
a=$(dpkg --print-architecture)
v=2.31-0ubuntu9.3
pkg='glibc-doc
glibc-source
libc6
libc6-lse
libc6-dbg
libc6-dev
libc-bin
libc-dev-bin
locales
locales-all
nscd'
debs=''
for p in $pkg; do
*** This bug is a duplicate of bug 1929213 ***
https://bugs.launchpad.net/bugs/1929213
As it happens I've just started to work on this. It's a duplicate of
another bug though, I'll mark this as such.
** This bug has been marked a duplicate of bug 1929213
Ubuntu server LVM creates clone
** Tags added: fr-2060
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960926
Title:
[VROC] Installation on RAID volume fails - ubuntu 22.04
To manage notifications about this bug go to:
https://github.com/canonical/probert/pull/110 should fix this. I'll try
to make an ISO including that change for testing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960926
Title:
[VROC]
I think we should change the installer but I haven't thought about what
that means in detail!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960926
Title:
[VROC] Installation on RAID volume fails -
Oh, it looks like this is caused by this upstream mdadm change:
https://git.kernel.org/pub/scm/utils/mdadm/mdadm.git/commit/?id=1a52f1fc0266d438c996789d4addbfac999a6139.
I guess the installer can't rely on udev for array memebership
information and will have to run mdadm --detail or similar
Can you try booting with udev.log_level=debug on the kernel command line
and attach the journal?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960926
Title:
[VROC] Installation on RAID volume
This looks like
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960392. I don't
really know what's going on there so perhaps this doesn't help very
much...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I wrote a script for making a core20 with glibc from proposed in it:
#!/bin/sh
set -eux
snap download --basename core20_prehax core20
unsquashfs -d core20 core20_prehax.snap
a=$(dpkg --print-architecture)
v=2.31-0ubuntu9.5
So the reason this doesn't work is that the udev data for the container,
/dev/md/imsm0, does not contain the keys we look for to work out which
devices are part of it. We expect to find keys called things like
MD_DEVICE_dev_sda_DEV but they are not there. There is
UDISKS_MD_DEVICE_dev_sda_DEV
Public bug reported:
mailman3 is currently not in testing, has an open RFH bug
(https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998223) and blocks
the migration of other packages (notably python-click). It should be
removed from the archive until such time as it becomes better maintained
in
Noah,
I'm not completely opposed to that but I would rather not. Which
projects are affected? Can we put some pressure on them to rebuild?
It'll be well over 6 months from this becoming an issue to the release
of 22.04 and all that's required is a rebuild with the latest point
release of whatever
Anyone who is caught in this position can use these commands (as root):
cat
I've been trying the test case attached to this report with -0ubuntu9.2
in a 2 core vm for a good few minutes and it has not hung yet. Are there
tips for getting it to hang more quickly? I'm guessing more cores, I'll
try that tomorrow...
--
You received this bug notification because you are a
1 - 100 of 2259 matches
Mail list logo
