| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
|
|
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
|
|
|
|
|
|
build-assignment has
|
|
which architecture that package should be built on
|
|
revert most of it and add a TODO
|
|
|
|
|
|
whether build slave of architecture `runs_on` can build package for architecture `built_for`
|
|
|
|
|
|
to 2k
|
|
|
|
even though -d is active
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
be changed!
|
