Thanks, Adrian
Yes, the method to drop rebuild event before is wrong, all schedule
was stopped. So, the adventure is failed :-)
I've considered 'meta change' before, but have not test that idea
because confused by the exact meanings of 'meta change'. Could you
give me a exact description ?
Now, I'm testing to drop 'meta change' event for rebuild, by add a
"next;" before set $reason :
----------------------------------------------------
# Jian Lee: drop 'meta change' event for rebuild
next;
my @diff = diffsortedmd5(0, \@meta, \@new_meta);
print " - $packid ($packtype)\n";
print " $_\n" for @diff;
print " meta change, start build\n";
$reason = { 'explain' => 'meta change', 'packagechange' =>
sortedmd5toreason(@diff) };
============================
I'll report that result.
Thanks,
Tuesday 22 December 200918:28:45Adrian Schröter
Thanks, Adrian
but how to set cycle of 3 ?
You can't set it somewhere, you can just change your package dependencies so that the cycles will reduce. Check the scheduler log file output to see your current cycles.
I'm hacking the bs_sched script, and want it to drop pkgs which would
relsync can be configured via BSConfig.pm, no need to change the scheduler for this. What you want is to avoid the trigger on "meta change" and only trigger on source change. Check for "meta change" string in the code. But be warned, you will most likely quite often build broken repostories. You will hunt problems in your packages which comes and go and you will never know when you have a clean state which can be tested. bye adrian -- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de ---- Jian Lee [ http://jianlee.ylinux.org ] -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org