| Age | Commit message (Collapse) | Author |
|---|
|
|
|
* config: drop SVNREPO
* cron-jobs/sourceballs: Replace commented out SVN code and active ABS code
with XBS code. The XBS code is fairly similar to the SVN code, the
difference being that it uses `xbs releasepath` instead of `svn export`.
* db-functions:
- Rename check_pkgsvn to check_pkgxbs
- check_pkgxbs: Drop the `svn export` bit, as `xbs releasepath` assumes
that a working directory already exists. Replace the paths created by
the `svn export` with calls to `xbs releasepath`.
- check_splitpkgs: Drop the ABS `cp` -r bit, as `xbs releasepath` assumes
that a working directory already exists. Replace the paths created by
the `cp -r` with calls to `xbs releasepath`. Rename the variables and
temporary files s/svn/xbs/ .
* db-move:
- First loop: Rename the variable svnrepo_from to xbsrepo_from, and get
the value from `xbs releasepath`.
- Second loop: Run `xbs move` before the inner loop to get a list of
architectures. Rename the variable `svnrepo_from` to `xbsrepo_to`, and
get the value for it from `xbs releasepath`. Because xbs guarantees
that the PKGBUILD exists for the architectures listed, replace the
check for whether the PKGBUILD exists with `if true`, to keep merging
easy (as opposed to removing the if, and de-indenting the whole thing).
* db-remove: Get the location of the PKGBUILD from `xbs releasepath`, call
`xbs unrelease`, and adjust a message to use `xbs name` and mention the
appropriate repo/arch pair.
|
|
|
|
|
|
|
|
Of course, this only works for things that use db-functions, so
db-sync won't touch it.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
I used this command to find them:
egrep -r --exclude-dir={test,.git} '(plain|msg|msg2|warning|error|stat_busy|stat_done|abort|die)\s+"?[^"]*\$'
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
- TODO: add trailing newline
- config: add text editor hint
- config.orig: remove
- getrepos: quote, use --
- db-functions: hardcode some paths, remove needless nullglob
|
|
|
|
|
|
Conflicts:
db-functions
|
|
|
|
In addition to this dbscripts wont accept unsigned pacakges when
REQUIRE_SIGNATURE is set to true.
Note: At this point no signature verification is performed at all.
|
|
|
|
|
|
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
|
|
|
|
|
|
* 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
|
|
PKGBUILDs expect CARCH to be set. This is needed when sourcing them directly.
|
|
|
|
|
|
In addition to pkgver and pkgrel it is checked if pkgname is defined in the PKGBUILD.
|
|
Don't use globing as this will match a package of the same version but another arch.
We can be more specific here as there are no longer packages without $arch extension.
|
|
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.
|
|
|
|
This also checks if the sam package exists within the old package
layout (without package pool)
|
|
See FS#20745
|
|
* 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.
|
|
* 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>
|
|
|
|
If reading from a PKGBUILD fails stop immediatly. Also put out more usefull error messages.
|
|
|
|
|
|
|
|
|
