Bug 154105 - java-1_4_2-gcj-compat: /var/tmp/rpm-tmp.34166: line 16: gcj: command not found
Summary: java-1_4_2-gcj-compat: /var/tmp/rpm-tmp.34166: line 16: gcj: command not found
Status: RESOLVED FIXED
Alias: None
Product: SUSE Linux 10.1
Classification: openSUSE
Component: Java (show other bugs)
Version: Beta 5
Hardware: Other Other
: P5 - None : Minor (vote)
Target Milestone: ---
Assignee: Johannes Meixner
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-02-28 14:18 UTC by Christoph Thiel
Modified: 2006-03-09 12:58 UTC (History)
0 users

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Christoph Thiel 2006-02-28 14:18:12 UTC 
Installation errors on SUSE Linux 10.1-beta5.2:

2006-02-28 09:37:53 java-1_4_2-gcj-compat-1.4.2.0-15.i586.rpm installed ok
Additional rpm output:
/var/tmp/rpm-tmp.34166: line 16: gcj: command not found
/usr/share/java /
/
/usr/lib/jvm-exports/java-1.4.2-gcj-1.4.2.0 /
/
Comment 1 Johannes Meixner 2006-02-28 15:09:23 UTC 
Ah!
One more of the never ending java-1_4_2-gcj-compat mess.

This one is a nice side-effect of bug #151732.
(Of course "Requires" was not sufficient, it should have been "PreReq".)

I will try to use "%triggerin -- gcc-java" instead of %post

Alternatively I may simply replace stuff like
`gcj%{gccsuffix} --version | head -n 1 | awk '{ print $3 }'`
during build with a constant string of our gcj version.

I think %triggerin is much better because it makes it always
automatically correct even when an installed gcc-java would be updated.
Comment 2 Johannes Meixner 2006-03-01 13:04:01 UTC 
Hopefully fixed now.
Submitted java-1_4_2-gcj-compat to STABLE.
Comment 3 Christoph Thiel 2006-03-08 15:34:38 UTC 
Just tested on test build 606 and still got this error with java-1_4_2-gcj-compat-1.4.2.0-17
Comment 4 Johannes Meixner 2006-03-09 08:21:47 UTC 
Is it really the RPM post install stuff and not bug #155729?
Comment 5 Christoph Thiel 2006-03-09 11:08:45 UTC 
The requires has been fixed, but I still get the output of

/usr/share/java /
/
/usr/lib/jvm-exports/java-1.4.2-gcj-1.4.2.0 /
/

which seems a bit strange ;)
Comment 6 Johannes Meixner 2006-03-09 12:33:56 UTC 
I see exactly the same messages when I build it locally:
-------------------------------------------------------------------
Preparing packages for installation...
java-1_4_2-gcj-compat-1.4.2.0-17
/usr/share/java /
/
/usr/lib/jvm-exports/java-1.4.2-gcj-1.4.2.0 /
/
java-1_4_2-gcj-compat-devel-1.4.2.0-17
-------------------------------------------------------------------
... testing for pre/postinstall scripts that break patchrpms
/usr/share/java /
/
/usr/lib/jvm-exports/java-1.4.2-gcj-1.4.2.0 /
/
-------------------------------------------------------------------

There is no error exit code from the postinstall stuff
and Christoph told me that there is also no error popup in YaST.
He found it by manually inspecting YaST's installation log.

=> Only a MINOR bug (perhaps only cosmetical).

I try to find what outputs the messages and add some ">/dev/null"
to get it quiet.
Comment 7 Johannes Meixner 2006-03-09 12:58:08 UTC 
Using "set -x" in postinstall script shows that it is cosmetical:
----------------------------------------------------------------------
+ pushd /usr/share/java/
/usr/share/java /
[...]
+ popd
/
[...]
+ pushd /usr/lib/jvm-exports/java-1.4.2-gcj-1.4.2.0
/usr/lib/jvm-exports/java-1.4.2-gcj-1.4.2.0 /
[...]
+ popd
/
----------------------------------------------------------------------

Added "1>/dev/null" to pushd and popd to get them quiet.
Submitted to STABLE.
Hopefully completely fixed now.