slackware current broken?

sweetnsourbkr · 03-09-2006, 07:35 PM

Am I the only one having missing libs/dependency problems when updating to the latest current?

gilead · 03-09-2006, 07:49 PM

What packages are you having problems with? I check for updates each weekend and as at last weekend it was fine for my installs. Now I'm curious as to what will happen this weeked

sweetnsourbkr · 03-09-2006, 07:53 PM

I fixed it. But here was the problem:

I'm using slackpkg to leech from current. For some reason, it never upgraded cairo, so everything that had a cairo dependency would not work. I went through the current changelog and found the package. Installed it, and now I'm good to go. Just be careful, you need to have the following package installed:

cairo-1.0.2-i486-1.tgz

in order for the libs to be compatible, for some reason. Somehow, that never got updated from 10.2.

gilead · 03-09-2006, 08:35 PM

I'll have a look at the list of packages on my installs - thanks for that

mlangdn · 03-09-2006, 09:02 PM

Cairo was not in 10.2, so it would not have upgraded. Has to be installed, not upgraded.

quip · 03-09-2006, 10:28 PM

That's why the automatic tools can get 'ya. Don't get me wrong, I use slackpkg on one machine and gslapt on the other two, but sometimes Pat adds a package that's needed, and since there's no dependency checking, stuff chokes. I had a similar problem with kmail recently. It's always good to take a quick look at the Changelog.

J.W. · 03-09-2006, 11:22 PM

Additionally and perhaps obviously, "current" should, at best, be considered beta. If you want to avoid unexpected surprises, go with the latest official release

sweetnsourbkr · 03-11-2006, 01:20 AM

Yep. I knew as much. Always a learning experience, and that's what makes it fun!

davidsrsb · 03-11-2006, 07:26 AM

There a few new packages recently, cairo was the only obvious one unless you run xfs file system