[Pkg-ltsp-devel] Bug#780591: ltsp-client-builder fails when installing Debian Edu combined server in virtualbox environment

[Vagrant Cascadian]

Control: severity -1 serious
Control: tags -1 patch

On 2015-03-20, Wolfgang Schweer wrote:
> Control: reassign -1 ltsp-client-builder-udeb
>
> On Wed, Mar 18, 2015 at 07:48:05PM +0100, Wolfgang Schweer wrote:
>> On Tue, Mar 17, 2015 at 10:00:08PM +0100, Wolfgang Schweer wrote:
>> > With this (trivial) modification installation succeeded.
>> > 
>> > --- a/postinst	2015-03-06 10:00:00.000000000 +0100
>> > +++ ltsp-client-builder.postinst	2015-03-17 21:39:38.824682599 +0100
>> > @@ -64,7 +64,7 @@
>> >  db_progress STEP 1
>> >  
>> >  if [ "$USE_CDROM" != "false" ] && [ ! -f /target/media/cdrom/.disk/info ]; then
>> > -    chroot /target mount /media/cdrom
>> > +    mount /dev/cdrom /target/media/cdrom
>> >      log "mounting /media/cdrom"
>> >  fi
>>   
>> Tested once again using the just rsynced usbstick ISO image (containing 
>> newest udebs): LTSP chroot installation fails as before.
>> 
>> After /var/lib/dpkg/info/ltsp-client-builder.postinst (d-i env) had been 
>> modified like stated above, choosing LTSP chroot installation out of the 
>> d-i main-menu once again made the chroot installation start.
>
> IMO there is no way for debian-edu-config to fix this LTSP chroot 
> installation failure as it seems to be related to d-i components.
>
> Please consider to check and test the provided patch.

I can test the patch to make sure it doesn't break anything, but I was
not able to reproduce the issue with debian-installer daily images using
libvirt+qemu+kvm; it would be surprising if virtualbox were different.

I suspect there may be something different in the debian-edu installer
images. There is also the very real possibility that something changed
in the debian-installer mounting of the cdrom again.

The patch effectively reverts the fix that corrected a nearly identical
problem earlier; I worry the patch would fix one problem only to
reintroduce a different variation of the same problem:

  https://bugs.debian.org/758500


In any case, ltsp-client-builder needs to be more resilient to a variety
of media mount locations and states... thus bumping the severity.


live well,
  vagrant
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 818 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-ltsp-devel/attachments/20150320/ed3a16e5/attachment.sig>