Hi Nick,
Thanks for the info. That pretty much answers my questions regarding
removal of packages, but I don't think you understood what I'm trying to
convey.
I'm trying to do the upgrade a bit differently. In order to minimize
down time, I'm attempting to rpmbuild all (or as many as possible)
packages while qmail is still running, then only rpm -Uvh them when
qmail is down. This will drastically reduce down time.
I think I understand why libdomainkeys-toaster needs to be installed
before qmail-toaster can be built. I don't see any problem with building
and installing libdomainkeys-toaster while the former qmail is still
running though. Do you?
I'm still not clear about the other packages I've listed below. I want to:
.) rpmbuild courier-imap-toaster before rpm -Uvh'ing courier-auth-toaster
.) rpmbuild maildrop-toaster before rpm -Uvh'ing courier-imap-toaster
.) rpmbuild isoqlog-toaster before rpm-Uvh'ing control-panel-toaster
.) rpmbuild simscan-toaster before rpm -Uvh'ing ripmime
I admittedly don't know (yet) enough about the inter-workings of the
various packages to understand why this won't work. Can you explain it
to me?
TIA.
Nick Hemmesch wrote:
Hi Eric,
On the website it shows which packages have to be removed for a clean
build of this new version. It is because qmail-toaster requires
libdomainkeys prior to the build of the new qmail-toaster, so remove
libdomainkeys with "--nodeps".
The package control-panel-toaster requires courier-imap-toaster which is
obsoletes courier-imap-toaster, less than version 4, so remove
control-panel-toaster with "--nodeps".
The previous version of spamassassin-toaster did not update cleanly, so
remove it with "--nodeps".
With those packages removes the build and install will "re-provide" all
the dependencies and install cleanly.
The others you listed will not bother the build and install because they
provide for packages that are installed later in the install.
Future updates will not require anything except to stop qmail and do the
updates.
Regards,
Nick
I'm working on a improving the upgrade.sh script. I'm attempting to make
it such that it recognizes it's environment to the extent that it can
tell what's already installed and what's already downloaded, so that it
can be rerun, or run in parts. (It might end up being smart enough to do
an install too - we'll see about that).
Along the line, I got the (maybe not-so) brilliant idea to do all the
builds first (while qmail is still running), then do all the upgrades.
This would drastically reduce the down time during an upgrade, and I
think would be a very good thing.
However, I ran into some *build* dependency problems, the first of which
was libdomainkeys-toaster is needed by qmail-toaster. This I don't
understand. Why would libdomainkeys-toaster need to be *installed* in
order to *build* qmail-toaster? Can someone please explain?
I also came across the following similar dependency issues:
courier-authlib required by courier-imap
courier-imap required by maildrop
control-panel required by isoqlog
ripmime required by simscan
Again, I can see (and appreciate) the *installation* dependencies, but
why are there *build* dependencies? I'm thinking that build dependencies
should be source related (you need compiler, headers, and such). What am
I missing?
--
-Eric 'shubes'
--
-Eric 'shubes'
---------------------------------------------------------------------
QmailToaster hosted by: VR Hosted <http://www.vr.org>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
