Can't emerge packages from subversion (bug #143480) (SOLVED)

jorgepeixoto

When I try to emerge something from subversion, I get access violations.
I have already tried upgrading to the ~x86 verions of portage, sandbox and subversion. No help.
Google yields nothing.

Example of error:

sudo emerge -av initng
Password:

These are the packages that would be merged, in order:

Calculating dependencies... done!
[ebuild U ] sys-apps/initng-99999 [0.6.7] USE="-as_init -busybox -check_ro -cmake_color_makefile -count_me -debug -force_nocolor -service_cache%" INITNG_PLUGINS="also bash_launcher chdir chroot conflict cpout critical envparser find fstat history idleprobe initctl interactive iparser last limit logfile netprobe ngc4 pause provide reload renice rlparser simple_launcher stcmd stdout suid syncron syslog unneeded -ctrlaltdel -daemon_clean -dbus_event -debug_commands -fmon -lockfile -netdev -ngcs -nge -selinux -service_file% -sysreq -usplash%" 0 kB [3]

Total size of downloads: 0 kB
Portage overlays:
[1] /usr/local/media-portage
[2] /usr/local/initng-portage
[3] /usr/local/jorge-portage

Would you like to merge these packages? [Yes/No]

>>> Emerging (1 of 1) sys-apps/initng-99999 to /
* checking ebuild checksums ;-)

... [ ok ]
* checking auxfile checksums ;-)

... [ ok ]
* checking miscfile checksums ;-)

... [ ok ]
>>> Unpacking source...
* subversion check out start -->
* repository: http://svn.initng.org/initng/trunk
ACCESS DENIED mkdir: /usr/portage/distfiles/svn-src/.subversion
ACCESS DENIED mkdir: /usr/portage/distfiles/svn-src/initng/trunk
svn: Can't make directory 'trunk': Permission denied

!!! ERROR: sys-apps/initng-99999 failed.
Call stack:
ebuild.sh, line 1543: Called dyn_unpack
ebuild.sh, line 707: Called src_unpack
initng-99999.ebuild, line 22: Called subversion_src_unpack
subversion.eclass, line 272: Called subversion_fetch
subversion.eclass, line 179: Called die

!!! subversion.eclass: can't fetch from http://svn.initng.org/initng/trunk.
!!! If you need support, post the topmost build error, and the call stack if relevant.

--------------------------- ACCESS VIOLATION SUMMARY ---------------------------
LOG FILE = "/var/log/sandbox/sandbox-sys-apps_-_initng-99999-5248.log"

mkdir: /usr/portage/distfiles/svn-src/.subversion
mkdir: /usr/portage/distfiles/svn-src/initng/trunk
--------------------------------------------------------------------------------
!!! This ebuild is from an overlay: '/usr/local/jorge-portage'

body · n00b Joined: 27 Jun 2004 Posts: 41

dito

jorgepeixoto · Posted: Tue Sep 05, 2006 10:49 am Post subject: This also happens

This also happens for ebuilds not from overlay

Slammer · Posted: Tue Sep 05, 2006 11:35 am Post subject:

Happens in both x86 and ~x86 machines... :cry:

Create a bug report in bugzilla, something is broken.....
_________________
Keep Slamming...

ikujam · Posted: Tue Sep 05, 2006 4:57 pm Post subject:

Had the same error here, seemed to be an access violation. I tried to delete the svn-src directory inside /usr/portage/distfiles, even made that dir world writeable, but portage would still not create directories inside.

After scratching my head a little, I figured out that the problem was related to sandboxing, and thus a simple workaround is to disable it :

in /etc/make.conf , look for FEATURES and add -sandbox or add the following line at the end of the file:

FEATURES="-sandbox"

good luck

jorgepeixoto · Posted: Tue Sep 05, 2006 5:07 pm Post subject: I have created Bug #146418

I have created Bug #146418.

About FEATURES=-sandbox:

I have thought about it too. But I'm not sure it is safe. I mean, it's there for a reason.

Specifically for the initng-9999 and initng-ifiles-9999 ebuilds, is it safe?

jorgepeixoto · Posted: Tue Sep 05, 2006 6:54 pm Post subject: Turns out that

Turns out that the bug was a duplicate of bug 143480, and the real problem is in subversion.eclass. I hope there is a fix soon.

ksleher · n00b Joined: 30 Jun 2004 Posts: 18

Is there a fix for this yet? if so how do i update it?

alienjon · Veteran Joined: 09 Feb 2005 Posts: 1709

Looks like there is a fix. Check out the bug and try what they suggest. I'm giving it a shot now, as all of my personal ebuilds are failing to complete.

** Update **
Basically, the bug site brought me to this page. I checked out the file and saw that the first change had been added, but the second had not. Even after adding the second, though, it still didn't work.

jorgepeixoto · Posted: Sat Sep 09, 2006 12:14 am Post subject: A fix

In bug #143480, they offer an alternative eclass that you can put in an overlay. I did that. Problem solved.

However, Portage have since then been upgraded and this alternative eclass is not needed anymore.

I'm using portage-2.1.1_rc1-r7, which is ~x86.

I don't know if there is already a fix for the latest x86 portage. Anyway, if you perform and emerge --sync && emerge -auv portage and the problem persists, you can put ~sys-apps/portage-2.1.1_rc1 in /etc/package.keywords to fetch the latest ~x86 portage, which does not have the problem.. It is stable for me.

mxc · Guru Joined: 05 Mar 2003 Posts: 442 Location: South Africa

I am also experiencing this problem. I have portage-2.1.1. Should this have fixed the problem?
Trying ACCEPT_KEYWORDS="~x86" emerge portage just wants to re-install portage-2.1.1

thanks
_________________
http://www.CyberDesigns.co.za
http://www.Jumpingbean.co.za

alienjon · Veteran Joined: 09 Feb 2005 Posts: 1709

jorgepeixoto

I have Portage-2.1.1 (since my last post, 2.1.1 have come to the tree) and I have no problem. I am emerging initng-ifiles-999 right now (it wasn't possible when I was affected by the problem).

didibe · n00b Joined: 13 Sep 2006 Posts: 1

Try
FEATURE=-sandbox emerge sandbox

Afterwards emerge your staff. That helped in my case.

wbr