Bug 5479 - 2_b3: Numerous dangling links from java openjdk package(s)
Summary: 2_b3: Numerous dangling links from java openjdk package(s)
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-04-19 03:23 CEST by Bit Twister
Modified: 2012-04-21 01:46 CEST (History)
1 user (show)

See Also:
Source RPM: java-1.*.0-openjdk
CVE:
Status comment:

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

Description Bit Twister 2012-04-19 03:23:37 CEST 
Description of problem:
Numerous dangling links from java openjdk package(s). No idea if from
java-1.6.0-openjdk-1.6.0.0-31.b24.1.mga2.src.rpm or java-1.7.0-openjdk-1.7.0.1-2.0.4.mga2.src.rpm

Following are dangling links:
/usr/share/man/man1/java.1.gz 
/usr/share/man/man1/keytool.1.gz 
/usr/share/man/man1/orbd.1.gz 
/usr/share/man/man1/pack200.1.gz 
/usr/share/man/man1/rmid.1.gz 
/usr/share/man/man1/rmiregistry.1.gz 
/usr/share/man/man1/servertool.1.gz 
/usr/share/man/man1/tnameserv.1.gz 
/usr/share/man/man1/unpack200.1.gz 
Version-Release number of selected component (if applicable):


How reproducible: Always


Steps to Reproduce:
1. clean install with runlevel 3 as default
2. Select Custom in DESKTOP SELECTION screen
3. in the PACKAGE GROUP SELECTION screen
   select all groups except LSB, LXDE and Other Graphical Desktops
4. In the SUMMARY screen, pick Graphical Interface 
   and set runlevel 3 as default
5. After reboot, as root, urpme --auto-orphans, apply all updates,
    reboot, urpme --auto-orphans
6. as user, startx
7. click up a terminal (I use xterm)
8. su - root
9. symlinks -r / | grep dangling
Manuel Hiebel 2012-04-19 09:09:48 CEST

CC: (none) => dmorganec
Source RPM: (none) => java-1.*.0-openjdk

Comment 1 Bit Twister 2012-04-21 01:46:14 CEST 
clean install + updates. Dangles not there.

Status: NEW => RESOLVED
Resolution: (none) => FIXED
Note You need to log in before you can comment on or make changes to this bug.