On Fri, May 13, 2011 at 08:00:48PM -0400, Brian K. White wrote:
Regressions happen no matter how hard we try, it's just a fact of life, sorry.
If you use tumbleweed, or heck, any release, I STRONGLY suggest that you keep at least one kernel installed on your system that you know works properly. zypper can easily handle multiple kernels, use that if you want, or keep one around by hand.
That's not good enough.
I'm sorry you feel that way about a free service :(
The repo should actually provide a way to manually choose older known-working builds.
That's not how tumbleweed, or the build service works. If you want to use something like the kernel in the build service (Kernel:stable), or Tumbleweed, you need to set your own system to retain older kernel packages. It's a trivial one line to uncomment, why can't you do that?
The updates repo does not delete the packages it updates. One is always the newest that gets installed by default, but every incremental package is still there also.
I don't think you understand the amount of disk space that would take up over time...
For kotd , especially stable , I think that is really called for. Maybe in head you can say "hey, this is head" just like Factory is Factory and is always turning over. But push an untested kernel out, blowing away the current one irrecoverably, into a "stable" repo ?
Why do you think that the kernel is not tested? It is, and it was, and it works here just fine on all of my systems, and the larger kernel.org developer community also did not have a problem with it. But remember, there will always be bugs that show up on different systems, the best we can do to handle this is respond quickly to them in resolving them, which we did here.
That is very unexpected, and now that I do know that it is allowed to happen, only _now_ I'll know, the hard way, to make my own one-way mirror of the repo so that in my copy the old packages don't go away. Merely enabling multiple kernels in zypper is not a good enough answer.
Why not?
If the current packages are bad in the repo, even if I have an old one still installed currently and don't uninstall it, I'm still screwed because I can't install any of the matching packages I might need, nor can I re-install the version I currently have, say if I uninstalled it or broke it, like say I had the source package, and some proprietary crapola 3rd party driver scribbled all over the source and I need to start over *cough*Dialogic/Eicon T1 cards*cough*.
If you have 3rd party kernel modules, I would STRONGLY suggest that you not use Tumbleweed or the Kernel:stable repo at all. Seriously, it's not worth the pain and extra work, unless you _really_ want to do it. And if you do do it, then again, you are on your own, sorry. Best of luck in the future, greg k-h -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org