Description of problem:
When I do a # yum -y update I get a lot of messages like the following sample below throughout the entire update
Cleanup : selinux-policy-3.8.8-20.fc14.noarch 50/52
/sbin/ldconfig: /usr/lib64/libbigloomail_es-3.4a.so is not a symbolic link
/sbin/ldconfig: /usr/lib64/libbigloogstreamer_es-3.4a.so is not a symbolic link
/sbin/ldconfig: /usr/lib64/libbigloopkgcomp_es-3.4a.so is not a symbolic link
/sbin/ldconfig: /usr/lib64/libbigloocrypto_es-3.4a.so is not a symbolic link
/sbin/ldconfig: /usr/lib64/libbigloopthread_es-3.4a.so is not a symbolic link
/sbin/ldconfig: /usr/lib64/libbigloopackrat_es-3.4a.so is not a symbolic link
/sbin/ldconfig: /usr/lib64/libbigloopkglib_es-3.4a.so is not a symbolic link
/sbin/ldconfig: /usr/lib64/libbiglootext_es-3.4a.so is not a symbolic link
/sbin/ldconfig: /usr/lib64/libbigloocalendar_es-3.4a.so is not a symbolic link
/sbin/ldconfig: /usr/lib64/libbiglooweb_es-3.4a.so is not a symbolic link
/sbin/ldconfig: /usr/lib64/libbigloomultimedia_es-3.4a.so is not a symbolic link
/sbin/ldconfig: /usr/lib64/libbigloofthread_es-3.4a.so is not a symbolic link
/sbin/ldconfig: /usr/lib64/libbigloosqlite_es-3.4a.so is not a symbolic link
/sbin/ldconfig: /usr/lib64/libbigloosrfi1_es-3.4a.so is not a symbolic link
Cleanup : 6:kdelibs-common-4.5.0-2.fc14.x86_64 51/52
Cleanup : oxygen-icon-theme-4.5.0-1.fc14.noarch 52/52
Something in the bigloo pkg seems to be wrong.
I see the same thing. Whenever a library is installed and ldconfig is run, the error messages occur. Also on F14.
bigloo has never versioned their shared libraries, but until recently it seems like ldconfig is just silent about it. We might have to fix it ourselves and send upstream the patch.
Incidentally, I just looked to see other distributions' packaging of Bigloo and, to my surprise, it got yanked from Debian/Ubuntu after the 2.8 release!
Was there a reason it got yanked? Mostly I'm wondering if there were security issues. But it would be interesting if they thought it was now redundant, or obsolete, or no longer met licensing requirements. Or perhaps it was just lack of interest.
It looks like Debian automatically remove a package from testing if it is FTBFS and nobody fixes it (much like we do the same, but only every release cycle, whereas testing is a rolling "distribution").
In this case, it's a pity; the bug seems quite trivial (if they could not fix the Java modules you can always turn it off!)
There's not that many Scheme compilers that can generate native code, and Scheme2JS, that I maintain, uses Bigloo, so I certainly hope they're not redundant. I'd suppose it's lack of interest.
Thank you for the clarification.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
*** Bug 664116 has been marked as a duplicate of this bug. ***
bigloo-3.6a-1.fc14 has been submitted as an update for Fedora 14.
bigloo-3.6a-1.fc15 has been submitted as an update for Fedora 15.
The release in updates testing fixes this on F14 x86_64. The messages no longer appear during updates of libraries.
bigloo-3.6a-1.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report.
I still get the message I included in the original report when I install new libraries.
After comment 13, I watched an update on F14 x86_64 with bigloo-3.6a-1.fc14 installed, and there were no messages.
What Fedora version are you running, Pablo? And what version of bigloo?
bigloo-3.6a-1.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report.