From: Bob Pearson <[EMAIL PROTECTED]>
Subject: Re: [Fink-beginners] Building bundle-kde-ssl on tiger
Date: Thu, 12 May 2005 09:51:58 -0400
To: Fink Beginners <[email protected]>
On May 12, 2005, at 7:17 AM, Dufour Eric wrote:
I built it and it works currently on my Tiger iMac G5 1.8 Ghz ,1 �
Gig RAM.
However it was a bit long task:
1) I used the SSL version of every alternative proposed by the �
installer
2) The installation often (10-12 times) stopped because of a wrong �
version of db42 or other package installed
�� � � � � � � 2,1) Each time I did dpkg -r --force-remove "name of �
the wrong version" (p.e. db42)
I am a newbie and this doesn't work for me. when I do a "dpkg -r --�
force-remove-reinstreq db42" I get
dpkg - warning: ignoring request to remove db42 which isn't installed.
And "dpkg -r --force-remove-essential db42"
dpkg - warning: ignoring request to remove db42 which isn't installed.
you could try the --force-all option instead: sudo dpkg -r --force-all db42
How history is good, I can also find there that I had to do:
sudo dpkg -r --force-all db42-shlibs to install db42-ssl-shlibs in place
Meaning that not only the db42 but also db42-shlibs may also be on the way of your db42-ssl installation (db42-ssl requires db42-ssl-shlibs).�
This may be your problem (the libraries are still non-ssl version and should be force-removed)
you could do a fink list db* (or use fink commander table) to see which versions and libraries are in use.�
If you use fink commander check what is the archived version (you want db42 archived) and current version (you want db42-ssl & db42-ssl-shlibs current).�
�� � � � � � � 2,2) I then fink installed the required version �
(p.e. db42-ssl) since the .deb are already built this goes fast
�� � � � � � � 2,2) The I unlocked the non-installed package
How do you do this?
Each time an installation fails you get a message at the end.�
The command to unlock the the package is written here
OK a little history and...
fink remove fink-buildlock-full name of the package
example: fink remove fink-buildlock-graphviz-1.16-11
�� � � � � � � 2,3) And fink installed this package alone
3) When this was done I relaunched the Bundle-kde-ssl installation
6) Several times it looked like the startup froze but it was just a �
long, very long, extremely long startup step (once I counted 11 �
minutes).
My old binaries before I decided to rebuild (stupid move) did this. I �
suspect it has to do with the initialization of sound which changes �
in tiger.
Sound and KDE, dunno why it's such an headache...
you may be right for sure.
Thanks.
