Simple: tags aren't guaranteed to not change what it references, the
hash is guaranteed to always point to the same thing. Thus, git is
double checking that the meaning of the tag hasn't changed.
On Thu, 2012-09-20 at 16:32 -0400, William Mills wrote:
> On 09/20/2012 04:08 PM, Evade Flow wrote:
> > To bring this full circle... if you want to build behind a restrictive
> > firewall using pre-mirrored sources and BB_NO_NETWORK, be aware that
> > recipes which:
> >
> > 1. Specify a git repo as the source, and,
> >
> > 2. Specify the revision to be built using a tag name
> >
> >
> > will cause your build to abort when bitbake tries to run 'git ls-remote'
> > to resolve the tag name. So don't specify SRC_URI like this:
> >
> >
> > SRC_URI =
> > "git://git.kernel.org/pub/scm/utils/kernel/kmod/kmod.git;protocol=git;tag=v${PV}"
> >
> > Instead, use:
> >
> > SRC_URI =
> > "git://git.kernel.org/pub/scm/utils/kernel/kmod/kmod.git;protocol=git;tag=8885ced062131214448fae056ef453f094303805;branch=master"
> >
> >
> > I added a note about this to the Wiki:
> >
> > -
> > http://wiki.yoctoproject.org/wiki/How_do_I#Non-networked_Builds_and_Cached_Git_Respositories
> >
> > I'm still new to Yocto, so someone please chime in if any of this
> > information is incorrect...
> >
>
> If true, this seems very unfortunate. This seems to push people in the
> wrong direction. Is there a reason the fetchers don't pull down the
> tags when they mirror in the first place?
>
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
