Sorry - I've been offline for a bit. Thanks Deepu & others. I think the dangling symlink problem is now in the right place & will probably get some attention by at least being brought up & thought about. I'm sure the Kernel people will deal with it when they can & they will be moved to the -devel package appropriately. Cheers johnd Deepu K S <deepuks86@xxxxxxxxx> wrote: On Thu, Apr 23, 2015 at 8:10 PM, Ralf Corsepius <rc040203@xxxxxxxxxx> wrote: > >> On 04/23/2015 02:35 PM, Dominik 'Rathann' Mierzejewski wrote: >> >>> On Thursday, 23 April 2015 at 06:51, John Dodson wrote: >>> >> >> Are there any other packages that create broken symlinks but don't have >>> them listed in their %files sections? That would be against the current >>> packaging guidelines. >>> >> Plenty. >> >> Many systemd packages and packages using alternatives are amongst them: >> # rpm -qf /etc/systemd/system/* >> # rpm -qf /etc/alternatives/* >> >> I guess, there are many more. >> >> >Yes, check for dangling links gives long output. ># symlinks -r / | grep -i dangling > >Listing a few below; >======================== >dangling: /usr/lib/gcc/x86_64-redhat-linux/4.8.3/32/libasan.a -> >../../../i686-redhat-linux/4.8.3/libasan.a >dangling: /usr/lib/gcc/x86_64-redhat-linux/4.8.3/32/libatomic.a -> >../../../i686-redhat-linux/4.8.3/libatomic.a >dangling: /usr/lib/gcc/x86_64-redhat-linux/4.8.3/32/libgcc_s.so -> >/lib/libgcc_s.so.1 >dangling: /usr/lib/gcc/x86_64-redhat-linux/4.8.3/32/libgomp.so -> >../../../../libgomp.so.1.0.0 >dangling: /usr/lib/gcc/x86_64-redhat-linux/4.8.3/32/libitm.a -> >../../../i686-redhat-linux/4.8.3/libitm.a >dangling: /usr/lib/gcc/x86_64-redhat-linux/4.8.3/32/libmudflap.a -> >../../../i686-redhat-linux/4.8.3/libmudflap.a >dangling: /usr/lib/gcc/x86_64-redhat-linux/4.8.3/32/libmudflapth.a -> >../../../i686-redhat-linux/4.8.3/libmudflapth.a >dangling: /usr/lib/gcc/x86_64-redhat-linux/4.8.3/32/libquadmath.a -> >../../../i686-redhat-linux/4.8.3/libquadmath.a >dangling: /usr/lib/gcc/x86_64-redhat-linux/4.8.3/32/libstdc++.a -> >../../../i686-redhat-linux/4.8.3/libstdc++.a >dangling: /usr/lib/gcc/x86_64-redhat-linux/4.8.3/32/libstdc++.so -> >../../../../libstdc++.so.6.0.19 >dangling: /usr/lib/gcc/x86_64-redhat-linux/4.8.3/32/libsupc++.a -> >../../../i686-redhat-linux/4.8.3/libsupc++.a >dangling: /usr/lib/modules/3.19.4-100.fc20.x86_64/build -> >/usr/src/kernels/3.19.4-100.fc20.x86_64 >dangling: /usr/lib/modules/3.19.4-100.fc20.x86_64/source -> build >========================= > >In above, the symlink is in gcc package, but the file comes with static >library package. (for eg: libatomic-static.i686) > >-deepuks > > >Ralf >> >> >> -- >> packaging mailing list >> packaging@xxxxxxxxxxxxxxxxxxxxxxx >> https://admin.fedoraproject.org/mailman/listinfo/packaging >> -- packaging mailing list packaging@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/packaging
