Re: Shutting down of the git-daemon (git protocol, https and ssh still remain)

[Claudius Heine <ch@denx.de>]

Hi Quentin,

On 2024-06-12 12:37 pm, Quentin Schulz wrote:
> Hi Claudius,
> 
> On 6/12/24 12:20 PM, Claudius Heine wrote:
>> Hi everyone,
>>
>> in the past we used cgit, which provided cloning the u-boot repo via 
>> http, https, ssh and the git protocol.
>>
>> When we migrated to gitlab, which doesn't support the git protocol, we 
>> implemented some additional service files to continue to support it 
>> for some of our git repositories.
>>
>> We just noticed that cloning via the git protocol is currently broken, 
>> likely some changes in gitlab happened and we would need to recreate 
>> the symlinks on the server to point to the right repositories again.
>>
>> Since that is another thing to maintain and keep up, we would like to 
>> just shut the git protocol down. AFAIK most projects moved to use 
>> https for cloning anyway, since there were not many reports of broken 
>> cloning.
>>
>> What are your thoughts? Is it worth the effort to keep the git 
>> protocol up?
>>
> 
> On the side of OpenEmbedded-Core, HTTPS is being used since Langdale 
> (4.1) and the first dot release of Kirkstone (4.0.1) so only outdated 
> layers would be impacted (provided they aren't already, but since 
> there's a download cache system in Yocto, it's possible they're hitting 
> their own local cache instead of fetching it from your server(s)).
> 
> It's never nice to see things going/breaking compatibility because it 
> may break old builds which is always a nice trick up one's sleeve to 
> figure out when things started to go wrong in one's image.

Well, this happens all the time, but maintaining backwards compatibility 
here should be done in a best-effort way.

With old build, they likely need old compilers and systems, which will 
probably break anyway if they use https or ssh, because obsolete crypto. 
If people want to build old stuff, they probably have to fiddle around 
everywhere anyway, or have a download cache.

The internet, or any network, isn't nice to old systems...

> Also, while I 
> checked OE-Core, other third party/community maintained layer could be 
> impacted. I assume this is the case of meta-amarula-engicam[1] and 
> meta-allwinner-hx[2] for example.
> 
> I would suggest sending a mail to the different build systems mailing 
> lists, I assume https://lists.openembedded.org/g/openembedded-devel and 
> https://lists.yoctoproject.org/g/yocto for the OE-Core/YP side? Either 
> to ask for their opinion or notify them (and specifically third party 
> layers) it's going away or both.

Not sure if I want to go through them all. Looking into all these 3rd 
party, downstream repos and informing everyone seems to be even more 
effort than maintaining the git protocol.

And if someone uses their repo, they will notice it quickly and can 
easily fix it.

Anyway, I fixed it yesterday, and it doesn't make much sense to stop it 
now. So I will leave it in place until it breaks again, then I just 
remove it.

thanks everyone for their input,
Claudius

> 
> [1] 
> https://github.com/amarula/meta-amarula-engicam/blob/master/recipes-bsp/u-boot/u-boot-common_2018.05.inc
> [2] 
> https://gitlab.com/dimtass/meta-allwinner-hx/blob/master/recipes-bsp/u-boot/u-boot-common.inc
> 
> Cheers,
> Quentin

-- 
DENX Software Engineering GmbH,        Managing Director: Erika Unter
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-54 Fax: (+49)-8142-66989-80 Email: ch@denx.de