[bug-notifications] [jbig2dec 0003880]: symbolic links in /opt/csw/lib/amd64/ lead nowhere, meaning amd64 libraries not included

[Mantis Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://www.opencsw.org/mantis/view.php?id=3880 
====================================================================== 
Reported By:                flod
Assigned To:                james
====================================================================== 
Project:                    jbig2dec
Issue ID:                   3880
Category:                   packaging
Reproducibility:            always
Severity:                   trivial
Priority:                   normal
Status:                     assigned
====================================================================== 
Date Submitted:             2009-09-04 13:27 CEST
Last Modified:              2009-09-04 14:09 CEST
====================================================================== 
Summary:                    symbolic links in /opt/csw/lib/amd64/ lead nowhere,
meaning amd64 libraries not included
Description: 
The included symbolic links 
/opt/csw/lib/amd64/libjbig2dec.so
/opt/csw/lib/amd64/libjbig2dec.so.0
lead nowhere as 
/opt/csw/lib/amd64/libjbig2dec.so.0.10 
is missing.
====================================================================== 

---------------------------------------------------------------------- 
 (0006664) james (manager) - 2009-09-04 14:09
 http://www.opencsw.org/mantis/view.php?id=3880#c6664 
---------------------------------------------------------------------- 
I can't view but I guess what it's doing.  The only problem might be where
a link is from one package to a file in another.  This can occur when a
file from another package supersedes a file in a package and the package
packs a link and a depend.  Example: CSWbdb4 is a package of links.

I have a package checker and this is one things that gets check.  To over
come the link to another package problem it has to do a virtual install of
the package and its depends.  For general unstable release packages are not
checked as a set.  Only when doing eg stable does the set get checked with
rigour. This takes time.  So the missing part in this case was me be
bothered to run the check... sorry, "current" used to be called "unstable"
for good reason.