Ron Jones wrote:
That still doesn't explain how /usr/src got wiped out though. You didn't run
it with SANDROOT=/usr/src did you?
Well... I don't believe so.
Also:
During the last 40 minutes, I've been running a fresh instance of the
upgrade script, it failed again.
Just to make sure everything worked as it should, I downloaded (via wget)
completely new copies of qmt-newmodel.sh & qmt-build-rpms.sh directly to
/usr/src/qmt/
Left the variables as shown below:
UPGRADE_DIR=/usr/src/qmt
SANDROOT=/opt/qmt-sandbox
Then I chmodded them to 755
Then I ran ./qmt-newmodel.sh, chose "new sandbox," it deleted the old and
created the new in /opt/qmt-sandbox/
Here is the output (after Creating /opt/qmt-sandbox/var ...:
Sandbox has been build successfully!
Starting to build the binary rpms ...(pizza anyone?)
If you want to view compile messages, you can open another terminal and:
#tail -f /opt/qmt-sandbox/usr/src/qmt/log/build-recent.log
Chroot: cannot run command '/usr/src/qmt/qmt-build-rpms.sh' : No such file
or directory
Build failed, Exiting
Am I missing something obvious?
Ron,
I've fixed the script so that it won't run with an erroneous SANDROOT
setting (/ and any others) any more, and it also downloads the
qmt-build-rpms.sh script automatically now (and sets permissions).
I don't have reason to believe that the "No such file" problem is fixed, but
I'd like you to do this (again):
.) delete the scripts you have
.) reboot the server if at all feasible. /etc/mtab might be a bit wacky with
the abnormal exits, and I just want to eliminate that from a possibility
.) download qmt-newmodel.sh and try running it again.
In the meantime, I'll continue to try and remember what has caused this "No
such file" error in the past.
Thanks for your patience and effort.
--
-Eric 'shubes'
---------------------------------------------------------------------
QmailToaster hosted by: VR Hosted <http://www.vr.org>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
