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 objections. 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 dan@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-1.5.5.3-1-i686.pkg.tar.gz' -> Removing existing package 'git-1.5.5.1-1'... -> Creating 'desc' db entry... -> Computing md5 checksums... -> Creating 'depends' db entry... ==> Creating updated database file /tmp/db-update.extra-i686.1026/build/extra.db.tar.gz No packages to delete Copying new files to '/home/ftp/extra/os/i686/' Cleaning staging dir dan@gerolde ~ $ ls staging/ core core64 extra extra64 testing testing64 unstable unstable64 dan@gerolde ~ $ ls /home/ftp/extra/os/i686/git-1.5.5. git-1.5.5.1-1-i686.pkg.tar.gz git-1.5.5.3-1-i686.pkg.tar.gz