On Thu, Oct 3, 2013 at 4:27 PM, Greg KH
On Thu, Oct 03, 2013 at 10:19:22PM +0200, Dimstar / Dominique Leuenberger wrote:
On Don, 2013-10-03 at 09:12 -0700, Greg KH wrote:
so why do you build TW against :Update instead of openSUSE:12.3?
Because sometimes we want to ensure updates rebuild things.
Update channels are considered 'API/ABI' break free for openSUSE...
Really? I have never heard this before, is it a guarantee?
It's probably not 100% true, but it would be close to impossible for ANY 3rd party if the :Update channel has an ABI incompatible change in libs.. There would be NO WAY for any 3rd party repo to work.
on SLE, there is sort of a guarantee, on openSUSE it's a best effort of course.. nevertheless, I'm rather use the maintenance team still cares a lot for it (and if not, they should).
and all the other stuff you have linked inside TW anyway, no?
What do you mean by "other stuff"?
GLIB updates, KDE Updates, Kernel Updates... TW is supposed to be 'more update than <Release> + Update'. So frankly, I don't see much of a reason to build TW against the Update channel.
For 12.1 and 12.2 I didn't do this, but changed to the update channel for 12.3 for some reason that I can't remember at the moment. So far it's been fine, with the exception of this last round of rebuilds.
Oh well, I'll just wait, I'm patient...
greg k-h
Looks like the build farm caught up a couple days ago at least for a few hours. Did tumbl -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org