AUTOREV problems

AUTOREV problems

[Seth Bollinger]

[-- Attachment #1: Type: text/plain, Size: 1411 bytes --]

Hello All,

I've been having some serious problems trying to get my image to rebuild
recipes when their upstream repositories have changed.  I have SRCREV =
${AUTOREV} in my recipe and in bitbake -e I see these 2 lines:
# SRCREV=${AUTOREV}
SRCREV="AUTOINC"

I've found BB_SRCREV_POLICY and I've set that explicitly to clear, even
though that seems to be the default.  Auto didn't seem to work, even though
it looks like it should from the code.

When I try rebuilding my recipe, it seems to find that everything is cached
and doesn't even attempt the fetch, even though I know the repository has
changed (that's the reason I want to rebuild :)).  I've tried whacking
tmp/cache/*, but that didn't help.  I tried whacking the stamp for
do_fetch.  That didn't help unless I explicitly built using the "fetch"
command, then it at least appeared to fetch.  However, when I tried to
build the image after that, it didn't try to rebuild the recipe that had
just fetched.

The only way I could get it to rebuild was to cleansstate on the recipe and
then rebuild the image.  I assume this isn't the way it should be working.

1.  What is the expected operation of bitbake builds for recipes using
autorev?
2.  How can I get my autorev recipes to rebuild when their repositories
change?
3.  If this is working for everyone else, how can I find what I have
screwed up?  :)

Thanks,

Seth

[-- Attachment #2: Type: text/html, Size: 1823 bytes --]

Re: AUTOREV problems

[Tomas Frydrych]

Hi,

On 22/10/12 12:56, Seth Bollinger wrote:
> 1.  What is the expected operation of bitbake builds for recipes using
> autorev?

It should just work (and FWIW, it's working here).

> 2.  How can I get my autorev recipes to rebuild when their repositories
> change?
> 3.  If this is working for everyone else, how can I find what I have
> screwed up?  :)

It's hard to say without seeing the recipe in question.

Tomas

Re: AUTOREV problems

[Jerrod Peach]

[-- Attachment #1: Type: text/plain, Size: 2548 bytes --]

Seth,

Like Tomas said, it's hard to say for sure without seeing the recipe in
question, but I know one way this could happen: AUTOREV, by itself, does
not permute your hash.  It ends up just resolving to the string "AUTOINC"
every time.  You *also *need the SRCPV variable somewhere in your recipe,
as it will contain the real revision the was retrieved from version
control.  I believe the normal way to use SRCPV is as follows:

PV = "<vcs>-<version>-${SRCPV}"

For example:

PV = "svn-1.0.0-${SRCPV}"

If you aren't using SRCPV, your hash won't permute, and you won't rebuild.

The reason for this behavior isn't obvious off-hand, but I suspect it's so
you can set AUTOREV for a specific package in local.conf and not force half
the world to get reparsed every time a revision updates.

Kind regards,

Jerrod

On Mon, Oct 22, 2012 at 7:56 AM, Seth Bollinger <seth.boll@gmail.com> wrote:

> Hello All,
>
> I've been having some serious problems trying to get my image to rebuild
> recipes when their upstream repositories have changed.  I have SRCREV =
> ${AUTOREV} in my recipe and in bitbake -e I see these 2 lines:
> # SRCREV=${AUTOREV}
> SRCREV="AUTOINC"
>
> I've found BB_SRCREV_POLICY and I've set that explicitly to clear, even
> though that seems to be the default.  Auto didn't seem to work, even though
> it looks like it should from the code.
>
> When I try rebuilding my recipe, it seems to find that everything is cached
> and doesn't even attempt the fetch, even though I know the repository has
> changed (that's the reason I want to rebuild :)).  I've tried whacking
> tmp/cache/*, but that didn't help.  I tried whacking the stamp for
> do_fetch.  That didn't help unless I explicitly built using the "fetch"
> command, then it at least appeared to fetch.  However, when I tried to
> build the image after that, it didn't try to rebuild the recipe that had
> just fetched.
>
> The only way I could get it to rebuild was to cleansstate on the recipe and
> then rebuild the image.  I assume this isn't the way it should be working.
>
> 1.  What is the expected operation of bitbake builds for recipes using
> autorev?
> 2.  How can I get my autorev recipes to rebuild when their repositories
> change?
> 3.  If this is working for everyone else, how can I find what I have
> screwed up?  :)
>
> Thanks,
>
> Seth
>
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
>

[-- Attachment #2: Type: text/html, Size: 3528 bytes --]

Re: AUTOREV problems

[Jerrod Peach]

[-- Attachment #1: Type: text/plain, Size: 2887 bytes --]

Correction: I'm wrong on the standard for PV.  The standard (after looking
through some BB files) appears to be this:

PV = "<version number>+<vcs>${SRCPV}"

On Mon, Oct 22, 2012 at 8:46 AM, Jerrod Peach <peachj@lexmark.com> wrote:

> Seth,
>
> Like Tomas said, it's hard to say for sure without seeing the recipe in
> question, but I know one way this could happen: AUTOREV, by itself, does
> not permute your hash.  It ends up just resolving to the string "AUTOINC"
> every time.  You *also *need the SRCPV variable somewhere in your recipe,
> as it will contain the real revision the was retrieved from version
> control.  I believe the normal way to use SRCPV is as follows:
>
> PV = "<vcs>-<version>-${SRCPV}"
>
> For example:
>
> PV = "svn-1.0.0-${SRCPV}"
>
> If you aren't using SRCPV, your hash won't permute, and you won't rebuild.
>
> The reason for this behavior isn't obvious off-hand, but I suspect it's so
> you can set AUTOREV for a specific package in local.conf and not force half
> the world to get reparsed every time a revision updates.
>
> Kind regards,
>
> Jerrod
>
> On Mon, Oct 22, 2012 at 7:56 AM, Seth Bollinger <seth.boll@gmail.com>wrote:
>
>> Hello All,
>>
>> I've been having some serious problems trying to get my image to rebuild
>> recipes when their upstream repositories have changed.  I have SRCREV =
>> ${AUTOREV} in my recipe and in bitbake -e I see these 2 lines:
>> # SRCREV=${AUTOREV}
>> SRCREV="AUTOINC"
>>
>> I've found BB_SRCREV_POLICY and I've set that explicitly to clear, even
>> though that seems to be the default.  Auto didn't seem to work, even
>> though
>> it looks like it should from the code.
>>
>> When I try rebuilding my recipe, it seems to find that everything is
>> cached
>> and doesn't even attempt the fetch, even though I know the repository has
>> changed (that's the reason I want to rebuild :)).  I've tried whacking
>> tmp/cache/*, but that didn't help.  I tried whacking the stamp for
>> do_fetch.  That didn't help unless I explicitly built using the "fetch"
>> command, then it at least appeared to fetch.  However, when I tried to
>> build the image after that, it didn't try to rebuild the recipe that had
>> just fetched.
>>
>> The only way I could get it to rebuild was to cleansstate on the recipe
>> and
>> then rebuild the image.  I assume this isn't the way it should be working.
>>
>> 1.  What is the expected operation of bitbake builds for recipes using
>> autorev?
>> 2.  How can I get my autorev recipes to rebuild when their repositories
>> change?
>> 3.  If this is working for everyone else, how can I find what I have
>> screwed up?  :)
>>
>> Thanks,
>>
>> Seth
>>
>> _______________________________________________
>> yocto mailing list
>> yocto@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto
>>
>>
>

[-- Attachment #2: Type: text/html, Size: 4193 bytes --]

AUTOREV problems

[Seth Bollinger]

Hello All,

I've been having some serious problems trying to get my image to rebuild
recipes when their upstream repositories have changed.  I have SRCREV =
${AUTOREV} in my recipe and in bitbake -e I see these 2 lines:
# SRCREV=${AUTOREV}
SRCREV="AUTOINC"

I've found BB_SRCREV_POLICY and I've set that explicitly to clear, even
though that seems to be the default.  Auto didn't seem to work, even though
it looks like it should from the code.

When I try rebuilding my recipe, it seems to find that everything is cached
and doesn't even attempt the fetch, even though I know the repository has
changed (that's the reason I want to rebuild :)).  I've tried whacking
tmp/cache/*, but that didn't help.  I tried whacking the stamp for
do_fetch.  That didn't help unless I explicitly built using the "fetch"
command, then it at least appeared to fetch.  However, when I tried to
build the image after that, it didn't try to rebuild the recipe that had
just fetched.

The only way I could get it to rebuild was to cleansstate on the recipe and
then rebuild the image.  I assume this isn't the way it should be working.

1.  What is the expected operation of bitbake builds for recipes using
autorev?
2.  How can I get my autorev recipes to rebuild when their repositories
change?
3.  If this is working for everyone else, how can I find what I have
screwed up?  :)

Thanks,

Seth