On Wed, 18 Jun 2008, Thomas Bächler wrote:
Tobias Kieslich schrieb:
Eric just reported that, the db has his user permission, which is why I can't overwrite it: -bash-3.2$ ls -l /home/ftp/extra/os/i686/extra.* -rw-r--r-- 1 eric users 412828 Jun 17 22:44 /home/ftp/extra/os/i686/extra.db.tar.gz -rw-r--r-- 1 eric users 412653 Jun 17 22:44 /home/ftp/extra/os/i686/extra.db.tar.gz.old -rw-rw-r-- 1 ftp ftp-extra 320495 May 21 05:36 /home/ftp/extra/os/i686/extra.db.tar.gz.orig -rw-r--r-- 1 pierre ftp-extra 3066292 Jun 18 03:57 /home/ftp/extra/os/i686/extra.files.tar.gz -rw-r--r-- 1 aaron ftp-extra 3059214 Jun 17 16:41 /home/ftp/extra/os/i686/extra.files.tar.gz.old
bye can anyone with permissions can take care of that? thanks -T
1) This shouldn't happen 2) There should be a cronjob in place to fix the permissions.
Dunno what happened to the cron job though, Aaron can probably answer that.
The extra repo and the unstable repo for both arches have that problem. On Tobias's request, I've set the permissions to 664 as temporary fix. My guess is that it was caused by the db-move script which I uses last night to move gimp-devel to extra as the testing x86_64 db has the right permissions. It might have been caused by the way I did it. I first updated the unstable package (unstablepkg on my system, db-unstable on gerolde), checked the output then ran db-move a few minutes later. Perhaps I should've waited longer before running db-move. Or maybe it's a problem with the cron jobs. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.