Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
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.
|
|
|
|
Signed-off-by: Eric Bélanger <snowmaniscool@gmail.com>
Signed-off-by: Pierre Schmitz <pierre@archlinux.de>
|
|
|
|
|
|
The package pool dir depends on the host; so we solve this similar to
get_repos_for_host()
Note: There is no "os" subdir for the package pool.
|
|
This is a relative var, descendent from FTP_BASE. We do this because
we also need a relative path to the package pool dir
|
|
This gets rid of a bash loop for link detection
|
|
|
|
* The per repo script now simply removes files as they should all be
symlinks at this time
* The cron job script will do the extra job of checking the global
pool. If there are no more symlinks, move the pooled package
Signed-off-by: Aaron Griffin <aaronmgriffin@gmail.com>
|
|
|
|
|
|
Moved all cleanup related code in sourceballs-cleanup script and moved,
now common, functions in db-functions. The cleanup script is now ran
after all the new sourceballs have been fetched.
Signed-off-by: Eric Bélanger <snowmaniscool@gmail.com>
|
|
Make the files DB include everything the original packages DB includes
instead of just being 'files' entries. This will allow tools to do more with
these generated files and they can be used as a drop-in replacement for a
regular package database.
Signed-off-by: Dan McGee <dan@archlinux.org>
|
|
Instead of wasting time extracting .PKGINFO twice from every single package
in the repos, use the package DB to eliminate most of the heavy lifting.
This way we only need to worry about looking at the packages that actually
have changed since the last time we built the package database.
This should give a noticeable performance increase to this job in addition to
reducing IO load and unnecessary reading of every package file.
Signed-off-by: Dan McGee <dan@archlinux.org>
|