- Arch-projects - lists.archlinux.org

[arch-projects] [dbscripts] [GIT] Official repo DB scripts branch pacman-git updated. 20131102-88-g2c68135
by eschwartz＠archlinux.org 28 May '18

28 May '18

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 "Official repo DB scripts". The branch, pacman-git has been updated discards cda3694d0b247849e12edcd56e0ca7a41ec90ae1 (commit) via 2c68135f4ab9db048db460bc949322ad7bb418eb (commit) via 656fd6d5d8f455492b1e51add9e6e1da8f911a7c (commit) via 0cf2ac49c18a71c050f5a9a9ff42e8dff89c2375 (commit) via 5b4b19cd7f4c0ef7a479306b73a4db3733df9c44 (commit) via a852b2822620b6294e2efa411ff88a3b0afe1754 (commit) via 7134da63690e0798d498fd15a09786db42091bfd (commit) via 4dbcc003b6aa8fcf009be1e98c8ff13fe1def2fb (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 (cda3694d0b247849e12edcd56e0ca7a41ec90ae1) \ N -- N -- N (2c68135f4ab9db048db460bc949322ad7bb418eb) 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 2c68135f4ab9db048db460bc949322ad7bb418eb Author: Eli Schwartz <eschwartz(a)archlinux.org> Date: Wed Mar 21 12:09:21 2018 -0400 pacman 5.1 compatibility The print_all_package_names function changed its behavior, adapt ----------------------------------------------------------------------- Summary of changes: README.md | 57 +++++++++++++++++++++- config | 7 ++- cron-jobs/check_archlinux/parse_pkgbuilds.sh | 42 ++++++++--------- cron-jobs/devlist-mailer | 7 ++- cron-jobs/ftpdir-cleanup | 28 +++++------ cron-jobs/integrity-check | 6 +-- cron-jobs/sourceballs | 30 ++++++------ cron-jobs/update-web-db | 20 ++++---- db-functions | 70 ++++++++++++++-------------- db-move | 56 +++++++++++----------- db-remove | 22 ++++----- db-repo-add | 22 ++++----- db-repo-remove | 22 ++++----- db-update | 36 +++++++------- test/cases/db-update.bats | 7 +++ test/lib/common.bash | 8 ++-- testing2x | 26 +++++------ 17 files changed, 266 insertions(+), 200 deletions(-) hooks/post-receive -- Official repo DB scripts

1 0

[arch-projects] [devtools] [PATCH] Do not assume the makechrootpkg user's groupname is the same as the username
by Eli Schwartz 16 May '18

16 May '18

chown support "$user:$group" but also "$user:" which infers $group rather than leaving it as root. This looks up the group name in cases where the default group is e.g. "users" and users do not get their own unique groups. Signed-off-by: Eli Schwartz <eschwartz(a)archlinux.org> --- This is even more common than I thought, I've found a person who's affected! :p cf. https://lists.archlinux.org/pipermail/arch-projects/2018-March/004868.html makechrootpkg.in | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/makechrootpkg.in b/makechrootpkg.in index f709955..37e97e7 100644 --- a/makechrootpkg.in +++ b/makechrootpkg.in @@ -245,7 +245,7 @@ download_sources() { local builddir builddir="$(mktemp -d)" - chown "$makepkg_user:$makepkg_user" "$builddir" + chown "$makepkg_user:" "$builddir" # Ensure sources are downloaded sudo -u "$makepkg_user" --preserve-env=GNUPGHOME \ -- 2.17.0

1 0

[arch-projects] [devtools] [GIT] The official devtools repository branch master updated. 20171108-13-g5713cd6
by Evangelos Foutras 12 May '18

12 May '18

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 5713cd629c97c7a12a600a1dd73ad81d87374eb1 (commit) from 40f0179a5e74d6d3babbefdeae21fd374be0e090 (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 5713cd629c97c7a12a600a1dd73ad81d87374eb1 Author: Evangelos Foutras <evangelos(a)foutrelis.com> Date: Sat May 12 11:52:18 2018 +0300 makechrootpkg: add /etc/shadow entry for builduser Without it, sudo 1.8.23 will return an error: sudo: PAM account management error: Authentication service cannot retrieve authentication info ----------------------------------------------------------------------- Summary of changes: makechrootpkg.in | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) hooks/post-receive -- The official devtools repository

1 0

[arch-projects] [archweb] [PATCH 0/2] mirrorlist: Accept GET parameter filters, improve tests
by Genki Sky 22 Apr '18

22 Apr '18

Hello, please find the following patches. One fixes a bug I noticed where the filter URLs generated by the [mirrorlist] form were not filtering as they should. While fixing this bug, I also improved (I hope!) the testing in the area. Let me know if I'm missing anything. I ran all the test cases, and they still pass. On that note, thanks for making the testing setup very easy to use. It is great to see. [mirrorlist]: https://www.archlinux.org/mirrorlist/ Genki Sky (2): mirrorlist: Accept GET parameters as filters mirrorlist: Complete /all/https success test case mirrors/tests/__init__.py | 11 ++++++----- mirrors/tests/test_mirrorlist.py | 30 +++++++++++++++++++++++------- mirrors/views/mirrorlist.py | 3 ++- 3 files changed, 31 insertions(+), 13 deletions(-) -- 2.17.0

1 2

[arch-projects] [PATCH] [namcap] Treat all non-tar files as PKGBUILD files, regardless of filename
by Luke Shumaker 16 Apr '18

16 Apr '18

From: Luke Shumaker <lukeshu(a)parabola.nu> https://bugs.archlinux.org/task/57193 If the user mistakenly passes in some other (non-package, non-PKGBUILD) file, instead of refusing to process it (saying "Error: Cannot process ${filename}"), it will now try to parse it as a PKGBUILD, probably encounter and print at least one error, but finally say "Error: ${filename} is not a valid PKGBUILD". This is actually probably *more* helpful to a confused user who passed in the wrong file. --- namcap.py | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/namcap.py b/namcap.py index b62a2fa..fd62d3c 100755 --- a/namcap.py +++ b/namcap.py @@ -248,9 +248,7 @@ for package in packages: if os.path.isfile(package) and tarfile.is_tarfile(package): process_realpackage(package, active_modules) - elif package.endswith('PKGBUILD'): + else: process_pkgbuild(package, active_modules) - else: - print("Error: Cannot process %s" % package) # vim: set ts=4 sw=4 noet: -- 2.15.1

3 3

[arch-projects] [dbscripts] [GIT] Official repo DB scripts branch master updated. 20131102-87-g656fd6d
by eschwartz＠archlinux.org 09 Apr '18

09 Apr '18

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 "Official repo DB scripts". The branch, master has been updated via 656fd6d5d8f455492b1e51add9e6e1da8f911a7c (commit) via 0cf2ac49c18a71c050f5a9a9ff42e8dff89c2375 (commit) via 5b4b19cd7f4c0ef7a479306b73a4db3733df9c44 (commit) via a852b2822620b6294e2efa411ff88a3b0afe1754 (commit) via 7134da63690e0798d498fd15a09786db42091bfd (commit) via 4dbcc003b6aa8fcf009be1e98c8ff13fe1def2fb (commit) from 8cc8e9cbbefdf6fac368031d3dacc74d001f23b7 (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 656fd6d5d8f455492b1e51add9e6e1da8f911a7c Author: Luke Shumaker <lukeshu(a)parabola.nu> Date: Mon May 25 01:00:46 2015 -0600 devlist-mailer: Make LIST and FROM configurable commit 0cf2ac49c18a71c050f5a9a9ff42e8dff89c2375 Author: Luke Shumaker <lukeshu(a)parabola.nu> Date: Tue Jun 17 23:47:21 2014 -0400 Consistently use "$(dirname "$(readlink -e "$0")")" This does correct handling of - executing a program by symlink - any weird characters in the full path - I'm sure there's another case I thought about when I originally did this. commit 5b4b19cd7f4c0ef7a479306b73a4db3733df9c44 Author: Luke Shumaker <lukeshu(a)parabola.nu> Date: Thu Mar 15 21:47:58 2018 -0400 Fixup quoting around variables, especially arrays Search for unquoted variables using the command: grep -Prn --exclude-dir=.git '(?<!["=]|\[\[ |\[\[ -[zn] )\$(?!{?#|\(|\? )' and ignore a bunch of false positives. You may verify that the only differences between the lines removed and lines added are double-quotes: diff -u \ <(git show|sed -n 's/^-//p'|grep -v '^-- a/'|sed 's/"//g') \ <(git show|sed -n 's/^+//p'|grep -v '^++ b/'|sed 's/"//g') commit a852b2822620b6294e2efa411ff88a3b0afe1754 Author: Luke Shumaker <lukeshu(a)parabola.nu> Date: Wed Jun 18 12:07:09 2014 -0400 test/: Verify that db-update won't release duplicate packages in the same transaction This is a leftover change from the patch that became 0432cff; v2 of that patch broke db-functions:getpkgfiles, but the testsuite didn't catch it. This patch adds a testcase that catches this type of breakage. commit 7134da63690e0798d498fd15a09786db42091bfd Author: Luke Shumaker <lukeshu(a)sbcglobal.net> Date: Sun Apr 17 18:56:14 2016 -0400 README.md: Write an overview of the programs included commit 4dbcc003b6aa8fcf009be1e98c8ff13fe1def2fb Author: Luke Shumaker <lukeshu(a)parabola.nu> Date: Thu Mar 15 23:54:14 2018 -0400 README.md: fix spelling mistake: "overriden"->"overridden" ----------------------------------------------------------------------- Summary of changes: README.md | 57 +++++++++++++++++++++- config | 7 ++- cron-jobs/check_archlinux/parse_pkgbuilds.sh | 42 ++++++++--------- cron-jobs/devlist-mailer | 7 ++- cron-jobs/ftpdir-cleanup | 28 +++++------ cron-jobs/integrity-check | 6 +-- cron-jobs/sourceballs | 30 ++++++------ cron-jobs/update-web-db | 20 ++++---- db-functions | 70 ++++++++++++++-------------- db-move | 56 +++++++++++----------- db-remove | 22 ++++----- db-repo-add | 22 ++++----- db-repo-remove | 22 ++++----- db-update | 36 +++++++------- test/cases/db-update.bats | 7 +++ testing2x | 26 +++++------ 16 files changed, 262 insertions(+), 196 deletions(-) hooks/post-receive -- Official repo DB scripts

1 0

[arch-projects] [devtools] [PATCH] makechrootpkg: fix verifysource with pacman-git
by Eli Schwartz 26 Mar '18

26 Mar '18

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(a)archlinux.org> --- Yay, I "broke" something. :D makechrootpkg.in | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/makechrootpkg.in b/makechrootpkg.in index afcd121..6bc82a4 100644 --- a/makechrootpkg.in +++ b/makechrootpkg.in @@ -249,7 +249,7 @@ download_sources() { local builddir builddir="$(mktemp -d)" - chmod 1777 "$builddir" + chown "$makepkg_user:$makepkg_user" "$builddir" # Ensure sources are downloaded sudo -u "$makepkg_user" env SRCDEST="$SRCDEST" BUILDDIR="$builddir" \ -- 2.16.2

2 2

[arch-projects] [devtools] [GIT] The official devtools repository branch master updated. 20171108-12-g40f0179
by Bartłomiej Piotrowski 24 Mar '18

24 Mar '18

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(a)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(a)archlinux.org> commit ffb5003fdacaece3540ba167f7e965a122133af0 Author: Emiel Wiedijk <me(a)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(a)aimileus.nl> ----------------------------------------------------------------------- Summary of changes: makechrootpkg.in | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/post-receive -- The official devtools repository

1 0

[arch-projects] [devtools] [GIT] The official devtools repository branch master updated. 20171108-11-g6da90b2
by Bartłomiej Piotrowski 24 Mar '18

24 Mar '18

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 6da90b2028da0bc504be7ff60873dd2719818a1e (commit) via ab3368f06182cc3f11f672e63ad18f174ba58e02 (commit) from 38c7a391b043547b946a99731a56a233458ba7a2 (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 6da90b2028da0bc504be7ff60873dd2719818a1e Author: Emiel Wiedijk via arch-projects <arch-projects(a)archlinux.org> 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(a)aimileus.nl> commit ab3368f06182cc3f11f672e63ad18f174ba58e02 Author: Bartłomiej Piotrowski <bpiotrowski(a)archlinux.org> Date: Sat Mar 24 20:35:09 2018 +0100 Remove corepkg symlink While still possible with 'commitpkg core', there is a chance it will prevent accidental pushes straight to [core]. ----------------------------------------------------------------------- Summary of changes: Makefile | 1 - makechrootpkg.in | 5 +++-- 2 files changed, 3 insertions(+), 3 deletions(-) hooks/post-receive -- The official devtools repository

1 0

[arch-projects] [netctl] [GIT] Network control utility based on systemd annotated tag 1.16 created. 1.16
by Jouke Witteveen 22 Mar '18

22 Mar '18

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 "Network control utility based on systemd". The annotated tag, 1.16 has been created at 82dffc523922a470b222198e49bb2f5ef384ef75 (tag) tagging dbc32d470420396f4af360af9ac17680fe99b368 (commit) replaces 1.15 tagged by Jouke Witteveen on Thu Mar 22 10:54:04 2018 +0100 - Log ----------------------------------------------------------------- Release 1.16 -----BEGIN PGP SIGNATURE----- iQFKBAABCAA0FiEEbql9KtO+F66lkufaVrYfv4JJLBUFAlqzfUEWHGoud2l0dGV2 ZWVuQGdtYWlsLmNvbQAKCRBWth+/gkksFU4vCADmnNsbgSnLiZso5sYcTzg8XhSV I1BIG9PfeDVXuDekpGQMhhCh0+GUyuPE3Pxsem07m6WZJ+O/89QGmisLggb23t7X P1/l97Y8AeSODhPIXAm7f3G1CWa1ciXyxEpFe3PACmajIE6CkTbTko4X2bi3ZYN4 8fSQTeOAfaTpEaaGgbjqRYHj7nlot+qbo1l/pApwv69ey4TKHItjN7umw6S43rvl 7f4NVZhWtulINlFNgFnsGoD9mW3k6mVKBHun6HUTfCfX5w5+O0SccazoKwanEEEL GSxl7CUw/6G3AmGRFL0Yg6Ncqf4vWcLMVRL784ZQkctiXfiGKVTOrKsmIJTg =eByd -----END PGP SIGNATURE----- Erich Eckner (1): Fix quoting of After= in generated service files (FS#57850) Jouke Witteveen (4): Technical documentation fixes Only wait when necessary in PPP cleanup code Reference profile options with a '='-suffix 1.16 release updates ----------------------------------------------------------------------- hooks/post-receive -- Network control utility based on systemd

1 0