This is fixed in casper 1.424. casper 1.423 introduced a systemd mount unit which was intended to facilitate unmounting of /cdrom.
But it was wrong: you cannot use DefaultDepdencies=no to override the BindsTo= that systemd generates for the corresponding device node (dev-sr0.device in this case). So if this wasn't available to the live system - because udev hadn't finished cold plugging by the time systemd got around to starting the mount unit - the device was *unmounted* instead.
You ended up with an empty directory in /cdrom. The minimal install option relies on reading a file out of there to decide if it should be presented. The file didn't exist, and so the minimal option wasn't shown.
Fixed, as I say. Seb closed a different bug with the upload, but this one can also be done away with.
It's a revert, so that means that the reliable unmounting that this was supposed to achieve is not present either.
This is fixed in casper 1.424. casper 1.423 introduced a systemd mount unit which was intended to facilitate unmounting of /cdrom.
But it was wrong: you cannot use DefaultDepdenci es=no to override the BindsTo= that systemd generates for the corresponding device node (dev-sr0.device in this case). So if this wasn't available to the live system - because udev hadn't finished cold plugging by the time systemd got around to starting the mount unit - the device was *unmounted* instead.
You ended up with an empty directory in /cdrom. The minimal install option relies on reading a file out of there to decide if it should be presented. The file didn't exist, and so the minimal option wasn't shown.
Fixed, as I say. Seb closed a different bug with the upload, but this one can also be done away with.
It's a revert, so that means that the reliable unmounting that this was supposed to achieve is not present either.