[arch-dev-public] dbscripts questions

Dan McGee dpmcgee at gmail.com
Thu May 29 20:33:59 EDT 2008

Quick questions about the DB scripts, the output is below for
reference. I haven't built a new package in quite a while and I have
been on vacation, so hopefully I'm not repeating old material here.

1. It didn't die, but they tell me to both delete my 64 staging dirs
and then throw errors on the stat. I guess it is a bit misleading, but
as long as the 64 bit dirs are on the way out, not too many
2. db-extra tells me there are no package to delete, and doesn't list
old files anymore. Yet the old package definitely still exists- are
these cleaned up by a cronjob now so I have nothing to worry about?


dan at gerolde ~
$ /arch/db-extra
Updating DB for extra i686
It looks like you have an old staging dir
Packages are now differentiated by the arch in the filename.
Please delete '/home/dan/staging/extra64'
/bin/mv: cannot stat `/home/dan/staging/extra64/add/*': No such file
or directory
/bin/mv: cannot stat `/home/dan/staging/extra64/del/*': No such file
or directory
==> Processing new/updated packages for repository 'extra'...
Checked out revision 2230.
    Checking SVN for git
==> Extracting database to a temporary location...
==> Adding package 'git-'
  -> Removing existing package 'git-'...
  -> Creating 'desc' db entry...
  -> Computing md5 checksums...
  -> Creating 'depends' db entry...
==> Creating updated database file
No packages to delete
Copying new files to '/home/ftp/extra/os/i686/'
Cleaning staging dir

dan at gerolde ~
$ ls staging/
core  core64  extra  extra64  testing  testing64  unstable  unstable64

dan at gerolde ~
$ ls /home/ftp/extra/os/i686/git-1.5.5.
git-  git-

More information about the arch-dev-public mailing list