On 05/19/2010 04:20 AM, Adam Williamson wrote: > On Wed, 2010-05-19 at 00:24 +0200, Kevin Kofler wrote: > >> Yes, the broken decision was to enable updates-testing by default for >> prereleases and we should never do this again. It just can't work, because >> updates-testing is like the Red Pill: once you're on it, you can't get off >> anymore. The fedora-release update which disabled updates-testing broke many >> user setups, suddenly unable to install packages due to dependencies. >> > Pre-release users, you mean. Who ought to be ready to deal with this > sort of thing, or else they shouldn't be installing pre-releases. Full > refunds available, etc. I'm not horribly bothered about it, really, now > we know it happens and can spot the symptoms. > While I understand the decision behind enabling updates-testing repo by default, I think it should be turned off much earlier, perhaps during the beta release phase. Due to the workflow I follow, one of the problems of having it enabled by default till very late in the release cycle is that once I get the update running on my system, I sometimes forgot to push the update from updates-testing to updates repo for some of the packages I maintain. That was partially the reason why a major deja-dup update didn't go in sooner. Rahul -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
