i just changed Swaret from version 10.2 to "current" and it did a bunch of new updates, and now KDE wont load :/
startkde: Starting up...
ksplash: error while loading shared libraries: libacl.so.1: cannot open
shared object file: No such file or directory
kdeinit: error while loading shared libraries: libacl.so.1: cannot open
shared object file: No such file or directory
startkde: Could not start kdeinit. Check your installation.
Error: Can't open display:
Warning: connect() failed: : No such file or directory
ksmserver: cannot connect to X server
ERROR: Couldn't attach to DCOP server!
startkde: Shutting down...
Warning: connect() failed: : No such file or directory
Error: Can't contact kdeinit!
startkde: Running shutdown scripts...
startkde: Done.


Is the "current" branch unstable or something?

[EDIT]

When i do a dep check it says alot of files are not found too :/ this is a new install

Current is fine but some time ago some new packages were made - acl and attr.

Looks like you need to install acl package with swaret or slackpkg

A user shouldn't really ever use current. Packages are built against eachother and are installed to work with eachother, and when a certain amount of stability is achieved the branch becomes a release.

Using current means you give up all of those things to use newer packages that probably contain no new features that you actually need.

Not to mention that automatic tools in slackware are really unable to upgrade between releases without dependency support, so you'll end up in your situation.

If I've gotten a nickel for every time I've said that, I'd be able to buy Microsoft.....

I've said it before: swaret is evil if doing a 'upgrade' to current, 'specially with the '-a' switch.

I'm running 'current', but only because I did a 'clean' install of it (not an upgrade), using a mirror of 'current' on my local nfs server.

Valuable lesson learned, I guess. Only update within the installed version. Mostly because of issues like yours when 'current' is so far along, it's more like a different version than an 'upgrade' to 10.2.

I'm not saying it's not possible, just going to be ALOT of work, more than, imho, it's worth.

thank you for the repleies though

Guess im still too noob for that then.

I was just following the instructions i found in the stickied post at the top where it talks about swaret setup

It would be fine if it was just after the release of 10.2, where they would still be close, but it's actually closer to 10.3/11 that it's hard to 'upgrade' now. Not impossible, but very hard....

ok i got ya next update release ill see about goin to current right after

Thatway i can keep ontop of the changes as they happen and know whats going on

just go here and search for whatever the error message says is missing:

http://slackware.it/en/pb/search.php...t&t=2&q=libacl

Assuming you did "swaret --update" first (which will put those packages in the list), installation is easy.

swaret --install acl will find the correct package name for "acl" and ask if you want to install it. Same goes for swaret --install attr.

You might have to run ldconfig afterwards, though.