| Age | Commit message (Collapse) | Author |
|---|
|
python, perl and ruby
|
|
|
|
|
|
|
|
"master-mirror-availability" test
|
|
|
|
repository-stability combinations
|
|
|
|
|
|
of the build command, not for the architecture of the build slave!
|
|
privileges non-fatal
|
|
message regex
|
|
insufficient for removing still mounted submounts (e.g. /run) - we now run recursively_umount_and_rm to (hopefully) clean the build chroot entirely
|
|
directory
|
|
|
|
|
|
|
|
parsing
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
architectures with toolchain build orders
|
|
built the longest time ago" (4th "digit")
|
|
|
|
worst that happens is that these architectures accumulate packages in their build lists
|
|
|
|
per-arch basis, now
|
|
|
|
and per-stability
|
|
|
|
|
|
|
|
prefered one
|
|
not getting the prefered package when -s :without_systemd-nspawn: was active
|
|
archlinux/devtool's lib/archroot.sh: is_subvolume(), is_same_fs() and subvolume_delete_recursive() - now it should do the correct thing on btrfs, too
|
|
|
|
|
|
end, too
|
|
|
|
|
|
|
|
|
|
|
|
|
|
thus we have also more invalid architecture combinations build_assignment <-> binary_package
|
|
architecture the installed packages actually are
|
