F-13 libtool broken by gcc update
mtasaka at ioa.s.u-tokyo.ac.jp
Mon May 3 20:31:29 UTC 2010
Jakub Jelinek wrote, at 05/04/2010 05:17 AM +9:00:
> On Mon, May 03, 2010 at 03:35:44PM -0400, Tom Lane wrote:
>> Mamoru Tasaka<mtasaka at ioa.s.u-tokyo.ac.jp> writes:
>>> $ TZ=UTC koji list-tag-history --build=gcc-4.4.4-1.fc13
>>> Sat May 1 00:57:24 2010: Tagged gcc-4.4.4-1.fc13 with dist-f13-updates-candidate [still active]
>>> Mon May 3 15:58:06 2010: Tagged gcc-4.4.4-1.fc13 with dist-f13-override
>>> Mon May 3 17:37:31 2010: Untagged gcc-4.4.4-1.fc13 from dist-f13-override
>>> The dependency was broken only for this 2 hours (perhaps to rebuild libtool for gcc 4.4.4).
>>> Once newrepo is created, dependency will be recovered again.
>> BTW, it's now two hours later and gcc 4.4.4 is still in the buildroot.
>> There is no newrepo task running for F-13, and no evidence that one has
>> been launched recently. Perhaps an untag event fails to force a repo
>> rebuild? If so seems like a bug.
> So what is
Well, it seems usually koji runs 3 newrepo tasks at the same time, but
two of them were hanging for 9 hours (for dist-rawhide and dist-rawhide)
so newrepo tasks were rolling very slowly (I noticed this because
I submitted one chain-build for dist-rawhide but it failed because wait-repo
I requested to cancel hanging 2 newrepo tasks and they were cancelled.
Now newrepo tasks seem to be going well and new F-13 build already appeared as
Jakub said above.
More information about the devel