Hi, since the binary rpms for redhat aren't available yet I'm trying to build the 3.5.13 rpms myself from source using the source tarballs from: http://mirror.its.uidaho.edu/pub/trinity/releases/3.5.13/ And the spec files and patches from: http://git.trinitydesktop.org/cgit/tde-packaging/tree/redhat/
I have found a couple of problems with the spec file (just starting with qt3), should I report bugs/corrections of spec files here on the dev ML or also in bugzilla?
In the meantime here is a couple of bugs I found in the qt.spec file:
First bug: error: File /home/packager/rpm/SOURCES/qt3-3.3.8d.tar.gz: No such file or directory spec file looks for: qt3-3.3.8d.tar.gz tarball is really called: qt3-3.3.8.d.tar.gz (notice the extra dot after the '8')
Second bug: + cd dependencies/qt3 /home/packager/rpm/tmp/rpm-tmp.HwIJZc: line 38: cd: dependencies/qt3: No such file or directory error: Bad exit status from /home/packager/rpm/tmp/rpm-tmp.HwIJZc (%prep) spec file contains: %setup -q -n dependencies/qt3 this should really be: %setup -q -n qt3
On 5 November 2011 22:29, Arnaldo Russo arnaldo-gmane@linuxtech.net wrote:
Hi, since the binary rpms for redhat aren't available yet I'm trying to build the 3.5.13 rpms myself from source using the source tarballs from: http://mirror.its.uidaho.edu/pub/trinity/releases/3.5.13/b And the spec files and patches from: http://git.trinitydesktop.org/cgit/tde-packaging/tree/redhat/
I have found a couple of problems with the spec file (just starting with qt3), should I report bugs/corrections of spec files here on the dev ML or also in bugzilla?
In the meantime here is a couple of bugs I found in the qt.spec file:
First bug: error: File /home/packager/rpm/SOURCES/qt3-3.3.8d.tar.gz: No such file or directory spec file looks for: qt3-3.3.8d.tar.gz tarball is really called: qt3-3.3.8.d.tar.gz (notice the extra dot after the '8')
Second bug:
- cd dependencies/qt3
/home/packager/rpm/tmp/rpm-tmp.HwIJZc: line 38: cd: dependencies/qt3: No such file or directory error: Bad exit status from /home/packager/rpm/tmp/rpm-tmp.HwIJZc (%prep) spec file contains: %setup -q -n dependencies/qt3 this should really be: %setup -q -n qt3
I recommend sending the email to the ML, since we don't have a spot (yet) on the bug tracker for red hat. You also could probably email the packager for redhat (we should probably compile some sort of list of these people)
Le 06/11/2011 03:29, Arnaldo Russo a écrit :
Hi, since the binary rpms for redhat aren't available yet I'm trying to build the 3.5.13 rpms myself from source using the source tarballs from: http://mirror.its.uidaho.edu/pub/trinity/releases/3.5.13/ And the spec files and patches from: http://git.trinitydesktop.org/cgit/tde-packaging/tree/redhat/
I have found a couple of problems with the spec file (just starting with qt3), should I report bugs/corrections of spec files here on the dev ML or also in bugzilla?
In the meantime here is a couple of bugs I found in the qt.spec file:
First bug: error: File /home/packager/rpm/SOURCES/qt3-3.3.8d.tar.gz: No such file or directory spec file looks for: qt3-3.3.8d.tar.gz tarball is really called: qt3-3.3.8.d.tar.gz (notice the extra dot after the '8')
Second bug:
- cd dependencies/qt3
/home/packager/rpm/tmp/rpm-tmp.HwIJZc: line 38: cd: dependencies/qt3: No such file or directory error: Bad exit status from /home/packager/rpm/tmp/rpm-tmp.HwIJZc (%prep) spec file contains: %setup -q -n dependencies/qt3 this should really be: %setup -q -n qt3
Hello, thanks for noticing it. The reason why the path is incorrect, is that the RPM packages were built against a frozen GIT snapshot that I made myself, because the QT3 official tarball was not available at time of building, so I had to choose a version and directory myself, which were uncorrect.
I've just commited the fix to the GIT repository, it should be available soon.
Francois