Ok, Francisco. I just tested the qtplus version, and I know what's going on now.

First of all, there still is an issue running the script from the menu. Please continue to run it from the CLI as you did on your second attempt.

The version which was rolled into qtplus wasn't quite the last one for release. My bad, as I fixed this bug and dropped the ball notifying Jake that it had a bug fixed. The pertinent (buggy) part of the script execution is:
mkdir: cannot create directory `/dev/shm': File exists
mknod: `/dev/null': File exists
mknod: `/dev/pts/0': File exists
mknod: `/dev/pts/2': Operation not permitted
mknod: `/dev/pts/3': Operation not permitted
mknod: `/dev/random': File exists
mknod: `/dev/urandom': File exists

I won't go in to how this happened, but you have 2 ways you can fix it. Either:

Download http://qtp.shubes.net/qtp-newmodel and use that. Put it in /usr/share/qmailtoaster-plus replacing the existing one, and make sure ownership and permissions are the same.

Or you can simply fix the script you have. Edit qtp-newmodel, locate c447_build_stub_branches(){ at line 529. Immediately following, you'll see 8 lines containing SANDROOT. Change all 8 occurrences to SANDBOX and save the file. That will fix it.

Sorry for the inconvenience, and thanks for using newmodel!

Francisco Paco Peralta wrote:
Just want to run this by you.

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.

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. 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)
**************************************************************************************

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. Or perhaps since the sandbox is "jailed" it might not have access to /dev/null?



*/"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]

Reply via email to