On Thu, 2017-12-07 at 11:08 -0600, Marcelo E. Magallon wrote: --snip!-- > My concern right now is a *different* case, where your goal is to modify > the class in order to affect all the recipes

From: Aníbal Limón <anibal.limon@...> Signed-off-by: Aníbal Limón <anibal.limon@...> --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md

From: Aníbal Limón <anibal.limon@...> In some ptest packages exists symlink in the ptest directory causing to load/run twice the same ptest, For example in perl5: /usr/lib/perl ->

From: Aníbal Limón <anibal.limon@...> Signed-off-by: Aníbal Limón <anibal.limon@...> --- Makefile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Makefile

From: Aníbal Limón <anibal.limon@...> Signed-off-by: Aníbal Limón <anibal.limon@...> --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md

From: Aníbal Limón <anibal.limon@...> In some ptest packages exists symlink in the ptest directory causing to load/run twice the same ptest, For example in perl5: /usr/lib/perl ->

From: Aníbal Limón <anibal.limon@...> Signed-off-by: Aníbal Limón <anibal.limon@...> --- Makefile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Makefile

A release candidate build for yocto-2.4.1.rc1 is now available at: https://autobuilder.yocto.io/pub/releases/yocto-2.4.1.rc1 Please begin QA on this build as soon as possible. Build hash

Hi, I'm in the process of cleaning up our usage of Yocto with the goal of improving longer-term maintainability, basically implementing something like

A recipe will rebuild if you change SRCREV or SRC_URI in it. What are you trying to do? Alex

I take it that this is not possible?

This command is very complicated to setup. It is easier for us to use it via the "whitelist" method. This isn't being done in a layer that will be released, otherwise I would. This is internal use

AUH will simple leave all commits in the repo, succeessful and failed. Even successful upgrades may need further work before they can be submitted. It's useful to mark failed ones as problematic

I'm not sure about this one. Commits shouldn't be created automatically on a person's behalf and then also signed-off - I'd say you need to first look at them. Alex

I have removed the logic that removes commits and manipulates branches altogether. AUH will always create a commit on the current branch, even if it caused a build or testimage failure, and otherwise

This one I have to reject. The loop that is executing the upgrade steps should not have to know or care what they are. Alex

Currently that is the intended behaviour. The fetcher is what is responsible for detecting if something changes, and re-fetching, etc. The fetcher only knows about the files on the SRC_URI (or the

Thanks, these do make sense. I'll integrate them into my devtool (and other fixes) work - hope to publish it in the next few days. Alex

I had added alexander.kanavin@... in the cc list, but it was gone, looks strange, now add him again. // Robert

It doesn't make any sense to build it when skip compile. Signed-off-by: Robert Yang <liezhi.yang@...> --- upgradehelper.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git