On Mon, Dec 1, 2008 at 6:44 PM, Pierre Schmitz <[EMAIL PROTECTED]> wrote: > Am Montag 01 Dezember 2008 23:34:55 schrieb Aaron Griffin: >> Go ahead and start with the kde-unstable repo, I created the dirs on >> gerolde so you should be able to do it at any time. > > Thanks. Just a sidenote: db-update does not work if there is no initial db > file. I think it just creates an empty file and repo-add fails later. > > I used repo-add manually for now. So this does not realy to be fixed soon. :-) > > I got the following output: > > [EMAIL PROTECTED] ~ % /arch/db-update kde-unstable x86_64 > Updating DB for kde-unstable x86_64 > ==> Copying DB file from 'kde-unstable'... > ==> Processing new/updated packages for repository 'kde-unstable'... > Checked out revision 20293. > Validating package arch (x86_64) akonadi > Checking SVN for akonadi > Validating package arch (x86_64) phonon > Checking SVN for phonon > ==> ERROR: Repository file '/srv/tmp/db-update.kde-unstable- > x86_64.1031/build/kde-unstable.db.tar.gz' is not a proper pacman database. > Copying new files to '/srv/ftp//kde-unstable/os/x86_64/' > Cleaning staging dir > 1 [EMAIL PROTECTED] ~ % file /srv/ftp/kde-unstable/os/x86_64/kde- > unstable.db.tar.gz > /srv/ftp/kde-unstable/os/x86_64/kde-unstable.db.tar.gz: empty
Hmm, sounds like a repo-add bug. It should create the file if it doesn't exist. I would assume a hack would be: touch kde-unstable.tar gzip kde-unstable.tar /me shrugs
