Bug 2013288 - git clone git://gcc.gnu.org/git/gcc.git doesn't work before a firewall
Summary: git clone git://gcc.gnu.org/git/gcc.git doesn't work before a firewall
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: git
Version: 35
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Todd Zullinger
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-10-12 14:05 UTC by H.J. Lu
Modified: 2021-10-12 21:45 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-10-12 21:45:21 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description H.J. Lu 2021-10-12 14:05:30 UTC 
I am behind a firewall and using gitproxy:

exec socat - socks4:proxy-server-name:$1:$2

I got

$ git clone git://gcc.gnu.org/git/gcc.git 
Cloning into 'gcc'...
fetch-pack: unexpected disconnect while reading sideband packet
fatal: early EOF
fatal: fetch-pack: invalid index-pack output
$

Both

$ git clone --depth 1 git://gcc.gnu.org/git/gcc.git

and

$ git clone https://gcc.gnu.org/git/gcc.git

work.

I have no problem on Fedora 34.
Comment 1 Todd Zullinger 2021-10-12 15:19:23 UTC 
This is almost surely going to have to end up on the git list... but you might try to use:

    git -c protocol.version=1 clone git://gcc.gnu.org/git/gcc.git

to see if that has an effect.

The release notes mention a fix to fetching which affects the v2 protocol:

    https://github.com/git/git/commit/ae1a7eefff

Either way, I would suggest bringing this up on the git list as that's where the folks most likely to know the problem will be found.
Comment 2 H.J. Lu 2021-10-12 19:59:18 UTC 
$ git -c protocol.version=1 clone git://gcc.gnu.org/git/gcc.git

works.
Comment 3 H.J. Lu 2021-10-12 20:00:45 UTC 
git 2.33.0 fails and git 2.32.0 works.
Comment 4 H.J. Lu 2021-10-12 21:42:12 UTC 
"socat -t 10" also works.
Note You need to log in before you can comment on or make changes to this bug.