[elbe-users] Create source CD-ROM

Yegor Yefremov yegorslists at googlemail.com
Wed Jul 3 09:37:45 CEST 2019


Hi Kurt,

On Tue, Jul 2, 2019 at 3:41 PM Kurt Kanzenbach
<kurt.kanzenbach at linutronix.de> wrote:
>
> Hi,
>
> On Tue, Jul 02, 2019 at 02:57:22PM +0200, Yegor Yefremov wrote:
> > I'm trying to create a source code CR-ROM using older ELBE version:
> >
> > % ./elbe --version
> > elbe v2.3 Ubuntu 18.04
> >
> > ./elbe initvm --skip-build-bin submit --directory=initvm some.xml
> >
> > The boot medium (sdcard.img.gz fro OMAP3) will be created without a
> > problem but I cannot see any CD-ROM image and the log file shows the
> > following text:
> >
> > running cmd +reprepro --keepunreferencedfiles --export=never --basedir
> > "/var/cache/elbe/3722489e-f070-4b08-9f47-1fd96abae043/srcrepo" -C main
> > -P normal -S misc includedsc stretch
> > /var/cache/elbe/3722489e-f070-4b08-9f47-1fd96abae043/ch
> > root/var/cache/elbe/sources/gnupg2_2.1.18-8~deb9u4.dsc+
> > ------------------------------------------------------------------------------
> > gpgme returned an general error verifing signature with
> > '7618196529AE5FF8' in
> > '/var/cache/elbe/3722489e-f070-4b08-9f47-1fd96abae043/chroot/var/cache/elbe/sources/gnupg2_2.1.18-8~deb9u4.dsc'!
> > Try running gpg --verify
> > '/var/cache/elbe/3722489e-f070-4b08-9f47-1fd96abae043/chroot/var/cache/elbe/sources/gnupg2_2.1.18-8~deb9u4.dsc'
> > manually for hints what is happening.
> > If this does not print any errors, retry the command causing this message.
> > There have been errors!
> > ------------------------------------------------------------------------------
> >
> > Command failed with errorcode 251
> > Build failed
> > Traceback (most recent call last):
> >   File "/var/cache/elbe/devel/elbepack/asyncworker.py", line 116, in execute
> >     skip_pbuild=self.skip_pbuilder)
> >   File "/var/cache/elbe/devel/elbepack/elbeproject.py", line 357, in build
> >     xml=self.xml)
> >   File "/var/cache/elbe/devel/elbepack/cdroms.py", line 65, in mk_source_cdrom
> >     repo.includedsc( dsc, force=True )
> >   File "/var/cache/elbe/devel/elbepack/repomanager.py", line 234, in includedsc
> >     self._includedsc (path, self.repo_attr.codename, component)
> >   File "/var/cache/elbe/devel/elbepack/repomanager.py", line 221, in _includedsc
> >     self.log.do( 'reprepro --keepunreferencedfiles --export=never
> > --basedir "' + self.fs.path  + '" -C ' + component + ' -P normal -S
> > misc includedsc ' + codename + ' ' + path )
> >   File "/var/cache/elbe/devel/elbepack/asciidoclog.py", line 72, in do
> >     raise CommandError(cmd, ret)
> > CommandError
> >
> >
> > Exception:
> >
> >
> > mhf)
> > pmstatus:libwacom-common:16.0028:Preparing libwacom-common (armhf)
> > pmstatus:libwacom-common:16.0727:Unpacking libwacom-common (armhf)
> >
> > Is this a known bug or am I missing some configuration?
>
> That seems like a known bug. It's fixed in ELBE v2.4 by
>
>  64c322bfeb70 (repomanager: add fallback, when reprepro fails to add dsc)
>
> Can you retry using ELBE v2.4?

I'm trying to perform the same operation with ELBE v8 and have the
following issue:

% elbe initvm create --directory=initvm


                   ✭
Import ubuntu-keyring-2012-cdimage.gpg:
gpg: key D94AA3F0EFE21092: 3 signatures not checked due to missing keys
gpg: key D94AA3F0EFE21092: public key "Ubuntu CD Image Automatic
Signing Key (2012) <cdimage at ubuntu.com>" imported
gpg: Total number processed: 1
gpg:               imported: 1
Import ubuntu-keyring-2012-archive.gpg:
gpg: key 3B4FE6ACC0B21F32: 3 signatures not checked due to missing keys
gpg: key 3B4FE6ACC0B21F32: public key "Ubuntu Archive Automatic
Signing Key (2012) <ftpmaster at ubuntu.com>" imported
gpg: Total number processed: 1
gpg:               imported: 1
--2019-07-03 09:26:35--  http://ftp.de.debian.org//debian/dists/stretch/Release
Resolving ftp.de.debian.org (ftp.de.debian.org)... 141.76.2.4
Connecting to ftp.de.debian.org (ftp.de.debian.org)|141.76.2.4|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 117943 (115K)
Saving to: ‘/tmp/tmp5O8QA7/Release’

/tmp/tmp5O8QA7/Release
100%[======================================================================================================================================>]
115.18K  --.-KB/s    in 0.07s

2019-07-03 09:26:35 (1.64 MB/s) - ‘/tmp/tmp5O8QA7/Release’ saved [117943/117943]

Debian Archive Automatic Signing Key <ftpmaster at debian.org>
(A1BD8E9D78F7FE5C3E65D8AF8B48AD6246925553):
KEY REVOKED!
Debian Archive Automatic Signing Key <ftpmaster at debian.org>
(126C0D24BD8A2942CC7DF8AC7638D0442B90D010):
VALID (Untrusted).
Debian Stable Release Key <debian-release at lists.debian.org>
(067E3C456BAE240ACEE88F6FEF0F382A1A7B6500):
VALID (Untrusted).
Failure to download kernel/initrd debian Package:

InvalidSignature Failed to verify Release file

Check Mirror configuration
'elbe init' Failed
Giving up

At first I had this issue [1]. Then I've added the keys via:

sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 8B48AD6246925553

Am I missing a special keys related FAQ in ELBE's documentation?

[1] https://github.com/Linutronix/elbe/issues/206

Cheers,
Yegor



More information about the elbe-users mailing list