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 549fe0017f44031b24fb5322726721b95cca395b (commit) via 1bf2b35e8d6574e507853102c5d4b464ff767956 (commit) from 61c9cc6f44e654a90a12da11be06e707e3f4b162 (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 549fe0017f44031b24fb5322726721b95cca395b Author: Luke Shumaker Date: Sun Jul 15 01:19:54 2018 -0400 test: Resolve "TODO: Does not fail if one arch is missing" - Implement the TODO by keeping a list/set of architectures found via "$repo-$arch" directory names, and another list/set of architectures named in arch=() in the PKGBUILD(s). This means turning the simple `compgen` in to a loop. - While we're at it loading PKGBUILDs in a loop, fix that it clearly isn't doing anything with the $pkgver argument; it should verify that the version in the found PKGBUILD(s) matches that argument. - Use extglob to more strictly match the "arch" part of the "repo-arch" dirname; the existing glob wouldn't have behaved correctly for values of $repo containing a "-" (like "community-testing"). We don't currently test with any of those, but it makes me nervous. - Also make that extglob change in checkRemovedPackage. While we're at it, let Bash do the glob expansion normally and check it with __isGlobfile, instead of compgen; it means we don't have to worry about escaping the non-glob part of the string. Not that we expect it to contain anything needing escaping, but again, it makes me nervous. commit 1bf2b35e8d6574e507853102c5d4b464ff767956 Author: Luke Shumaker Date: Sun Jul 15 22:47:19 2018 -0400 test: db-remove: Verify that it accepts pkgname (in addition to pkgbase) It is important that db-remove be able to remove a single pkgname, without being able to look it up by pkgbase in SVN. For instance, when a split package update removes one of its members; there will be no reference to the removed pkgname in SVN, and it won't be removed by db-update. If db-remove doesn't accept pkgnames, then this outdated orphan could not be removed. ----------------------------------------------------------------------- Summary of changes: test/cases/db-remove.bats | 19 +++++++++++++++++++ test/lib/common.bash | 27 ++++++++++++++++++++++++--- 2 files changed, 43 insertions(+), 3 deletions(-) hooks/post-receive -- Official repo DB scripts