dev-java/jaxen-1.1.4 was updated ealier today {Oct 14} fails attempting to create what I believe is a suspicious or at least incorrectly located directory. # emerge jaxen Calculating dependencies... done! >>> Verifying ebuild manifests >>> Emerging (1 of 1) dev-java/jaxen-1.1.4 >>> Jobs: 0 of 1 complete, 1 running Load avg: 4.53, 3.97, 3.35 (null)*(null) (null)ACCESS DENIED(null): mkdir: /root/.maven (null)*(null) (null)ACCESS DENIED(null): mkdir: /root/.maven (null)*(null) (null)ACCESS DENIED(null): mkdir: /root/.maven (null)*(null) (null)ACCESS DENIED(null): mkdir: /root/.maven >>> Failed to emerge dev-java/jaxen-1.1.4, Log file: >>> '/var/tmp/portage/dev-java/jaxen-1.1.4/temp/build.log' >>> Jobs: 0 of 1 complete, 1 failed Load avg: 4.57, 3.99, 3.36 * Package: dev-java/jaxen-1.1.4 * Repository: gentoo * Maintainer: java@gentoo.org * USE: amd64 elibc_glibc kernel_linux userland_GNU * FEATURES: preserve-libs sandbox * Using: icedtea-bin-6 >>> Unpacking source... >>> Unpacking jaxen-1.1.4-src.tar.gz to /var/tmp/portage/dev-java/jaxen-1.1.4/work >>> Source unpacked in /var/tmp/portage/dev-java/jaxen-1.1.4/work >>> Preparing source in /var/tmp/portage/dev-java/jaxen-1.1.4/work/jaxen-1.1.4 ... ‘/usr/portage/dev-java/jaxen/files/jaxen-1.1.4_maven1-build.xml’ -> ‘build.xml’ >>> Source prepared. >>> Configuring source in /var/tmp/portage/dev-java/jaxen-1.1.4/work/jaxen-1.1.4 ... Rewriting attributes Rewriting ./build.xml >>> Source configured. >>> Compiling source in /var/tmp/portage/dev-java/jaxen-1.1.4/work/jaxen-1.1.4 ... * Disabling all optional ANT_TASKS Buildfile: /var/tmp/portage/dev-java/jaxen-1.1.4/work/jaxen-1.1.4/build.xml get-deps: compile: [mkdir] Created dir: /var/tmp/portage/dev-java/jaxen-1.1.4/work/jaxen-1.1.4/target/classes [javac] Compiling 197 source files to /var/tmp/portage/dev-java/jaxen-1.1.4/work/jaxen-1.1.4/target/classes init: BUILD FAILED /var/tmp/portage/dev-java/jaxen-1.1.4/work/jaxen-1.1.4/build.xml:29: Directory /root/.maven/repository creation was not successful for an unknown reason Total time: 9 seconds * ERROR: dev-java/jaxen-1.1.4 failed (compile phase): * eant failed
See version bump bug #426384.
(In reply to comment #1) > See version bump bug #426384. I don't understand why you've linked to that bug thread? That is a request to bump the jaxen version in the tree, which has now been done. The build error the OP is having with the newly included ebuild isn't mentioned in that thread. I too am suffering from the same build error as the OP on my ~amd64 laptop. Reading the mentioned bug report does nothing to help me resolve this build error. Please enlighten me (us) as to what I'm (we're) missing or how that thread helps to resolve this. TIA
(In reply to comment #2) > (In reply to comment #1) > > See version bump bug #426384. > > I don't understand why you've linked to that bug thread? That is a request > to bump the jaxen version in the tree, which has now been done. The build > error the OP is having with the newly included ebuild isn't mentioned in > that thread. > > I too am suffering from the same build error as the OP on my ~amd64 laptop. > Reading the mentioned bug report does nothing to help me resolve this build > error. > > Please enlighten me (us) as to what I'm (we're) missing or how that thread > helps to resolve this. TIA This broken build wasn't available until today. The version bump is what made the build available. This is why the version bump was referenced. If you're performing a world update and encountering this problem, you should mask this version. i.e.: echo "=dev-java/jaxen-1.1.4" >> /etc/portage/package.mask As far as I know, there is no package out there that requires 1.1.4. All the packages I have which require jaxen are happy with 1.1.1. YMMV and all that.
(In reply to comment #2) > > Please enlighten me (us) as to what I'm (we're) missing or how that thread > helps to resolve this. TIA Also - the problem reported here is extremely unusual. No package is ever supposed to attempt to create a hidden work directory under /root as thjs bug report plainly shows. Hence the bug report and the added emphasis on including a reference to the version bump.
Because the build borks for attempting to write a work directory under /root, I've raise the importance level.
same here (~amd64)
Doesn't look malicious, looks screwed up though, why is this still in the tree? I could patch out build.xml in 1.1.4 to dodge around this issue, but who knows what else is broken. Seems they messed up quite a bit in the shift from CVS to subversion. Just run a diff of the build.xml from 1.1.1 to 1.1.4 and you'll see what I mean.
Fixed in CVS, thanks for the report. 15 Oct 2012; Ralph Sennhauser <sera@gentoo.org> files/jaxen-1.1.4_maven1-build.xml: Don't create maven download dir in HOME. Fixes sandbox violation if it not already exists. #438400 PS: the build.xml looks that way as it was generated from a pom.xml, for 1.1.1 this wasn't necessary. Also it's doesn't try to access /root specifically but the build users HOME.
*** Bug 438524 has been marked as a duplicate of this bug. ***