Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 99078 - log4j-1.2.9; error in ebuild; missing "="; ebuild fail to emerge
Summary: log4j-1.2.9; error in ebuild; missing "="; ebuild fail to emerge
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Unspecified (show other bugs)
Hardware: x86 Linux
: High normal (vote)
Assignee: Java team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-07-15 00:04 UTC by gentoo
Modified: 2005-07-18 05:55 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments
new log4j-1.2.9-ebuild (log4j-1.2.9.ebuild,1.52 KB, text/plain)
2005-07-15 00:22 UTC, gentoo
Details
changed Manifest for log4j-1.2.9.ebuild (Manifest,468 bytes, text/plain)
2005-07-15 00:22 UTC, gentoo
Details

Note You need to log in before you can comment on or make changes to this bug.
Description gentoo 2005-07-15 00:04:13 UTC
While emergin log4j-1.2.9, the following error occurs: 
 
>>> Source unpacked. 
Missing value for property 
activation.jar/usr/share/sun-jaf-bin/lib/activation.jar 
 
!!! ERROR: dev-java/log4j-1.2.9 failed. 

Reproducible: Always
Steps to Reproduce:
1. emerge log4j 
2. 
3. 
 



Solution: 
In dev-java/log4j/log4j-1.2.9.ebuild at line 36 is a "="-sign missed: 
 
wrong: 
use javamail && antflas[...]-Dactivation$(java-pkg_getjar sun-jaf-bin 
activation.jar) 
 
must be: 
use javamail && antflas[...]-Dactivation=$(java-pkg_getjar sun-jaf-bin 
activation.jar) 
 
"=" is after "-Dactivation"
Comment 1 gentoo 2005-07-15 00:22:16 UTC
Created attachment 63444 [details]
new log4j-1.2.9-ebuild
Comment 2 gentoo 2005-07-15 00:22:56 UTC
Created attachment 63445 [details]
changed Manifest for log4j-1.2.9.ebuild
Comment 3 gentoo 2005-07-15 00:24:51 UTC
Solution is printed in the Bug-Info; additional files were added, which contain 
the right code 
Comment 4 Jakub Moc (RETIRED) gentoo-dev 2005-07-15 00:29:16 UTC
Please, don't close bugs that have not been fixed in portage tree, fixing the
problem for yourself is really not enough. This bug has not been even assigned
yet - how do you suppose that maintainer will get notified about the problem?
Comment 5 Thomas Matthijs (RETIRED) gentoo-dev 2005-07-15 02:58:17 UTC
Fixed
Comment 6 gentoo 2005-07-18 05:42:11 UTC
One additional comment: 
Is there a guideline to "writing a bug report"? If it is, please let me know, 
where. If it is not, maybe it's possible/better to not allow someone new to the 
system as me to mark a bug as fixed. - How do you suppose should one (I) know, 
which steps are intended? (just for thinking about it ;-) ) 
Comment 7 Thomas Matthijs (RETIRED) gentoo-dev 2005-07-18 05:55:19 UTC
all i know is this doc
http://www.gentoo.org/doc/en/bugzilla-howto.xml
which may or may not contain usefull information(didn't read it)
chapter 6 + 7 look like they could be usefull to new people