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

[Marek Vasut <marex@denx.de>]

On 6/13/24 4:13 PM, Claudius Heine wrote:

Hi,

>> I suspect the following patch to oe-core (or local.conf equivalent) 
>> might also entirely mitigate the issue by providing https fallback 
>> automatically, without the need to modify the legacy layer/recipe ?
>>
>> If so, maybe this could be added to OE LTS releases at least ?
>>
>> "
>> diff --git a/meta/classes-global/mirrors.bbclass 
>> b/meta/classes-global/mirrors.bbclass
>> index 862648eec5..50a14c5881 100644
>> --- a/meta/classes-global/mirrors.bbclass
>> +++ b/meta/classes-global/mirrors.bbclass
>> @@ -77,6 +77,7 @@ https?://downloads.yoctoproject.org/mirror/sources/ 
>> https://mirrors.kernel.org/y
>>
>>   MIRRORS += "\
>>   git://salsa.debian.org/.* git://salsa.debian.org/PATH;protocol=https \
>> +git://git.denx.de/.*          git://git.denx.de/PATH;protocol=https \
> 
> Well the path will change a bit as well:
> 
> git://git.denx.de/u-boot.git -> https://source.denx.de/u-boot/u-boot.git
> git://git.denx.de/u-boot-efi.git -> 
> https://source.denx.de/u-boot/custodians/u-boot-efi.git

Better avoid custodian trees in OE builds unless this is a test build.

> git://git.denx.de/xenomai.git -> https://source.denx.de/xenomai/xenomai.git
> git://git.denx.de/mxssb.git -> https://source.denx.de/denx/mxssb.git

mxssb is I think long superseded by U-Boot mkimage integration, so this 
can also be dropped.

The remaining two, u-boot and xenomai, yeah, those would likely need to 
be separate.

> If we want to make it perfect, it will be more difficult than that.
> 
>>   git://git.gnome.org/.* 
>> git://gitlab.gnome.org/GNOME/PATH;protocol=https \
>>   git://git.infradead.org/.* git://git.infraroot.at/PATH;protocol=https \
>>   git://.*/.*                   git://HOST/PATH;protocol=https \
>> "
>>
>>> 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.
>>
>> Do you know how long it was actually broken ? (i.e. how long nobody 
>> noticed and complained about it?)
> 
> So since 3rd of June, so about 5-8 days or so until someone noticed.

Hum, since it works now again, I think we can wrap this discussion up.

However, maybe this can serve as a wake up call for people to switch to 
https cloning ?