On 02/26/2018 05:14 PM, Luke Shumaker wrote:
> On Mon, 26 Feb 2018 00:46:48 -0500,
> Eli Schwartz wrote:
>>> +++ b/db-functions
>>> @@ -450,7 +450,7 @@ arch_repo_add() {
>>> # package files might be relative to repo dir
>>> pushd "${FTP_BASE}/${repo}/os/${arch}" >/dev/null
>>>
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
On Mon, 26 Feb 2018 00:46:48 -0500,
Eli Schwartz wrote:
> > +++ b/db-functions
> > @@ -450,7 +450,7 @@ arch_repo_add() {
> > # package files might be relative to repo dir
> > pushd "${FTP_BASE}/${repo}/os/${arch}" >/dev/null
> > /usr/bin/repo-add -q "${repo}${DBEXT}" ${pkgs[@]} \
> > -
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 signature
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
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