[arch-dev-public] Permissions of community-staging need to be reset
Hi, Could an AUR admin (or Andrea) reset the perms of the community-staging repo db for both arches? Thanks
On Sun, 12 Sep 2010 02:40:36 -0400, Eric Bélanger <snowmaniscool@gmail.com> wrote:
Hi,
Could an AUR admin (or Andrea) reset the perms of the community-staging repo db for both arches?
Thanks
What's wrong with the permissions? dbscripts should have taken care of them. -- Pierre Schmitz, https://users.archlinux.de/~pierre
On Sun, Sep 12, 2010 at 2:51 AM, Pierre Schmitz <pierre@archlinux.de> wrote:
On Sun, 12 Sep 2010 02:40:36 -0400, Eric Bélanger <snowmaniscool@gmail.com> wrote:
Hi,
Could an AUR admin (or Andrea) reset the perms of the community-staging repo db for both arches?
Thanks
What's wrong with the permissions? dbscripts should have taken care of them.
-- Pierre Schmitz, https://users.archlinux.de/~pierre
They should be chmod 664. I guess Andrea updated the db without using the dbscripts and forgot to chmod 664 them (we are no longer running the cron job to adjust permissons). $ /arch/db-update ==> ERROR You don't have permission to update packages in community-staging ==> Removing left over lock from [community-staging] (i686) ==> Removing left over lock from [community-staging] (x86_64) 29 ebelanger@sigurd $ ls -l /srv/ftp/community-staging/os/i686/community-staging.db.tar.gz -rw-r--r-- 1 andrea tusers 1.8K Sep 12 00:17 /srv/ftp/community-staging/os/i686/community-staging.db.tar.gz 30 ebelanger@sigurd $ ls -l /srv/ftp/community-staging/os/x86_64/community-staging.db.tar.gz -rw-r--r-- 1 andrea tusers 1.8K Sep 12 00:18 /srv/ftp/community-staging/os/x86_64/community-staging.db.tar.gz
Am 12.09.2010 09:16, schrieb Eric Bélanger:
Could an AUR admin (or Andrea) reset the perms of the community-staging repo db for both arches? What's wrong with the permissions? dbscripts should have taken care of them.
Done.
They should be chmod 664. I guess Andrea updated the db without using the dbscripts and forgot to chmod 664 them (we are no longer running the cron job to adjust permissons).
Well, nobody is supposed to touch the DBs without dbscripts, and if they do, they must fix up the permissions (there is one rare corner case that dbscripts don't handle right). The cronjob was an ugly hack that just increased our load needlessly.
On 12 September 2010 11:27, Thomas Bächler <thomas@archlinux.org> wrote:
Well, nobody is supposed to touch the DBs without dbscripts, and if they do, they must fix up the permissions (there is one rare corner case that dbscripts don't handle right). Damn! I manually re-added a package because it was already into the repo db and I forgot to fix permissions. Also, I was without and internet connection until now...
Sorry guys! -- andreascarpino.it Arch Linux Developer
participants (4)
-
Andrea Scarpino
-
Eric Bélanger
-
Pierre Schmitz
-
Thomas Bächler