app-forensics/foremost x11-plugins/gkrellmms x11-plugins/gkrelltop metadata.xml doesn't need executable bit ;)
Can only be fixed by CVS admin.
Does not appear to be a problem on lark. -r--r--r-- 1 pylon cvs 907 Dec 15 15:35 app-forensics/foremost/metadata.xml,v -r--r--r-- 1 pylon cvs 559 Dec 15 15:44 x11-plugins/gkrellmms/metadata.xml,v -r--r--r-- 1 pylon cvs 559 Dec 15 15:44 x11-plugins/gkrelltop/metadata.xml,v Does not appear to be a problem in any of my local trees either. Make sure you rm *.xml local then cvs up again. Reopen if incorrect.
*** Bug 137089 has been marked as a duplicate of this bug. ***
Well, reopening this, it's broken on mirrors, not in CVS. Every time I delete the files and emerge --sync, I get them +x. Additionally, merged from Bug 137089: -rwxr-xr-x 1 portage portage 3.6K Oct 7 2003 BCS -rwxr-xr-x 1 portage portage 15K Mar 4 2004 CAPS -rwxr-xr-x 1 portage portage 1.7K Sep 4 2003 FastCGI -rwxr-xr-x 1 portage portage 5.4K Jun 10 2005 OGTSL -rwxr-xr-x 1 portage portage 1.8K Sep 29 2004 PBZIP2 -rwxr-xr-x 1 portage portage 2.8K Jul 12 2003 blackshades -rwxr-xr-x 1 portage portage 2.2K May 9 2005 libSPF
Looks like it was set +x on the mastermirror, but not on CVS. No idea how that happened, but I changed the perms. Lets see if it gets fixed downstream now. Close when it finally does.
I've synched now, and all files in /usr/portage/licenses/ have the correct permissions. I've even deleted that directory and rsync created it with correct permissions. Those metadata.xml files still has +x permissions, even after deleting those files and resynching. I hope the servers forgive me... I had synched three times in a row for checking this. :)
(In reply to comment #6) > Those metadata.xml files still has +x permissions, even after deleting those > files and resynching. Doh, forgot to do those too :) I just changed it as well. You should see it in an hour.
All good here as well, thanks.
