Re: Latest upgrade broke Aegyptan

On Wed 07 Jan 2004 8:07 pm, Bob Underwood wrote: > On Wednesday 07 January 2004 8:53 pm, Doug Holland wrote: > > I had kmail working fine with Aegyptan until the last KDE update, > > now when I try to send a signed message, It briefly shows the > > enter-your-passphrase dialog, but that quickly dis

Re: Packagers: What should we recommend about KDE 2 -> 3 upgrades?

On Wednesday 07 of January 2004 19:35, Ross Boylan wrote: > I would like to raise an issue for the Debian KDE package maintainers: > will someone who has been running woody KDE 2.2 run into troubles if > they upgrade to 3.x? And if so, what should we do about this? Probably, the safest way is t

Re: Latest upgrade broke Aegyptan

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wednesday 07 January 2004 8:53 pm, Doug Holland wrote: > I had kmail working fine with Aegyptan until the last KDE update, > now when I try to send a signed message, It briefly shows the > enter-your-passphrase dialog, but that quickly disappears an

Latest upgrade broke Aegyptan

I had kmail working fine with Aegyptan until the last KDE update, now when I try to send a signed message, It briefly shows the enter-your-passphrase dialog, but that quickly disappears and is replaced with an error message saying "This message could not be signed! The Crypto Plug-In '/usr/lib

Source Code

I would like to apt-get source code and projects that can be loaded into KDevelop so I can learn KDE programming. Can anyone help a young (sic), budding programmer? -- Comments are appreciated, Bob

Packagers: What should we recommend about KDE 2 -> 3 upgrades?

I would like to raise an issue for the Debian KDE package maintainers: will someone who has been running woody KDE 2.2 run into troubles if they upgrade to 3.x? And if so, what should we do about this? I asked about this earlier, but want to raise it a bit more forcefully now, because subsequent