[SOLVED] How recover from damage from slackpkg 'upgrade' (scilab) ?

jrch · 06-26-2019, 05:55 PM

Thanks 'luvr' - whoever you are.

It DOES work. 'Law of Unintended Consequences' strikes again!

I admire your persistence and nongiveup-itess. I will have to study your post some more to try to understand how you found that link to what we are doing.

It works here as well, all those still-present 'miscellaneous errors' were always there before when running scilab, here.

So as far as I am concerned, this is 'Solved'. Thanks to all who contributed time and effort!

jrc

jrch · 06-26-2019, 06:00 PM

Just to make it clear, I applied this simple fix by 'luvr' just now, but the current installation DOES HAVE Alien's 'openjdk-8u212_b04-x86_64-1alien.txz' installed as the java suite.

jrc

jrch · 06-26-2019, 06:57 PM

Comments helping solve this:

1. 'montagdude' suggested I do 'ls -lrt /var/log/packages', which allowed me to see the packages upgraded on June 23; I then posted that list of 18 upgraded packages here.

2. 'luvr' eventually noticed the presence of 'libpng' in my list, and an apparent conflict with the 'redist' folder in the scilab installation. 'luvr' then just renamed that folder and presto: scilab worked.

3. I applied that fix to my installation as well. It now works as before.

4. Several people suggested that the problem was the use of Oracle's jdk 8u202, instead of openjdk. This has not been firmly established; 'luvr' has openjdk installed now, as do I, and it works for us both. But, I don't think anyone on here has tried this 'fix' with Oracle's 8u202 installed.

Thanks to all who contributed suggestions here, I learned a lot in the process.

jrc

luvr · 06-27-2019, 12:11 AM

Quote:

Originally Posted by jrch

Thanks 'luvr' - whoever you are.

You're welcome, 'jrch' - whoever you are.

Glad I could help!

luvr · 06-29-2019, 03:23 PM

Oh, by the way, …

Quote:

Originally Posted by jrch

The comments in 'blacklist' say that,

'Automated upgrade of kernel packages aren't a good idea ... if you think the same, uncomment the lines below...' (I take the advice here, to NOT automatically upgrade kernels...is this somehow wrong??) ..

… this is totally right.

However, without further action on your part, your Slackware system will, then, not receive any updated kernels. To keep your Slackware kernel up-to-date, you will have to use the ‘installpkg’ command—which will install a package, but leave older versions of the package installed. If you haven’t yet worked out how to go about this in practice, you may want to look at the thread on keeping slackware up-to-date for some ideas.

Shameless Plug:

The second post on that thread explains how I keep my Slackware systems updated.

kingbeowulf · 06-29-2019, 10:51 PM

Thanks to all for working through this issue. I have an updated scilab-6.0.2 ready for SBo. I've added a comment in the README about $HOME/.Scilab and the need to log out and back in so that all the profile scripts get run to find the appropriate paths. The big fix (thanks luvr!) was the lib version conflicts in /opt/scilab/lib/thirdparty/redist:

Code:

libncurses.so -> libncurses.so.5.5
libncurses.so.5 -> libncurses.so.5.5
libncurses.so.5.5
libncurses.so.5.5.debug
libpng16.so
libpng16.so -> libpng16.so.16.34.0
libpng16.so.16 -> libpng16.so.16.34.0
libpng16.so.16.34.0
libpng16.so.16.34.0.debug
libxml2.so -> libxml2.so.2.9.1
libxml2.so.2 -> libxml2.so.2.9.1
libxml2.so.2.9.1
libxml2.so.2.9.1.debug
libz.so -> libz.so.1.2.8
libz.so.1 -> libz.so.1.2.8
libz.so.1.2.8
libz.so.1.2.8.debug

The Slackware versions of these are either the same, newer or plenty good enough. openjdk-8u202 should work (not tested); tested on jdk-8u202.