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 6da90b2028da0bc504be7ff60873dd2719818a1e (commit) via 40f0179a5e74d6d3babbefdeae21fd374be0e090 (commit) via ffb5003fdacaece3540ba167f7e965a122133af0 (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 (6da90b2028da0bc504be7ff60873dd2719818a1e) \ N -- N -- N (40f0179a5e74d6d3babbefdeae21fd374be0e090) 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 40f0179a5e74d6d3babbefdeae21fd374be0e090 Author: Eli Schwartz <eschwartz@archlinux.org> Date: Sun Mar 18 01:46:44 2018 -0400 makechrootpkg: fix verifysource with pacman-git In pacman-git commit d8717a6a9666ec80c8645d190d6f9c7ab73084ac makepkg started checking that the setuid/setgid bit could be removed on the $BUILDDIR in order to prevent this propagating to the packages themselves. Unfortunately, this requires the temporary builddir used during the --verifysource stage of makepkg, to be owned by $makepkg_user which was not the case as it is created as root using mktemp (and given world rwx in addition to the restricted deletion bit.) Obviously makepkg cannot chmod a directory that it does not own. Fix this by making $makepkg_user the owner of that directory, as should have been the case all along. (Giving world rwx is illogical on general principle. The fact that this is a workaround for makepkg demanding these directories be writable even when they are not going to be used for the makepkg options in question, is not justification for being careless.) Signed-off-by: Eli Schwartz <eschwartz@archlinux.org> commit ffb5003fdacaece3540ba167f7e965a122133af0 Author: Emiel Wiedijk <me@aimileus.nl> Date: Tue Feb 27 11:16:24 2018 -0500 makechrootpkg: respect GNUPGHOME Previously, makechrootpkg hardcoded ~/.gnupg. Therefore, if a user uses a custom GPG home directory, the siganture checking would fail. Now makechrootpkg uses $GNUPGHOME, with a fallback to ~/.gnupg. Signed-off-by: Emiel Wiedijk <me@aimileus.nl> ----------------------------------------------------------------------- Summary of changes: makechrootpkg.in | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/post-receive -- The official devtools repository