diff options
| author | Dan McGee <dan@archlinux.org> | 2010-08-25 18:39:57 +0200 |
|---|---|---|
| committer | Dan McGee <dan@archlinux.org> | 2010-08-25 18:40:01 +0200 |
| commit | 3c07e2e3ff951242a5d9fc124c6937e75e961da2 (patch) | |
| tree | b4fae5b3ef6f46ef57231cf03aaec2b65df5b71b | |
| parent | 1d6eb15bcc4c355edef1d6c249e9c67bca7d0404 (diff) | |
| download | dbscripts-3c07e2e3ff951242a5d9fc124c6937e75e961da2.tar.gz dbscripts-3c07e2e3ff951242a5d9fc124c6937e75e961da2.tar.xz | |
update-web-db: flip the arch/repo loops
This will really make sure [core] packages flow to the top of the list,
regardless of architecture. They should anyway, but anything that was only
updated in the first architecture updated could get artificially pushed
down before.
Signed-off-by: Dan McGee <dan@archlinux.org>
| -rwxr-xr-x | cron-jobs/update-web-db | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/cron-jobs/update-web-db b/cron-jobs/update-web-db index 3504813..8f91ca2 100755 --- a/cron-jobs/update-web-db +++ b/cron-jobs/update-web-db @@ -23,8 +23,8 @@ echo "$cmd: Updating DB at $(date)" >> "${LOGOUT}" ## do the dirty, then output the result to a file. cd $SPATH -for arch in ${ARCHES}; do - for repo in ${REPOS}; do +for repo in ${REPOS}; do + for arch in ${ARCHES}; do case "$cmd" in update-web-db) dbfile="/srv/ftp/${repo}/os/${arch}/${repo}.db.tar.gz" |