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 discards 5b5cd407c14c50976455f337ca479f5c012c3eab (commit) discards aa7a454e03c9252cbb4fea7c3689abff88fa4ba4 (commit) discards 9aad92338c3150fe5314b2fe20c8bf6dceaee778 (commit) discards b3fca0a2e6f1162cec99f23ba3fc8693c4236ba5 (commit) via 774774961025b79d84a466f75c651ce17c946928 (commit) via 25b4ef279925a964b0de0ed8675d75e1532bf577 (commit) via ad4b66830a6198a9920570380f673f547a488c2f (commit)

This update added new revisions after undoing existing revisions. That is to say, the old revision is not a strict subset of the new revision. This situation occurs when you --force push a change and generate a repository containing something like this:

* -- * -- B -- O -- O -- O (5b5cd407c14c50976455f337ca479f5c012c3eab) \ N -- N -- N (774774961025b79d84a466f75c651ce17c946928)

When this happens we assume that you've already had alert emails for all of the O revisions, and so we here report only the revisions in the N branch from the common base, B.

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 774774961025b79d84a466f75c651ce17c946928 Author: Eli Schwartz via arch-projects arch-projects@archlinux.org Date: Tue Jun 4 12:11:20 2019 -0400

doc: add manpage for the new offload-build tool

Signed-off-by: Eli Schwartz eschwartz@archlinux.org

commit 25b4ef279925a964b0de0ed8675d75e1532bf577 Author: Eli Schwartz via arch-projects arch-projects@archlinux.org Date: Tue Jun 4 12:11:19 2019 -0400

Add new tool: offload-build

This tool is useful for running makechrootpkg on a remote build server, and is by default hooked up to send a PKGBUILD and initiate a build on our shiny new build server "dragon".

Signed-off-by: Eli Schwartz eschwartz@archlinux.org

commit ad4b66830a6198a9920570380f673f547a488c2f Author: Eli Schwartz via arch-projects arch-projects@archlinux.org Date: Thu May 9 22:58:26 2019 -0400

Revert "makechrootpkg: sync_chroot: Make more general."

This reverts commit 6d1992909cc46e293027ff488ae2632047603e66.

It has never worked. In commit c86823a2d4a4152c71faa1c3bab227756232996f it was noted that it compared the device numbers for [[ $1 = $1 ]] which was a useless check and always returned true, for *any* btrfs filesystem. Now that the function is corrected to compare [[ $1 = $2 ]] the check is still useless, but this time because it always returns false -- btrfs subvolumes on the same filesystem do *not* share device numbers.

So let's go back to the original working implementation that only matters in terms of makechrootpkg, and just checks if makechrootpkg's root working directory is btrfs (in which case we know it will be a subvolume because mkarchroot will create it that way).

This restores our special support for the btrfs filesystem.

Signed-off-by: Eli Schwartz eschwartz@archlinux.org

-----------------------------------------------------------------------

Summary of changes: .gitignore | 1 + Makefile | 1 + finddeps.in | 41 +++++++++++++++++++++++++++++++++++++++++ zsh_completion.in | 6 +++++- 4 files changed, 48 insertions(+), 1 deletion(-) create mode 100644 finddeps.in

hooks/post-receive