Then I'll ask a follow up question... Which mailer? I can tell right now I don't want to use mutt if I can avoid it. I haven't tried pine or mail as Patrick suggested but I have a feeling neither of them are as nimble as nmh. What I really liked about nmh was that it felt integrated in the shell. On a debian system I have used mailx a little. It worked good enough, but as I can remember it only used the mbox format. I realize this is just a question about taste, but perhaps I can get some useful hints anyway. Arvid fredag 27 februari 2004 00:52 skrev Charles Philip Chan:

On Thu, 26 Feb 2004 22:42:01 +0100

Arvid Johansson wrote:

...

Is there a tool to read mails from the console easily?

Any mailer that supports maildir such as mutt.

...

I prefered to use nmh to read mails in console but it uses a format which seems to be slightly different from whatever kmail is using.

Mh and maildir are totally different mail storage systems.

Charles

On Suse 9.0, I ran into the following problems when updating kdelibs 3.2.0-7 to 3.2.0-27 using the RPM packages. I am using apt, with the kde repository of the gwdg ftp-server. I tried both from synaptic and from console mode (init 3) to upgrade kdelibs3 but I'm always getting a conflict error against kdebase3-3.2.0-7: file /opt/kde3/share/services/ssh.protocol conflicts with file from package kdebase3-3.2.0-7 I tried to force the installation from init level 3 (rpm -Uhv --force) but then I got KDE not working properly: there was an error message loading and applet and I didn't have status bar nor universal location bar. I had to downgrade to 3.2.0-7 to have everything working again (apt remove kdelibs3#3.2.0-27, rpm -i kdelibs3... --force) Now is this a known bug? Is there a way I can upgrade to the latest kdelibs3? Why is this conflict happening? regards, Timur Note: Is it better that I stick to the old lib for a bit? __________________________________ Do you Yahoo!? Get better spam protection with Yahoo! Mail. http://antispam.yahoo.com/tools

Hello Helmut,

...

Hallo Timur, i had the same problem some days bevor. I did the update of kdelibs and kdebase with yast. There was no problem.

Do you know what was the reason for that? If the conflict is between two RPM packages how is Yast able to solve them? BTW, how do you do the update with Yast? regards, Timur __________________________________ Do you Yahoo!? Get better spam protection with Yahoo! Mail. http://antispam.yahoo.com/tools

* C. Richard Matson (goldfarm@ranch-farm.com) [040301 12:18]:

On Mon March 1 2004 8:16 am, Timur wrote:

...

Hello Helmut,

...

Hallo Timur, i had the same problem some days bevor. I did the update of kdelibs and kdebase with yast. There was no problem.

Hello.I had the same problem with the rpm's from Suse. I installed using fvwm and forced the installation. I had to reboot before using kde 3.2, otherwise it wouldn't work. I just did it yesterday, but so far ok, except for the multimedia applications which I couldn't get to work. Rich

The answer is that rpm's installed via YOU are patch rpm's and most likely don't have the conflicting file in them that they fat rpm that you can ftp down or get via apt have. So that's why YOU users aren't seeing the issues that those who just upgrade via the full rpm are seeing. It's simply that the kdelib3 full rpm is broken because it contains the same file as the kdebase3 pkg that wasn't upgraded. It's simply a screw up from the pkg maintainer. -- Linux User #147972 ---===--- mailto:ben@whack.org -- "There is no need to teach that stars can fall out of the sky and land on a flat Earth in order to defend religious faith."

* Timur (blackdir@yahoo.com) [040302 00:42]:

--- Ben Rosenberg wrote:

...

The answer is that rpm's installed via YOU are patch rpm's and most likely don't have the conflicting file in them that they fat rpm that you can ftp down or get via apt have. So that's why YOU users aren't seeing the issues that those who just upgrade via the full rpm are seeing. It's simply that the kdelib3 full rpm is broken because it contains the same file as the kdebase3 pkg that wasn't upgraded. It's simply a screw up from the pkg maintainer.

is there a way we can notify this issue to the mantainer so that he prepare a new (-28) version which is working? How can I find out who is the rpm maintainer?

The person who made the RPM is adrian@suse.de. You can email him and explain that kdelibs3 conflicts with kdebase3 in the current packages that are posted on the ftp site. He should be aware of this by now but since the supplementry directory is "unsupported" he's a bit slow sometimes to fix these issues. You can always findout who has had their hands on a pkg by executing this... rpm -qa --changelog foo being the name of the pkg. -- Linux User #147972 ---===--- mailto:ben@whack.org -- "There is no need to teach that stars can fall out of the sky and land on a flat Earth in order to defend religious faith."