Without this setting, Git exits with an error when the repository is not
owned by the current user. This messes with our shared srcdest.

yaml: truthy value should be one of [false, true] (truthy)
yaml: wrong indentation: expected 4 but found 2 (indentation)
yaml: too few spaces before comment (comments)
yaml: missing starting space in comment (comments)
yaml: too many blank lines (1 > 0) (empty-lines)
yaml: too many spaces after colon (colons)
yaml: comment not indented like content (comments-indentation)
yaml: no new line character at the end of file (new-line-at-end-of-file)
load-failure: Failed to load or parse file
parser-error: couldn't resolve module/action 'hosts'. This often indicates a misspelling, missing collection, or incorrect module path.

rmdir of subvolumes is supported since 4.18

Frederik Schwan authored 4 years ago and Sven-Hendrik Haase committed 4 years ago

also use systemd instead of service module

Needed to get rid of subvolumes created by tmpfiles.

Added makerepropkg to the list of tools allowed on archbuild role.

Uniformly use the expension flag instead of the modifier.

Use single quotes instead of backslashes for the outer quoting to reduce
the amount of quoting needed.

Needed because we still have the login (command) shell to deal with.

Very useful to debug upgrades, especially when doing things like meson
ports, where I caught problems multiple times.

Try not to scan deep into directory trees and exit early if we find a
new enough file. An LLVM SVN checkout has a lot of files.

I don't think zsh glob can do this so reimplement in bash+find.

Signed-off-by: Florian Pritz <bluewind@xinu.at>

Installing some services and config files doesn't really matter. What
matters is if they are enabled so only use the conditional there. The
rest is easier and less confusing if it just installs the files all the
time. Otherwise we'd need a second task that performs the other case and
then if we change something we'd also have to adjust that task. That's
unnecessarily error prone.

Signed-off-by: Florian Pritz <bluewind@xinu.at>

Signed-off-by: Florian Pritz <bluewind@xinu.at>

Eli Schwartz authored 6 years ago and Florian Pritz committed 6 years ago

When using restrictive sudoers profiles, the builtin mechanism for
whitelisting this variable on the sudo command line does not work.

Explicitly whitelist it anyway by matching on the ARCHBUILD role.

The container buildusers need to be able to write to SRCDEST, so we need
world-writeability. Argh.