Age | Commit message (Collapse) | Author | Files | Lines |
|
instead from fs
|
|
* usage of db-functions
* Lock the db and work on a copy to avoid long lock times
* Lock the script itself to avoid multiple calls
* Adjust to coding style to other dbscripts
|
|
|
|
* use correct locking of the repos
* added test case
* removes file lists of deleted packages
* add compression independent symlink to files db
|
|
|
|
Signed-off-by: Eric Bélanger <snowmaniscool@gmail.com>
Signed-off-by: Pierre Schmitz <pierre@archlinux.de>
|
|
Signed-off-by: Eric Bélanger <snowmaniscool@gmail.com>
Signed-off-by: Pierre Schmitz <pierre@archlinux.de>
|
|
|
|
|
|
|
|
|
|
|
|
* Decrease file stats as much as possible
* Create a list of all packages and meta data only once
* Create a list of available source packages only once
* Create a list of expected packages only once
* Combine all three scripts into one to share data and code
* Use as much information from the db files as possible and avoid using svn
* Avoid attempting to create the same source package twice
Logic works as follows:
1) create a list of all packages
2) Check for each package if we need a src package and create one
3) During this process create a list of all src packages that should be there
4) Diff both lists for the cleanup
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This is consistent with the other dbscripts.
The output will be send to the mailinglist.
|
|
|
|
* Read package lists directly from DB file
* Make SVNREPO configurable
|
|
* add unit test for sourceballs and cleanup
* introduce SRCPOOL and LOGDIR variables in config
|
|
|
|
Signed-off-by: Dan McGee <dan@archlinux.org>
|
|
Signed-off-by: Dan McGee <dan@archlinux.org>
|
|
|
|
Signed-off-by: Dan McGee <dan@archlinux.org>
|
|
Using the hostname to decide which repos to use is not releiable and hard to test.
Instead use config.local to configure these.
config files for sigurd and gerolde were added which can be copied or symlinked to config.local
on the specific host.
|
|
|
|
Don't duplicate the user:group pair all over the place; put all of the
associated repos and directories in the same case statement for a given set
of credentials.
Signed-off-by: Dan McGee <dan@archlinux.org>
Signed-off-by: Pierre Schmitz <pierre@archlinux.de>
|
|
* Repositories can now be defined in the config file for each host
* added community-staging, gnome-unstable and kde-unstable
* Exception is the adjust-permission cron-job; but we might want to use acls in future anyway
Signed-off-by: Pierre Schmitz <pierre@archlinux.de>
|
|
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>
|
|
Signed-off-by: Dan McGee <dan@archlinux.org>
|
|
Signed-off-by: Dan McGee <dan@archlinux.org>
|
|
This has been untracked by version control for a while on gerolde in both
the cron-jobs directory and in /etc/cron.hourly/. Add it here so we can make
changes and know what is going on.
This is an improved script over what we currently have. It is one script
instead of two, and it does things a little smarter with the logging.
Signed-off-by: Dan McGee <dan@archlinux.org>
|
|
|
|
|
|
|
|
* runtime reduced to < 1 second
* uses file lists and the comm command
* searches for missing packages
* removes empty legacy directories like extra/os/any
|
|
|
|
These functions are copied from makepkg
|
|
There are no longer architecture-specific subdirs and the structure was switch to this:
ftp
└── pool
├── community
└── packages
packages contains all packages from core, extra and testing; this naming is in sync with the svn repo naming:
svn-packages and svn-community
|
|
|
|
|
|
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.
|
|
|