On Tue, 21 Jul 2015 20:04:08 -0700 (PDT)
RK <ravikirangoud.palpano...@gmail.com> wrote:

> We are using git on AIX 6.1 server. Recently AIX patches
> applied on the AIX box and git stopped working. git is failing to
> extract the code. 
> Error attached . The error is mentioned below in blue color.
> <https://lh3.googleusercontent.com/-2FdsPT7FvE0/Va8H416bPkI/AAAAAAAAAUo/Z4LjS_JvzAI/s1600/git_Error.JPG>

Please refrain from posting screenshots of errors to a mailing list
until you're absolutely have no way to just copy and paste its text:
not everyone reads mailing lists using Google Groups web interface.

> Dependent module /usr/lib/libcrypto.a (libcrypto.so.1.0.1) could not
> be loaded.
> Member libcrypto.so.1.0.1 is not found in archive
> How to resolve this issue. It is stopping us to apply AIX patches
> which is mandatory as part of company policy. Please help.

This error most probably means that one of the recent "patches" -- as
you call them -- replaced the libcrypto software package with another
version which changed that library's name (say, to something like
libcrypto.so.1.0.2 -- you might just try to use your system's standard
tools to find all the files matching "libcrypto*" and see for yourself).

Since Git is not a package provided by AIX, the "patches" released by
AIX are not concerned with Git or any other software package installed
from external sources, and are free to replace any libraries Git
depends on, breaking it.  (If Git would be a standard part of AIX, it
would get updated in sync.)

So basically the choices you have are like this:

1) Manually maintain old versions of libraries your Git installation
   depends on.  Say, obtain a previous package containing the replaced
   libcrypto.so.1.0.1, extract it and place alongside with the new
   version with that library.

   The upside: relatively easy to achieve.

   The downsides:
   * Libraries get patched/upgraded on purpose: the new version might
     have fixed an important or critical security flaw.
   * Once you have hand-rolled files on your filesystem, this has to
     be thoroughly documented or -- better -- wrapped in their own
     custom packages (and then see option (2)).

2) If you have compiled your Git installation from the sources,
   just reconfigure it afresh, recompile and reinstall: the
   recompilation will pick the new versions of all the libraries
   and the resulting binary will work again.

   Ideally you should do this on a non-production box (or on a virtual
   machine), and create a package (using `checkinstall` or whatever
   there is suitable for AIX), test it, and then transfer to the
   production servers and install.

   Installing from sources on production machines is, in most cases,
   the least suitable solution because Makefiles in most software
   packages support the "install" target but not "uninstall", and hence
   after running `make install` you have no sensible way to remove all
   what was installed.

3) If you have obtained Git from an external source, just obtain a newer
   version, and if it works, use it.  This way you will rely on
   someone else doing the hard work.

   The upside is that it's super easy to employ.
   The downside is that you're trusting that person in that there's no
   malware/spyware/whatever in what they will deliver to your system.

   Please see [1, 2] and investigate the resources they link to.
   In essense, there is quite a number of unofficial software
   repositories hosting Git for AIX packages.

   Searching the list for the word "AIX" in the Google Web interface
   will bring more results (I have just did that).

1. https://groups.google.com/d/topic/git-users/-uVl99fQXlI/discussion
2. https://groups.google.com/d/topic/git-users/tq5vFid_Jqo/discussion

You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to