[git-users] Re: git clone and package fatal error: symbol deflateBound: referenced symbol not found
Dear Team I am facing the similar kind of issue , request to help soon, bash-3.00$ export LD_LIBRARY_PATH=/usr/local/lib:/usr/sfw/lib:$LD_LIBRARY_PATH bash-3.00$ export LD_LIBRARY_PATH=/usr/lib:/usr/sfw/lib:$LD_LIBRARY_PATH bash-3.00$ git pull Already up-to-date. bash-3.00$ git push Counting objects: 1813, done. Delta compression using up to 32 threads. Compressing objects: 100% (1529/1529), done. ld.so.1: git: fatal: relocation error: file /usr/local/libexec/git-core/git: symbol deflateBound: referenced symbol not found error: pack-objects died of signal 9 error: failed to push some refs to 'isgit@111:SP/x.git' bash-3.00$ echo $LD_LIBRARY_PATH /usr/lib:/usr/sfw/lib:/usr/local/lib:/usr/sfw/lib:/usr/lib:/usr/local/lib:/usr/local/lib On Tuesday, October 23, 2012 9:44:03 PM UTC+5:30, Diego A. Torres wrote: Hello there, May some of you help me to troubleshoot this one?: Just download and installed packages for Solaris 10, as my server does not have exit to the internet, just follow: https://groups.google.com/forum/?fromgroups=#!searchin/git-users/solaris$20install/git-users/RupbBGmhWTM/R1l_Cyp9KU0J Now, I can create bare repositories, and everything seems to work well, but when removing the local repository folder and trying: $ git clone user@server:path/to/repository/repository.git I get the following error: error: pack-objects died of signal 9 error: git upload-pack: git-pack-objects died with error.remote: ld.so.1: git: fatal: relocation error: file /usr/local/libexec/git-core/git: symbol deflateBound: referenced symbol not found remote: aborting due to possible repository corruption on the remote side. fatal: git upload-pack: aborting due to possible repository corruption on the remote side.fatal: protocol error: bad pack header also, if i execute in the server: # cd /path/to/repository/repository.git # git repack I receive the following error: Counting objects: 3, done. ld.so.1: git: fatal: relocation error: file /usr/local/libexec/git-core/git: symbol deflateBound: referenced symbol not found Here some ideas: 1. Which libraries are involved in the package/repackage process? 2. Is there a command line process to follow in order to test the package process step by step? 3. Is there a verbose mode of the package process so we can see step by step what's happening and debug the process? Thanks in advance. Diego. -- 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.
[git-users] Re: Understanding Cherry-Pick
Dear Team , Need your help at earliest , i am getting following error while push commnad , bash-3.00$ export LD_LIBRARY_PATH=/usr/local/lib:/usr/sfw/lib:$LD_LIBRARY_PATH bash-3.00$ export LD_LIBRARY_PATH=/usr/lib:/usr/sfw/lib:$LD_LIBRARY_PATH bash-3.00$ git pull Already up-to-date. bash-3.00$ git push Counting objects: 1813, done. Delta compression using up to 32 threads. Compressing objects: 100% (1529/1529), done. ld.so.1: git: fatal: relocation error: file /usr/local/libexec/git-core/git: symbol deflateBound: referenced symbol not found error: pack-objects died of signal 9 error: failed to push some refs to 'isgit@172.x.x.x.:SP/xx.git' bash-3.00$ echo $LD_LIBRARY_PATH /usr/lib:/usr/sfw/lib:/usr/local/lib:/usr/sfw/lib:/usr/lib:/usr/local/lib:/usr/local/lib Thanks safi On Tuesday, September 2, 2014 9:29:06 PM UTC+5:30, Brian Wall wrote: Thank you both for your replies. Clearly I have more to learn about this, and the learning curve is steep with Git! But I'll mull it over and let it sink in. So what brought me down this road initially was going through the lessons at http://pcottle.github.io/learnGitBranching/. In the A Mixed Bag series of lessons, the first lesson is Grabbing just 1 commit. The use case is taking some buggy code, adding debug and print statements to it, tracking down the bug and fixing it, then merging just the bug fixes back in to master, without the debug and print statements. The link above is a great visual tool, but now I'd like to see a tangible example, because this use case is powerful if I can get it to work! Thanks again, Brian -- 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.
[git-users] Confusion about Key-based SSH authentication
Hi, every one! I recently read Git on the Server - Setting Up the Server http://git-scm.com/book/en/Git-on-the-Server-Setting-Up-the-Server, I have a confusion about this paragraph as below: Key-based SSH authentication usually enforces security by requiring restricted rights on the involved files. To prevent SSH from refusing to work, type this: $ chmod -R go= ~/.ssh --- I had once met this issue in practice, I suddenly can't connect to my server using ssh key, and I resolved it by executing the command as above. But I don't understand how it works, what does enforces security by requiring restricted rights on the involved files mean? Can anybody help me with this? Thanks very much -- 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.
Re: [git-users] Confusion about Key-based SSH authentication
From: Xavier Yin wonderera2...@gmail.com Hi, every one! I recently read Git on the Server - Setting Up the Server http://git-scm.com/book/en/Git-on-the-Server-Setting-Up-the-Server, I have a confusion about this paragraph as below: Key-based SSH authentication usually enforces security by requiring restricted rights on the involved files. To prevent SSH from refusing to work, type this: $ chmod -R go= ~/.ssh --- I don't know exactly what causes your issue, and I am not an expert in SSH. But I do know that the SSH server daemon enforces certain restrictions on the permissions of the files in ~user/.ssh. For security it is important that no-one other than the user can read any of the private key files. Similarly, it is important that no-one other than the user can modify any of the files in .ssh. When a client tries to authenticate as the user, the SSH daemon verifies that the files in ~user/.ssh meet these requirements, and if they do not, the daemon refuses the connection. Probably the easiest way to ensure that the .ssh directory meets these requirements is the chmod command listed above. Dale -- 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.
Re: [git-users] Confusion about Key-based SSH authentication
On Wed, 3 Sep 2014 09:09:39 -0400 wor...@alum.mit.edu (Dale R. Worley) wrote: Key-based SSH authentication usually enforces security by requiring restricted rights on the involved files. To prevent SSH from refusing to work, type this: $ chmod -R go= ~/.ssh --- I don't know exactly what causes your issue, and I am not an expert in SSH. But I do know that the SSH server daemon enforces certain restrictions on the permissions of the files in ~user/.ssh. For security it is important that no-one other than the user can read any of the private key files. Similarly, it is important that no-one other than the user can modify any of the files in .ssh. When a client tries to authenticate as the user, the SSH daemon verifies that the files in ~user/.ssh meet these requirements, and if they do not, the daemon refuses the connection. You're absolutely correct. One more point is that ~/.ssh on a server also typically contains a file named authorized_keys which is crucial for functioning of the pubkey-based authentication: this file contains fingerprints of the keys the account trusts to authenticate remote parties as the owner of this account and authorize them as such. Obviously, no one but the account's owner must have write access to this file, and this is also checked by the server. Directory/file insecurities related to SSH on the server are typically logged appropriately (on a stock Debian-based system that will be /var/log/auth.log). -- 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.
Re: [git-users] Confusion about Key-based SSH authentication
From: Konstantin Khomoutov flatw...@users.sourceforge.net Directory/file insecurities related to SSH on the server are typically logged appropriately (on a stock Debian-based system that will be /var/log/auth.log). On Fedora, it looks like they go into either /var/log/messages or /var/log/secure. Dale -- 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.
