JDK-6717770 : warning message shows during linux 32bit rpm bundle installation
  • Type: Bug
  • Component: install
  • Sub-Component: install
  • Affected Version: 1.4.2_18-rev
  • Priority: P3
  • Status: Closed
  • Resolution: Fixed
  • OS: linux_suse_sles_9
  • CPU: x86
  • Submitted: 2008-06-23
  • Updated: 2010-04-04
  • Resolved: 2010-01-27
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
Other Other
1.3.1_24Fixed 1.4.2_19 b02Fixed
Related Reports
Relates :  
Description
When installing j2sdkfb-1_4_2_18-rev-b07-linux-i586.rpm using the rpm command, the warning 
"user java_re does not exist - using root" is displayed.
Verified fixed in 1.4.2_19b02

Comments
EVALUATION Problem (warning msg) started seen from 1.4.2_17-rev-b13. 1.4.2_18-fcs j4b bundle also has the same warning msg. It was introduced during build m/c change for J4B. No issue with the functionality of the bundle. # By default, /bin/rpm generates a .rpm files which contains files owned # by the builder (in Javasoft's case, the user 'java_re'). When # the .rpm is installed, /bin/rpm tries to set file ownership based on # ownership within the .rpm bundle. If the original file owner does not # exist on the install system, then warnings like: # "user java_re does not exist - using root" # are generated for each installed file. The install works, but many # messages are displayed. We have chosen to force the /bin/rpm executable # to setuid of all rpm bundle files, and the .rpm file itself, to 'root'. # We do this by modifying the /bin/rpm executable in the following as # 'root': # chmod 4755 /bin/rpm .
24-06-2008