[elbe-devel] Source-Code CD image in isolated network
Mueller Benjamin (MH/EES1)
b.mueller2 at moehwald.de
Thu Aug 9 13:04:14 CEST 2018
Hi Manuel,
thanks for the feedback.
I have applied the patch to the version 2.9.11. Now the Source CD will be created.
But I get a lot messages, regarding missing source packages.
The build log contains about ~800 "source packages can not be downloaded" messages.
After a short investigation it seems that the missing packages are Jessie packages. It seems that the Jessie packages comes from the initvm. Because the initvm will be created based on Jessie by default.
Is it possible to skip the download for the initvm packages?
Or how can I avoid this error messages? Because if there is a really needed error message this gets lost in the fog.
Thanks in advance.
Mit freundlichen Grüßen / Best regards
Benjamin Mueller
Engineering Electrical and Software Systems, Test Technology (MH/EES1)
Moehwald GmbH | Postfach 1456 | 66405 Homburg | GERMANY | www.moehwald.de
Tel. +49 6841 707-235 | Mobil +49 173 3059139 | Fax +49 6841 79-0 | b.mueller2 at moehwald.de
Sitz: Homburg/Saar, Registergericht: Saarbrücken HRB 2812
Geschäftsführung: Dr. Christian Artmann, Sven Steib
-----Ursprüngliche Nachricht-----
Von: Manuel Traut [mailto:manut at linutronix.de]
Gesendet: Mittwoch, 8. August 2018 11:26
An: Mueller Benjamin (MH/EES1) <b.mueller2 at moehwald.de>
Cc: elbe-devel at linutronix.de; lucia at linutronix.de; jan at linutronix.de
Betreff: Re: [elbe-devel] Source-Code CD image in isolated network
Hi,
> we are evaluating the Elbe tooling in our company and have the following problem.
>
> Our buildsystem is isolated from the internet. To establish a build we have an internal mirror of the debian repositories (binaries and sources).
> The build of our linux prototype work as expected and we have a running system. The build produce all needed binaries and images (e.g. the binary CD-ROM image).
>
> But the source-code CD-ROM image will not be generated. The elbe build tries to fetch the sources from the official debian repositories instead of from our internal repository, which is not possible in an isolated environment.
>
> BTW: It also does not result in a error message during the build. Only a exception in the log files....
>
> running cmd +reprepro --export=force --basedir
> "/var/cache/elbe/b3bb314d-f93b-42d7-9edb-02dad3aba205/srcrepo" update+
> ----------------------------------------------------------------------
> -------- aptmethod error receiving
> 'http://ftp.de.debian.org/debian/dists/jessie/Release':
> 'Could not resolve 'ftp.de.debian.org''
> There have been errors!
> ----------------------------------------------------------------------
> --------
>
> Command failed with errorcode 255
> Build failed
> Traceback (most recent call last):
> File "/usr/lib/python2.7/dist-packages/elbepack/asyncworker.py", line 129, in execute
> skip_pbuild=self.skip_pbuilder)
> File "/usr/lib/python2.7/dist-packages/elbepack/elbeproject.py", line 514, in build
> xml=self.xml)
> File "/usr/lib/python2.7/dist-packages/elbepack/cdroms.py", line 41, in mk_source_cdrom
> cdrom_size)
> File "/usr/lib/python2.7/dist-packages/elbepack/repomanager.py", line 398, in __init__
> maxsize)
> File "/usr/lib/python2.7/dist-packages/elbepack/repomanager.py", line 91, in __init__
> self.gen_repo_conf()
> File "/usr/lib/python2.7/dist-packages/elbepack/repomanager.py", line 165, in gen_repo_conf
> '" update')
> File "/usr/lib/python2.7/dist-packages/elbepack/asciidoclog.py", line 62, in do
> raise CommandError(cmd, ret)
> CommandError
this is already fixed, but not released:
https://github.com/Linutronix/elbe/issues/153
5d4d96b28f2d970b6eba8e85800bd5c64f9ae5f3
it will be in the next elbe-testing release.
Regards,
Manuel
> Is it a configuration issue in our elbe build?
>
> How we have done it:
>
> · Build has been done with elbe 2.9.11
>
> · We have created a initvm: elbe initvm create --directory=<dir>
>
> · We submit a build xml file: elbe initvm submit mh-production.xml --directory=<dir> --output=<dir2>
>
>
> Mirrors in mh-production.xml
>
> <mirror>
> <primary_host>apt-cacher:3142/ftp.de.debian.org</primary_host>
> <primary_path>debian</primary_path>
> <primary_proto>http</primary_proto>
> <url-list>
> <url>
> <binary>http://apt-cacher:3142/ftp.debian.org/debian stretch-backports main contrib</binary>
> <source>http://apt-cacher:3142/ftp.debian.org/debian stretch-backports main contrib</source>
> </url>
> <url>
> <binary>http://apt-cacher:3142/security.debian.org/debian-security stretch/updates main contrib non-free</binary>
> <source>http://apt-cacher:3142/security.debian.org/debian-security stretch/updates main contrib non-free</source>
> </url>
> <url>
> <binary>http://apt-cacher:3142/ftp.debian.org/debian stretch main contrib non-free</binary>
> <source>http://apt-cacher:3142/ftp.debian.org/debian stretch main contrib non-free</source>
> </url>
> <url>
> <binary>http://reprepro:8081/apt/debian/prisma-unstable stretch main</binary>
> <source>http://reprepro:8081/apt/debian/prisma-unstable stretch main</source>
> </url>
> </url-list>
> </mirror>
>
>
> So in our eyes the source code fetch should be done with the related source entries specified in the mirror node.
>
>
> Could you please help us?
>
>
> Mit freundlichen Grüßen / Best regards
>
> Benjamin Mueller
>
> Engineering Electrical and Software Systems, Test Technology (MH/EES1)
> Moehwald GmbH | Postfach 1456 | 66405 Homburg | GERMANY |
> www.moehwald.de<http://www.moehwald.de>
> Tel. +49 6841 707-235 | Mobil +49 173 3059139 | Fax +49 6841 79-0 |
> b.mueller2 at moehwald.de<mailto:b.mueller2 at moehwald.de>
>
> Sitz: Homburg/Saar, Registergericht: Saarbrücken HRB 2812
> Geschäftsführung: Dr. Christian Artmann, Sven Steib
>
>
>
> _______________________________________________
> elbe-devel mailing list
> elbe-devel at linutronix.de
> https://lists.linutronix.de/mailman/listinfo/elbe-devel
More information about the elbe-devel
mailing list