On Mon, Mar 06, 2017 at 01:27:14PM -0000, Sebastian Marsching wrote: > I guess there is only one case where the current "fix" would help. If > someone had some library providing libungif in a different place, the > broken symlinks in /usr/lib might take precedence, thus hiding the > correct files.
Do we know if anyone has reported this case? > In my opinion, removing the dangling symlinks is a slight improvement on > the current situation and the risk of breaking something is very low. On > the hand, I do not know whethere there are other considerations > regarding a SRU in addition to the potential for regressions (which is > low in this case). The risk may be low but it is non-zero. If we don't know of any user impacted, I don't think there is any justification for an SRU. > Sure, it's low priority but the fix isn't wrong. Sure, but that's something for the development release. In the stable release, I think we need a better reason (such as non-hypothetical affected users). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to giflib in Ubuntu. https://bugs.launchpad.net/bugs/1337898 Title: Invalid symlinks for libungif.so and libungif.a Status in giflib package in Ubuntu: Fix Released Status in giflib source package in Trusty: Fix Committed Status in giflib package in Debian: Unknown Bug description: Impact ====== Linking programs that need libungif ("-lungif") will fail. Test Case ========= apt-get install build-essential libgif-dev cat >>test.c EOF int main(int argc, char **argv) { return 0; } EOF gcc -lungif test.c GCC will fail with "/usr/bin/ld: cannot find -lungif" on affected systems. Regression Potential ==================== None, just removing some dangling symlinks that couldn't work any way. Original Bug Report =================== In Ubuntu 14.04 LTS on x86_64 I am experiencing the following bug in libgif-dev 4.1.6-11: Symbol links for libungif.a, libungif.la, and libungif.so are created in /usr/lib that point to libgif.a, libgif.la and libgif.so.4.1.6 respectively. However, these files are not in /usr/lib but in /usr/lib/x86_64-linux-gnu. Therefore, the symbol links are invalid. I suggest fixing this by placing the symbol links in the same directory as the target files. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/giflib/+bug/1337898/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
