Re: [yocto-patches] [meta-rockchip][PATCH] linux-torvalds-next: use AUTOREV

[Trevor Woerner <twoerner@gmail.com>]

On Tue 2024-06-18 @ 12:04:48 PM, Quentin Schulz via lists.yoctoproject.org wrote:
> Hi Trevor,
> 
> On 6/18/24 1:07 AM, Trevor Woerner via lists.yoctoproject.org wrote:
> > Already the SRCREV that was used for -next has been rebased out of existence.
> 
> Mmmm, no. It's still there, just not in the master branch.
> 
> > Also that tag that was originally proposed no longer exists. With a repository
> 
> It still exists. https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/log/?h=next-20240611

Yesterday at noon my time I cloned the linux-next repository on a machine I
had never done this build on and that tag and commit ID were not there, and
this is still true:

	$ git tag
	...
	next-20230310
	next-20230314
	next-20230315
	next-20230316
	next-20230317
	next-20230829
	next-20240613
	v2.6.11
	v2.6.11-tree
	v2.6.12
	v2.6.12-rc2
	...

	$ git show a957267fa7e9159d3d2ee1421359ebf228570c68
	fatal: bad object a957267fa7e9159d3d2ee1421359ebf228570c68

	$ git pull
	...

	$ git tag
	...
	next-20230829
	next-20240613
	next-20240617
	v2.6.11
	v2.6.11-tree
	v2.6.12
	v2.6.12-rc2
	...

	$ git show a957267fa7e9159d3d2ee1421359ebf228570c68
	fatal: bad object a957267fa7e9159d3d2ee1421359ebf228570c68

> > that is rebased so regularly, the only thing we can safely use to hope for
> > valid builds that don't need to be tweaked every few days is AUTOREV.
> > 
> 
> Or... use ;tag=next-20240611 in the git fetcher and force people to use the
> network for radxa-zero-e boards.
> 
> I personally would vote for using the tag instead of AUTOREV. Kernel
> maintainers rarely (have they ever done it?) move tags around so that should
> be fine. Whereas using AUTOREV on linux-next is basically hoping that
> nothing breaks from a development branch, maybe too much to ask for right
> now?

When I click on the commit of the link you provided earlier it says: "Notice:
this object is not reachable from any branch". If the tag is not accessible
from any branch then I can't specify a branch to the fetcher. If I don't
specify the branch to the fetcher then I get flooded with "...you didn't
specify a branch, and we're going to make this mandatory soon..." messages,
flooded!

I also got an email from someone yesterday who had tried the radxa-zero-3w
build and it failed for them. When I do the builds on my machine that I've
been using for development, the build succeeds (because the repository
predates the assumed rebasing). If I then go to the ${DL_DIR}/git2/ directory
and delete the linux-next repository, then retry the build, it fails.

When I try the build on a machine that has never done this build, it fails.

I started my change yesterday by using the "tag=next-20240611" addition to the
fetcher and was surprised when the build failed on a different build machine.

I think AUTOREV is that safest bet here.