F-13 libtool broken by gcc update

Mamoru Tasaka mtasaka at ioa.s.u-tokyo.ac.jp
Mon May 3 18:38:30 UTC 2010


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.x86_64 (build)
> DEBUG util.py:256:  Error: Missing Dependency: gcc = 4.4.3 is needed by package libtool-2.2.6-18.fc13.x86_64 (build)
> DEBUG util.py:256:   You could try using --skip-broken to work around the problem
>
> apparently as a result of the fact that gcc was updated to 4.4.4 over
> the weekend.  Could we have a fix for this ASAP, please?  And why
> weren't there loud bleats from broken-dependencies checking?
>
> 			regards, tom lane

$ 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).
Now:
$ koji latest-pkg dist-f13-build gcc libtool
Build                                     Tag                   Built by
----------------------------------------  --------------------  ----------------
gcc-4.4.3-18.fc13                         dist-f13              jakub
libtool-2.2.6-18.fc13                     dist-f13              jakub

Once newrepo is created, dependency will be recovered again.

Regards,
Mamoru


More information about the devel mailing list