Re: linux-media checkout failing for KernelCI

[Mauro Carvalho Chehab <mchehab@kernel.org>]

Em Fri, 17 May 2024 19:56:27 +0100
Mauro Carvalho Chehab <mchehab@kernel.org> escreveu:

> Em Fri, 17 May 2024 09:45:53 -0400
> Gustavo Padovan <gus@collabora.com> escreveu:
> 
> > ...linuxtv-ci mailing-list rejected me for not being a member, so moving 
> > to the media list.
> > 
> > On 5/17/24 09:41, Gustavo Padovan wrote:  
> > >
> > > Hi Media maintainers,
> > >
> > > We are struggling to use the media tree, in the same way we usually 
> > > virtually all other trees in KernelCI. The following commands gives 
> > > KernelCI a fatal error.
> > >
> > > git clone 
> > > git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
> > > cd linux
> > > git remote add media https://git.linuxtv.org/media_tree.git
> > > git remote update media
> > > git fetch --tags https://git.linuxtv.org/media_tree.git
> > > fatal: Couldn't find remote ref HEAD  
> 
> First of all, the best is to use, instead, media_stage.git, as this
> contains the most recent patches. You should notice, however, that
> we might need to rebase media_stage.git. That doesn't happen often,
> but if you use it for CI, just in case, be sure that it will do a
> 
> 	git reset --hard FETCH_HEAD
> 
> To avoid potential problems if a rebase is needed.
> 
> We periodically update media_tree.git as well (which never rebases),
> but the update is manual. I usually do it once per week between
> -rc1 to -rc7, by the time I handle myself pull requests.
> 
> For CI, the best is to use media_stage.git.
> 
> -
> 
> With regards to merge/fetch, please use the git protocol
> whenever possible, e. g.:
> 
> 	git://linuxtv.org/media_tree.git
> 	git://linuxtv.org/media_stage.git
> 
> you may, alternatively use:
> 
> 	https://linuxtv.org/git/media_tree.git
> 	https://linuxtv.org/git/media_stage.git
> 
> The 4 above url's are handled by git daemon.
> 
> If you use, instead:
> 
> 	https://git.linuxtv.org/media_tree.git
> 
> It will use cgit, which will try to do the right thing, but
> results may not be consistent, as the main goal for cgit is to
> provide a web visual interface (which is IMO a *lot* better than
> what git??b provides).
> 
> The problem with https is that it may require a hook during
> push time to update https references:
> 
> 	git update-server-info

I actually changed the setup today, removing the need of having
such hook, and dropping it from all repositories there. Now,
the https server (either via cgit or directly) shouldn't need it
anymore.

I suspect that the problem of having HEAD outdated/broken from time
to time should be gone now, and all 3 alternatives should work
properly.

Please let me know if you find any issues.

Regards,
Mauro