trying to emerge app-office/openoffice-3.0.0 after some time of compiling Looking for ooo300-m9-filters.tar.bz2 ... ok Looking for ooo300-m9-testing.tar.bz2 ... ok Looking for ooo300-m9-bootstrap.tar.bz2 ... ok Looking for ooo300-m9-libs_gui.tar.bz2 ... ok Looking for ooo300-m9-libs_core.tar.bz2 ... ok Looking for ooo300-m9-libs_extern.tar.bz2 ... ok Looking for ooo300-m9-libs_extern_sys.tar.bz2 ... ok Looking for ooo300-m9-components.tar.bz2 ... ok Looking for ooo300-m9-postprocess.tar.bz2 ... ok Looking for ooo300-m9-extensions.tar.bz2 ... ok Looking for /var/tmp/portage/app-office/openoffice-3.0.0/distdir/scsolver.2008-10-07.tar.bz2 ... ok Unpacking OO.o build tree - [ go and have some tea ] ... unpacking sdk... tar: ooo300-m9-sdk/autodoc/CVS/Root: Cannot change ownership to uid 1698768, gid 262331: Invalid argument tar: ooo300-m9-sdk/autodoc/CVS/Repository: Cannot change ownership to uid 1698768, gid 262331: Invalid argument tar: ooo300-m9-sdk/autodoc/CVS/Entries: Cannot change ownership to uid 1698768, gid 262331: Invalid argument tar: ooo300-m9-sdk/autodoc/CVS/Template: Cannot change ownership to uid 1698768, gid 262331: Invalid argument tar: ooo300-m9-sdk/autodoc/CVS/Tag: Cannot change ownership to uid 1698768, gid 262331: Invalid argument tar: ooo300-m9-sdk/autodoc/CVS: Cannot change ownership to uid 1698768, gid 262331: Invalid argument tar: ooo300-m9-sdk/autodoc/inc/CVS/Root: Cannot change ownership to uid 1698768, gid 262331: Invalid argument tar: ooo300-m9-sdk/autodoc/inc/CVS/Repository: Cannot change ownership to uid 1698768, gid 262331: Invalid argument Reproducible: Always
Created attachment 170112 [details] build.log
Created attachment 170114 [details] emerge --info
Created attachment 170116 [details] environment
Can't reproduce here. Is there anything special about your system which could interfere with ownership rights? Or do you use a different tar as usual?
(In reply to comment #4) > Can't reproduce here. Is there anything special about your system which could > interfere with ownership rights? Or do you use a different tar as usual? > nothing special. filesystem ACL's and "Security options" are disabled, standard tar app-arch/tar-1.20
I can't reproduce this also in five different machines with amd64 and x86 arches
Sorry, can't help here, definately something in your build setup, nothing we can do here.
FYI, I had someone report similar thing for googlearth in bug 320395. Was fixed by using unpack instead of 'tar xf' where unpack adds the -o (--no-same-owner) option. I dunno however under which conditions not using the parameter results in the bug.
