This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "The official devtools repository". The branch, master has been updated via 2243a276e4b84dedc8d362ad66716026688949c0 (commit) via 578a62f1e0713b0df9722470146fb85fb819202c (commit) via 4228d79b635d1a2f448492f64eacbe83bc40e0cc (commit) via 5b9c06d275dd1a2dca09514e39f853bd9c57be3a (commit) via 82e6bfcd7ae9a0dc2e9ef3c48d5477aa615bef9e (commit) via 35da846ddeecbdb99cd4f7a5ea13d650b1fdfda3 (commit) via 2fd5931a8c67289a8a4acd327b3ce99a5d64c8c7 (commit) via 6098253f6f362909c8a9bfc972b3ea72b30428a1 (commit) from c1a056c9a8f42e1a8e1f66b265b7ccbd1a2cb1ee (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- commit 2243a276e4b84dedc8d362ad66716026688949c0 Author: Jan Alexander Steffens (heftig) Date: Wed Apr 5 22:20:01 2017 +0200 makechrootpkg: Unindent as suggested in 2fd5931 commit 578a62f1e0713b0df9722470146fb85fb819202c Author: Luke Shumaker Date: Wed Apr 5 15:36:03 2017 -0400 mkarchroot: Don't let the environment affect pacstrap (sans proxy settings). A previous iteration of this change (libretools commit d7dcce53396d) simply inserted `env -i` to clear the environment. However, that lead to it ignoring proxy settings, which some users had problems with: https://labs.parabola.nu/issues/487: > To fix other bugs, the pacstrap environment is blank, which also > means that the proxy settings are blank. So (in libretools commit d17d1d82349f), I changed it to use `declare -x` to inspect the environment, and create a version of it only consisting of variables ending with "_proxy" (case-insensitive). I honestly don't remember what "other bugs" prompted me to clear the environment in the first place. commit 4228d79b635d1a2f448492f64eacbe83bc40e0cc Author: Luke Shumaker Date: Wed Apr 5 15:36:02 2017 -0400 makechrootpkg: Improve status messages. In sync_chroot(), this makes the messages be a bit more precise with exactly which thing they are syncing where. This is based on my users expressing confusion at what is going on (especially when something is taking a long time, and they have to blame something for blocking). With these changes, I haven't gotten such confusion in a long time (but maybe my users just got used to it). In delete_chroot(), this changes "temporary copy" to "chroot copy", since in Parabola's version of the tools, the function can get called from other places, and it isn't necessarily operating on a temporary copy. commit 5b9c06d275dd1a2dca09514e39f853bd9c57be3a Author: Luke Shumaker Date: Wed Apr 5 15:36:01 2017 -0400 mkarchroot, arch-nspawn: Add an `-s` flag to inhibit `setarch`. This allows us to run an ARM chroot on an x86 box; as the binfmt runner will set the architecture for us, and the x86 `/usr/bin/setarch` program won't know about the ARM architecture string. commit 82e6bfcd7ae9a0dc2e9ef3c48d5477aa615bef9e Author: Luke Shumaker Date: Wed Apr 5 15:36:00 2017 -0400 mkarchroot, arch-nspawn: Add an `-f` flag to add files to copy. This allows us to copy in files like `qemu-arm-static`, which is necessary for running an ARM chroot on an x86 box. commit 35da846ddeecbdb99cd4f7a5ea13d650b1fdfda3 Author: Luke Shumaker Date: Wed Apr 5 15:35:59 2017 -0400 makechrootpkg: Adjust to have the functions work with `set -u`. Even though main() doesn't call `set -u`; this way the functions will continue to work if copied into an environment with `set -u`, or so that we are ready if we ever want to start using `set -u`. commit 2fd5931a8c67289a8a4acd327b3ce99a5d64c8c7 Author: Luke Shumaker Date: Wed Apr 5 15:35:58 2017 -0400 makechrootpkg: Have functions be more function-y. Rather than them simply being named blocks of code with braces around them. That is: have them take things via arguments rather than global variables. Specific notes: - create_chroot->sync_chroot: I pulled out locking the destination chroot; getting that lock is now the caller's responsibility. It still handles locking the source chroot though. I pulled the `if [[ ! -d $copydir ]] || $clean_first;` check out; it is now the caller's responsibility to use that check when deciding if to call sync_chroot. However, when pulling that check out, I left it as `if true;`, to keep an indentation level. This patch has had to be rebased/merged many times, and changing the indentation is a sure way to make that go less smoothly; I'm not going to re-indent this block until I see the check removed in the git.archlinux.org/devtools.git repository. - install_packages: 1. Receive the list of packages as arguments, rather than a global variable. 2. Make the caller responsible for looking at PKGBUILD. From the name and arguments, one would never expect it to look at PKGBUILD. commit 6098253f6f362909c8a9bfc972b3ea72b30428a1 Author: lukeshu@parabola.nu Date: Wed Apr 5 15:35:57 2017 -0400 Handle makepkg.conf more consistently ----------------------------------------------------------------------- Summary of changes: arch-nspawn.in | 16 ++++++- checkpkg.in | 6 ++- commitpkg.in | 6 ++- makechrootpkg.in | 131 ++++++++++++++++++++++++++++++++++++++++--------------- mkarchroot.in | 19 +++++++- rebuildpkgs.in | 7 +++ 6 files changed, 144 insertions(+), 41 deletions(-) hooks/post-receive -- The official devtools repository