Peter Peltonen wrote:
Thanks for your work with the upgrade script.
Welcome. It's been fun (so far).
You mentioned earlier that the earlier version of the upgrade script
was not suitable for my old install of qmail-toaster-1.03-1.0.15. Is
this true with the new script also?
I don't know what the issues are going from 1.0 to 1.3, so I can't say
for sure. I will attempt to make the new script as encompassing as
feasible. I think it's safe to say that the new script would be a better
choice than the old one, since it gives you a sandbox to play in.
Just to let you know, here are some glitches I ran into with the old
script and my old qmailtoaster installation on CentOS 3.
Thanks. I'll try to modify the new script to take them into account.
I don't
know if the new script does it, but it would be great if the script
would check for dependencies first before it would go and try to
install the packages. One could then fix the deps and then continue
with the upgrade.
I agree. That's essentially what the script allows you to do, but it
does it in a somewhat roundabout fashion.
Writing a script to check for all dependencies is something I don't
think is advisable (for me at least) to tackle. That's where the sandbox
comes in to play (so to speak). All of the upgrades are initially
applied in the sandbox (apart from the 'live' system), where
dependencies are identified. If there are problems, they can be resolved
in the sandbox (# chroot /opt/qmt-sandbox) first, then continue building
the binary rpms. Once the build process completes, all of the
dependencies have been ironed out, and the 'live' system is yet
untouched. The actual upgrade process then processes all packages with a
single "rpm -Uvh" command, so that rpm itself can resolve all
dependencies at once, and there should be no more conflicts (in theory).
--
courier-authlib-toaster:
PROBLEM:
file /usr/share/man/man8/makeuserdb.8.gz from install of
courier-authlib-toaster-0.58-1.3.1 conflicts with file from package
courier-imap-toaster-doc-3.0.3-1.0.6
FIX:
remove courier-imap-toaster-doc with rpm -e and restart upgrade
This package apparently became obsolete at some point.
I will modify the upgrade script thus:
if courier-imap-toaster-doc is installed, remove it.
--
maildrop-toaster
PROBLEM:
checking for pcre/pcre.h... no
configure: error: pcre.h not found - install PCRE from www.pcre.org
FIX:
yum install pcre-devel and restart upgrade
This is outside the scope of the upgrade script at this point. The
dependencies script should handle that. Of course, you (logically) don't
run the deps script as part of an upgrade. ;)
At some point, I'd like to incorporate more of the installation process
(dependency script included) into the upgrade script. Until that
happens, your fix is what it takes in these situations (package not
installed).
Note: when using the new upgrade script, after adding a missing package
to the system, you would have to either choose to rebuild the sandbox
(the script gives you that option), or install the package manually in
the sandbox before restarting the upgrade script. Rebuilding the sandbox
would be the safest route.
--
spamassassin-toaster
PROBLEM:
error: Failed build dependencies:
perl-forward-compat is needed by
spamassassin-toaster-3.1.3-1.3.1
FIX:
download and install perl-forward-compat-5.8.0-0.fdr.2.i386.rpm from
rpm.pbone.net
and restart upgrade
This is apparently due to differences between CentOS3 and CentOS4. I'm
sure you have a reason for not upgrading to 4 (like XFree vs Xorg? ;) ),
but this is just a consequence of that. "Note" for maildrop-toaster
above applies here too.
--
Regards,
Peter
Thanks for your input, Peter. Your situation is one that is very
difficult to anticipate/create a test scenario for. I hope that others
in similar situations provide feedback as well.
--
-Eric 'shubes'
---------------------------------------------------------------------
QmailToaster hosted by: VR Hosted <http://www.vr.org>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
