Re: F-13 libtool broken by gcc update

2010-05-03 Thread Jesse Keating
On Mon, 2010-05-03 at 14:54 -0400, Tom Lane wrote: > Jakub Jelinek writes: > > gcc-4.4.4-1.fc13 has just been tagged temporarily into dist-f13-override > > so that new libtool could be built. Likely you tried to built during > > that short window or NewRepo has been too slow after it has been unt

Re: F-13 libtool broken by gcc update

2010-05-03 Thread Mamoru Tasaka
Mamoru Tasaka wrote, at 05/04/2010 05:31 AM +9:00: > 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) small correction: for dist-rawhide and for dist-f14 -- devel mailing list devel@lists.fedoraproj

Re: F-13 libtool broken by gcc update

2010-05-03 Thread Mamoru Tasaka
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 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 acti

Re: F-13 libtool broken by gcc update

2010-05-03 Thread Tom Lane
Jakub Jelinek writes: > On Mon, May 03, 2010 at 03:35:44PM -0400, Tom Lane wrote: >> 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

Re: F-13 libtool broken by gcc update

2010-05-03 Thread Jakub Jelinek
On Mon, May 03, 2010 at 03:35:44PM -0400, Tom Lane wrote: > Mamoru Tasaka 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.f

Re: F-13 libtool broken by gcc update

2010-05-03 Thread Tom Lane
Mamoru Tasaka 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-

Re: F-13 libtool broken by gcc update

2010-05-03 Thread Tom Lane
Jakub Jelinek writes: > gcc-4.4.4-1.fc13 has just been tagged temporarily into dist-f13-override > so that new libtool could be built. Likely you tried to built during > that short window or NewRepo has been too slow after it has been untagged > from dist-f13-override already. I see. It seems l

Re: F-13 libtool broken by gcc update

2010-05-03 Thread Thomas Spura
Am Montag, den 03.05.2010, 14:30 -0400 schrieb Tom Lane: > F-13 builds requiring libtool are now failing with > > DEBUG util.py:256: libtool-2.2.6-18.fc13.x86_64 from build has depsolving > problems > DEBUG util.py:256:--> Missing Dependency: gcc = 4.4.3 is needed by > package libtool-2.2.6

Re: F-13 libtool broken by gcc update

2010-05-03 Thread Mamoru Tasaka
Tom Lane wrote, at 05/04/2010 03:30 AM +9:00: > F-13 builds requiring libtool are now failing with > > DEBUG util.py:256: libtool-2.2.6-18.fc13.x86_64 from build has depsolving > problems > DEBUG util.py:256:--> Missing Dependency: gcc = 4.4.3 is needed by > package libtool-2.2.6-18.fc13.x8

Re: F-13 libtool broken by gcc update

2010-05-03 Thread Jakub Jelinek
On Mon, May 03, 2010 at 02:30:54PM -0400, Tom Lane wrote: > F-13 builds requiring libtool are now failing with > > DEBUG util.py:256: libtool-2.2.6-18.fc13.x86_64 from build has depsolving > problems > DEBUG util.py:256:--> Missing Dependency: gcc = 4.4.3 is needed by > package libtool-2.2.

F-13 libtool broken by gcc update

2010-05-03 Thread Tom Lane
F-13 builds requiring libtool are now failing with DEBUG util.py:256: libtool-2.2.6-18.fc13.x86_64 from build has depsolving problems DEBUG util.py:256:--> Missing Dependency: gcc = 4.4.3 is needed by package libtool-2.2.6-18.fc13.x86_64 (build) DEBUG util.py:256: Error: Missing Dependency