Just ran qtp-newmodel to update one of my servers and ran into this:

Connecting to mirrors.qmailtoaster.net|68.115.175.140|:80... failed:
Connection timed out.

This is okay as qtp-newmodel then tried out the next mirror. But what
I found out a bit frustrating was that with the next package the
mirror 68.115.175.140 was tried again and then qtp-newmodel needed to
wait for the timeout again. I think it would be better if after the
first timeout the server would be blacklisted for this run?

Another issue I encountered:

qtp-dependencies v0.3.0
qtp-install-rpmforge v0.3.1 - getting latest version of rpmforge-release ...
qtp-install-rpmforge -
http://svn.rpmforge.net/svn/trunk/rpms/rpmforge-release/rpmforge-release.spec
not found, please try again later.

This shouldn't happen, right? Although I already had rpmforge installed ok:

# rpm -qa |grep rpmforge
rpmforge-release-0.5.2-2.el5.rf

And in the end I got this:

umount: /mnt/qtp-sandbox/usr: device is busy
umount: /mnt/qtp-sandbox/usr: device is busy
qtp-umount-sandbox: Error: sandbox still mounted!!!!

and mount tells me:

/opt/qtp-overlay/usr on /mnt/qtp-sandbox/usr type fuse (rw,default_permissions)

This was probably because I was tailing
mnt/qtp-sandbox/usr/src/qtp-upgrade/log/build-recent.log in another
console window (as suggested). After stopping that umount worked ok,
but perhaps the user should be informed about the probable cause and
how to fix it?

Anyhow, its nice to have qtp-newmodel around as it makes updating quite easy!

Best,
Peter

---------------------------------------------------------------------------------
Qmailtoaster is sponsored by Vickers Consulting Group 
(www.vickersconsulting.com)
    Vickers Consulting Group offers Qmailtoaster support and installations.
      If you need professional help with your setup, contact them today!
---------------------------------------------------------------------------------
     Please visit qmailtoaster.com for the latest news, updates, and packages.
     
      To unsubscribe, e-mail: [email protected]
     For additional commands, e-mail: [email protected]


Reply via email to