Commit 30d9ce83 authored by Holger Levsen's avatar Holger Levsen

reproducible Arch: chown $BUILDDIR to build2 user so that it becomes writeable

Signed-off-by: Holger Levsen's avatarHolger Levsen <holger@layer-acht.org>
parent 3977ee6a
......@@ -319,20 +319,19 @@ See link:https://jenkins.debian.net/userContent/about.html["about jenkins.debian
* use db - see https://tests.reproducible-builds.org/reproducibledb.html
** scheduler.sh:
*** comparing versions is probably needed: if its not empty it must be higher (due to repo constraints), but it can be even higher than in the repo, because we build trunk
*** dont delete packages which are building?
*** check/make sure that packages which are newer in trunk than repo are only scheduled once (they are not scheduled when trunk is updated at all... we need to use asp to find that out)
*** use asp to update trunk packages?
** html:
*** leave all pkg.html files, delete them (much) later, then check all pkg.* files are gone
*** recreate them newly as index.html
*** create new job to recreate all pkg pages
*** create json
** misc:
*** nothing to do here: we share /var/log/jenkins/reproducible-race-conditions.log and reproducible-remote-error.log with debian, is ok? should be. (else fix maintenance job and handle_race_condition() and handle_remote_error())
*** make build.sh respect pacman exit code, see FIXME in _html_.sh
*** comparing versions (in scheduler) is probably needed: if its not empty it must be higher (due to repo constraints), but it can be even higher than in the repo, because we build trunk
*** debian uses a table removed_packages, should this be used here too?
*** debian uses a table manual_scheduler to limit the amount of packages someone can schedule per day...
*** should breakages job look for archlinux breakages?
*** should breakages job look for archlinux breakages? for which case
** using notes.git could be next
* rebuilding against the archlinux repos
......
......@@ -408,6 +408,7 @@ second_build() {
# create group and user
schroot --run-session -c $SESSION --directory "$BUILDDIR" -u root -- groupadd build2
schroot --run-session -c $SESSION --directory "$BUILDDIR" -u root -- useradd -g build2 build2
schroot --run-session -c $SESSION --directory "$BUILDDIR" -u root -- chown -R build2:build2 "$BUILDDIR"
# some more output for debugging
set -x
# remove possible lock in our local session (happens when root maintenance update running while session starts)
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment