* [meta-ti][scarthgap/master][PATCH] layer: add github MIRRORS definitions @ 2025-11-07 1:01 rs 2025-11-07 1:05 ` PRC Automation 2025-11-07 1:22 ` Denys Dmytriyenko 0 siblings, 2 replies; 6+ messages in thread From: rs @ 2025-11-07 1:01 UTC (permalink / raw) To: praneeth, reatmon, denis; +Cc: meta-ti 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 ^ permalink raw reply related [flat|nested] 6+ messages in thread
* Re: [meta-ti][scarthgap/master][PATCH] layer: add github MIRRORS definitions 2025-11-07 1:01 [meta-ti][scarthgap/master][PATCH] layer: add github MIRRORS definitions rs @ 2025-11-07 1:05 ` PRC Automation 2025-11-07 1:22 ` Denys Dmytriyenko 1 sibling, 0 replies; 6+ messages in thread From: PRC Automation @ 2025-11-07 1:05 UTC (permalink / raw) To: Randolph Sapp; +Cc: praneeth, reatmon, denis, meta-ti meta-ti / na / 20251107010115.1974047-2-rs PRC Results: FAIL ========================================================= check-yocto-patches: PASS ========================================================= Patches ---------------------------------------- All patches passed ========================================================= apply-yocto-patch: PASS ========================================================= scarthgap ===================== Summary: - Patch Series: [meta-ti][scarthgap/master][PATCH] layer: add github MIRRORS definitions - Submitter: From: <rs@ti.com> From: Randolph Sapp <rs@ti.com> - Date: Date: Thu, 6 Nov 2025 19:01:16 -0600 - Num Patches: 1 - Mailing List (public inbox) Commit SHA: 20f49577563b42818b14c485636e117652dd7335 Applied to: - Repository: lcpd-prc-meta-ti - Base Branch: scarthgap-wip - Commit Author: Vishnu Singh <v-singh1@ti.com> - Commit Subject: recipes-bsp: Add TI PCM6240 ADC firmware recipe - Commit SHA: 92a0b3c1bc93bc8d62b5140b7e1d4a45c6f9e65b Patches ---------------------------------------- All patches applied master ===================== Summary: - Patch Series: [meta-ti][scarthgap/master][PATCH] layer: add github MIRRORS definitions - Submitter: From: <rs@ti.com> From: Randolph Sapp <rs@ti.com> - Date: Date: Thu, 6 Nov 2025 19:01:16 -0600 - Num Patches: 1 - Mailing List (public inbox) Commit SHA: 20f49577563b42818b14c485636e117652dd7335 Applied to: - Repository: lcpd-prc-meta-ti - Base Branch: master-wip - Commit Author: Ryan Eatmon <reatmon@ti.com> - Commit Subject: conf: j784s4: Add k3_bist tie-test-builds config - Commit SHA: baccfb9302822df66ff0d9435a28be1a80d3865f Patches ---------------------------------------- All patches applied ========================================================= check-yocto-repo: FAIL ========================================================= scarthgap ===================== PASS master ===================== FAIL WARN: .bbappend files might need a guard to make them check-layer compliant. (GUARD-1) meta-ti-bsp/dynamic-layers/openembedded-layer/recipes-ti/initramfs/packagegroup-ti-core-initramfs.bbappend Code Summary ============ GUARD-1 ------------------------------------------- To maintain Yocto Compatibility, we need to add a guard around the .bbappend files for upstream recipes. In the event that a layer is simply included in a build, it should not make changes to the recipe in a way that breaks the upstream recipe from doing what it sets out to do. In order for our .bbappends to actually make changes, we need to gate them behind building something either the Arago distribution or building a TI machine. ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [meta-ti][scarthgap/master][PATCH] layer: add github MIRRORS definitions 2025-11-07 1:01 [meta-ti][scarthgap/master][PATCH] layer: add github MIRRORS definitions rs 2025-11-07 1:05 ` PRC Automation @ 2025-11-07 1:22 ` Denys Dmytriyenko 2025-11-07 2:59 ` Res Sapp 1 sibling, 1 reply; 6+ messages in thread From: Denys Dmytriyenko @ 2025-11-07 1:22 UTC (permalink / raw) To: rs; +Cc: praneeth, reatmon, meta-ti 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 ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [meta-ti][scarthgap/master][PATCH] layer: add github MIRRORS definitions 2025-11-07 1:22 ` Denys Dmytriyenko @ 2025-11-07 2:59 ` Res Sapp 2025-11-07 3:17 ` Denys Dmytriyenko 0 siblings, 1 reply; 6+ messages in thread From: Res Sapp @ 2025-11-07 2:59 UTC (permalink / raw) To: denis, rs; +Cc: praneeth, reatmon, meta-ti 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. - Randolph ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [meta-ti][scarthgap/master][PATCH] layer: add github MIRRORS definitions 2025-11-07 2:59 ` Res Sapp @ 2025-11-07 3:17 ` Denys Dmytriyenko 2025-11-07 4:00 ` Res Sapp 0 siblings, 1 reply; 6+ messages in thread From: Denys Dmytriyenko @ 2025-11-07 3:17 UTC (permalink / raw) To: Res Sapp; +Cc: rs, praneeth, reatmon, meta-ti 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. ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [meta-ti][scarthgap/master][PATCH] layer: add github MIRRORS definitions 2025-11-07 3:17 ` Denys Dmytriyenko @ 2025-11-07 4:00 ` Res Sapp 0 siblings, 0 replies; 6+ messages in thread From: Res Sapp @ 2025-11-07 4:00 UTC (permalink / raw) To: Denys Dmytriyenko, Res Sapp; +Cc: rs, praneeth, reatmon, meta-ti On Thu Nov 6, 2025 at 9:17 PM CST, Denys Dmytriyenko wrote: > 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. Fair enough. I think this should be allowed. Other layers adjust MIRRORS in specific recipes, but this variable still ends up being globally referenced. If necessary I can request oe-core append a DISTRO_MIRRORS/LAYER_MIRRORS section to the mirrors.bbclass. Would be a little cleaner I suppose. ^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2025-11-07 4:00 UTC | newest] Thread overview: 6+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2025-11-07 1:01 [meta-ti][scarthgap/master][PATCH] layer: add github MIRRORS definitions rs 2025-11-07 1:05 ` PRC Automation 2025-11-07 1:22 ` Denys Dmytriyenko 2025-11-07 2:59 ` Res Sapp 2025-11-07 3:17 ` Denys Dmytriyenko 2025-11-07 4:00 ` Res Sapp
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.