SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I've built a bunch of packages over the past few years, but I haven't done much with patches. What's required to apply this patch and get things working?
Has anyone one got akonadi to work under Slackware 13.0 x86_64 stable with 4.3.1 package? It's not really that critical to me but it bothers me that it doesn't work. I upgraded to the new mysql package under -current to get the innod inclusion peice. However I have still had no luck. I can generally get past the mysql stuff but akonadi has issues registering with d-bus.
and on that note, if anyone downloaded the 4.3.2 packages before the BUILD tag included "_vb", then you may need to reinstall the kde packages (including oxygen-icons, soprano, PyQt, sip, akonadi, ktorrent, skanlite)
either using "slackpkg reinstall" or download the new packages from -current and "upgradepkg --install-new --reinstall"
this new kde stuff (+dependencies) should go to slackware(64)-13.0/patches
Of course it won't.
The /patches directory of any Slackware release is for security fixes, not for software upgrades. You can always upgrade to slackware-current.
Of course it won't.
The /patches directory of any Slackware release is for security fixes, not for software upgrades. You can always upgrade to slackware-current.
Eric
Of course it won't, was clear and it is more wish I have couse it would spare me a lot of administration time and kde cost me already enought time (and nerves) until now.
there was some xpdf security problem in the last time.
(sorry for the trial, but I have currently somehow enough of doing system administration tasks, need time and concentration for my every day(real) work)
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.