Hi, when i attempt to run emerge -pu world after an emerge rsync, i get the following: bash-2.05a# emerge -pu world These are the packages that I would merge, in order. Calculating world dependencies |portage: aux_get(): error processing DEPEND for dev-perl/MIME-Base64-2.12-r1; exiting. I included an strace -o dump.log emerge -pu world to help you find this bug. I could just file the ebuild as well, but that seems unnecessary to me right now. However i fail to see, why this ebuild should work, since it doesn't have any compile() or install() methods included. Perhaps this ebuild should be masked/removed? portage 2.0.36 gcc 2.95.3-r7 CHOST="i686-pc-linux-gnu" CFLAGS="-march=i686 -O3 -pipe" CXXFLAGS="-march=i686 -O3 -pipe"
Created attachment 3893 [details] strace log of the emerge -pu world process
Actually, this looks like a problem with a package that is depending on MIME-64, not on the MIME-64 ebuild itself (though just to be safe I just rsynch'd and re-emerged it on all my machines). Will see if I can track down which ebuild has the errant depend line.
This ebuild does not have any built in depends. It works because it utilizes the perl modules eclass, which handles the generic functions for setting up, compiling, and installing the module, leaving the ebuild to handle the specifics, if there are any.
Which version of portage are you currently running?
This isn't a blocker...
talk to us, jochem, we need info!
Micheal, this info was already posted the first time, but here it is: used to be portage 2.0.36, i currently use 2.0.37 and the problem still exists for emerge -pu world gcc 2.95.3-r7 CHOST="i686-pc-linux-gnu" CFLAGS="-march=i686 -O3 -pipe" CXXFLAGS="-march=i686 -O3 -pipe"
okay, I've run into this myself: running emerge -pu world as user give aux_get for all ebuilds that dont have cache entries in portage, and the user is unable to write those for some reason. run emerge -pu world as root and it will work, after that the user can also do emerge -pu world and it still works. why though? no idea. perhaps assigning this to daniel is a good idea
To Spider: I believe this is another issue, most likely related to Bug 7719...
See if the related package /var/cache/edb/dep/ entry is empty or not. I found this problem on bash and just deleted the empty /var/cache/edb/dep/ entry and I could emerge bash again to regerate the entry and since then has worked fine. I don't know if there is an easer way of regenerating that entry or not...
Thanks Henti, your post helped me to work around my problem. For those who also have the same problem(s), here's what i did: /* to check if it's empty inside */ less /var/cache/edb/dep/dev-perl/MIME-Base64-2.12-r1 /* to see what kind of info it should have inside */ less /var/cache/edb/dep/dev-perl/$other-package$ /* become root, remove the package and emerge bash */ su - rm /var/cache/edb/dep/dev-perl/MIME-Base64-2.12-r1 emerge bash emerge -pu world /** * NOTE: emerge -pu world, will still give the aux_get() error when you're * a non-root user and haven't run emerge -pu world as root after emerging bash. * However the emerge process will continue and just list the files. The error * will disappear for the non-root user, when the root user has run * emerge -pu world. */
Hi Jochem I think you missunderstood a section. I had to emerge bash because my bash with giving the problem. if it worked for you ... I'm not sure why ... it should not have from what I uderstood the problem to be. you should have emerged dev- perl/MIME-Base64 after deleting the /var/ entry that was empty. A note for portage/ebuild developers ... maybe having error on file parsing would help ? Henti
