[elbe-devel] (not) very informative error message

[Manuel Traut]

Hi Lukasz,

> >But probably the chroot directory was deleted after detecting a failure
> >:-/
> >You can avoid this by editing elbepack/rfs.py 'def debootstrap' and set
> >the cleanup variable in the exception handler to False.
> 
> I must admit I am having a hard time debugging my builds even if I get past the debootstrap stage. The output in log.txt ends in:
> 
> I: Base system installed successfully.
> 
> which I assume is a positive sign, but then I don't get any update for a long time (I assume elbe is trying to execute the <finetuning> section and then install the packages in the <pkg-list> during that time) and finally I get:
> 
> commiting changes failed
> Build failed !!!
> 
> Failed to commit the AptCache changes.
> Most likely is, that packages failed to download.
> Probable cause might be:
> - Problems with Internet Connection
> - Broken mirrors
> 
> Is there a way to increase verbosity for finetuning and installing stages? Or how could I otherwise check what went wrong? - I used 'elbe initvm --keep-files submit' to be able to inspect the project's directory in the intitvm but it only contains log.txt, source.xml and chroot directory.

please try the following:

elbe initvm attach
elbe chroot /var/cache/elbe/<UUID>
apt-get install vim-nox # or sth. else

maybe your apt-cache is in a strange state, e.g. by invalid dependencies.

  Manuel