The SCM-Manager is lightweight and flexible, with many benefits. The SCM-Manager gives you full control over your source code, and allows you to manage Mercurial, Subversion, and Git repositories. It's easy to keep track of your team's progress with detailed branching diagrams. Keep track of your work and keep up-to-date with your code. Changes can be made by the file, hunk, or line. Visualize your work, and then push with confidence. It is a fully-featured GUI that allows for consistent, efficient development right out of the box. With a single click, you can access information about any branch or commit. You can review changesets, stash, cherry pick between branches, and many other things. Advanced users will be even more productive with a Git client. You can say goodbye to the command-line - a Git client simplifies distributed version control and brings everyone up to speed quickly. Sourcetree's simple Git GUI allows you to visualize and manage your repositories.
Sourcetree makes it easy to interact with your Git repositories, so you can concentrate on coding. When I want to know the package version should I be looking for package version and not the package name? which is in this case 1.0.2n according to this website īy symlink openssl 1.1 to openssl 1.0.Simple and powerful in a beautiful Git GUI. So normally, it's providing the same version as TW libopenssl1_0_0 package. I didn't figure that much because the package name is libssl1.0.0. TSUDoes this mean that the package that I have from ubuntu repo is for openssl 1.0.1. You might also submit a bug to that we probably should be packaging libssl 1.0.1 instead of or in addition to libssl 1.0.0.Īn interesting try might have been to symlink openssl 1.1 to openssl 1.0.1 to see if the app would work. On TW while it appears that openssl 1.0.0 is available, you should have openssl 1.1 installed which is more current than what their code requires. I'm guessing that their code requires openssl 1.0.1 exactly Without looking at the code but based on your results, Note: only ubuntu lib worked for me the lib form the other distribution package doesn't seems to work.IMO you should submit a bug to Axosoft. Normally, I have now to lock the package libopenssl1_0_0 in yast so that it doesn't update and replace my new files. If so if there any similar solution that doesn't have drawbacks. I have a question about this, can this solution lead to a problem in the future. Then, I have replaced my system similar files /usr/lib64/ libcrypto.so.1.0.0 and /usr/lib64/ libssl.so.1.0.0 with this Ubuntu lib that I got.
I have manage to solve all the problems and get gitkraken to work.įirst I got the two lib libcrypto.so.1.0.0 and libssl.so.1.0.0 from a ubuntu based package libssl1.0.0_1.0.2n-1ubuntu6_b (/usr/lib/gitkraken/resources/app.asar/node_modules/nodegit/dist/nodegit.js:1145:3)Do you have any idea how to fix this problem.
(/usr/lib/gitkraken/resources/app.asar/node_modules/nodegit/dist/nodegit.js:12:12)Īt Object. usr/lib64/libcrypto.so.1.0.0: version `OPENSSL_1.0.1' not found (required by /usr/lib/gitkraken/resources//node_modules/nodegit/build/Release/nodegit.node)Įrror: /usr/lib64/libcrypto.so.1.0.0: version `OPENSSL_1.0.1' not found (required by /usr/lib/gitkraken/resources//node_modules/nodegit/build/Release/nodegit.node)Īt process.module.(anonymous function) (ELECTRON_ASAR.js:166:20)Īt Object.Module._extensions.node (module.js:671:18)Īt Object.module.(anonymous function) (ELECTRON_ASAR.js:180:18)Īt Function.Module._load (module.js:496:3)Īt Object.
0 kommentar(er)
