On Thu, 5 Dec 2013, Richard Biener wrote:
On Thu, 5 Dec 2013, Ludwig Nussel wrote:
Sascha Peilicke wrote:
On Monday 02 December 2013 16:17:26 Stephan Kulow wrote:
The fun part about rolling release you can decide yourself when to jump on it. There is no reason to update daily.
Quite frankly, I consider this still the best option to have a stable Factory. It's brain-dead simple and may just require a little social interaction:
0) If you are not subscribed to opensuse-factory@ (and probably packaging / buildservice), you should not run Factory.
1) So check opensuse-factory@ for issues regularly. If there was a mail two weeks ago about udev (random choice of mine) being heavily broken and no fix was pushed meanwhile, it may be a good hint to not update today :-)
Coming back from vacation and sick leave I just experience again how much it sucks to find relevant information in old email threads :-) Maybe package meta data could be made to carry some kind of good/bad score. If a certain build of a package is rated down by people, zypper could display a warning. Maybe the solver could even try to come up with a solution that does not upgrade to the faulty build.
If we have package metadata amendable by users can we at least record (open) bugreports there? OTOH bugreports should be eventually visible to the maintainer so he can do the association as well.
Then you could implement
zypper show-bugs-I-get-when-dup
New bugs, of course. And I'd rather restrict metadata to contain (important) regressions. You can then pin the packages you don't want to regress and the solver should be able to update the rest as far as possible. Richard. -- Richard Biener <rguenther@suse.de> SUSE / SUSE Labs SUSE LINUX Products GmbH - Nuernberg - AG Nuernberg - HRB 16746 GF: Jeff Hawn, Jennifer Guild, Felix Imend"orffer -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org