The fix I've sent upstream is https://go-
review.googlesource.com/#/c/13037/. It hasn't been reviewed yet, but
I've confirmed it works to my own satisfaction on arm64.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gccgo-4.9
FWIW, I haven't seen this for a few months now. It's always hard when
things are so intermittent, but I think it might be fixed...
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
Public bug reported:
Go shared libraries depend on -Bsymbolic-functions working, which
unfortunately doesn't in the version of binutils on trusty. The fix is
in binutils-2_24-branch: https://sourceware.org/git/?p=binutils-
gdb.git;a=commit;h=cd3813a8c9e59ccba0c42f5e3664465428e0e89c so could
this
Filed upstream as https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67508
** Bug watch added: GCC Bugzilla #67508
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67508
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gccgo-4.9 in
** Patch added: "binutils_2.24-5ubuntu13_2.24-5-ubuntu14.diff"
https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1490352/+attachment/4460452/+files/binutils_2.24-5ubuntu13_2.24-5-ubuntu14.diff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
** Description changed:
- Go shared libraries depend on -Bsymbolic-functions working, which
- unfortunately doesn't in the version of binutils on trusty. The fix is
- in binutils-2_24-branch: https://sourceware.org/git/?p=binutils-
- gdb.git;a=commit;h=cd3813a8c9e59ccba0c42f5e3664465428e0e89c so
Oh yes, and dann and I confirmed yesterday that the bug is no longer
present in wily.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gccgo-4.9 in Ubuntu.
https://bugs.launchpad.net/bugs/1472650
Title:
[arm64] gccgo
Here's a patch for trusty, based on the gccgo-4.9 from ~ubuntu-
toolchain-r/+archive/ubuntu/ppa:
http://people.canonical.com/~mwh/gccgo-4.9_4.9.3-0ubuntu3_4.9.3-0ubuntu4.diff
(not tested yet).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
I verified the fix in a lxd. Before enabling proposed:
root@trusty:~# gccgo --version
gccgo (Ubuntu 4.9.1-0ubuntu1) 4.9.1
Copyright (C) 2014 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS
So I started doing verification for this, found that the patches from
bug 1361946 are required, brought them up to date, and then the arm64
node I was testing fell over. Next week, I guess.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Got access to another machine and tested. My test was pretty basic,
using this file:
ubuntu@ms10-36-mcdivittB0:~$ cat trivialcgo.go
package main
import "C"
func main() {
}
Even with the patch in https://bugs.launchpad.net/ubuntu/+source/gccgo-
go/+bug/1361946/comments/16 this file cannot be
I don't know much about this package, but it looks to me like this
applies to the version in Debian there. Have you considered sending the
patch to them?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to console-setup in
Ah sorry, I invalidated it because the original reporter asked me to.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1572493
Title:
pulseaudio 8.0 drops connections
** Changed in: pulseaudio (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1572493
Title:
pulseaudio 8.0 drops connections after
Which version of docker were you upgrading from/to? I don't have a
/var/lib/docker/devicemapper, was that from an older version? (Sorry,
I'm not familiar with the history of the docker packaging)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
That makes sense I guess. It seems networkctl prints "Type: ether" for
things that have DEVTYPE=bridge, just to make things more confusing?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Public bug reported:
I'm experiencing something very like https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=834367 but on 16.04.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: systemd 229-4ubuntu7
ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
Uname: Linux 4.4.0-36-generic
Fun. This bug affects Debian too it seems, I'll forward it along there
unless you have already?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ifupdown in Ubuntu.
https://bugs.launchpad.net/bugs/1618726
Title:
ifup &
I posted https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837732
** Bug watch added: Debian Bug tracker #837732
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837732
** Also affects: ifupdown (Ubuntu Xenial)
Importance: Undecided
Status: New
** Description changed:
+ [Impact]
+
Oops, meant to say a bit more than just that. I verified the problem in
Debian unstable, verified that the patch fixed the problem, and
forwarded the bug/patch along to debian.
I've also uploaded the patch to Yakkety and put it into the SRU queue
for Xenial. Thanks for the report and patch!
--
This bug was fixed in the package krb5 - 1.14.3+dfsg-2
Sponsored for Sam Hartman (hartmans)
---
krb5 (1.14.3+dfsg-2) UNRELEASED; urgency=medium
* Fix gcc -O3, thanks Ben Kaduk/Steve Langasek, Closes: #833798
* Fix kdb5_util create on 32-bit platforms, thanks Greg Hudson, Closes:
Hi, thanks for the patch! I've uploaded it to zesty. I don't know if it
counts as severe enough to be SRUed to yakkety, can start that process
if you think it is :)
** Changed in: kbd (Ubuntu)
Assignee: (unassigned) => Michael Hudson-Doyle (mwhudson)
** Changed in: kbd (Ubu
Public bug reported:
The build of the test package fails with:
make[6]: Leaving directory '/tmp/tmp9tnlt7ag/melticecream'
dpkg-genbuildinfo --build=binary
dpkg-genbuildinfo: error: binary build with no binary artifacts found;
.buildinfo is meaningless
dpkg-buildpackage: error:
Your test program works in artful with python 3.6 for me; I guess
something got updated to fix it but am not going to dig into why unless
you really want me to...
** Changed in: python3.5 (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member
This will end up blocking the enablement of python 3.6 as a supported
version. Any idea who might know how to fix this?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pygobject in Ubuntu.
Public bug reported:
Tests fail with Python 3.6:
==
FAIL:
autopilot.tests.unit.test_application_launcher.ApplicationLauncherInternalTests.test_get_application_launcher_wrapper_raises_runtimeerror
Yeah, we're kinda talking about two things, the problem with ubuntu core
and the problem with the artful daily-live server installer. Both of
those use networkd :) I'm think xnox has a plan for artful, I'm not sure
if it will apply to ubuntu core though, maybe he can confirm?
--
You received
Python 3.6 is not part of 16.04 and so no package that contains
extension modules has them built for python 3.6. 17.10 has everything
built for 3.6 and obviously 18.04 will too.
** Changed in: python-apt (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you
I tried and failed to reproduce this in an artful vm:
ubuntu@mwhudson-artful:~$ cat /etc/udev/rules.d/my.rules
KERNELS=="*", ACTION=="*", DEVPATH=="/devices/*", RUN+="/bin/touch /run/my-file"
ubuntu@mwhudson-artful:~$ sudo rm -f /run/my-file
ubuntu@mwhudson-artful:~$ sudo udevadm trigger
** Changed in: initramfs-tools (Ubuntu)
Assignee: (unassigned) => Michael Hudson-Doyle (mwhudson)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1782802
Ti
python3-defaults is a source package name, that builds binaries python3,
python3-venv, python3-minimal, python3-examples, python3-dev, etc. Those
are the packages you can install with apt.
** Changed in: python3-defaults (Ubuntu)
Status: New => Invalid
--
You received this bug
I'm not sure I see a path to switching away from klibc-utils completely.
As far as I can tell, every upload of initramfs-tools ever has still
invoked ipconfig for some arguments.
Most configs can be handled by writing some shell to replace what
ipconfig does and some functionality can probably be
Public bug reported:
I have some tests written which I will upload soon, I'm filing this bug
so I can use it to block migration until they pass.
** Affects: initramfs-tools (Ubuntu)
Importance: High
Assignee: Michael Hudson-Doyle (mwhudson)
Status: In Progress
** Tags: block
** Tags removed: block-proposed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1786130
Title:
initramfs-tools has no autopkgtests
Status in initramfs-tools
Well there are quite a few uploads to choose from, but this one
https://git.launchpad.net/ubuntu/+source/initramfs-
tools/tree/scripts/functions?id=import/0.125ubuntu6#n339 is about the
least "ipconfig-y" and it still calls it sometimes...
--
You received this bug notification because you are a
Here is my proposed patch.
** Changed in: maas (Ubuntu)
Status: Confirmed => Invalid
** Package changed: cloud-init (Ubuntu) => base-files (Ubuntu)
** Changed in: base-files (Ubuntu)
Assignee: (unassigned) => Michael Hudson-Doyle (mwhudson)
** Changed in: base-file
I've tested this in a minimal image and it appears to work as designed.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to base-files in Ubuntu.
https://bugs.launchpad.net/bugs/1134036
Title:
Failure when using ssh with a
On Wed, 8 Aug 2018 at 02:46, Scott Moser
wrote:
> @mwhudson,
> your suggested change seems reasonable to me.
> I don't love the use of 'eval', but it seems reasonably safe here.
>
I don't either, but I don't think there is any alternative here is
there?
> Instead of quoting you could just
** Also affects: base-files (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: maas (Ubuntu Bionic)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Ah sorry, now done.
** Description changed:
- If LC_ALL is not set (which seems to be the default on a few server
- installations I've done now), mid way through installing, you get this
- backtrace and then the installation just hangs. You can ctrl-c out of
- it but the package is left half
I'm not incredibly happy about this approach (doing it in pam_env.so
would be best I think) but it does the job for now. I verified this in a
minimal bionic image with and without base-files from proposed and the
behaviour was as expected.
** Tags removed: verification-needed
I had a quick look at unbound, it seems quite difficult. People who
install unbound probably want it so they can have DNSSEC supported in
their local resolver which we can't really do by integrating with
resolved. OTOH, if installing unbound replaces (in some sense) resolved
and everything else
On 2 March 2018 at 11:37, Jamie Strandboge wrote:
So long as snapd starts before preinstalled snaps then all is fine.
>
Given that "preinstalled" snaps are merely seeded, there's nothing to be
worried about here :-)
--
You received this bug notification because you are a
Public bug reported:
[impact]
elfutils ftbfs on sid on arm64 currently:
FAIL: run-backtrace-dwarf.sh
0xb3c5373c raise
0xb3c418e8 abort
/<>/tests/backtrace-dwarf: dwfl_thread_getframes: (null)
dwarf: no main
FAIL run-backtrace-dwarf.sh (exit status: 1)
** Also affects: elfutils (Ubuntu Cosmic)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to elfutils in Ubuntu.
https://bugs.launchpad.net/bugs/1798700
Title:
ftbfs on arm64
As above, the build passing is a sufficient test for this.
** Tags removed: verification-needed verification-needed-cosmic
** Tags added: verification-done-cosmic
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to elfutils in
Ubuntu Cosmic)
Status: Confirmed => In Progress
** Changed in: kmod (Ubuntu Bionic)
Assignee: (unassigned) => Michael Hudson-Doyle (mwhudson)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to kmod in U
** Also affects: kmod (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Also affects: kmod (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: kmod (Ubuntu Bionic)
Importance: Undecided
Status: New
--
You received this bug notification because
** Also affects: kmod (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: kmod (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Also affects: kmod (Ubuntu Xenial)
Importance: Undecided
Status: New
--
You received this bug notification because
Public bug reported:
Bug 1782802 used to be about ripping ipconfig entirely out of the
initramfs. But that was too hard to do for cosmic, hence this bug.
** Affects: initramfs-tools (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a
** Summary changed:
- ditch ipconfig in favor of dhclient -4 in 18.10
+ use dhclient -4 instead of ipconfig in easy cases in 18.10
** Description changed:
When adding ipv6 netboot support to initramfs-tools in yakkety/zesty,
this was initially attempted with replacing ipconfig with
On Mon, 3 Sep 2018 at 20:01, Ćukasz Zemczak <1788...@bugs.launchpad.net>
wrote:
> I guess we need an ubiquity rebuild with the new console-setup now.
>
The version in bionic-proposed has the fix (seems the ubiquity build
process includes packages from -proposed)
--
You received this bug
Well the missing chown is not going to be a problem because there is
only one user in the initramfs (root!). The chmod failing might be a
problem but it seems a bit unlikely.
I think this code can only be executed if two DHCP leases are accepted.
Are you doing both DHCP4 and DHCP6 or something
Public bug reported:
This looks an awful lot like bug 1645232 but that is claimed to be
fixed:
mwhudson@ringil:~/tmp$ mkfs.ext4 -V
mke2fs 1.44.1 (24-Mar-2018)
Using EXT2FS Library version 1.44.1
mwhudson@ringil:~/tmp$ dd if=/dev/zero count=0 bs=1M seek=100 of=./fake.img
0+0 records in
Thanks for the report. I'm a bit confused though, because although
you're right that the call to chown will probably fail, I can't see how
that failure will result in networking not being configured. Can you
post the console log of networking failing to be configured?
--
You received this bug
There is also a problem in dhclient where it forks off the daemon and
exits before writing the pidfile which needs a separate fix.
** Changed in: isc-dhcp (Ubuntu Disco)
Status: Invalid => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Public bug reported:
In an eoan armhf container on a disco arm64 vm:
root@helped-oyster:~# gdb /bin/true
GNU gdb (Ubuntu 8.3-0ubuntu1) 8.3
...
(gdb) r
Starting program: /usr/bin/true
Program received signal SIGSEGV, Segmentation fault.
0xf7fc8ee0 in ?? () from /lib/ld-linux-armhf.so.3
It
I don't really know what is happening here but I suspect pretty strongly
it's related to systemtap static probes, because if I do this:
root@helped-oyster:~# cp /lib/ld-linux-armhf.so.3 .
root@helped-oyster:~# objcopy -R .note.stapsdt ld-linux-armhf.so.3
ld-linux-armhf.so.3-nostap
No.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to binutils in Ubuntu.
https://bugs.launchpad.net/bugs/1841006
Title:
gdb reports a segfault in ld-linux.so.3 on armhf
Status in binutils package in Ubuntu:
New
Bug
Public bug reported:
Booting the latest focal live server daily gets us this:
Begin: Disabling snap refresh... ... date: unrecognized option
'--iso-8601=seconds'
BusyBox v1.30.1 (Ubuntu 1:1.30.1-4ubuntu5) multi-call binary.
Usage: date [OPTIONS] [+FMT] [TIME]
Display time (using +FMT), or set
Turns out to be easy to fix in casper.
** Changed in: initramfs-tools (Ubuntu)
Status: New => Invalid
** Changed in: casper (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
We found the issue -- I think xnox is going to report it via proper
channels. But basically it's this:
sizeof(dev_t) = 4 sizeof(__kernel_old_dev_t) = 8
This makes the kernel's loop_info 8 bytes bigger than klibc's and so the
kernel is writing past the end of the loopinfo on the stack, which
I finally got around to reporting this upstream as
https://sourceware.org/bugzilla/show_bug.cgi?id=25215
** Bug watch added: Sourceware.org Bugzilla #25215
https://sourceware.org/bugzilla/show_bug.cgi?id=25215
--
You received this bug notification because you are a member of Ubuntu
Touch
Ah oops, this one fell through the cracks. Should try to do a quick fix.
** Package changed: subiquity (Ubuntu) => subiquity
** Changed in: subiquity
Status: New => Triaged
** Changed in: subiquity
Importance: Undecided => High
--
You received this bug notification because you are a
** Also affects: apport (Ubuntu)
Importance: Undecided
Status: New
** Also affects: apport (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: apport (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: apport (Ubuntu Eoan)
Chad pointed out in IRC that cloud-init query platform is the supported
way to get that information, but also that cloud-init query in general
can probably be the source for all this information, on clouds other
than EC2 as well.
--
You received this bug notification because you are a member of
Public bug reported:
This probably made sense in 2012 but in focal all servers are going to
have cloud-init installed. I *think* apport should consult "< /run
/cloud-init/instance-data.json jq .v1.platform" but someone from server
should probably check that.
** Affects: apport (Ubuntu)
I think this got fixed in ubuntu11, but there are more test failures
yet, see bug 1854237
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1853383
Title:
autopkgtest
So this was somehow caused by the ftbfs fix for klibc. On my eoan
system:
mwhudson@anduril:~/images$ sudo /usr/lib/klibc/bin/losetup -f
loop: can't get info on device /dev/loop30: No such device or address
mwhudson@anduril:~/images$ sudo apt install klibc-utils=2.0.6-1ubuntu1
Talking about this more, the Ubuntu solution for this sort of thing is
to configure sudo appropriately, so we'll close the bug here.
** Changed in: iproute2 (Ubuntu)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
> Ah, no I think this might be along right lines: udev is calling blkid
> on the _partition_ of course, so it can probe for filesystem etc without
> looking at the partition table. After it's done that, it does look for
> the partition table so it can read the ID_PART_ENTRY_* values from it,
> but
This seems to occur when an executable that has been deleted crashes --
the apport hook is called with the executable name set to "/path/to/exe
(deleted)" and somehow this is being split on spaces and the extra
(deleted) argument causes this crash. But simple attempts at reproducing
this scenario
Ah, no I think this might be along right lines: udev is calling blkid on
the _partition_ of course, so it can probe for filesystem etc without
looking at the partition table. After it's done that, it does look for
the partition table so it can read the ID_PART_ENTRY_* values from it,
but if it
Oh yeah and one other thing I don't understand: why udev is processing
the partition while sgdisk is still running.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1834875
So I've been handed the job of moving this bug forward this iteration.
Having just re-read all the comments again and read some source code
while listening to loud techno music my observations/questions are
these:
1) this is a doozy
2) I would really like to see complete udevadm monitor and
On another tangent, I wonder if the change that brought this to light
was the switch to booting without initrd. The timing is about right, and
fits with the fact that it doesn't occur with the generic kernel (which
cannot boot without initrd in Azure). So if someone has an excess of
time to test ,
Hi, could someone prepare an image with
https://paste.ubuntu.com/p/HYGv6m8gCc/ at /etc/systemd/system/systemd-
udevd.service.d/udevd-debugging.conf, boot it on azure until it fails
and put the journalctl output (probably a few megs) somewhere I can read
it? Output from a successful boot would also
Well this is a consequence of this upstream change in iproute2:
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?h=v4.16.0=ba2fc55b99f8363c80ce36681bc1ec97690b66f5.
Upstream discussion, such as it is, of the patch appears to be here:
** Package changed: libcap2 (Ubuntu) => iproute2 (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iproute2 in Ubuntu.
https://bugs.launchpad.net/bugs/1856045
Title:
capabilities set with setcap are not honoured
Can someone from CPC confirm that this has fixed the issues in the Azure
tests?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1834875
Title:
cloud-init growpart race
Great, thanks for confirming.
I wonder if we should SRU this. You see it on Eoan I presume? The bug is
theoretically present in Bionic too aiui but if it never crops up I
don't know if it's worth it.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
** No longer affects: linux-azure (Ubuntu)
** No longer affects: systemd (Ubuntu)
** Also affects: cloud-utils (Ubuntu Eoan)
Importance: Undecided
Status: New
** Also affects: cloud-initramfs-tools (Ubuntu Eoan)
Importance: Undecided
Status: New
--
You received this bug
** Changed in: initramfs-tools (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1868246
Title:
No network after
** Changed in: subiquity
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1870408
Title:
casper-md5check should leave a breadcrumb which
- - Worker 0 (159 tests) => 0:00:01.182108
- - Worker 1 (159 tests) => 0:00:01.607279
- - Worker 2 (159 tests) => 0:00:01.570729
- - Worker 3 (158 tests) => 0:00:01.650056
- make[1]: *** [debian/rules:24: override_dh_auto_test] Error 1
- make[1]: Leaving directory '/<>
So we believe this bug is now fixed but can you confirm Frank?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1868246
Title:
No network after subiquity LPAR
Pretty sure it's initramfs-tools that is putting the mac addresses in
the netplan. That probably needs to grow a little platform-dependent
behaviour around this.
** Also affects: initramfs-tools (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because
Actually it seems this was caused by subiquity running vgscan --mknodes
during block probing:
root@ubuntu-server:/# rm -rf /dev/mapper/mpath*
root@ubuntu-server:/# ls -l /dev/mapper/
total 0
crw--- 1 root root 10, 236 Apr 24 05:57 control
root@ubuntu-server:/# vgscan --mknodes
FWIW I reported this upstream at
https://bugzilla.redhat.com/show_bug.cgi?id=1828617, you might want to
attach the patch there too?
** Bug watch added: Red Hat Bugzilla #1828617
https://bugzilla.redhat.com/show_bug.cgi?id=1828617
--
You received this bug notification because you are a member
** Changed in: subiquity
Status: New => Fix Released
** Changed in: initramfs-tools (Ubuntu)
Status: New => Fix Released
** Changed in: ubuntu-z-systems
Status: New => Fix Released
** Changed in: cloud-init
Status: Incomplete => Invalid
--
You received this bug
(was fixed in subiquity for release)
** Changed in: subiquity
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1870408
Title:
I'm not sure what this bug is asking for any more.
** Changed in: subiquity
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1871439
Title:
** Changed in: subiquity
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1862846
Title:
Crash and failure installing focal
Status in
This got fixed quite a while ago I think, apologies for the lack of
updates.
** Changed in: subiquity
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to hostname in Ubuntu.
Hi I've updated the patch to the latest version and uploaded the package
to my PPA as version 1.2.11.dfsg-2ubuntu2~ppa2 which should appear here
soon:
https://launchpad.net/~mwhudson/+archive/ubuntu/devirt/+packages?field.name_filter=zlib.
Can you test this on your hardware and let me know how it
Great thanks for testing. I've uploaded to groovy -- th ext step is to
SRU to focal I guess -- can you provide an impact statement / test case
/ regression potential as described at
https://wiki.ubuntu.com/StableReleaseUpdates#SRU_Bug_Template ?
--
You received this bug notification because you
Hi, is it correct to say that fixing this bug and bug 1882494 just
requires updating the patch we have to the current state of the
https://github.com/madler/zlib/pull/410 pull request? If so, the package
that is currently building at
And bionic:
mwhudson@anduril:~$ ssh ubuntu@10.187.142.63 "sh -c 'dpkg-query -W
libpam-modules; type go '"
libpam-modules:amd641.1.8-3.6ubuntu2.18.04.1
go: not found
mwhudson@anduril:~$ lxc exec test-pam-bionic -- apt install -y
libpam-modules/bionic-proposed
Reading package lists... Done
Verified on focal:
mwhudson@anduril:~$ ssh ubuntu@10.187.142.128 "sh -c 'dpkg-query -W
libpam-modules; type go '"
libpam-modules:amd641.3.1-5ubuntu4
go: not found
mwhudson@anduril:~$ lxc exec test-pam-focal -- apt install -y
libpam-modules/focal-proposed
Reading package lists... Done
The focal autopkgtest failures are in cyrus-imapd:
Mail::JMAPTalk version 0.15 required--this is only version 0.13 at
./Cassandane/Cyrus/JMAPCore.pm line 47.
BEGIN failed--compilation aborted at ./Cassandane/Cyrus/JMAPCore.pm line 47.
This seems very unlikely to be due to pam, and it happens
1 - 100 of 192 matches
Mail list logo