You are not logged in.

Dear visitor, welcome to KDE-Forum.org. If this is your first visit here, please read the Help. It explains in detail how this page works. To use all features of this page, you should consider registering. Please use the registration form, to register here or read more information about the registration process. If you are already registered, please login here.

1

Wednesday, March 10th 2004, 10:10pm

Debian Packages for 3.2 or 3.2.1!!!

Ok, I just installed Debian from Knoppix 3.3 CD (which rocks by the way... why hadn't I found this sooner?)...

Now, I'm looking to update to KDE 3.2 or 3.2.1, but I can't find any KDE 3.2 packages now that 3.2.1 is out!! The sources listed in the Debian/KDE Wiki are there (one of them is) but I don't know how to configure my sources.list so that it recognizes the packages for dselect and apt-get. The Wiki says to put:
deb http://URL/ ./

I did that and apt-get update doesn't add the packages...

Any other sources?

Thanks!

2

Thursday, March 11th 2004, 3:42am

The line in /etc/apt/sources.list should be:

deb http://ftp.debian.org/debian/ unstable main contrib

which is quite possibly already there.
apt-get update should then find the 3.2.1 packages.
If you are just after kde 3.2.1 you might try saving your existing /etc/apt/sources.list to a backup filename then do a new sources.list with only this one line in it. Apt-get update will then go much faster.
You may have to remove the existing KDE 3.1, apt-get will see the existing packages as conflicts. I have had apt-get just quit with an error message something like 'Over 50 conflicts found, refusing to continue'.
I found it was absolutely necessary to remove the existing KDE before I could install 3.2 on Mandrake but of course that was with RPM's.
If you have to remove the existing KDE, set up an alternate first (I use xFCE) then apt-get remove anything kde (kdelibs-data should trash most of it in one go) then reboot before installing 3.2.
And also, if you are using an alternate WM in addition to KDE, be aware there is almost no way to access it after 3.2 is installed because the setup procedure for the login manager isn't finished yet. (see bug 75882)