Hi, I forgot to mention: Right before sending the below mail: I did do a fsck.reier4 --fix. It found some stuff, fixed it, told me everything is fine now with the FS, thenn I tried again: same problem! (I also double checked the FS permissions.) dmesg did NOT show anything, the build log did NOT show anything (turned on all debug available) (and the emerge went actually through fine, just the file was 0 bytes ;) --> That's why it took me so long to figure out that it's actually my FS ;) I have a emerge.log with the JAVA_PKG_DEBUG=1: http://tormen.pastebin.com/AEkDdQ1n emerge --info: http://tormen.pastebin.com/EfZe3afK About the reproducibility: It was reproducible yesterday all day and night :) ... Unfortunately I was tired and fed-up and wanted to move on --> I rsynced the content, reformatted the partition with ext4... I will nevertheless try to restore the the original setup ... again this evening. Sorry about that. I should have waited at least for a response from you... :( Best, Knuth On 26/08/10 04:07, Jonáš Vidra wrote: > On Thu, 26 Aug 2010 03:00:47 +0200 K. Posern <quickhelp@xxxxxxxxx> wrote: > >> Hi, > > Hello! > > >> How can I further investigate? >> And/Or >> What other informations would you need to further track down the problem? > > Try running fsck.reiser4, that might help. Knowing your plugin profile > would be good as well. > > Is the bug reproducible? I can't reproduce it here, could you send me your > emerge --info and build logs? > > >> >> Thanks for any advise! >> >> Best, >> >> Knuth >> > >
Attachment:
smime.p7s
Description: S/MIME Cryptographic Signature
