[arch-projects] [dbscripts] [GIT] Official repo DB scripts annotated tag archlinux/20111105 created. 20111105
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 annotated tag, archlinux/2005 has been created at 3ba457e78645d348217038f922b35791b898d5d8
[arch-projects] [dbscripts] [GIT] Official repo DB scripts annotated tag archlinux/20100410 created. 20100410
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 annotated tag, archlinux/20100410 has been created at a496da550323440a491aac908edeaad37fc5721d
[arch-projects] [dbscripts] [GIT] Official repo DB scripts annotated tag archlinux/20121003 created. 20121003
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 annotated tag, archlinux/20121003 has been created at e0defb8cd96a60193b7bc0f2e93450a94e54c3c4
[arch-projects] [dbscripts] [GIT] Official repo DB scripts annotated tag archlinux/20100223 created. 20100223
his file was modifed crontab file for repo-based cron jobs Add a script to generate source tarballs for GPL compliance Link the new testing2x script to the 64 version too Minor changes to the make-sourceball script Merge branch 'master' of /srv/projects/git/dbscripts
[arch-projects] [dbscripts] [GIT] Official repo DB scripts annotated tag archlinux/20110326 created. 20110326
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 annotated tag, archlinux/20110326 has been created at b4d8cfbc80b0eb1faa295e56e5969d1619a3b95c
[arch-projects] [dbscripts] [GIT] Official repo DB scripts annotated tag archlinux/20120616 created. 20120616
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 annotated tag, archlinux/20120616 has been created at 8b915ad3b0e744a09051f768570c65ec187fe9e5
[arch-projects] [dbscripts] [GIT] Official repo DB scripts annotated tag archlinux/20120805 created. 20120805
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 annotated tag, archlinux/20120805 has been created at c1913555a6baafbc55f9bc05eb0a0f0a1717b0e7
[arch-projects] [dbscripts] [GIT] Official repo DB scripts annotated tag archlinux/20110813 created. 20110813
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 annotated tag, archlinux/20110813 has been created at 0faa6ed72d8d396d2d47a7a734bf9836857a2de9
[arch-projects] [dbscripts] [GIT] Official repo DB scripts annotated tag archlinux/20120610 created. 20120610
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 annotated tag, archlinux/20120610 has been created at ae9ceabc80e625b94ab2bc0580a2cdf468e95ca4
[arch-projects] [dbscripts] [GIT] Official repo DB scripts annotated tag archlinux/20100411 created. 20100411
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 annotated tag, archlinux/20100411 has been created at b44f0e9df79c2e86d348e5bb252efb7d0d095b79
[arch-projects] [dbscripts] [GIT] Official repo DB scripts annotated tag archlinux/20131102 created. 20131102
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 annotated tag, archlinux/20131102 has been created at d201b99599d45e139e0721294834107c8eb43bb4
[arch-projects] [dbscripts] [GIT] Official repo DB scripts annotated tag archlinux/20101209 created. 20101209
fic format Merge branch 'master' of gerolde.archlinux.org:/srv/projects/git/dbscripts Fix typos Dont try to index empty repos Fix sourceballs cron job Simplify sourceballs creation sourceballs: skip in a clean way if source package should not be created s
[arch-projects] [dbscripts] [GIT] Official repo DB scripts annotated tag archlinux/20100906 created. 20100906
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 annotated tag, archlinux/20100906 has been created at 6da1776d23da23a8842d2dd1412995fa74832bb2
[arch-projects] [dbscripts] [GIT] Official repo DB scripts annotated tag archlinux/20110409 created. 20110409
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 annotated tag, archlinux/20110409 has been created at b925016368c03344fb8fa01d11b1c0585ca02c80
[arch-projects] [pyalpm] Workaround https://bugs.python.org/issue33012
This fixes building with GCC 8 --- setup.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/setup.py b/setup.py index 887b7a1..ba3ae2a 100644 --- a/setup.py +++ b/setup.py @@ -9,7 +9,7 @@ os.putenv('LC_CTYPE', 'en_US.UTF-8') pyalpm_version = '0.8' cflags = ['-Wall',
[arch-projects] [devtools] [PATCH] Do not assume the makechrootpkg user's groupname is the same as the username
@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/makechroot
[arch-projects] [devtools] [GIT] The official devtools repository branch master updated. 20171108-13-g5713cd6
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)
[arch-projects] [archweb] [PATCH 2/2] mirrorlist: Complete /all/https success test case
Also, remove test_generate(), as it was testing no more than test_mirrorlist_filter() already was. Signed-off-by: Genki Sky--- mirrors/tests/test_mirrorlist.py | 16 ++-- 1 file changed, 10 insertions(+), 6 deletions(-) diff --git a/mirrors/tests/test_mirrorlist.py
[arch-projects] [archweb] [PATCH 0/2] mirrorlist: Accept GET parameter filters, improve tests
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,
[arch-projects] [archweb] [PATCH 1/2] mirrorlist: Accept GET parameters as filters
This fixes a regression. Originally request.REQUEST was used, but django 1.9 removed this. In its stead, request.POST was used unconditionally. However, this results in any GET request returning *all* mirrors, rather than filtering as requested in the parameters. This patch uses POST or GET based
WARN: project from a retired committee but PMC not changed to Attic in http://svn.apache.org/repos/asf/oltu/site/doap_org.apache.oltu.parent.rdf
WARN: project in Attic but not in 'retired' category: http://svn.apache.org/repos/asf/oltu/site/doap_org.apache.oltu.parent.rdf
[arch-projects] [dbscripts] [GIT] Official repo DB scripts branch master updated. 20131102-87-g656fd6d
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)
Re: [arch-projects] [devtools] [PATCH] makechrootpkg: fix verifysource with pacman-git
On 03/26/2018 06:19 PM, Luke Shumaker wrote: >> -chmod 1777 "$builddir" >> +chown "$makepkg_user:$makepkg_user" "$builddir" > > $makepkg_user isn't nescessarily a valid group name. Not all users > have an identically named group, some people like to use 'users' as > their primary group.
[arch-projects] [netctl] [GIT] Network control utility based on systemd branch master updated. 1.15-5-gdbc32d4
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 branch, master has been updated via dbc32d470420396f4af360af9ac17680fe99b368
[arch-projects] [netctl] [GIT] Network control utility based on systemd annotated tag 1.16 created. 1.16
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
[arch-projects] [dbscripts] [GIT] Official repo DB scripts branch pacman-git created. 20131102-82-gcda3694
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 created at cda3694d0b247849e12edcd56e0ca7a41ec90ae1 (commit) - Log
[arch-projects] [dbscripts] [GIT] Official repo DB scripts branch master updated. 20131102-81-g8cc8e9c
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 8cc8e9cbbefdf6fac368031d3dacc74d001f23b7 (commit)
[arch-projects] [devtools] [PATCH] 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
[arch-projects] [netctl] [GIT] Network control utility based on systemd branch master updated. 1.15-3-gcef231d
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 branch, master has been updated via cef231d762e7bb65bcf9a6a040ba367c5062a8f8
[arch-projects] [dbscripts] [GIT] Official repo DB scripts branch master updated. 20131102-73-gda49ea6
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 da49ea616e162d3cfcb4b6a4242f497e94c36564 (commit) via
Re: [arch-projects] [dbscripts] [PATCH 3/8] Export TMPDIR, and use mktemp -t instead of making it part of the template
On 03/13/2018 09:52 PM, Luke Shumaker wrote: > From: Luke Shumaker> diff --git a/test/cases/db-update.bats b/test/cases/db-update.bats > index e7e4489..2e44b91 100644 > --- a/test/cases/db-update.bats > +++ b/test/cases/db-update.bats > @@ -222,7 +222,7 @@ load
Re: [arch-projects] [dbscripts] [PATCH 1/8] Fix quoting around variables, especially arrays.
On 03/14/2018 12:53 AM, Luke Shumaker wrote: > Part of it is to have a common style. Trying to rectify two codebases > that diverged 7 years ago is rough. When trying to come up with clean > diffs, having to guess "did the other one quote this variable?" makes > it harder. If you can say
Re: [arch-projects] [dbscripts] [PATCH 4/8] Use `grep &>/dev/null` instead of `grep -q` when operating on piped stdin.
On 03/13/2018 09:52 PM, Luke Shumaker wrote: > From: Luke Shumaker> > `grep -q` may exit as soon as it finds a match; this is a good optimization > for when the input is a file. However, if the input is the output of > another program, then that other program will receive
Re: [arch-projects] [dbscripts] [PATCH 8/8] devlist-mailer: Make LIST and FROM configurable
On 03/13/2018 09:52 PM, Luke Shumaker wrote: > From: Luke ShumakerTBH we don't even send out integrity check email anymore, do you? -- Eli Schwartz Bug Wrangler and Trusted User signature.asc Description: OpenPGP digital signature
Re: [arch-projects] [dbscripts] [PATCH 1/8] Fix quoting around variables, especially arrays.
On 03/13/2018 09:51 PM, Luke Shumaker wrote: > From: Luke Shumaker> > Other than pure quoting, this involved: > - swapping */@ for array access in a few places > - fiddling with printf in a pipeline > - replacing `$(echo ${array[@]})` with `${array[*]}` > -
Re: [arch-projects] [dbscripts] [PATCH 0/8] Backports from Parabola
On 03/13/2018 09:51 PM, Luke Shumaker wrote: > BTW, now that dbscripts is on GitHub, is that the preferred way of > submitting these? Or is this mailing list still best? It's been on github for quite some time, but I am okay with looking at things in either location. -- Eli Schwartz Bug
[vpn-help] Shrew Soft VPN, AD Login NAT issues
Dear Members I have paid for the professional license. I have an issue with the Shrew Soft VPN Client, I have configured the connection to my VPN Appliance and Enabled: force-rfc, in the Shrew Soft Client as this is required with the clients behind NAT and or on mobile data, the problem is
Re: [arch-projects] [devtools] makechrootpkg: respect GNUPGHOME
On Tue, Feb 27, 2018 at 03:44:07PM +0100, Eli Schwartz via arch-projects wrote: > On 02/27/2018 05:41 AM, Emiel Wiedijk via arch-projects wrote: > > Correct, but makepkg --verifysource is run with sudo -u $myuser, and sudo > > resets the environment. And the code that copies ~/.gnup
[arch-projects] [devtools] [PATCH v2] 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--- makechrootpkg.in | 5 +++-- 1 file changed,
Re: [arch-projects] [devtools] makechrootpkg: respect GNUPGHOME
On 02/27/2018 05:41 AM, Emiel Wiedijk via arch-projects wrote: > Correct, but makepkg --verifysource is run with sudo -u $myuser, and sudo > resets the environment. And the code that copies ~/.gnupg to the chroot > apparantly hasn't been re
Re: [arch-projects] [devtools] makechrootpkg: respect GNUPGHOME
> On 02/26/2018 02:03 PM, Emiel Wiedijk via arch-projects wrote: > > > Previously, makechrootpkg hardcoded ~/.gnupg. Therefore, if a user > > > > uses a custom GPG home directory, the siganture checking would fail. > > > > Now makechrootpkg uses $GN
Re: [arch-projects] [dbscripts] [PATCH v2 3/3] Update messages to make fuller use of printf formatters
or consistency we should use the same style which means using >> "${dbfile@Q}" > > I was going for consistency with the repo-add version, which doesn't > have a single dbfile variable to @Q. Would you have me introduce a > dbfile variable in arch_repo_add? Well, we b
[arch-projects] [dbscripts] [PATCH] db-functions: unify the repo-add/repo-remove caller
Use less duplicated logic, opening the way to more elegantly change the interface for the repo-add/repo-remove scripts which are themselves symlinked together and mostly have the same interface. Signed-off-by: Eli Schwartz--- db-functions | 34
Re: [arch-projects] [devtools] makechrootpkg: respect GNUPGHOME
On 02/26/2018 02:03 PM, Emiel Wiedijk via arch-projects wrote: > 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. There is no
Re: [arch-projects] [dbscripts] [PATCH v2 3/3] Update messages to make fuller use of printf formatters
On 02/22/2018 09:15 PM, Luke Shumaker wrote: > From: Luke Shumaker> > These are things that were (IMO) missed in 5afac1e. I found them using: > > git grep -E '(plain|msg|msg2|warning|error|die) "[^"]*\$' > > I went a little above-and-beyond for escaping strings for
[arch-projects] [devtools] 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--- makechrootpkg.in | 12 +++- 1 file
Re: [arch-projects] [dbscripts] [PATCH v2 2/3] test: Fixup glob matching
On 02/22/2018 09:15 PM, Luke Shumaker wrote: > - common.bash: Globbing happens on the RHS of a [[ = ]] test. >This means that we must quote variables on the RHS that are to be taken >verbatim. This is surprising, because we don't need to quote the LHS. Unless we intend to do a general
Re: [arch-projects] [dbscripts] [PATCH 3/3] Update messages to make fuller use of printf formatters
On 02/22/2018 08:52 PM, Luke Shumaker wrote: > I guess I *should* have explained it a bit more; the escaping of the > package list happens when assigning pkgs_str: > > printf -v pkgs_str -- '%q ' "${pkgs[@]}" Hmm, true. But the version without the additional variable wins IMO. > Anyway,
Re: [arch-projects] [dbscripts] [PATCH 1/3] test: common.bash:__getCheckSum: Don't rely on IFS
On 02/22/2018 06:43 PM, Luke Shumaker wrote: > On Thu, 22 Feb 2018 16:43:36 -0500, > Eli Schwartz wrote: >>> __getCheckSum() { >>> - local result=($(sha1sum $1)) >>> - echo ${result[0]} >>> + local result >>> + result="$(sha1sum "$1")" >>> + echo "${result%% *}" >> >> Why are you moving
Re: [arch-projects] [dbscripts] [PATCH 3/3] Update messages to make fuller use of printf formatters
On 02/22/2018 06:54 PM, Luke Shumaker wrote: >> I do see what you're doing, I'm just not sure why. Is the whole idea >> with this extra variable floating around, to avoid tokenizing >> "${pkgs[@]}" as separate messages? That's why "${pkgs[*]}" tokenizes the >> members of an array as one word by
Re: [arch-projects] [dbscripts] [PATCH 2/3] test: Fixup glob matching
On 02/22/2018 03:43 PM, Luke Shumaker wrote: > From: Luke Shumaker> > - ftpdir-cleanup.bats: Glob expansion does not occur in [[ -f ]] tests. >The [[ ! -f .../${pkgname}-*${PKGEXT} ]] checks were checking that there >were no files containing a literal '*' for that
Re: [arch-projects] [dbscripts] [PATCH 3/3] Update messages to make fuller use of printf formatters
On 02/22/2018 03:43 PM, Luke Shumaker wrote: > From: Luke Shumaker> > These are things that were (IMO) missed in 5afac1e. I found them using: > > git ls-files|xargs grep -E '(plain|msg|msg2|warning|error|die) "[^"]*\$' Consider using git grep next time :p rather than
Re: [arch-projects] [dbscripts] [PATCH 1/3] test: common.bash:__getCheckSum: Don't rely on IFS
On 02/22/2018 03:43 PM, Luke Shumaker wrote: > From: Luke Shumaker> > I managed to stumble across a bug in BATS where the run() function > screwed with the global IFS. The bug has been fixed in git, but isn't > in a release yet. > >
[arch-projects] [dbscripts] [GIT] Official repo DB scripts branch master updated. 20131102-69-ge53cad6
s did not cause a test failure. https://lists.archlinux.org/pipermail/arch-projects/2018-February/004742.html The broken function checks if the repo already contains a package that matches the one being released. This did not trigger a test-suite failure be
Re: [arch-projects] [dbscripts] [PATCH v2 1/5] Use even more bashisms.
On 02/20/2018 12:24 PM, Emil Velikov wrote: > Seems like I wasn't clear enough: > The goal is not to appease zsh - but a step closer to POSIX sh friendly. > > I've been staring and writing bash (closer to POSIX sh really) scripts > for over a decade, haven't seen what makes X cleaner over Y. >
Re: [arch-projects] [dbscripts] [PATCH v2 1/5] Use even more bashisms.
that zsh arrays are > 1-indexed while bash arrays are 0-indexed, but if I had to guess, > probably not. > > ... > > I can see some compelling reasons to write scripts targeting POSIX sh as > a baseline, which is being *sh* friendly, not zsh friendly. > But, for projects th
Re: [arch-projects] [dbscripts] [PATCH v2 1/5] Use even more bashisms.
line, which is being *sh* friendly, not zsh friendly. But, for projects that make heavy use of bashisms anyways, I dislike using POSIX because it implies that sh will be supported in any way when it really won't be. Essentially, I prefer to go "all in". As for why you'd want them, ba
Re: [arch-projects] [dbscripts] [PATCH v2 1/5] Use even more bashisms.
Hi Eli, Disclaimer: the following is a bit subtle topic, so I hope it doesn't spur a lot of off-topic. On 19 February 2018 at 20:11, Eli Schwartz via arch-projects <arch-projects@archlinux.org> wrote: > Catch some cases that were missed in the previous run. > > Signed-off-b
Re: [arch-projects] [dbscripts] [PATCH v3] test: db-update: @test "update same any package to same repository fails": change PKGEXT
Context: I wrote a makepkg patch whose sole purpose is to ensure that people can extract a newline-separated list of absolute filepaths for each package that a PKGBUILD would/did create. No globs needed. :) I'm hoping this will simplify some rather hackish and fragile logic in *many* project
Re: [arch-projects] [dbscripts] [PATCH v3] test: db-update: @test "update same any package to same repository fails": change PKGEXT
test failure because the checks >>> right after it were tripping anyway. >>> >>> https://lists.archlinux.org/pipermail/arch-projects/2018-February/004742.html >>> >>> v2: Follow Eli's suggestion to simplify it using the check in __buildPackage >>>
Re: [arch-projects] [dbscripts] [PATCH v3] test: db-update: @test "update same any package to same repository fails": change PKGEXT
e regression where db-functions:check_pkgrepos isn't > treating PKGEXT as a glob. > > Without this, that regression didn't cause test failure because the checks > right after it were tripping anyway. > > https://lists.archlinux.org/pipermail/arch-projects/2018-February/004742.html >
Re: [arch-projects] [dbscripts] [PATCH v2 5/5] Globally set $PKGEXT to a bash extended glob representing valid choices.
On 02/19/2018 04:59 PM, Luke Shumaker wrote: > Is there a reason you reject '.pkg.tar' (no compression, which makepkg > accepts)? I don't think there is any utility in supporting uncompressed packages in dbscripts. Anyone who wants to customize this in a non-Arch Linux deployment is free to do
Re: [arch-projects] [dbscripts] [PATCH v2 3/5] db-update: replace external find command with bash globbing
On 02/19/2018 04:53 PM, Luke Shumaker wrote: > Isn't [[ -d ]] there redundant? If globbing gave us $dir/file, of > course $dir is a directory! True. I think I still had that in from some point where I hadn't enabled nullglob yet. > Meanwhile, this dropped the `-type f` check, though I'm not
[arch-projects] [dbscripts] [PATCH v2 5/5] Globally set $PKGEXT to a bash extended glob representing valid choices.
The current glob `*.pkg.tar.?z` is both less restrictive and more restrictive than makepkg, as it accepts any valid unicode character. To be more exact, it's almost completely orthogonal to the one in makepkg. makepkg only accepts .tar.gz, .tar.bz2, .tar.xz, .tar.lzo, .tar.lrz, and .tar.Z and
[arch-projects] [dbscripts] [PATCH v2 1/5] Use even more bashisms.
Catch some cases that were missed in the previous run. Signed-off-by: Eli Schwartz--- This patch is new + refactor some changes from: ftpdir-cleanup,sourceballs: replace external find command with bash globbing cron-jobs/devlist-mailer | 6 +++---
[arch-projects] [dbscripts] [PATCH v2 3/5] db-update: replace external find command with bash globbing
Don't bother emitting errors. bash doesn't show globbing errors if it cannot read a directory to try globbing there. And the former code never aborted on errors anyway, as without `set -o pipefail` the sort command swallowed the return code. Signed-off-by: Eli Schwartz
[arch-projects] [dbscripts] [PATCH v2 2/5] Fix overloading PKGEXT to mean two things.
PKGEXT is a makepkg variable referring to a fixed filename suffix, but we were also using it to mean a bash glob referring to candidate filenames. This is wrong, so rename it to PKGEXTS which is more descriptive of its purpose. Exclude the testsuite from this change, as the testsuite actually
[arch-projects] [dbscripts] [PATCH v2 0/5] Fix ambiguous uses of $PKGEXT
Comes with fancy checkmarks from travis saying that the testsuite passed: https://github.com/archlinux/dbscripts/commits/pkgext-real-wildcards Eli Schwartz (5): Use even more bashisms. Fix overloading PKGEXT to mean two things. db-update: replace external find command with bash globbing
Re: [arch-projects] [dbscripts] [PATCH v2 0/8] PKGEXT fixup
On 02/18/2018 12:17 PM, Luke Shumaker wrote: > From: Luke Shumaker> > This incorporates and improves on work from 3 previously submitted > patch sets: > > 1. My testcase patch, but > - take Eli's suggestion to simplify db-update.bats > - add another commit so we
Re: [arch-projects] [dbscripts] [PATCH 2/3] ftpdir-cleanup, sourceballs: replace external find command with bash globbing
On 02/17/2018 02:29 PM, Luke Shumaker wrote: > On Thu, 15 Feb 2018 22:45:03 -0500, > Eli Schwartz via arch-projects wrote: >> diff --git a/cron-jobs/ftpdir-cleanup b/cron-jobs/ftpdir-cleanup >> index 2f3d5aa..2d33047 100755 >> --- a/cron-jobs/ftpdir-cleanup >>
Re: [arch-projects] [dbscripts] [PATCH 1/1] test: db-update: @test "update same any package to same repository fails": change PKGEXT
On 02/16/2018 04:43 PM, Luke Shumaker wrote: > On Thu, 15 Feb 2018 23:21:42 -0500, > Eli Schwartz via arch-projects wrote: >> >> This looks reasonable, thanks. BTW no need to send a cover letter for >> one patch. :) > > I felt silly sending it, but I wanted to note
Re: [arch-projects] [dbscripts] [PATCH 1/1] test: db-update: @test "update same any package to same repository fails": change PKGEXT
e regression where db-functions:check_pkgrepos isn't > treating PKGEXT as a glob. > > Without this, that regression didn't cause test failure because the checks > right after it were tripping anyway. > > https://lists.archlinux.org/pipermail/arch-projects/2018-February/004742.html Thi
[arch-projects] [dbscripts] [PATCH] test: fix misuse of $PKGEXT
As per the previous commits, this never worked and nobody noticed because the use of globbing was undocumented. Fortunately, we can fix that now, by using the new is_globfile() proxy function. Signed-off-by: Eli Schwartz--- test/cases/ftpdir-cleanup.bats | 4 ++-- 1
[arch-projects] [dbscripts] [PATCH 2/3] ftpdir-cleanup, sourceballs: replace external find command with bash globbing
This fully removes the use of find from the codebase, leads to a micro-optimization in a couple cases, and ensures that $PKGEXT is consistently treated as a shell globbing character (which is important because it is used as one). Of the eight instances in these files: - One was unnecessary as
[arch-projects] [dbscripts] [PATCH 3/3] Globally set $PKGEXT to a bash extended glob representing valid choices.
This can be anything makepkg.conf accepts, therefore it needs to be able to match all that. Document the fact that this has *always* been some sort of glob, and update the two cases where this was (not!) being evaluated by bash [[ ... ]], to use a proxy function is_globfile() Signed-off-by: Eli
[arch-projects] [dbscripts] [PATCH 0/3] Fix ambiguous uses of
This was sort of cobbled together and not really tested, so I'm not 100% sure it will work, but it looks okay, so I am posting this to get more eyes on it. I think I've actually gotten this to work properly, which is yay, and support multiple extensions, which is meh but we may need this as Luke
[arch-projects] [dbscripts] [PATCH] Do not support wildcards in PKGEXT, and standardize on xz compression.
This results in unpredictable behavior when used across, variously, bash [[, POSIX sh [, and find -name Its usage depended on matching only one result, which is bad practice. Moreover, it never worked in the first place as - The majority of alternative compression extensions available in
Re: [arch-projects] [dbscripts] [PATCH 1/2] Don't quote $PKGEXT
On 02/15/2018 05:17 PM, Luke Shumaker wrote: > Huh? My version isn't broken. Unless you mean that the glob is more > restrictive than the one used by makepkg? As you saw my other message, this should be answered already, but consider this additional perspective on globs: The glob is both
Re: [arch-projects] [dbscripts] [PATCH 1/2] Don't quote $PKGEXT
On 02/15/2018 04:43 PM, Luke Shumaker wrote: > That's not a bad idea. But then someone reading the code might wonder > "why does such a trivial function exist?". I think it would be silly, > and ultimately hurt readability to go through and replace all > > "[[ -f ... ]]" instances with
Re: [arch-projects] [dbscripts] [PATCH 1/2] Don't quote $PKGEXT
On 02/15/2018 03:48 PM, Dave Reisner wrote: > Nope, changing the kind of glob doesn't work here. There's simply no > glob expansion of any kind inside [[ -f ]] (or any other stat-like > check). I was thinking maybe something like the way makepkg compares filenames to various extended globs, but
Re: [arch-projects] [dbscripts] [PATCH 1/2] Don't quote $PKGEXT
On 02/15/2018 03:11 PM, Dave Reisner wrote: > Rather than making this stand out like a sore thumb for the next person > to trip over, why don't we just define a "file_exists" function? > > file_exists() { > [[ -f $1 ]] > } > > Now you're free to do this: > > file_exists >
Re: [arch-projects] [dbscripts] [GIT] Official repo DB scripts branch master updated. 20131102-59-g36b71d3
On 02/15/2018 02:04 PM, Luke Shumaker wrote: >> -[ -f "${FTP_BASE}/${PKGPOOL}/${pkgname}-${pkgver}-${pkgarch}"${PKGEXT} >> ] && return 1 >> -[ -f >> "${FTP_BASE}/${PKGPOOL}/${pkgname}-${pkgver}-${pkgarch}"${PKGEXT}.sig ] && >> return 1 >> +[[ -f
[arch-projects] [dbscripts] [GIT] Official repo DB scripts branch master updated. 20131102-63-g134aff7
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 134aff74d16331231ed94f34d8417d1325d4600f (commit) via
[arch-projects] [dbscripts] [GIT] Official repo DB scripts branch master updated. 20131102-59-g36b71d3
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 discards be2971eca4cb08aa5c128d8b206f6943d58a7dd9 (commit) via
[arch-projects] [dbscripts] [GIT] Official repo DB scripts branch master updated. 20131102-54-gbe2971e
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 be2971eca4cb08aa5c128d8b206f6943d58a7dd9 (commit) from
[arch-projects] [dbscripts] [GIT] Official repo DB scripts branch eschwartz/bash-cleanup created. 20131102-59-g3555edf
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, eschwartz/bash-cleanup has been created at 3555edf50a5f6ef32f870f7a9199df168bb3d929
Re: [arch-projects] [mkinitcpio] fsck install hook improvements
2018-02-13 16:27 GMT-02:00 Dave Reisner <d...@falconindy.com>: > On Tue, Feb 13, 2018 at 04:19:33PM -0200, Marcos Mello via arch-projects > wrote: >> - EXT, JFS and ReiserFS cleanup (install main tools and create >> required symlinks). >> - Only install /etc/e
[arch-projects] [mkinitcpio] fsck install hook improvements
- EXT, JFS and ReiserFS cleanup (install main tools and create required symlinks). - Only install /etc/e2fsck.conf for EXT filesystems. - Btrfs and XFS are special: their fscks do nothing (well, at least they show what tool to run). Users need xfs_repair and btrfs installed to try to fix the
Spett.le Azienda - Presentazione specialisti ICT-- NewsLetter 01/2018.
ai nostri strumenti potete individuare i profili migliori ed al miglior prezzo con un solo click ! Consulenza ITC La Programs & Projects Consulting e' il partner ideale per le aziende. Proponiamo un'offerta di servizi completa ed integrata, dalla consulenza nella progettazione di sis
Spett.le Azienda - Presentazione specialisti ICT-- NewsLetter 01/2018.
ai nostri strumenti potete individuare i profili migliori ed al miglior prezzo con un solo click ! Consulenza ITC La Programs & Projects Consulting e' il partner ideale per le aziende. Proponiamo un'offerta di servizi completa ed integrata, dalla consulenza nella progettazione di sis
Spett.le Azienda - Presentazione specialisti ICT-- NewsLetter 01/2018.
ai nostri strumenti potete individuare i profili migliori ed al miglior prezzo con un solo click ! Consulenza ITC La Programs & Projects Consulting e' il partner ideale per le aziende. Proponiamo un'offerta di servizi completa ed integrata, dalla consulenza nella progettazione di sis
Re: [arch-projects] [namcap] possibility to use renamed PKGBUILD files
On 01/25/2018 10:24 AM, Luke Shumaker wrote: >> But it would be better to just consider every non-archive file as a >> PKGBUILD file. > > +1 As I said on the bugreport: > Personally, I wonder why we bother checking the filename at all, > rather just assuming that the non-tar files are PKGBUILDs
Re: [arch-projects] [namcap] possibility to use renamed PKGBUILD files
> Now you cannot randomly rename PKGBUILD files and use them with > namcap. I have filed a bug here: > https://bugs.archlinux.org/task/57193I created a patch for my > needs: diff --git a/namcap.py > b/namcap.pyindex b62a2fa..aae20c7 100755--- > a/namcap.py+++ b/namcap.py@@ -248,7 +248,7 @@
Re: [arch-projects] [namcap] possibility to use renamed PKGBUILD files
Whatever patch you were trying to post, it got lost in hoardes of div tags. Alad signature.asc Description: PGP signature
[arch-projects] [devtools] [PATCH 2/2] Proper fix for pacman-git returning file urls from the cache
It is much nicer to use a proper configuration parser to retrieve the primary mirror, rather than clever hacks using undocumented APIs, especially when their behavior as used then breaks in later releases. Fortunately, pacutils exists now and pacconf handles this quite elegantly. It has since
[arch-projects] [devtools] [PATCH] makechrootpkg: Do not copy the user keyring into the chroot.
Since commit 75fdff1811a0487f82c75b2e260da905102b4eea we no longer run integrity checks inside the chroot anyway, so this is no longer needed and will never be used. Signed-off-by: Eli Schwartz--- makechrootpkg.in | 7 +-- 1 file changed, 1 insertion(+), 6
Re: [arch-projects] [devtools] [PATCH 7/7] makechrootpkg: Put "keyserver-options auto-key-retrieve" in gpg.conf
On 01/15/2018 11:57 AM, Luke Shumaker wrote: > From: Luke Shumaker> > This allows signature verification by `makepkg --verifysource`, `git > verify-tag`, and such without requiring the user to manually retrieve > the keys first. > > This is based off of devtools32 commit
Re: [arch-projects] [devtools] [PATCH 5/7] lib/common.sh: Adjust to work properly with `set -u`
On 01/15/2018 11:57 AM, Luke Shumaker wrote: > From: Luke Shumaker> libmakepkg does not work with `set -u`; but mostly because of the include > guards! So we just need to temporarily disable `set -u` (nounset) while > loading libmakepkg. Instead of introducing a new
Re: [arch-projects] [devtools] [PATCH 3/7] arch-nspawn: make sure that makepkg.conf is always parsed as text
On 01/15/2018 11:57 AM, Luke Shumaker wrote: > From: Luke Shumaker> > https://lists.parabola.nu/pipermail/dev/2017-June/005576.html > --- > arch-nspawn.in | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/arch-nspawn.in b/arch-nspawn.in > index