[ubuntu-studio-devel] LiveFS ubuntustudio/disco/amd64 failed to build on 20190309

[Erich Eickmeyer]

Hi Ross,

On Sun, Mar 10, 2019 at 7:36 AM, Ross Gammon <rosco at ubuntustudio.org> 
wrote:
> Hi Erich,
> 
> On 3/10/19 1:55 PM, Ross Gammon wrote:
>>  Hi Erich,
>> 
>>  It seems there is a problem with the plymouth theme post-install
>>  maintainer script in ubuntustudio-look.
>> 
>>  On 3/9/19 7:31 PM, CD Image wrote:
>>>  Setting up plymouth-theme-ubuntustudio (0.57) ...
>>>  update-alternatives: using 
>>> /usr/share/plymouth/themes/ubuntustudio-logo/ubuntustudio-logo.plymouth 
>>> to provide /usr/share/plymouth/themes/default.plymouth 
>>> (default.plymouth) in auto mode
>>>  update-alternatives: using 
>>> /usr/share/plymouth/themes/ubuntustudio-text/ubuntustudio-text.plymouth 
>>> to provide /usr/share/plymouth/themes/text.plymouth (text.plymouth) 
>>> in auto mode
>>>  update-initramfs: diverted by livecd-rootfs (will be called later)
>>>  /usr/sbin/grub-probe: error: cannot find a device for / (is /dev 
>>> mounted?).
>>>  dpkg: error processing package plymouth-theme-ubuntustudio 
>>> (--configure):
>>>   installed plymouth-theme-ubuntustudio package post-installation 
>>> script subprocess returned error exit status 1
>> 
>>  I haven't tried upgrading my test Disco machine yet, which I will do
>>  some time today. Any ideas?
>> 
>>  Cheers,
>> 
>>  Ross
>> 
> 
> Well, the update went fine on an already installed Disco:
> Setting up plymouth-theme-ubuntustudio (0.57) ...
> update-alternatives: updating alternative
> /usr/share/plymouth/themes/ubuntustudio-logo/ubuntustudio-logo.plymouth
> because link group default.plymouth has changed slave links
> update-initramfs: deferring update (trigger activated)
> Sourcing file `/etc/default/grub'
> Sourcing file `/etc/default/grub.d/init-select.cfg'
> Generating grub configuration file ...
> Found linux image: /boot/vmlinuz-4.19.0-13-lowlatency
> Found initrd image: /boot/initrd.img-4.19.0-13-lowlatency
> Found linux image: /boot/vmlinuz-4.19.0-13-lowlatency
> Found initrd image: /boot/initrd.img-4.19.0-13-lowlatency
> Found Ubuntu 18.10 (18.10) on /dev/sda2
> Found Ubuntu 18.04.2 LTS (18.04) on /dev/sdb1
> Found Ubuntu 18.10 (18.10) on /dev/sdb2
> Found Ubuntu Disco Dingo (development branch) (19.04) on /dev/sdb3
> Adding boot menu entry for EFI firmware configuration
> done
> 
> I am a bit out of my comfort zone here, but it seems that /dev might 
> not
> mounted at this stage in the LiveCD installation process.
> 
> Do we need to add back in the guard that was taken out recently?:
> if [ -e /boot/grub/grub.cfg ] && which update-grub2 >/dev/null 2>&1; 
> then

Steve Langasek (whom I have CC'd in this email) said it's nothing we 
should worry about, but rather a bug in livecd-rootfs revealed by our 
grub/plymouth themes. I suggested putting the code back which you 
suggested, but he said something along the lines of that it shouldn't 
even be a factor to begin with. He has code for a change up for reveiw 
at 
https://code.launchpad.net/~ubuntu-core-dev/livecd-rootfs/+git/livecd-rootfs/+merge/364206.

So, this is one of those "Wait-and-see" things. Steve can chime-in too 
if he feels so inclined and can probably give more details than I.


Erich