Re: [meta-ti][scarthgap/master][PATCH] layer: add github MIRRORS definitions

[Denys Dmytriyenko <denis@denix.org>]

On Thu, Nov 06, 2025 at 08:59:26PM -0600, Res Sapp wrote:
> On Thu Nov 6, 2025 at 7:22 PM CST, Denys Dmytriyenko via lists.yoctoproject.org wrote:
> > I wonder how that will affect the signatures for the YP Compat... [Not even 
> > talking about evil github reliance...]
> >
> >
> > On Thu, Nov 06, 2025 at 07:01:16PM -0600, rs@ti.com wrote:
> >> From: Randolph Sapp <rs@ti.com>
> >> 
> >> We have some projects mirrored to GitHub currently. It makes sense to
> >> add a MIRRORS entry for git.ti.com sources to fall back on in the event
> >> git.ti.com is unreachable.
> >> 
> >> Placing this in the main BSP layer configuration file should be all that
> >> is required for this and any other layers that depend this core layer to
> >> fall back to GitHub.
> >> 
> >> Signed-off-by: Randolph Sapp <rs@ti.com>
> >> ---
> >> 
> >> Tested locally by making git.ti.com ns lookups return NXDOMAIN and then
> >> requesting to fetch linux-ti-staging.
> >> 
> >>  meta-ti-bsp/conf/layer.conf | 5 +++++
> >>  1 file changed, 5 insertions(+)
> >> 
> >> diff --git a/meta-ti-bsp/conf/layer.conf b/meta-ti-bsp/conf/layer.conf
> >> index e3a28628..d87d040b 100644
> >> --- a/meta-ti-bsp/conf/layer.conf
> >> +++ b/meta-ti-bsp/conf/layer.conf
> >> @@ -36,3 +36,8 @@ TI_COMMON_DEPLOY ?= "${TOPDIR}/deploy-ti"
> >>  DEPLOY_DIR_IMAGE:ti-soc = "${TI_COMMON_DEPLOY}/images/${MACHINE}"
> >>  SDK_DEPLOY:ti-soc = "${TI_COMMON_DEPLOY}/sdk"
> >>  PSEUDO_IGNORE_PATHS:append:ti-soc = ",${TI_COMMON_DEPLOY}"
> >> +
> >> +MIRRORS += " \
> >> +    git://git.ti.com/.* git://github.com/TexasInstruments/BASENAME;protocol=https \
> >> +    gitsm://git.ti.com/.* gitsm://github.com/TexasInstruments/BASENAME;protocol=https \
> >> +"
> >> -- 
> >> 2.51.1
> 
> I hate M$ as much as anyone else, but reliable infrastructure as a *fallback* is
> still useful. As far as signatures go, you guys have been doing this in
> meta-arago with the arago distro since 2019.

Yes, meta-arago is not yet fully YP Compat yet - we are still figuring it out.