On Monday 2010-01-18 15:10, Adrian Schröter wrote:
Am Montag, 18. Januar 2010 14:51:03 schrieb Jon Nelson:
I continue to have build loops (not actual loops) I can't explain. They do eventually run themselves out, but sometimes I see packages rebuild 30, 40, 100 or more times. In some cases, there are explanations for why they might rebuild a few times, but not 10 times much less over a hundred.
For example, one package in x86_64 has rebuilt (around) 47 times in the last 3 days. The jobhistory shows only 'rebuild counter'.
We deliver the obs in default config that i586 and x86_64 packages should always have the same release number. This means, if it builds for one architecture, the other one gets triggered as well.
If you done like this, define this in your BSConfig.pm to have seperate pools:
our $relsync_pool = { ... "i586" => "i586", "x86_64" => "x86_64", ... }
Speaking of build loops, I still seem to have some, and it is rather delicate. - gcc44.sparc64 depends(BuildRequires) on glibc-devel-32bit. - gcc44.sparcv9 depends(BuildRequires) on glibc-devel-64bit. ExportFiltering glibc-devel however will cause a meta change cycle. Building glibc-devel.sparcv9 leads to: - baselibs generation glibc-devel-32bit.sparc64 - leads to meta change in gcc44.sparc64 (rebuild) - this in turn leads to meta change in glibc.sparc64 - glibc-devel-64bit.sparcv9 baselibs generation - leads to meta change in gcc44.sparcv9, rebuild - in turn leads to meta change in glibc.sparcv9, completing the circle At least this is what it looks like. There are entries in package/reason that are not obvious at all: # /sparc64/elfutils/reason: <packagechange change="added" key="gcc44/libdb-4_5-32bit" /> Why does gcc44 depend(?) on libdb-4_5-32bit? I had made sure that there is no libdb-4_5-32bit in /srv/obs/repos/$project/sparc64 at all. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org