[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Replacing Vcs-Git URIs to use https instead of git protocol



Hi Axel,

Thanks for your comments!

On Sat, Jan 30, 2016 at 03:39:51PM +0100, Axel Beckert wrote:
> Hi,
> 
> Salvatore Bonaccorso wrote:
> > Any objection to a mass commit to replace all Vcs-Git URI's which use
> > git as transport to use https?
> 
> I must admit, I wasn'tt very happy with that new lintian warning.
> 
> At least in the past, "git fetch" over HTTP(S) was not recommended due
> to massiv performance penalties over the native git protocol.
> 
> But having read
> https://git-scm.com/book/en/v2/Git-on-the-Server-The-Protocols#The-HTTP-Protocols
> since Git 1.6.6 there seem to be two different ways to do git over
> HTTP.
>
> Do we know which way Alioth uses? If it uses the new/smart way, I
> think that change is ok. Otherwise, I'd not recommend it.

Git 1.6.6 is even in Squeeze, so I can't immagine there are out git
servers set up with the 'dump http' variant. I might be proved wrong
though :-). Looking/Skimming quickly though over the fusionforge vhost
configs, it enables (/etc/gforge/httpd.conf.d/vhost-scm.conf) the git
smart http transport integration.

Furthermore this would not have an impact for us working on the
packages, since we still use the git+ssh transport.

Fine if I go ahead?

Note, some changes are as well needed to dpt-packagecheck. The one for
dh-make-perl for creating new packages is already done (reason: when
we create new packages we can follow straight what lintian suggests
for the Vcs-Git URI).

Regards,
Salvatore


Reply to: