| Age | Commit message (Collapse) | Author |
|---|
|
This allows invoking these commands for more than one package at a time
which is incredibly more efficient as the database doesn't need to be
locked, unpacked, modified, changed, and unlocked for every single
passed package name or file if you have more than one.
Signed-off-by: Dan McGee <dan@archlinux.org>
|
|
This matches what we do in db-update, and makes the most sense if we
want to expand these commands to take multiple arguments at the same
time. Especially in the case of db-repo-add and db-repo-remove, these
wrapper commands should be no more limiting than repo-add and
repo-remove which always allow multiple arguments and are more efficient
that way.
This patch simply reorders the arguments; a later patch will support
multiple pkgname/pkgbase/pkgfile arguments on the command line.
Although this does break backwards compatibility and requires some
changing of muscle memory, I think it is a worthwhile change to make as
the functionality of these commands becomes more powerful and the order
of arguments becomes the same in all of them.
Signed-off-by: Dan McGee <dan@archlinux.org>
|
|
We know what the user wants us to do (remove a package from the repo and
svn) so if it's not in svn it should still be removed from the db.
Having to use a seperate tool (db-repo-remove) is confusing.
Signed-off-by: Florian Pritz <bluewind@xinu.at>
Signed-off-by: Pierre Schmitz <pierre@archlinux.de>
|
|
|
|
repo-add and repo-remove is now indirectly called by arch_repo_add/remove.
This simplifies future extensions like incremental file list creations. See FS#11302
|
|
|
|
* When writing the db file ensure that it has write permission of the group which owns the parent directory.
* This should make the adjust-permissions cron job obsolete.
|
|
|
|
|
|
|
|
|
|
These functions are copied from makepkg
|
|
Added a function to check if user has permission to alter the repos
and db files.
|
|
This patch sources a PKGBUILD in a subshells instead of directly.
This way we don't polute our scope or overwrite our vars which might lead to unexpected behavior.
|
|
db-functions now sets an individual $WORKDIR and implements trap functinos that
remove locks on exit or error. There are new functions to lock and unlock the running script.
misc-scripts/ftpdir-cleanup was renamed to ftpdir-cleanup-repo as the cron-job had the same name.
Script names have to be unique when using db-functions.
|
|
|
|
There is no need to have a variable for things like PKGBUILD
that are very unlikely to ever change.
|
|
* There is no need to copy the db into a working dir
* cleanup is automatically called on exit
|
|
Only inform of errors and processes that might take longer.
|
|
|
|
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>
|
|
db-remove use the arch variable to handle the arch parameter passed to the
script. As the arch variable is already used in PKGBUILD, this variable
conflict cause unwanted behaviour.
Signed-off-by: Aaron Griffin <aaronmgriffin@gmail.com>
|
|
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>
|
|
Signed-off-by: Aaron Griffin <aaronmgriffin@gmail.com>
|
|
Also: changed empty variable '$ftpdir' in db-remove
to '$ftppath/$architecture'
|
|
This could be useful if we move community to a separate
SVN repo
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>
|
|
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>
|
|
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>
|
|
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>
|
|
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>
|
|
Signed-off-by: Aaron Griffin <aaronmgriffin@gmail.com>
|
|
This script deletes by package NAME only. Additionally, it
also removes from svn. The goal is to simplify the process
of removing packages.
Signed-off-by: Aaron Griffin <aaronmgriffin@gmail.com>
|
