From: Henning Schild <henning.schild@siemens.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: <isar-users@googlegroups.com>
Subject: Re: [PATCH] buildchroot: build debian packages as "builder" not "root"
Date: Thu, 8 Nov 2018 15:54:23 +0100 [thread overview]
Message-ID: <20181108155423.590f43de@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <9fc6082e-49ae-2e9c-6331-90b80b66baf0@siemens.com>
Am Thu, 8 Nov 2018 14:32:42 +0100
schrieb Jan Kiszka <jan.kiszka@siemens.com>:
> On 26.10.18 12:49, [ext] Henning Schild wrote:
> > We used to build packages as "root" and now do that as a regular
> > user. Not building as "root" allows us to find mistakes in
> > debian/rules where privileged operations are used while they should
> > not (a sudo was found in a rules-file). Further some build steps
> > might actually expect to not run as root (seen in openssl test
> > suite).
> >
> > Not building as root should increase overall quality and brings us
> > closer to how debian packages are build by others.
>
> I strongly suspect this is the cause for more and more rebuild errors
> of this kind:
>
> | make[1]: Leaving directory '/home/builder/u-boot/u-boot-v2018.09'
> | dh_clean -O--parallel
> | dpkg-source -I -b u-boot-v2018.09
> | dpkg-source: warning: no source format specified in
> debian/source/format, see dpkg-source(1) | dpkg-source: warning:
> source directory 'u-boot-v2018.09' is not
> <sourcepackage>-<upstreamversion> 'u-boot-2018.09' | dpkg-source:
> info: using source format '1.0' | dpkg-source: info: building u-boot
> in u-boot_2018.09.tar.gz | dpkg-source: error: cannot write
> u-boot_2018.09.dsc: Permission denied | dpkg-source: info: building
> u-boot in u-boot_2018.09.dsc | dpkg-buildpackage: error: dpkg-source
> -I -b u-boot-v2018.09 gave error exit status 13 | WARNING: exit code
> 13 from a shell command. | ERROR: Function failed: do_build (log file
> is located
> at /work/build/tmp/work/long-life-ebsy-armhf/u-boot-2018.09-r0/temp/log.do_build.15761)
>
> Are we missing some cleandirs in dpkg[-base].class?
Does the file exist and can not be written by builder, or does it not
exist and the dir must not receive new files. I am guessing the former
but have not clue why.
Maybe you can tell be how to reproduce this.
Henning
> Jan
>
next prev parent reply other threads:[~2018-11-08 14:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-26 10:49 Henning Schild
2018-10-29 10:54 ` Baurzhan Ismagulov
2018-10-29 11:27 ` Henning Schild
2018-10-29 11:44 ` Baurzhan Ismagulov
2018-11-01 13:27 ` Maxim Yu. Osipov
2018-11-08 13:32 ` Jan Kiszka
2018-11-08 14:54 ` Henning Schild [this message]
2018-11-09 9:14 ` Jan Kiszka
2018-11-09 9:34 ` Henning Schild
2018-11-09 9:37 ` Jan Kiszka
2018-11-09 11:16 ` Jan Kiszka
2018-11-09 15:49 ` Baurzhan Ismagulov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20181108155423.590f43de@md1za8fc.ad001.siemens.net \
--to=henning.schild@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox