After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 776217 - https:// http:// and git:// all throwing error in gnome-buiilder3.22.3 clone page
https:// http:// and git:// all throwing error in gnome-buiilder3.22.3 clone ...
Status: RESOLVED FIXED
Product: gnome-builder
Classification: Other
Component: plugins
unspecified
Other Linux
: Normal major
: ---
Assigned To: GNOME Builder Maintainers
GNOME Builder Maintainers
Depends on:
Blocks:
 
 
Reported: 2016-12-17 20:08 UTC by Vivek
Modified: 2017-02-15 04:19 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
above shows the error (33.37 KB, image/png)
2016-12-17 20:08 UTC, Vivek
Details
libgit2 user agent original (11.89 KB, image/png)
2016-12-19 16:33 UTC, sébastien lafargue
Details
libgit2 user agent changed (14.39 KB, image/png)
2016-12-19 16:34 UTC, sébastien lafargue
Details

Description Vivek 2016-12-17 20:08:10 UTC
Created attachment 342129 [details]
above shows the error

git clone not working in gb3.22.3
Comment 1 Christian Hergert 2016-12-17 21:02:47 UTC
How have you installed Builder (from source, jhbuild, packages, flatpak?) On what distribution?
Comment 2 Matthew Leeds 2016-12-18 00:17:17 UTC
Using gnome-builder master built from jhbuild, I also get the 403 error when trying to clone git.gnome.org/browse/gnome-music via https:// or http:// (I can't get git:// to work for that repo even from the command line). However, cloning github.com/mwleeds/android-malware-analysis from Builder works with https://, http://, and git://. So perhaps it's something specific to git.gnome.org?

I did notice that there's an extra forward slash after git.gnome.org when I go to the URL in firefox; not sure if that's relevant.

I checked my ~/.gitconfig and the line that translates https:// into ssh://git@ is commented out, so that can't be the issue.
Comment 3 Vivek 2016-12-18 05:12:30 UTC
(In reply to Christian Hergert from comment #1)
> How have you installed Builder (from source, jhbuild, packages, flatpak?) On
> what distribution?

i have installed gb using flatpak over gnome-buntu 16.10 .
Comment 4 Vivek 2016-12-18 05:19:30 UTC
I came across this problem and  looking forward to resolve it . Developers please help me out. (how can i using flatpak as i have also gb using jhbuild but the master has given me with 3.20.4 .It might be as i built 3 weeks ago .)
Comment 5 sébastien lafargue 2016-12-18 22:12:07 UTC
Same for me, everything look fine from Builder side, i have let a message to #sysadmin in case
Comment 6 sébastien lafargue 2016-12-19 16:26:50 UTC
After investigation, seems that libgit2 use a user agent "git/1.0", blocked by your server config:

https://infrastructure.gnome.org/browse/puppet/tree/modules/httpd/files/sites.d/git.gnome.org.conf#n81

I have tried using in Builder:

git_libgit2_opts (GIT_OPT_SET_USER_AGENT, "git/1.6.6");

but it's only a way to append to the existing string so i get:

"git/1.0 (git/1.6.6)" still matching the bad agent regex

What i can't understand is why it happen now, there's no recent changes on the server config, nor libgit2
Comment 7 sébastien lafargue 2016-12-19 16:33:54 UTC
Created attachment 342224 [details]
libgit2 user agent original
Comment 8 sébastien lafargue 2016-12-19 16:34:21 UTC
Created attachment 342225 [details]
libgit2 user agent changed
Comment 9 sébastien lafargue 2016-12-19 18:35:51 UTC
from #sysadmin:

<ovitters> slaf: inefficient clients are blocked, efficient clients are allowed

<ovitters> slaf: if one connection is opened and then everything is done, it is efficient. old clients opened thousands of connections

It's clear that libgit2 should update their user agent version
Comment 10 sébastien lafargue 2016-12-19 19:49:17 UTC
ho, i have forgotten:

You can use git:// protocol, it works like:
git://git.gnome.org/gnome-calendar (so without the /browse part)
Comment 11 Vivek 2016-12-19 19:53:09 UTC
(In reply to sébastien lafargue from comment #10)
> ho, i have forgotten:
> 
> You can use git:// protocol, it works like:
> git://git.gnome.org/gnome-calendar (so without the /browse part)

and also everything works fine for github.com i mean to say
https://github.com/---.git
Comment 12 Christian Hergert 2016-12-19 23:41:16 UTC
I've updated the flatpak builds to patch libgit2 so that it says "git/1.7" instead of "git/1.0".

I've also talked to the libgit2 maintainer, and it sounds like we might get an update of the version string in the next RC.
Comment 13 Matthew Leeds 2017-02-03 19:17:04 UTC
This appears to have been fixed by https://github.com/libgit2/libgit2/commit/fafafb1f37d21ebf4b0bbf02651b910d842cfe27 so once we upgrade to v0.25.1 we can drop the patch.
Comment 14 Matthew Leeds 2017-02-15 04:19:00 UTC
This has been fixed by commit c1489fd8d and commit 14cc0f65d