Ignore the last email, this one is complete On Wed, Oct 9, 2013 at 12:59 PM, Greg Freemyer <greg.freemyer@gmail.com> wrote:
On Thu, Oct 3, 2013 at 4:27 PM, Greg KH <gregkh@linux.com> wrote:
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 tumbleweed get fully built? If so, it looks like it has already started building again. Lots of scheduled and blocked packages. I looked at one that was built and I see this at the end of the build log: Retried build at Tue Apr 30 17:38:40 2013 returned same result, skipped Retried build at Fri May 3 18:10:11 2013 returned same result, skipped Retried build at Thu May 23 05:11:29 2013 returned same result, skipped Retried build at Sat Jun 15 11:32:13 2013 returned same result, skipped Retried build at Mon Jun 17 17:44:26 2013 returned same result, skipped Retried build at Wed Jun 19 14:16:05 2013 returned same result, skipped Retried build at Thu Jun 20 20:53:25 2013 returned same result, skipped Retried build at Wed Jul 3 04:48:48 2013 returned same result, skipped Retried build at Sat Jul 20 12:14:24 2013 returned same result, skipped Retried build at Mon Jul 22 19:54:10 2013 returned same result, skipped Retried build at Sun Aug 11 10:32:45 2013 returned same result, skipped Retried build at Mon Sep 2 14:45:15 2013 returned same result, skipped Retried build at Fri Sep 13 16:23:55 2013 returned same result, skipped Retried build at Tue Oct 1 02:15:10 2013 returned same result, skipped Retried build at Mon Oct 7 21:02:42 2013 returned same result, skipped I suspect that is lowing the priority of individual package builds like that, but then all packages dependent on ones like that one are delayed waiting on something like that to rebuild. Seems like tumbleweed never finishes building a full set of packages before an update to a core package restarts the whole process. Does the prioritization take into account the number of packages that are blocked based on the specific package in question? If not, should it? Greg -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org