On Ter, 2012-07-31 at 22:42 +0200, Kevin Kofler wrote: > I'm looking into these: > > Bill Nottingham wrote: > > Package komparator (fails to build) can't resolve this fail g++ -DHAVE_CONFIG_H -I. -I.. -I/usr/include/kde -I/usr/lib64/qt-3.3/include -I. -DQT_THREAD_SUPPORT -D_REENTRANT -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -c -o kdatecombo.o kdatecombo.cpp g++ -DHAVE_CONFIG_H -I. -I.. -I/usr/include/kde -I/usr/lib64/qt-3.3/include -I. -DQT_THREAD_SUPPORT -D_REENTRANT -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -c -o kfileitemext.o kfileitemext.cpp g++ -DHAVE_CONFIG_H -I. -I.. -I/usr/include/kde -I/usr/lib64/qt-3.3/include -I. -DQT_THREAD_SUPPORT -D_REENTRANT -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -c -o klistviewitemdups.o klistviewitemdups.cpp g++ -DHAVE_CONFIG_H -I. -I.. -I/usr/include/kde -I/usr/lib64/qt-3.3/include -I. -DQT_THREAD_SUPPORT -D_REENTRANT -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -c -o klistviewitemsingle.o klistviewitemsingle.cpp kdatecombo.cpp:17:26: fatal error: kdatecombo.moc: No such file or directory compilation terminated. make[2]: *** [kdatecombo.o] Error 1 > > Package krecipes (fails to build) > > Package qalculate-kde (fails to build) > > Package tesseract (fails to build) > > but since the build.log files are no longer available, I need to run new > builds first, so it's going to take a while. :-( > > Are those build.log files really so large that they cannot be kept for > longer? :-( It's so annoying to see those build failures and to have no idea > why the builds failed. > > I also really dislike the way FTBFS are handled now. In the past, bugs were > filed for the build failures and they were all tracked on a tracking bug in > Bugzilla, so it was always possible to see what needed fixing, and it was > possible for provenpackagers to work on that in a coordinated fashion. These > days, we get surprised with the failures at the last moment when they have > actually been happening for 2 or 3 releases (depending on whether they would > have built on F16 had there been a mass rebuild there)! We really need to > track those failures in Bugzilla again. > > Kevin Kofler > -- Sérgio M. B. -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
