[Grml] Cannot build grml from within grml

[Marc Haber]

On Sat, Sep 16, 2017 at 02:59:46PM +0200, Michael Prokop wrote:
> * Marc Haber [Fri Sep 15, 2017 at 02:11:41PM +0200]:
> > On Thu, Sep 14, 2017 at 09:41:55AM +0200, Marc Haber wrote:
> > > I retried with grml-live 0.29.7 as it is on 2017.05 proper.
> 
> > > On Sun, Sep 10, 2017 at 01:55:43PM +0200, Marc Haber wrote:
> > > > [ WARN ] Skipping stage 'fai dirinstall' as /root/output/grml_chroot exists already.
> 
> > > This warning is also present in the output of 0.29.7, but...
> 
> > > > [  OK  ] No missing packages found, generating empty junit report.
> > > > [  OK  ] Generating /conf/bootid.txt with entry grml001.
> > > > [ FAIL ] Can not access GRUB efi image /root/output/grml_chroot//boot/bootx64.efi, required for Secure Boot support
> 
> > > ... this FAIL does not happen with 0.29.7. 0.29.7 fails significantly
> > > later than 0.31.
> 
> > On a grml-full built on Debian unstable, with the current jenkins
> > grml-live, using:
> > sudo grml-live -A -V -s sid -c DEBORPHAN,GRMLBASE,GRML_FULL,RELEASE,AMD64,IGNORE,SNAPSHOT -r "test20170915" -g grml64 -o ~/grml-remaster/tmp
> > the behavior is the same. Can't get any more current than that, can I?
> 
> I'd need the full command line output (including the startup message
> which prompts for user input before execution) to be able to tell
> you why:
> 
> | Executing shell: GRMLBASE/45-grub-images
> 
> doesn't seem to be executed on your system.

Pasted below.

> Though I'm a bit lost on what exactly you're doing

My idea is the following:

- on a disconnected, airgapped system:
- boot an especially tailored grml flavor from r/o medium
- generate a GnuPG Master Key
- generate a new iso of the same grml flavor _including_ the key
- burn that one to a new r/o medium
- have a self-contained system for GnuPG operation that _includes_ the
  master key, eliminating the need to wriggle wround with two mediums

> and how your
> environment looks like. Should I be able to reproduce your situation
> with just taking the official grml64-small 2017.05 ISO and rebuild
> that one with grml-live -e...?

- boot grml-full 2017.05 (the official release)
- install grml-live_0.31.0+0~20170907073759.330~1.gbp7f38fb_all.deb
- grml-live -e /dev/cdrom -o output/

> > I can just guess that grml-live -e /dev/cdrom doesn't copy bootx86.efi
> > correctly from the mounted ISO image. The file _is_ in
> > /efi/boot/bootx64.efi on the medium mounted to /lib/live/mount/medium.
> > Where does grml-live expect it to be?
> 
> As the error message says, it expects
> /boot/bootx64.efi to be there
> (/root/output/grml_chroot//boot/bootx64.efi in your case)

that file is not there.

Greetings
Marc


root at grml ~ # grml-live -e /dev/cdrom -o output/
[  OK  ] Sourcing configuration file /etc/grml/grml-live.conf

grml-live [0.31.0+0~20170907073759.330~1.gbp7f38fb]: check your configuration (or use -F to force execution):

  FAI classes:       GRMLBASE,GRML_FULL,AMD64
  Config directory:  /etc/grml/fai
  main directory:    /root/output
  Extract ISO:       /dev/sr0
  Chroot target:     /root/output/grml_chroot
  Build target:      /root/output/grml_cd
  ISO target:        /root/output/grml_isos
  Grml name:         grml
  Release name:      grml-live rocks
  Build date:        2017-09-17
  Grml version:      0.0.1
  Debian suite:      testing
  Architecture:      amd64
  Boot method:       isolinux
  Hybrid method:     isohybrid
  Template files:    /usr/share/grml-live/templates

Is this ok for you? [y/N] y

[  OK  ] Logging actions to logfile /root/output/grml_logs/grml-live.log
[  OK  ] Unpacking ISO from /dev/sr0
Parallel unsquashfs: Using 4 processors
69110 inodes (72966 blocks) to write

[===========================================================-] 72966/72966 100%

created 59674 files
created 6713 directories
created 9365 symlinks
created 37 devices
created 0 fifos
[ WARN ] Skipping stage 'fai dirinstall' as /root/output/grml_chroot exists already.
[  OK  ] No missing packages found, generating empty junit report.
[  OK  ] Generating /conf/bootid.txt with entry grml001.
[ FAIL ] Can not access GRUB efi image /root/output/grml_chroot//boot/bootx64.efi, required for Secure Boot support
[ WARN ] Possible reason is failure to run /etc/grml/fai/config/scripts/GRMLBASE/45-grub-images
grml-live -e /dev/cdrom -o output/  37.49s user 3.31s system 334% cpu 12.206 total
50 root at grml ~ # ls output/grml_chroot                                       :(

-- 
-----------------------------------------------------------------------------
Marc Haber         | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany    |  lose things."    Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature |  How to make an American Quilt | Fax: *49 6224 1600421