Francisco Paco Peralta wrote:
Just want to run this by you.
Thanks.
In my first email, I had selected to have my sandbox linked and soon
after I made that selection, I recieved the qtp-whatami not found
message. So really, I don't think I got too far.
That is very odd. The execution of qtp-whatami happens during
initialization, one of the very first things. The selection for
linked/copied sandbox is well after that. I don't see how you could have
selected a linked sandbox with a qtp-whatami not found error. qtp-newmodel
should have exited at that point.
The second time I attempted the upgrade I did:
# cd /usr/share/qmailtoaster-plus
# ./qtp-newmodel
But this time I selected to have my sandbox copied, as I think it is
recommended in other mailings I have read.
That's the safest. The linked option is primarily there if you're tight on
disk space.
And that is when I received
the error messages shown below regarding qtp-build-rpms line 91
/dev/null not found message.
Since then I have tried several times to and the script terminates with
the same error.
***************************************************************************
# tail -15 /opt/qtp-sandbox/usr/src/qtp-upgrade/log/build-recent.log
/bin/sh: /dev/null: No such file or directory
make: [install] Error 1 (ignored)
cd /var/tmp/zlib-1.2.3-root/usr/lib; if test -f libz.so.1.2.3; then \
rm -f libz.so libz.so.1; \
ln -s libz.so.1.2.3 libz.so; \
ln -s libz.so.1.2.3 libz.so.1; \
(ldconfig || true) >/dev/null 2>&1; \
fi
/bin/sh: /dev/null: No such file or directory
make: *** [install] Error 1
error: Bad exit status from /var/tmp/rpm-tmp.91032 (%install)
RPM build errors:
Bad exit status from /var/tmp/rpm-tmp.91032 (%install)
This tells me that the sandbox was not built properly for some reason.
/dev/null should be relative to the sandbox at this point. Is there a
/opt/qtp-sandbox/dev/null file? It should be identical to the /dev/null one.
**************************************************************************************
So I looked at the script for update.sh (the old way) and the way zlib
is built is as follows:
rpmbuild --rebuild $ZLIB
rpm -Uvh --replacefiles --replacepkgs /usr/src/$BDIR/RPMS/$ARCH/zlib*.rpm
Whereas in the qtp-build-rpms file, I believe and I could be wrong, the
structure used is as follows:
rpmbuild --rebuild $buildparm --target=$ARCH $UPGRADE_DIR/SRPMS/${QMT_PKG}
I am wondering if this could be at the heart of the issue.
No, but thanks for checking.
Or perhaps since the sandbox is "jailed" it might not have access to
/dev/null?
The script should be creating a new one at /opt/qtp-sandbox/dev/null.
What you you have in /opt/qtp-sandbox/dev?
*/"Eric \"Shubes\"" <[EMAIL PROTECTED]>/* wrote:
Jake and I are working this out.
It appears to me that the sandbox didn't build entirely/properly.
Now that I've looked a little closer into the matter, I'm kind of
surprised
that what I told you before didn't result in the same error.
Please try moving (or symlinking, doesn't matter)
/usr/share/qmailtoaster/qtp-whatami to /usr/sbin/qtp-whatami
I think it'll work that way. Please reply either way.
Francisco Paco Peralta wrote:
> Thanks for the reply.
>
> I did as instructed but now I have the followiing message:
>
> qtp-build-rpms 0.1.3
> /usr/share/qmailtoaster-plus/qtp-build-rpms: line 91: /dev/null:
No such
> file or directory
> /usr/share/qmailtoaster-plus/qtp-build-rpms: line 91: /dev/null:
No such
> file or directory
> /usr/share/qmailtoaster-plus/qtp-build-rpms: line 91: /dev/null:
No such
> file or directory
> /usr/share/qmailtoaster-plus/qtp-build-rpms: line 91: /dev/null:
No such
> file or directory
> /usr/share/qmailtoaster-plus/qtp-build-rpms: line 91: /dev/null:
No such
> file or directory
> /usr/share/qmailtoaster-plus/qtp-build-rpms: line 91: /dev/null:
No such
> file or directory
> Building zlib-1.2.3-1.0.3 ...
> qtp-build-rpms - rpmbuild failed for zlib-1.2.3-1.0.3
> qtp-build-rpms - see
> /opt/qtp-sandbox/usr/src/qtp-upgrade/log/build-recent.log
> Build failed, Exiting.
>
>
> Any ideas?
>
> */"Eric \"Shubes\"" /* wrote:
>
> Francisco Paco Peralta wrote:
> > Did the following:
> >
> > #qtp-menu
> >
> > When I select Newmodel in the menu I get the following output:
> >
> > qtp-newmodel 0.1.9
> > qtp-newmodel starting Sat Sep 9 10:17:56 EDT 2006
> > /usr/share/qmailtoaster-plus/qtp-newmodel: line 126:
qtp-whatami: No
> > such file or directory
> >
> > Any ideas how I can fix this?
> >
> >
> > Francisco "Paco" Peralta
>
> For now, just
> # cd /usr/share/qmailtoaster-plus
> # ./qtp-newmodel
>
> We'll get the menu interface for this fixed up soon. I want to talk
> with
> Jake about this.
>
> --
> -Eric 'shubes'
>
>
>
>
> Francisco "Paco" Peralta
--
-Eric 'shubes'
---------------------------------------------------------------------
QmailToaster hosted by: VR Hosted
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Francisco "Paco" Peralta
--
-Eric 'shubes'
---------------------------------------------------------------------
QmailToaster hosted by: VR Hosted <http://www.vr.org>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
