Summary: | dev-java/log4j-1.2.9; invalid tarball | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Karol Krizka <kkrizka> |
Component: | New packages | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | RESOLVED NEEDINFO | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Karol Krizka
2005-07-11 20:19:31 UTC
(In reply to comment #0) > >>> Unpacking source... > >>> Unpacking logging-log4j-1.2.9.tar.gz to /var/tmp/portage/log4j-1.2.9/work > tar: A lone zero block at 17639 This happens with many tarballs yet they are not invalid. What happends if you try to unpack it manually? No it's not the tarball. I just noticed it succeded after that. The error was in the failed message: aoxx failed openjam or something like that. I disabled all the flags and it worked. There were no further error messages. |