[ebuild U ] app-misc/mc-4.6.0-r14 [4.6.0-r13] +7zip* -X -debug -gpm +ncurses +nls +samba +slang +unicode 0 kB --------------------------- ACCESS VIOLATION SUMMARY --------------------------- LOG FILE = "/tmp/sandbox-app-misc_-_mc-4.6.0-r14-9984.log" access_wr: /etc/krb5.conf access_wr: /etc/krb5.conf --------------------------------------------------------------------------------
I got the same thing when building samba-3.0.10 and samba-3.0.14a-r1 with USE="ldap kerberos".
I also get the same with php-4.4.0_rc1 and mod_php-4.4.0_rc1 and samba-3.0.14a-r1 Anyone got any idea what is causing this? Is there a workaround? Use flags for Samba are: -acl +cups +doc +kerberos + ldap -libclamav -mysql -oav +pam -postgresq +python -quotas +readline -selinux +winbind +xml +xml2 Error is the same as in the Description of this bug (access_wr: /etc/krb5.conf)
For a workaround, disable sandbox with FEATURES="-sandbox". Alternatively, create an overlay ebuild with "addpredict /etc/krb5.conf" inside src_compile.
It seems like that something similar to 'touch /etc/krb5.conf' is required for proper configuration: no change is made in case of successful write. mit-krb5<1.3.6-r2 doesn't have this behaviour. Adding 'addpredict /etc/krb5.conf' to samba ebuilds.
(In reply to comment #4) > Adding 'addpredict /etc/krb5.conf' to samba ebuilds. So is this fixed now?
I can confirm that this bug is still open for current x86-stable-mc. Somebody should update the ebuild soon, as this bug is pretty old and easy to fix.
Any news on this? Just tried to remerge mc on an amd64 machine, and all 3 ebuilds fail with this error message.
I think also that this should be easy to fixe and the bug can clossed immediately. Thanks
it seems to need a fix in the samba ebuilds, still i don't know what "addpredict /etc/krb5.conf" does and if it is the correct solution
samba should be ok since June (and particularly samba-3.0.14a-r2, which is going to be marked stable for all archs). Are still there issues with it?
I don't like the addpredict fix. However, I'm a little confused as to what exactly the problem is. Which packages are showing this access violation?
*** Bug 96453 has been marked as a duplicate of this bug. ***
Can someone who's experiencing this please duplicate this for me and then give me a tarball of /var/tmp/portage/whatever-package (mc or samba or whatever) that I can download and investigate please? I'm *not* happy with the addpredict fix, because I don't think it is a fix. It's just a workaround for a symptom of something else which isn't fixed. I will be removing that from the ebuilds.
Hi, I get this error when emerging mc too, I have made a tar.gz file available as requested here: ftp://ftp.farmorg.co.uk/pub/other/ farmorg
Please try with sandbox-1.2.12.
It works for me with sandbox-1.2.12
works for me also with sandbox-1.2.12 farmorg
(In reply to comment #13) > Can someone who's experiencing this please duplicate this for me and then give > me a tarball of /var/tmp/portage/whatever-package (mc or samba or whatever) that > I can download and investigate please? I'm *not* happy with the addpredict fix, > because I don't think it is a fix. It's just a workaround for a symptom of > something else which isn't fixed. I will be removing that from the ebuilds. Well, if someone knows where I can put a 44MB gz file, I will gladly upload the content of my samba-3.0.14a-r2 build. Unfortunately, I don't have any webspace over 10MB I can use. E-mail me at pubare1026-at-hotmail.com or my bugzilla-listed addy if you know someplace I can ftp this to. Can also confirm that it does build properly with sandbox-1.2.12, the above mentioned gz was using sandbox-1.2.11.
You can upload it to here: ftp.farmorg.co.uk/pub/other/ I'm not sure if the server is configured correctly to allow uploads, please let me know asap if you cannot upload the file & i'll correct it, it's my first ftp server. farmorg
CMIIW but my impression is that this bug was fixed with sandbox-1.2.12 so the tarball request from comment #10 is now outdated.
sandbox-1.2.12 fixes that, marking as a dupe of Bug 101433. Thanks for reporting back. *** This bug has been marked as a duplicate of 101433 ***
*** Bug 102120 has been marked as a duplicate of this bug. ***
*** Bug 103710 has been marked as a duplicate of this bug. ***
*** Bug 128507 has been marked as a duplicate of this bug. ***