Red Hat Bugzilla – Bug 344311
mock broken during rebuild of package ktorrent
Last modified: 2013-01-09 20:42:38 EST
Description of problem: Recently the mass package rebuild failed for my package "ktorrent" for the architecture x86 (and only for that one!). The error is that Qt headers are not found: http://linux.dell.com/files/fedora/FixBuildRequires/mock-results-core/i386/ktorrent-2.2.2-1.fc8.src.rpm/result/build.log However, that should not have happened, the dependency on kdebase-devel should have worked as it did in the past and as they still does on the other architectures. Since I have no idea what else could be broken I fill this bug report against mock.
Not a bug in mock. $ rpm -qp ktorrent-2.2.2-1.fc8.src.rpm --requires kdelibs-devel gettext gmp-devel avahi-devel desktop-file-utils automake rpmlib(CompressedFileNames) <= 3.0.4-1 According to the root log, all of the 'requires' were installed: http://linux.dell.com/files/fedora/FixBuildRequires/mock-results-core/i386/ktorrent-2.2.2-1.fc8.src.rpm/result/root.log --> search for 'yum --installroot' As far as I can see, mock installed all of the deps that were specified and their respective dep trees.
But that doesn't explain why it works on x86_64. And: kdebase-devel requires kdelibs-devel explicitely, and kdelibs-devel requires qt-devel: http://cvs.fedoraproject.org/viewcvs/devel/kdebase/kdebase.spec?rev=1.272&view=markup http://cvs.fedoraproject.org/viewcvs/devel/kdelibs3/kdelibs3.spec?rev=1.1&view=markup
And if you look at the logs, they *are* being installed. qt-devel is installed in the buildroot.
Created attachment 235021 [details] Part of the config log showing the qt-problem This shows that the configuration checks for the wrong places. Is this a problem with the config script, the environment variables or with the Qt packages? And why the hell does it work with x86_64? And why did it work with all the other Fedora versions before?
I'm going to close this bug for now. Please ensure (with scratch builds) that ktorrent builds in koji. If it fails again in the next mock rebuild test a new bug will be opened.