On Tue, Jan 03, 2017 at 08:08:32AM -0000, Lukas Slebodnik wrote: > > On Mon, 2017-01-02 at 20:43 -0800, Adam Williamson wrote: > > > > ...but to expand on that, that's for stable releases. So far as Rawhide > > is concerned, historically my understanding has been the same as > > Florian's, we haven't ever claimed that dependencies will be so > > comprehensive that you can just cherry-pick packages and be sure > > everything will work, you have always been expected to do a full system > > update each time for Rawhide. > I use rawhide on many machines and even on my laptop. I know it can break > sometimes and i am fine with that. Because I have a btrfs snapshots of > older working rawhide and I can try to upgrade functional version to > broken version. But in this case i need to "bisect" which upgrade caused > the bug. And every time I am surprised which package cause the bug. > Mostly I suspected a different package. However, if the upgrade of glibc > breaks things due to missing symbols then it is really huge complication > If you cannot upgrade packages with dnf and need to use rpm with URLs from > koji. That's the reason why upgrade of glibc should be treated more > seriously in rawhide. (IMHO) But there is nothing that can be done about it. The symbol versions come from upstream, every release that adds new symbols adds new symbol version, and we do want to test glibc before it is released, we can't just wait until it is released and then push it into the distro, hoping other distros have tested it. Adding a symbol version for each set of symbols added together would be major change for upstream, one that would have severe runtime implications, and also effectively require that as soon as you add something you've done everything right, no further changes to the API are possible. While in the current development model, until glibc is released, there is still time to fix stuff up, remove symbols again (doesn't happen often) etc. Jakub _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
