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 (commit)

- Log -----------------------------------------------------------------
commit 3555edf50a5f6ef32f870f7a9199df168bb3d929
Author: Eli Schwartz <>
Date:   Mon Feb 12 20:53:06 2018 -0500

    db-functions: deduplicate some repeated logic
    reuse getpkgfile() in getpkgfiles()

commit 653056f43d73de53b4fb39ab24afe621f7361cbc
Author: Eli Schwartz <>
Date:   Mon Feb 12 20:50:57 2018 -0500

    Use more bashisms

commit 45d696b3b0bcdf55e53422e2cb9010a017b2153b
Author: Eli Schwartz <>
Date:   Mon Feb 12 20:39:30 2018 -0500

    Use modern bash to append to strings/arrays.
    Rather than using ugly hacks like arr[${#arr[*]}]="foo", bash 3.1 has
    the += operator.
    Update strings to use the same operator while we are at it.

commit f281c1ca6658112ef920792ca208aea7ed81dc7a
Author: Luke Shumaker <>
Date:   Sun May 17 19:44:18 2015 -0400

    db-functions: Fix check_repo_permission checking all architectures
    It mistakenly looped over just the first element of the ARCHES array,
    instead of the entire array.  This meant that it only checked the
    permissions for one architecture.
    Signed-off-by: Gabriel Souza Franco <>

commit 86f925da35e50acf62c941a74b47f3bfdb2d9ec3
Author: Eli Schwartz <>
Date:   Mon Feb 12 17:53:10 2018 -0500

    Update messages to make full use of printf formatters
    libmakepkg messaging functions provide automatic access to gettext
    (which we do not currently make use of) in addition to cleanly
    separating data from message strings.
    In order for this to work properly, pass argv correctly from die() to
    libmakepkg's error()

commit c953b0bea48726f9bcd735bde7c1483ddf616195
Author: Eli Schwartz <>
Date:   Mon Feb 12 17:21:39 2018 -0500

    Use return codes properly when checking for failed commands.
    Rather than doing a test(1) on the numerical value of the return code,
    use the `if !` and `||` operators during control flow.


Official repo DB scripts

Reply via email to