Age | Commit message (Collapse) | Author |
|
Add 'any' to the items looped over in the ${ARCHES[@]} loop
Signed-off-by: Aaron Griffin <aaronmgriffin@gmail.com>
|
|
Signed-off-by: Aaron Griffin <aaronmgriffin@gmail.com>
|
|
Signed-off-by: Dan McGee <dan@archlinux.org>
|
|
We can't really do the basedir magic from db-functions as it is just being
sourced and is not the currently executing script. Although a bit
repetitive, it is a lot safer to just include the config file everywhere.
Noticed this when trying to run the latest available scripts on sigurd.
Signed-off-by: Dan McGee <dan@archlinux.org>
|
|
Removed the need for makepkg.conf
* Killed off CARCH
* Added PKGEXT to the config file
* Remove source_makepkg function
* Source config file where makepkg.conf was needed
Signed-off-by: Aaron Griffin <aaronmgriffin@gmail.com>
|
|
DBEXT contains the full extension for the db files (.db.tar.gz)
and is recorded in the config file
Signed-off-by: Aaron Griffin <aaronmgriffin@gmail.com>
|
|
Signed-off-by: Dan McGee <dan@archlinux.org>
|
|
Signed-off-by: Aaron Griffin <aaronmgriffin@gmail.com>
|
|
[Aaron: keep WORKDIR creation outside the loop, as its
removed at the end]
Signed-off-by: Aaron Griffin <aaronmgriffin@gmail.com>
|
|
Because we lock/unlock in a loop, simply remove the cleanup trap
at the end of the process, and manually clean up the work dir
Signed-off-by: Aaron Griffin <aaronmgriffin@gmail.com>
|
|
Signed-off-by: Aaron Griffin <aaronmgriffin@gmail.com>
|
|
Signed-off-by: Aaron Griffin <aaronmgriffin@gmail.com>
|
|
* also added error msg for repo_lock in db-functions
[Aaron: keep quotes around $WORKDIR]
Signed-off-by: Aaron Griffin <aaronmgriffin@gmail.com>
|
|
[Aaron: Don't remove quotes around $WORKDIR]
Signed-off-by: Aaron Griffin <aaronmgriffin@gmail.com>
|
|
* When calling cleanup at the end of db-update, the function
repo_unlock is called, but the repo-locks have already been unlocked!
So we get a spurious error message. This commit replaces "cleanup" by
"rm -rf $WORKDIR".
Signed-off-by: Aaron Griffin <aaronmgriffin@gmail.com>
|
|
Signed-off-by: Aaron Griffin <aaronmgriffin@gmail.com>
|
|
Signed-off-by: Aaron Griffin <aaronmgriffin@gmail.com>
|
|
Signed-off-by: Aaron Griffin <aaronmgriffin@gmail.com>
|
|
Signed-off-by: Aaron Griffin <aaronmgriffin@gmail.com>
|
|
Signed-off-by: Aaron Griffin <aaronmgriffin@gmail.com>
|
|
Original-work-by: François Charette <francois@archlinux.org>
Signed-off-by: Aaron Griffin <aaronmgriffin@gmail.com>
|
|
Signed-off-by: Aaron Griffin <aaronmgriffin@gmail.com>
|
|
repo-add handles this on its own
Signed-off-by: Aaron Griffin <aaronmgriffin@gmail.com>
|
|
Signed-off-by: Aaron Griffin <aaronmgriffin@gmail.com>
|
|
Signed-off-by: Aaron Griffin <aaronmgriffin@gmail.com>
|
|
Also fixes the bug in the previous commit, in which the
arch-independent packages would be deleted from the staging
directory after only one iteration.
|
|
Signed-off-by: Aaron Griffin <aaronmgriffin@gmail.com>
|
|
This could be useful if we move community to a separate
SVN repo
Signed-off-by: Aaron Griffin <aaronmgriffin@gmail.com>
|
|
ARCHES is defined in config. db-update should now loop
over all arches on each run and update whatever is in the
staging dir.
Remove the db-*64 scripts due to this
Signed-off-by: Aaron Griffin <aaronmgriffin@gmail.com>
|
|
Conflicts:
db-update
Signed-off-by: Aaron Griffin <aaronmgriffin@gmail.com>
|
|
Signed-off-by: Aaron Griffin <aaronmgriffin@gmail.com>
|
|
This prevents some errors where packages where removed
from the staging dir when they shouldn't have been.
Original-idea-by: Pierre Schmitz <pierre@archlinux.org>
Signed-off-by: Aaron Griffin <aaronmgriffin@gmail.com>
|
|
This assumes the -q flag patch is accepted for pacman 8)
Signed-off-by: Aaron Griffin <aaronmgriffin@gmail.com>
|
|
repo-add works fine if no db file exists
Signed-off-by: Aaron Griffin <aaronmgriffin@gmail.com>
|
|
We were copying our DB file from the repo to
our temp build dir all the time. We should only
do this if there are packages to add
Signed-off-by: Aaron Griffin <aaronmgriffin@gmail.com>
|
|
If add/del dirs exist, we try to fix it all up and it can
error quite loudly
Signed-off-by: Aaron Griffin <aaronmgriffin@gmail.com>
|
|
The chmod doesn't work unless the user is the owner of the file
Resorting to umask changes here
Signed-off-by: Aaron Griffin <aaronmgriffin@gmail.com>
|
|
The local variable 'arch' was being overwritten when we
source PKGBUILDs. Change it to _arch wherever we deal
with PKGBUILD files
Signed-off-by: Aaron Griffin <aaronmgriffin@gmail.com>
|
|
db-remove is superior and requiring package files is dumb.
Kill off this dir and clean up some code, yay!
Signed-off-by: Aaron Griffin <aaronmgriffin@gmail.com>
|
|
This prevents us from trying to remove the lockfile
twice, and calling cleanup multiple times
Signed-off-by: Aaron Griffin <aaronmgriffin@gmail.com>
|
|
Additionally, make TMPDIR configurable so we can move that
Signed-off-by: Aaron Griffin <aaronmgriffin@gmail.com>
|
|
This should allow us to move FTP and SVN placement
around
Signed-off-by: Aaron Griffin <aaronmgriffin@gmail.com>
|
|
Signed-off-by: Aaron Griffin <aaronmgriffin@gmail.com>
|
|
This will force all files copied back and forth to have
0664 permissions so that we can attempt to do away with
this permission adjusting cron job
Signed-off-by: Aaron Griffin <aaronmgriffin@gmail.com>
|
|
Signed-off-by: Aaron Griffin <aaronmgriffin@gmail.com>
|
|
This is to allow moves to /home/ftp/ to remain on the same
filesystem, thus making the final moves atomic
Signed-off-by: Aaron Griffin <aaronmgriffin@gmail.com>
|
|
Apparently, people seem to be renaming files as a "hack" and
breaking things. Let's make sure they edited the PKGINFO too
Signed-off-by: Aaron Griffin <aaronmgriffin@gmail.com>
|
|
Common functions, such as sourcing makepkg, and locking a repo
Additionally, repo-locking has been unified to prevent multiple
users from corrupting a repo (i.e. db-move run while db-remove
in progress)
Signed-off-by: Aaron Griffin <aaronmgriffin@gmail.com>
|
|
This stops files being removed from the staging area if they were not
successfully copied to the repo. This can happen due to permission
issues with the database when multiple people update the repo in quick
succession.
Original-work-by: Allan McRae <allan@archlinux.org>
Signed-off-by: Aaron Griffin <aaronmgriffin@gmail.com>
|
|
This way, all package files get cleaned up properly
at the end of the process.
Signed-off-by: Aaron Griffin <aaronmgriffin@gmail.com>
|