git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Bug pushing branch to new remote via SSH

From
DDDavid Dynerman <david@block-party.net>
Date
Aug 16, 2015, 01:56 UTC
Message-ID
<m2si7katdu.fsf@block-party.net>
Hello,

I am encountering a bizarre error message trying to push a branch to a new remote over SSH. The error message is

fatal: packfile name 'remotehost.com' does not end with '.pack'

Here, remotehost.com is the internet domain name of the remote host I'm trying to push to.

Obviously pushing to SSH remotes isn't broken generally, so I think this is caused by some bad state in my repository. But the error message seems odd enough that I think I might be encountering a bug.

If anyone has any hints on how to resolve this, I'd really appreciate it.

On my laptop, which is running OS X:

$ git fsck Checking object directories: 100% (256/256), done. Checking objects: 100% (398/398), done.

$ ssh remotehost.com "git init ~/git/my_repo --bare" Initialized empty Git repository in /home/user/git/my_repo/

$ git remote add remotehost ssh://remotehost.com/home/user/git/my_repo

$ git push remotehost master Counting objects: 405, done. Delta compression using up to 2 threads. Compressing objects: 100% (298/298), done. fatal: packfile name 'remotehost.com' does not end with '.pack' error: pack-objects died of signal 13 error: failed to push some refs to 'ssh://remotehost.com/home/user/git/my_repo/'

$ git --version git version 2.2.0

$ ssh remotehost.com "git --version" git version 1.7.10.1

Thank you very much, David

Message 1 of 1 in “Bug pushing branch to new remote via SSH”
  1. David DynermanAug 16, 2015

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.