Am 22.06.2012 14:45, schrieb Sam Varshavchik: >> Well, yeah. But the Law of unintended consequences applies and that is why i cried out loud that the UsrMove has zero benfits in the real world and crying for troubles long ago before F17 was GA >> so we must be careful FESCo should HAVE BEEN and should be more careful by approve "features" >> I don't think that people expected symlinking >> /usr/bin to /bin to be risky either nobody linked /usr/bin to /bin the opposite happended [harry@srv-rhsoft:~]$ stat /bin Datei: „/bin“ -> „usr/bin“ > Errr… Wait. Then UsrMove script that ran when I upgraded F16 to F17 symlinked /bin → usr/bin > > If new F17 installs have /usr/bin → /bin, then this is an even bigger clusterfrak. If that's the case, bash should > be left alone, as doing that is going to break all the new installs. they do not the problems we now have are the usual ones the new features was not implemneted carefully because nobody knows how often absolute paths were used all over the years in SPEC-files, patches, sources and the UsrMove was done not careful enough upgrade survived and now we will see problem after problem becasue things containing one time /usr/bin and one time /bin and the result of yum update sis simplay RANDOM and LUCK i noticed this TWO times wit the same package combination samba / glibc you could update both with each koji-version alone but you ran in trouble update them both at the same time https://bugzilla.redhat.com/show_bug.cgi?id=834209 https://bugzilla.redhat.com/show_bug.cgi?id=829197 the reason for this problem is simply that /usr/sbin/ldconfig in samba-packages is simp,ly correct after UsrMove and glibc still provies /sbin/ldconfig which is a MAJOR BUG looking how a critical thing glibc is for not dealing correct with UsrMove
Attachment:
signature.asc
Description: OpenPGP digital signature
-- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
