Install KDE 4.2.1 on Slackware 12.2

r00tb33r · 03-21-2009, 03:23 AM

What's the easiest way to install KDE 4.2.1 which is in slackware-current, but not in the DVD-ISO?
DVD-ISO included 3.5 which was installed.
I am not familiar with Slackware's package management and don't know how to properly install the entire KDE 4.2.1 and meeting all dependencies for shared libraries.
I simply installed all packages in the the slackware/kde directory on the server using pkgtool, but KDE 4 won't start up because of missing libraries. I manually downloaded and installed some of them using pkgtool, but now KDE crashes after running kdeinit4 back to KDM without showing any error messages.
I'm sure I'm doing this wrong, so I would like to know the proper way of downloading and installing packages satisfying all dependencies.
Thanks in advance!

bathory · 03-21-2009, 04:48 AM

You should use a tool like slapt-get, or swaret to download and install the new kde, as they can take care of dependencies.

Hangdog42 · 03-21-2009, 07:01 AM

At this point, I would not advise you to do it unless you move entirely to the -current branch. A couple of the initial releases of KDE4.2 in -current were compatible with 12.2 because -current hadn't moved on yet. However, now there are substantial differences between 12.2 and -current that do have an impact on KDE4.2.

If you do want to move to -current, read the UPGRADE.TXT and CHANGES_AND_HINTS.TXT files for detailed instructions on how to do the migration. Also be sure to look at the changelogs as those can have useful information about -current as well.

What I would NOT do is use a tool like slapt-get. Using those sorts of monstrosities to move from stable to current is going to cause serious problems.

r00tb33r · 03-22-2009, 01:22 AM

Quote:

Originally Posted by Hangdog42

At this point, I would not advise you to do it unless you move entirely to the -current branch. A couple of the initial releases of KDE4.2 in -current were compatible with 12.2 because -current hadn't moved on yet. However, now there are substantial differences between 12.2 and -current that do have an impact on KDE4.2.

If you do want to move to -current, read the UPGRADE.TXT and CHANGES_AND_HINTS.TXT files for detailed instructions on how to do the migration. Also be sure to look at the changelogs as those can have useful information about -current as well.

What I would NOT do is use a tool like slapt-get. Using those sorts of monstrosities to move from stable to current is going to cause serious problems.

Do you think I can just pick http/ftp source during DVD install and it would just install -current for me?
Or do I have to install 12.2 first and only then update to current?

r00tb33r · 03-22-2009, 04:09 AM

Quote:

Originally Posted by bathory

You should use a tool like slapt-get, or swaret to download and install the new kde, as they can take care of dependencies.

slapt-get did not check for dependencies. KDE 4.2.1 needs new qt and strigi, and lots of other stuff I don't know about, yet slapt-get did not install them. Perhaps those packages don't have dependency data or something.
Either way, this is definitely an annoyance. I don't have a working KDE right now.

metrofox · 03-22-2009, 06:14 AM

Do not use any slapt-get or swaret, they aren't good to upgrade the system. I made this mistake,I upgraded my slackware-current with the KDE updates(and others..)and slapt-get forgot qt package to install. So I can give you a little suggestion, download all updates on your system(you can even do it with slapt-get typing --download-only like option), once done, install them with

Code:

upgradepkg *.tgz

you've also to make sure to install these packages with the right sequence, or you'll have problems. Read the UPGRADE.TXT file to know which packages must to be installed first.

Hangdog42 · 03-22-2009, 07:52 AM

Quote:

Do you think I can just pick http/ftp source during DVD install and it would just install -current for me?
Or do I have to install 12.2 first and only then update to current?

In theory, installing straight from -current should work just fine. Just be aware that -current is the Slackware development branch and from time to time, things can get ugly.

Quote:

slapt-get did not check for dependencies. KDE 4.2.1 needs new qt and strigi, and lots of other stuff I don't know about, yet slapt-get did not install them. Perhaps those packages don't have dependency data or something.

Something you should be aware of is that Slackware does NOT support automated dependency resolution. Abominations like slapt-get and swaret have never worked particularly well because they rely on third-party repositories. If you need automatic dependency resolution, then I would suggest using a distro other than Slackware. However, if you don't mind administering your system as [INSERT FAVORITE DEITY HERE] intended, which means you resolve dependencies on your own, then Slackware is a good choice.

brianL · 03-22-2009, 08:05 AM

Or you could try using slackpkg. Comment (put # in front of) your 12.2 mirror in /etc/slackpkg/mirrors, and uncomment the current entry. Then run these commands (as root, of course):

Code:

slackpkg update
slackpkg install-new
slackpkg upgrade-all

Then, I'm not sure whether this is needed or what:

Code:

slackpkg clean-system

IGNORE THIS POST. Could cause serious problems.

skaldicpoet9 · 04-11-2009, 12:37 AM

Ok, so I was trying upgrade to KDE 4.2 and used the commands in the previous post and now I can't even get login to slack. It gives me the following error messages at startup:

Code:

INIT: cannot execute "/sbin/agetty"
INIT: Id "c1" respawning too fast: disabled for 5 minutes"

whenever I used slackpkg upgrade-all, it gave me a WARNING! stating that it could not find some directory and when I tried to use any program (firefox etc..) it said it could not locate those as well. I then restarted slack and then was given the errors stated above.

What can I do?

Hangdog42 · 04-11-2009, 07:05 AM

I suspect you're looking at a re-install. With all due respect to brianL, using slackpkg to upgrade from a stable Slackware release to current is like playing with a lit stick of dynamite. Sooner or later you're gonna lose, and lose big. Following the official upgrade instructions are really the only way to go.

One thing you might try to get control is to try booting into single user mode. Get to the LILO prompt, select your kernel and add the number 1 after it. That might give you control of your machine again (but I doubt it).

brianL · 04-11-2009, 11:46 AM

Sorry about that, skaldicpoet9. I tried that method, following a post in the Slackware forum that I can't find now, and it worked. So, for the benefit of anybody else coming across this thread, ignore my previous post (#8) and upgrade to current the correct way.

skaldicpoet9 · 04-12-2009, 01:29 AM

It's all good man, it's a learning experience, right? I'll have her up and running in no time again