There was some discussion regarding this particular bug in #ubuntu-
release on 20190620 - https://irclogs.ubuntu.com/2019/06/20/%23ubuntu-
release.html. I will not summarize the conversation here but only
capture what I understand the bug in initramfs-tools to be.
update-initramfs no longer uses
** Tags removed: rls-ee-incoming
** Tags added: rls-ee-notfixing
--
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/1829805
Title:
Lubuntu Eoan Daily Image fails to
For initramfs-tools... please provide steps to reproduce the issue of
when initrds are expected to be created and are not, with steps how to
get in such situation (e.g. rm /boot/initrd*; update-initramfs...)
*without* requiring to use calamares, or specific images. ie. from any
regular normal
The bug was only fixed in our Calamares configuration and still needs to
be fixed in initramfs-tools.
Adjusting bug statuses appropriately and adding the release tag. I'll
ping vorlon and xnox on IRC to get their take.
** Also affects: calamares-settings-ubuntu (Ubuntu)
Importance: Undecided
The fix is now released. Spinning up a new ISO as we speak.
calamares-settings-ubuntu (1:19.10.2) eoan; urgency=medium
* Fix initramfs job failing. Thanks to TJ for the fix! (LP: #1829805)
* Move before_bootloader_mkdirs process before initramfs.
* Workaround bug in
Just to add my $.02 . . . I also had this problem with perhaps 6/12
daily and then I zsyncd what I think is the 6/15 daily . . . finding the
same "kernel panic" report as Dan found. A couple days later I
downloaded a fresh 19.04 iso and ran the install . . . and that went
well.
Glad to hear that
I have tested this patch in virtualbox and it works for me.
--
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/1829805
Title:
Lubuntu Eoan Daily Image fails to boot
We got a potential fix thanks to TJ that seems to be working wonderfully from
what I can ascertain:
https://phab.lubuntu.me/D15
Download the raw diff, cd /etc/calamares, sudo patch --strip 2 <
/path/to/diff, and install like normal. Done!
--
You received this bug notification because you are a
Or is it? Actually I not, because the test in update-
initramfs::get_sorted_versions() expects an existing
initrd.img-$version:
get_sorted_versions()
{
version_list="$(
linux-version list |
while read -r version; do
test -e
We have a second bug that causes the call by update-
initramfs::get_sorted_versions() to report nothing when calling
(/usr/bin/) "linux-versions list".
This because the target root file-system is copied from the
filesystem.squashfs on the ISO which does NOT contain a
/boot/vmlinuz-$(uname -r).
I should have made clear, this 'second bug' is the only bug.
initrmafs-tools is in the clear - it wasn't finding a kernel image
because there wasn't one when update-initramfs was executed.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
After many hours diving down rabbit holes it turns out this is due to a
major change in the behaviour of update-initramfs introduced by Debian
in July 2018 which made its way into the Ubuntu archive end of april
2019.
01:02 Right! initramfs-tools had a MAJOR import from Debian with
** Also affects: initramfs-tools (Ubuntu)
Importance: Undecided
Status: New
** Changed in: initramfs-tools (Ubuntu)
Status: New => Confirmed
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of
13 matches
Mail list logo
