Emerging commons-net fails after trying to untar the tar.gz file.
Steps to Reproduce:
tar: A lone zero block at 3060
!!! ERROR: Package jakarta-oro-2.0 was not found!
!!! ERROR: dev-java/commons-net-1.4.1-r1 failed.
ebuild.sh, line 1637: Called dyn_unpack
ebuild.sh, line 763: Called qa_call 'src_unpack'
ebuild.sh, line 44: Called src_unpack
commons-net-1.4.1-r1.ebuild, line 32: Called java-pkg_jar-from 'jakarta-oro-2.0' 'jakarta-oro.jar' 'oro.jar'
java-utils-2.eclass, line 876: Called die
!!! There was a problem getting the classpath for jakarta-oro-2.0.
!!! If you need support, post the topmost build error, and the call stack if relevant.
!!! A complete build log is located at '/var/tmp/portage/dev-java/commons-net-1.4.1-r1/temp/build.log'.
!!! When you file a bug report, please include the following information:
GENTOO_VM=sun-jdk-1.5 CLASSPATH="" JAVA_HOME="/opt/sun-jdk-1.5.0.08"
JAVACFLAGS="-source 1.3 -target 1.3" COMPILER=""
and of course, the output of emerge --info
The ebuild should have completed successfully.
Portage 2.1.3_rc5 (default-linux/amd64/2006.1, gcc-3.4.6, glibc-2.5-r0, 2.6.20-gentoo-r2 x86_64)
System uname: 2.6.20-gentoo-r2 x86_64 AMD Athlon(tm) 64 Processor 3500+
Gentoo Base System version 1.12.6
Timestamp of tree: Fri, 29 Jun 2007 02:00:01 +0000
ccache version 2.3 [disabled]
dev-java/java-config: 1.3.7, 2.0.33
dev-lang/python: 2.3.6, 2.4.4
sys-devel/autoconf: 2.13, 2.60
sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2, 1.10
CONFIG_PROTECT="/etc /usr/kde/3.4/env /usr/kde/3.4/share/config /usr/kde/3.4/shutdown /usr/kde/3.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/share/X11/xkb /usr/share/config"
CONFIG_PROTECT_MASK="/etc/env.d /etc/env.d/java/ /etc/gconf /etc/java-config/vms/ /etc/revdep-rebuild /etc/terminfo /etc/texmf/web2c"
FEATURES="distlocks metadata-transfer sfperms strict unmerge-orphans"
PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --delete-after --stats --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages --filter=H_**/files/digest-*"
USE="X a52 aac alsa amd64 apache2 arts asf audiofile avi bash-completion berkdb bitmap-fonts bzip2 cdr cli cracklib crypt css cups curl cvs cxx doc dri dts dv dvd dvdr dvdread encode examples expat fast flac fortran gdbm gimp glx gnome gpm graphviz iconv ieee1394 imagemagick info ipod ipv6 isdnlog jpeg kde ldap libg++ live logitech-mouse mad midi mikmod mng mp3 mp3rtp mpe mpeg mudflap nas ncurses nls nptl nptlonly ogg oggvorbis openal opengl openmp pam pcre pda pdf perl php plib png postgres ppds pppd python qt quicktime readline reflection scanner session snmp spl ssl tcl tcltk tcpd theora threads tiff truetype truetype-fonts type1-fonts unicode usb vcd visualization vorbis xamin xlib xml xml2 xorg xrandr xv zlib" ALSA_CARDS="ali5451 als4000 atiixp atiixp-modem bt87x ca0106 cmipci emu10k1x ens1370 ens1371 es1938 es1968 fm801 hda-intel intel8x0 intel8x0m maestro3 trident usb-audio via82xx via82xx-modem ymfpci" ALSA_PCM_PLUGINS="adpcm alaw asym copy dmix dshare dsnoop empty extplug file hooks iec958 ioplug ladspa lfloat linear meter mulaw multi null plug rate route share shm softvol" ELIBC="glibc" INPUT_DEVICES="keyboard mouse" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" USERLAND="GNU" VIDEO_CARDS="nvidia"
Unset: CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LANG, LC_ALL, LDFLAGS, LINGUAS, MAKEOPTS, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS
(In reply to comment #0)
> Actual Results:
> tar: A lone zero block at 3060
> !!! ERROR: Package jakarta-oro-2.0 was not found!
This is saying that you don't have jakarta-oro-2.0 installed but:
elgeuse@pena ~ $ qdepends -d dev-java/commons-net
dev-java/commons-net-1.4.1-r1: >=virtual/jdk-1.3 >=dev-java/ant-core-1.5.4 >=dev-java/jakarta-oro-2.0 >=dev-java/java-config-2.0.31 >=sys-apps/portage-18.104.22.168 >=dev-java/javatoolkit-0.2.0-r1 >=sys-apps/portage-22.214.171.124 dev-java/ant-core
it is dependent on just fine. Please attach the output of
emerge -pv commons-net
emerge -pv jakarta-oro
> !!! When you file a bug report, please include the following information:
> GENTOO_VM=sun-jdk-1.5 CLASSPATH="" JAVA_HOME="/opt/sun-jdk-1.5.0.08"
> JAVACFLAGS="-source 1.3 -target 1.3" COMPILER=""
> and of course, the output of emerge --info
Your sun-jdk is at least very much out of date:
(1.5) 126.96.36.199 (~)188.8.131.52-r1 (~)184.108.40.206
Do you use emerge -uD world to update?
Any it pulls in jakarta-oro in just fine here:
pena commons-net # emerge -pv commons-net
These are the packages that would be merged, in order:
[ebuild N ] dev-java/jakarta-oro-2.0.8-r2 USE="-doc -examples -source" 338 kB
[ebuild R ] dev-java/commons-net-1.4.1-r1 USE="-doc -examples -source" 0 kB
please reope with info on what I asked
betelgeuse@pena /usr/portage/profiles $ grep jakarta-oro -r .
./updates/2Q-2005:move dev-java/oro dev-java/jakarta-oro
Hmm maybe you still have oro installed. So please post the output of
qlist jakarta-oro before doing anything else.
(In reply to comment #2)
> betelgeuse@pena /usr/portage/profiles $ grep jakarta-oro -r .
> ./updates/2Q-2005:move dev-java/oro dev-java/jakarta-oro
> Hmm maybe you still have oro installed. So please post the output of
> qlist jakarta-oro before doing anything else.
You hit it right on the head. The output of qlist list showed some oro related files. The dependencies for commons-net did not include jakarta-oro, but emerging jakarta-oro separately seems to have resolved this bug. Thank you all for your help on this matter.
(In reply to comment #3)
> You hit it right on the head. The output of qlist list showed some oro related
> files. The dependencies for commons-net did not include jakarta-oro, but
> emerging jakarta-oro separately seems to have resolved this bug. Thank you all
> for your help on this matter.
jakarta-oro did not show up in the list because you had it installed. It's just that package moves were used in not the best way. They should only be used when you don't need to change the installed files (which is almost never the case of java packages) or can easily force people to update. I recommend running emerge -uD world to update in the future. If you don't you might bump into some other old artifacts like this.
Don't you think that doing an emerge world (and the hours that it would take) is a bit overkill to upgrade a single piece of software that, obviously, is rarely, if ever used? It seems to me that a better solution would have been to block on jakarta-oro, if the old oro is installed. Perhaps display some output on the emerge of that package to give the user a clue as to the solution. That seems like a more "gentooish" way of doing things. Just my $0.02.
The package move made the block quite impossible. Also, the block would not be processed at all without --deep. The only solution I see is upgrade all =dev-java/jakarta-oro-2.0* deps in the tree to >=dev-java/jakarta-oro-2.0.8-r2. But I don't think it's not worth it, and we can spend time more usefully.
After all, upgrading your system frequently is also more "gentooish" than just one package after two years...
(In reply to comment #5)
> Don't you think that doing an emerge world (and the hours that it would take)
> is a bit overkill to upgrade a single piece of software that, obviously, is
> rarely, if ever used? It seems to me that a better solution would have been to
> block on jakarta-oro, if the old oro is installed.
Please consider that we developers might sometimes actually know what we are doing. You might want to read up on what package moves do... No-one can't have had oro installed since mid 2005. jakarta-oro with oro files sure but not oro in the vdb sense. As I said earlier if you don't use emerge --deep while updating you will be hitting other problems too.