On Fri, 2004-09-17 at 00:32, Michael Schwendt wrote: > On Thu, 16 Sep 2004 15:12:46 -0600, Rodolfo J. Paiz wrote: > > [...] how do I (as a user, not a coder) help to review this? > > New package submissions at fedora.us need GPG signed approvals before > they would be passed on to the build server by a release manager and > be put in a publicly accessible repository. > Bear with me since this is the first time I've used fedora.us, the fedora-rpmdevtools package, etc. 1. As my normal user, I issued the commands "/usr/bin/fedora-buildrpmtree" and "/usr/bin/fedora-installdevkeys" which appeared to work fine. I also imported the fedora.us GPG key via "rpm --import http://www.fedora.us/FEDORA-GPG-KEY"; run as root. 2. I copied the qcad-2.0.3.3-0.fdr.1.src.rpm file into my rpmbuild/SRPMS directory and tried to check the signatures, getting this output (the command wraps, but it was on one line): [rpaiz@rodolfo SRPMS]$ /usr/bin/fedora-rpmchecksig qcad-2.0.3.3-0.fdr.1.src.rpm qcad-2.0.3.3-0.fdr.1.src.rpm: MISSING KEY - 3321270a 3. I then tried to rebuild the package in that same directory, and got the following: [rpaiz@rodolfo SRPMS]$ rpmbuild --rebuild qcad-2.0.3.3-0.fdr.1.src.rpm Installing qcad-2.0.3.3-0.fdr.1.src.rpm warning: user gemi does not exist - using root warning: group gemi does not exist - using root warning: user gemi does not exist - using root warning: group gemi does not exist - using root error: Failed build dependencies: qt-devel >= 0:3.1.2 is needed by qcad-2.0.3.3-0.fdr.1 python-devel is needed by qcad-2.0.3.3-0.fdr.1 XFree86-devel is needed by qcad-2.0.3.3-0.fdr.1 4. I attempted to install qt-devel and python-devel with up2date, and to my surprise also got libjpeg-devel, libmng-devel, libpng-devel, xorg-x11-devel, fontconfig-devel, and freetype-devel. XFree86-devel is provided actually by xorg-x11-devel. Isn't that a lot of dependencies for the package? Or is that just for *rebuilding* the package? 5. The rebuild failed and the last few lines of output are copied here, since I don't really understand them: g++ -c -pipe -Wall -W -O2 -g -pipe -march=i386 -mcpu=i686 -DQT_NO_DEBUG -DQT_SHARED -DQT_THREAD_SUPPORT -I/usr/lib/qt-3.3/mkspecs/default -I. -I../include -I../../dxflib/include -I../../qcadlib/include -I../../qcadcmd/include -I../../fparser/include -I/usr/lib/qt-3.3/include -Imoc/ -o obj/rs_actionlayersremove.o rs_actionlayersremove.cpp obj/rs_actionlayersremove.o: No space left on device {standard input}: Assembler messages: {standard input}:82096: FATAL: Can't write obj/rs_actionlayersremove.o: Illegal seek make[2]: *** [obj/rs_actionlayersremove.o] Error 1 make[2]: Leaving directory `/home/rpaiz/rpmbuild/BUILD/qcad-2.0.3.3-1.src/qcadactions/src' make[1]: *** [lib/libqcadactions.a] Error 2 make[1]: Leaving directory `/home/rpaiz/rpmbuild/BUILD/qcad-2.0.3.3-1.src/qcadactions' make: *** [all] Error 2 Building qcadactions failed + exit 0 Executing(%install): /bin/sh -e /var/tmp/rpm-tmp.67491 + umask 022 + cd /home/rpaiz/rpmbuild/BUILD + cd qcad-2.0.3.3-1.src + LANG=C + export LANG + unset DISPLAY + rm -rf '/var/tmp/qcad-2.0.3.3-%{subversion}-0.fdr.1-root-rpaiz' + mkdir -p '/var/tmp/qcad-2.0.3.3-%{subversion}-0.fdr.1-root-rpaiz/usr/share/qcad' + mkdir -p '/var/tmp/qcad-2.0.3.3-%{subversion}-0.fdr.1-root-rpaiz/usr/share/qcad/library' + cd qcad + cp -fp qcad '/var/tmp/qcad-2.0.3.3-%{subversion}-0.fdr.1-root-rpaiz/usr/share/qcad' cp: cannot stat `qcad': No such file or directory error: Bad exit status from /var/tmp/rpm-tmp.67491 (%install) RPM build errors: user gemi does not exist - using root group gemi does not exist - using root user gemi does not exist - using root group gemi does not exist - using root Bad exit status from /var/tmp/rpm-tmp.67491 (%install) [rpaiz@rodolfo SRPMS]$ > Most important would be that a package rebuilds from src.rpm, > installs, works, and uninstalls again without errors [...] [However, > everyone should be able to run "rpmbuild --rebuild filename.src.rpm" > after installing the fedora-rpmdevtools package.] Well, no success here. Even though the sequence seems simple, I would guess the failure is most likely due to user error. Can someone point out where I went wrong? I have no idea what the "no space left on device" means... lots of space everywhere on this disk. Cheers, -- Rodolfo J. Paiz <rpaiz@xxxxxxxxxxxxxx> Simpaticus.com
