Re: git-2.12.3-1: Cannot push to a remote with a Windows network path URL

2017-10-30 Thread Jonathan Chan
Hopefully I'm not breaking etiquette, but an update may be useful for
others.

It looks like this issue is no longer an issue in git-2.14.3-1, though it
may be fixed in earlier releases.
The relevant patch is probably https://github.com/git/git/commit/496f256
merged into master for 2.13.4.

The earliest Cygwin git with this fix was probably git-2.14.0-1 released
2017-08-09.

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple



Re: git-2.12.3-1: Cannot push to a remote with a Windows network path URL

2017-06-23 Thread Jonathan Chan
Thanks for the quick response :)

$ git remote -vv
origin  file:network/path/to/git-repository (fetch)
origin  file:network/path/to/git-repository (push)

> Your URL is invalid.
> Try file://network/path/to/git-repository
$ git remote add testing file://network/path/to/git-repository
$ git remote -vv
origin  file:network/path/to/git-repository (fetch)
origin  file:network/path/to/git-repository (push)
testing  file://network/path/to/git-repository (fetch)
testing  file://network/path/to/git-repository (push)
$ git fetch origin
$ git fetch testing
fatal: '/path/to/git-repository' does not appear to be a git repository
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

To be thorough:
$ git remote set-url testing //network/path/to/git-repository
$ git remote -vv
origin  file:network/path/to/git-repository (fetch)
origin  file:network/path/to/git-repository (push)
testing  //network/path/to/git-repository (fetch)
testing  //network/path/to/git-repository (push)
$ git push testing test:master
Counting objects: 3, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (2/2), done.
Writing objects: 100% (3/3), 276 bytes | 0 bytes/s, done.
Total 3 (delta 1), reused 1 (delta 0)
remote: error: object directory
/network/path/to/git-repository/objects does not exist; check
.git/objects/info/alternates.
remote: fatal: unresolved deltas left after unpacking
error: remote unpack failed: unpack-objects abnormal exit
To //network/path/to/git-repository
 ! [remote rejected]   test -> master (unpacker error)
error: failed to push some refs to '//network/path/to/git-repository'
Fetching works with both "origin" and "testing" remotes. Pushing does not.

To be even more thorough:
$ cd ~/Temp
$ git clone file:network/path/to/git-repository
Cloning into 'git-repository'...
remote: Counting objects: 53426, done.
remote: Compressing objects: 100% (10982/10982), done.
remote: Total 53426 (delta 32970), reused 53361 (delta 32921)
Receiving objects: 100% (53426/53426), 33.85 MiB | 8.15 MiB/s, done.
Resolving deltas: 100% (32970/32970), done.
Checking out files: 100% (2240/2240), done.
$ rm -rf git-repository
$ git clone file://network/path/to/git-repository
Cloning into 'emf'...
fatal: '/path/to/git-repository' does not appear to be a git repository
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

So cloning works with the "file:..." URL.

On Fri, Jun 23, 2017 at 2:29 AM, Andrey Repin <anrdae...@yandex.ru> wrote:
> Greetings, Jonathan Chan!
>
>> After updating to git-2.12.3-1, I have been unable to push to a remote
>> with a Windows network path URL:
>> $ git push origin
>> Counting objects: 3, done.
>> Delta compression using up to 4 threads.
>> Compressing objects: 100% (2/2), done.
>> Writing objects: 100% (3/3), 273 bytes | 0 bytes/s, done.
>> Total 3 (delta 1), reused 1 (delta 0)
>> remote: error: object directory
>> /network/path/to/git-repository/objects does not exist; check
>> .git/objects/info/alternates.
>> remote: fatal: unresolved deltas left after unpacking
>> error: remote unpack failed: unpack-objects abnormal exit
>> To file:network/path/to/git-repository
>>   ! [remote rejected]   master -> master (unpacker error)
>> error: failed to push some refs to
>> 'file:network/path/to/git-repository'
>
> Your URL is invalid.
> Try file://network/path/to/git-repository
>
>> Notes:
>> - Fetching works
>> - Pushing works if I use EGit (in Eclipse)
>> - Pushing works if I change the remote URL to use a drive mapped to
>> the network path
>
>> Additional searching turned up Issue #979 on git-for-windows:
>> https://github.com/git-for-windows/git/issues/979
>
>> Issue #979 appears to have been fixed in git and included in
>> 2.11.1..2.13.1 releases:
>> 
>> https://github.com/git/git/commit/7814fbe3f1e7cea1a675408df7b5dd1f5be731cc
>
>> I did not encounter this behavior prior to git-2.12.2-1. This is for x86_64.
>
>
> --
> With best regards,
> Andrey Repin
> Friday, June 23, 2017 12:28:54
>
> Sorry for my terrible english...
>

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple



git-2.12.3-1: Cannot push to a remote with a Windows network path URL

2017-06-22 Thread Jonathan Chan
After updating to git-2.12.3-1, I have been unable to push to a remote
with a Windows network path URL:
$ git push origin
Counting objects: 3, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (2/2), done.
Writing objects: 100% (3/3), 273 bytes | 0 bytes/s, done.
Total 3 (delta 1), reused 1 (delta 0)
remote: error: object directory
/network/path/to/git-repository/objects does not exist; check
.git/objects/info/alternates.
remote: fatal: unresolved deltas left after unpacking
error: remote unpack failed: unpack-objects abnormal exit
To file:network/path/to/git-repository
  ! [remote rejected]   master -> master (unpacker error)
error: failed to push some refs to 'file:network/path/to/git-repository'

Notes:
- Fetching works
- Pushing works if I use EGit (in Eclipse)
- Pushing works if I change the remote URL to use a drive mapped to
the network path

Additional searching turned up Issue #979 on git-for-windows:
https://github.com/git-for-windows/git/issues/979

Issue #979 appears to have been fixed in git and included in
2.11.1..2.13.1 releases:
https://github.com/git/git/commit/7814fbe3f1e7cea1a675408df7b5dd1f5be731cc

I did not encounter this behavior prior to git-2.12.2-1. This is for x86_64.

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple