Thanks, Justice. FWIW, it appears to me to be x86_64 related, but not unionfs related (same error w/ linked sandbox).
I know you'll keep us posted. Justice London wrote: > I'm going to work on a fix for this. I have a centos 5 x86_64 machine to > play with qtp on. I believe it's mainly due to the highly, highly > modified kernel that cent and fedora ship with. > > Justice London > [EMAIL PROTECTED] > > On Fri, 2008-09-12 at 22:02 +0200, Wim Godden wrote: >>> Not without a little more info. Sorta looks like a bug to me. >>> >>> What distro/arch are you running? >>> # qtp-whatami" >>> >>> Are your OS packages all up to date? >>> >>> What version of qmailtoaster-plus do you have installed? >>> >>> By "small sandbox" do you mean unionfs sandbox? What sort of error(s) did >>> you get with that failure? >>> >>> >> qtp-whatami : >> qtp-whatami v0.3 >> DISTRO=CentOS >> OSVER=5.2 >> QTARCH=x86_64 >> BUILD_DIST=cnt5064 >> BUILD_DIR=/usr/src/redhat >> This machine's OS is supported, but this version/arch has not been tested. >> >> >> The error upon trying the unioned sandbox : >> If you want to view compile messages, you can open another terminal and: >> # tail -f /mnt/qtp-sandbox/usr/src/qtp-upgrade/log/build-recent.log >> >> cp: cannot create regular file >> `/mnt/qtp-sandbox/usr/src/qtp-upgrade/log/build-20080912-220150.log': No >> such file or directory >> ln: creating symbolic link >> `/mnt/qtp-sandbox/usr/src/qtp-upgrade/log/build-recent.log' to >> `build-20080912-220150.log': No such file or directory >> /usr/sbin/qtp-newmodel: line 627: /mnt/qtp-sandbox: is a directory >> cp: cannot stat >> `/mnt/qtp-sandbox/usr/src/qtp-upgrade/log/build-20080912-220150.log': No >> such file or directory >> >> Build failed, Exiting. >> >> >> >> >> -------- Original Message -------- >> Subject: qtp-newmodel failing on sandbox >> Date: Thu, 11 Sep 2008 18:04:23 +0200 >> From: Wim Godden <[EMAIL PROTECTED]> >> Organization: FirstLink Networks >> To: [email protected] >> >> >> >> Hi, >> >> I just tried running qtp-newmodel for the first time, because I noticed >> there was a new clamav package. >> >> I first tried building a small sandbox, but that failed. Then I tried a >> linked sandbox and this gave me a few errors : >> <START> >> Copying files from clamav-toaster-0.93.3-1.3.20 to the linked sandbox ... >> unexpected: /usr/share/clamav/daily.cvd in package >> clamav-toaster-0.93.3-1.3.20 does not exist >> Continuing ... >> unexpected: /usr/share/clamav/main.cvd in package >> clamav-toaster-0.93.3-1.3.20 does not exist >> Continuing ... >> cp: cannot create regular file >> `/mnt/qtp-sandbox/etc/cron.daily/squirrelmail.cron': No such file or >> directory >> Copying files from simscan-toaster-1.3.1-1.3.6 to the linked sandbox ... >> Sandbox has been built successfully! >> qtp-newmodel - installing perl-DB_File perl-MIME-Base64 perl-Net-SMTP >> perl-Time-HiRes ... >> Loading "fastestmirror" plugin >> Loading mirror speeds from cached hostfile >> * rpmforge: ftp-stud.fht-esslingen.de >> * qmailtoaster-plus: qtp.qmailtoaster.com >> * base: ftp.tudelft.nl >> * updates: mirror.liteserver.nl >> * addons: ftp.tudelft.nl >> * extras: ftp.tudelft.nl >> Setting up Install Process >> Parsing package install arguments >> No package perl-Net-SMTP available. >> Package perl - 4:5.8.8-10.el5_2.3.i386 already installed and latest version >> Package perl - 4:5.8.8-10.el5_2.3.i386 already installed and latest version >> Package perl - 4:5.8.8-10.el5_2.3.i386 already installed and latest version >> Nothing to do >> >> Starting to build the binary rpms ...(pizza anyone?) >> >> If you want to view compile messages, you can open another terminal and: >> # tail -f /mnt/qtp-sandbox/usr/src/qtp-upgrade/log/build-recent.log >> >> /usr/sbin/qtp-newmodel: line 627: /mnt/qtp-sandbox: is a directory >> >> Build failed, Exiting. >> <END> >> >> Any ideas what might be the cause ? >> >> Kind regards, >> >> Wim >> -- -Eric 'shubes' --------------------------------------------------------------------- QmailToaster hosted by: VR Hosted <http://www.vr.org> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
