[SOLVED] Git error after today's batch of updates in -current

kikinovak · 10-30-2015, 07:07 AM

Hi,

I have Slackware -current running on a box for testing and development purposes. After today's batch of updates, Git seems broken. Here's what I get:

Code:

[root@buildbox:microlinux] # git pull
git-remote-https: error while loading shared libraries: libssh2.so.1: cannot open shared 
object file: No such file or directory

What now?

ponce · 10-30-2015, 07:16 AM

I think you missed

Code:

slackpkg install-new

ppr:kut · 10-30-2015, 07:16 AM

Do you have libssh2 installed?

Quote:

n/libssh2-1.6.0-x86_64-1.txz: Added.

kikinovak · 10-30-2015, 07:19 AM

OK, I just found out what was wrong. aaa_elflibs is blacklisted in slackpkg's default configuration, so it went under the radar. I commented it out and updated it, and everything's OK now.

Problem solved, thanks.

volkerdi · 10-30-2015, 01:04 PM

Quote:

Originally Posted by kikinovak

OK, I just found out what was wrong. aaa_elflibs is blacklisted in slackpkg's default configuration, so it went under the radar. I commented it out and updated it, and everything's OK now.

Problem solved, thanks.

If that's all that you did, then you'll still need to install the new libssh2 package.

kikinovak · 10-30-2015, 02:45 PM

Quote:

Originally Posted by volkerdi

If that's all that you did, then you'll still need to install the new libssh2 package.

Yeah, I thought about installing the new additions. Thanks!

Just out of curiosity: how comes aaa_elflibs is blacklisted in slackpkg's default configuration?

Didier Spaier · 10-30-2015, 02:59 PM

Quote:

Originally Posted by kikinovak

Just out of curiosity: how comes aaa_elflibs is blacklisted in slackpkg's default configuration?

There is a sticky thread about that

the3dfxdude · 10-30-2015, 03:04 PM

Quote:

Originally Posted by kikinovak

Yeah, I thought about installing the new additions. Thanks!

Just out of curiosity: how comes aaa_elflibs is blacklisted in slackpkg's default configuration?

That was the original advice. I do not know how true it is anymore. The thing to watch out for is using slackpkg on -current. I'm not sure if slackpkg should be used on -current due to periodic special scenarios such as this. slackpkg could be made to handle aaa_elflibs automatically following drmozes' advice, but personally I never use slackpkg, so I do not know if this should be in it's design. If slackpkg remains the same, people need to watch the changelog closely in -current for certain keywords such as "aaa_elflibs".

willysr · 10-30-2015, 08:17 PM

Quote:

Originally Posted by kikinovak

Yeah, I thought about installing the new additions. Thanks!

Just out of curiosity: how comes aaa_elflibs is blacklisted in slackpkg's default configuration?

slackpkg is designed to run for -stable
it does work for -current too, but requires more considerations, so that's why several part of important/core packages are blacklisted