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 was in the mood of bumping my 14.2 installation to -current to mess a bit with Eric's latest plasma5, but then I noticed the very recent poppler .so bump in the changelog and I got scared of breakages (also since judging by his latest blog post, Eric seems on pause with his packages updates).
Can someone confirm that indeed the plasma5 packages are now broken or can I go on with no doubts?
You can check the ktown ChangeLog.txt to see if it was updated since poppler was upgraded in Slackware. As of right now, it was last updated July 3rd, so not before the poppler update (July 20th).
However, looking at the changelog entry for poppler, the only KDE app that was recompiled was caligra (as well as cups-filter, texlive, and tumbler), so it's very likely it will still work.
thanks bassmadrigal, my doubts regarded exactly the amount of components broken by the update.
Looking at previous happenings of the sort, I'm afraid that plasma5 could be quite a bit more dependent on poppler than kde4.
I think I'll sit out for this one and enjoy the rock solidness a bit longer
The list below shows all packages with name matching "poppler".
[ Status ] [ Repository ] [ Package ]
installed ktown poppler-0.66.0-x86_64-1alien
installed slackware64 poppler-data-0.4.9-noarch-1
uninstalled(masked) slackware64 poppler-0.67.0-x86_64-1
I am back in business and will have to build up some infrastructure first. Then I can start compiling whole new Plasma 5 package set. You need to have a bit of patience, things are not yet all going according to plan here. But I'll try to get a new Chromium out first (security update).
Here, here! You've been missed, Eric! Your post about being "indisposed" had us native English speakers fearing you'd been struck down by some terrible lurgy! Very glad to hear you are back in the saddle!
Here, here! You've been missed, Eric! Your post about being "indisposed" had us native English speakers fearing you'd been struck down by some terrible lurgy! Very glad to hear you are back in the saddle!
May as well comment... even though issue will be resolved soon.
Ktown is working great here. No issues. I have installed slackpkg+, that will prevent packages installed as part of ktown from being upgraded when they are updated in -current. This also means my other "non-slack" packages that depend on poppler are working ok.
As noted by RadicalDreamer's Post, poppler-0.66.0-x86_64-1alien is part of ktown, poppler-0.67.0-x86_64-1 is masked, no upgrade will take place.
Of course once the next update to ktown is release, I will have to do some rebuilds of my "non-slack" packages. <grin>
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.