This bug was fixed in the package ubiquity - 19.10.16
---
ubiquity (19.10.16) eoan; urgency=medium
[ Iain Lane ]
* Drop zfs-0.8-support.patch. We're goind to do this via the main
grub-installer package in the archive instead.
* ubi-partman.py: Handle ZFS option not being
** Merge proposal linked:
https://code.launchpad.net/~mwhudson/ubiquity/+git/ubiquity/+merge/373809
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1841672
Title:
CryptSetup packages should not be
That didn't quite work so I had another go:
https://code.launchpad.net/~mwhudson/ubiquity/+git/ubiquity/+merge/373809
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1841672
Title:
CryptSetup
The correct fix in livecd-rootfs would be to run the minimizing script
on the install layer, rather than the live layer which includes
ubiquity.
The livecd-rootfs change above is too conservative, it also marks stuff
manual that another metapackage depends upon.
The ubiquity change might work,
Following a hint from Adam, I propose this change
https://code.launchpad.net/~mwhudson/ubiquity/+git/ubiquity/+merge/373794
which should fix the bug properly (not tested though).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Merge proposal linked:
https://code.launchpad.net/~mwhudson/ubiquity/+git/ubiquity/+merge/373794
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1841672
Title:
CryptSetup packages should not be
I downloaded the squashfses for all the flavours and none of them are
affected by this bug (either cryptsetup is not marked automatically
installed or a metapackage depends on it and will keep it installed) so
I don't think this is super critical for release.
--
You received this bug
That said, it does seem attempts have been made to fix it in livecd-
rootfs before. I wrote this https://git.launchpad.net/~mwhudson/livecd-
rootfs/+git/livecd-
rootfs/commit/?id=b235dfb718730a0a83fec0a1b366ddef8468a0b5 but I'm not
sure about landing this in the space between now and release
> Let's add a livecd-rootfs task, as livecd-rootfs marks it as
automatic.
But that's fine though, it's the installer that should mark the required
if they are in fact being used by the particular install configuration
the user selects.
** Changed in: livecd-rootfs (Ubuntu Eoan)
Status:
This bug was fixed in the package ubuntu-mate-meta - 1.253
---
ubuntu-mate-meta (1.253) eoan; urgency=medium
* Refreshed dependencies
* Added cryptsetup to core, desktop (LP: #1841672, #1801629)
* Added libnotify-bin to core-recommends, desktop-recommends
-- Martin Wimpress
** Changed in: ubuntu-mate-meta (Ubuntu Eoan)
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/1841672
Title:
CryptSetup packages should not be removed by
** Changed in: ubuntu-mate-meta (Ubuntu Eoan)
Status: Confirmed => In Progress
** Changed in: ubuntu-mate-meta (Ubuntu Eoan)
Assignee: (unassigned) => Martin Wimpress (flexiondotorg)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
CryptSetup issue remains on the 20190921 ISO
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1841672
Title:
CryptSetup packages should not be removed by `apt-get autoremove` on
system installed
CryptSetup issue remains on the 20190917
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1841672
Title:
CryptSetup packages should not be removed by `apt-get autoremove` on
system installed with
** Tags added: id-5d67fa92e3efdf15acdae69d
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1841672
Title:
CryptSetup packages should not be removed by `apt-get autoremove` on
system installed with
The latest Ubuntu MATE 20190830 ISO is affected.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1841672
Title:
CryptSetup packages should not be removed by `apt-get autoremove` on
system installed
** Also affects: cryptsetup (Ubuntu Eoan)
Importance: Undecided
Status: Invalid
** Also affects: ubiquity (Ubuntu Eoan)
Importance: Undecided
Status: Confirmed
** Also affects: livecd-rootfs (Ubuntu Eoan)
Importance: Undecided
Status: Triaged
** Also affects:
Let's add a livecd-rootfs task, as livecd-rootfs marks it as automatic.
** Also affects: livecd-rootfs (Ubuntu)
Importance: Undecided
Status: New
** Changed in: livecd-rootfs (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of
** Tags added: rls-ee-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1841672
Title:
CryptSetup packages should not be removed by `apt-get autoremove` on
system installed with encryption
Not a bug in cryptsetup itself, the autoremovability sits at a higher
layer.
** Changed in: cryptsetup (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Confirm issue exists on bare metal as well.
Installed on laptop and followed exact commands as above and upon reboot
booted into busybox and not able to access filesystem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ubuntu-mate-meta (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1841672
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: cryptsetup (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1841672
Title:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ubiquity (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1841672
Title:
This is a screenshot after running `apt-get autoremove` showing messages
Volume group "vgubuntu-mate" not found.
Cannot process volume group vgubuntu-mate
so the system is un-bootable and encrypted.
** Attachment added: "un-bootable and encrypted system"
25 matches
Mail list logo
