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:
On Thu, Sep 20, 2012 at 3:12 PM, Evade Flow wrote:
> This doesn't appear to be done in a couple of the Yocto recipes:
>
> - meta/recipes-devtools/btrfs-tools/btrfs-tools_git.bb
> - meta/recipes-devtools/mtd/mtd-utils_1.4.9.bb
>
good. Send patches we will accept.
> SRCREV is not set in either
> You should not need to be specifying the revision within SRC_URI as you are
> doing, however, it is correct that you must specify the revision in
> SRCREV...
This doesn't appear to be done in a couple of the Yocto recipes:
- meta/recipes-devtools/btrfs-tools/btrfs-tools_git.bb
- meta/recipe
On Thursday 20 September 2012 16:08:41 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 t
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 na
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 bitba
Fortunately, you caught me before I pulled out a bigger hammer. :-} I was
going to report that this still didn't work after typing:
% bitbake -c cleanstate
But re-reading your post, I saw that there were supposed to be two 'esses'[!]
The following:
% bitbake kmod -c cleansstate
% bitbake k
On Thursday 20 September 2012 09:30:19 Evade Flow wrote:
> I guess I'll try the BFI approach of restarting the build from scratch next.
> `:-o.
We'd really rather people didn't do this as it does not help us to diagnose
and fix problems.
> Incidentally, searching the OpenEmbedded manual for 'c
On 2012-09-20 07:30, Evade Flow wrote:
Try doing 'bitbake kmod -c cleansstate;bitbake kmod' - does that still fail?
Thanks for the suggestion. I get this when I try to run 'bitbake kmod -c
cleanslate':
ERROR: Task do_cleanslate does not exist for target kmod
typo: it needs to be 'cleanss
> Try doing 'bitbake kmod -c cleansstate;bitbake kmod' - does that still fail?
Thanks for the suggestion. I get this when I try to run 'bitbake kmod -c
cleanslate':
ERROR: Task do_cleanslate does not exist for target kmod
Because I don't know any better, I tried this instead:
% bitbake km
On Wednesday, September 19, 2012, Gary Thomas wrote:
> On 2012-09-19 16:30, Evade Flow wrote:
>>>
>>> I'm just trying to build the thing. :-) I'll try converting the tag
>>> name into a commit hash and see if that helps, thanks a lot...
>>
>> ::SIGH:: I changed the SRC_URI var in kmod.inc from t
On 2012-09-19 16:30, Evade Flow wrote:
I'm just trying to build the thing. :-) I'll try converting the tag
name into a commit hash and see if that helps, thanks a lot...
::SIGH:: I changed the SRC_URI var in kmod.inc from this:
SRC_URI =
"git://git.kernel.org/pub/scm/utils/kernel/kmod/km
> I'm just trying to build the thing. :-) I'll try converting the tag
> name into a commit hash and see if that helps, thanks a lot...
::SIGH:: I changed the SRC_URI var in kmod.inc from this:
SRC_URI =
"git://git.kernel.org/pub/scm/utils/kernel/kmod/kmod.git;protocol=git;tag=v${PV}"
to thi
I'm not sure how to answer your questions, unfortunately, this is all
quite new to me. I'm not the maintainer of said layer, and don't know
anything at all yet about 'layer etiquette'. There does seem to be a
README.md file in meta-systemd, though:
- http://git.yoctoproject.org/cgit/cgit.cgi/met
On 2012-09-19 11:15, Evade Flow wrote:
Where did you get that meta-systemd layer?
From here:
- http://git.yoctoproject.org/cgit/cgit.cgi/meta-systemd/
Why are there conflicting meta-systemd layers (and pointers thereto)??
This layer in git.yoctoproject.org doesn't seem even "legal" - wh
> Where did you get that meta-systemd layer?
>From here:
- http://git.yoctoproject.org/cgit/cgit.cgi/meta-systemd/
On Wed, Sep 19, 2012 at 12:50 PM, Gary Thomas wrote:
> On 2012-09-19 10:34, Evade Flow wrote:
>>
>> Trying to build the meta-ivi discovery-image behind a firewall is
>> proving
On 2012-09-19 10:34, Evade Flow wrote:
Trying to build the meta-ivi discovery-image behind a firewall is
proving to be quite a challenge. I tried modifying my conf/local.conf
file as follows:
CONNECTIVITY_CHECK_URIS=""
BB_GENERATE_MIRROR_TARBALLS = "1"
SOURCE_MIRROR_URL ?= "file:///home/evadeflo
Trying to build the meta-ivi discovery-image behind a firewall is
proving to be quite a challenge. I tried modifying my conf/local.conf
file as follows:
CONNECTIVITY_CHECK_URIS=""
BB_GENERATE_MIRROR_TARBALLS = "1"
SOURCE_MIRROR_URL ?= "file:///home/evadeflow/projects/poky-mirror/"
INHERIT += "own-
18 matches
Mail list logo
