From: Jonathan Liu <net147@gmail.com>
To: "Andreas Müller" <schnitzeltony@googlemail.com>
Cc: Yocto Project <yocto@yoctoproject.org>
Subject: Re: [meta-raspberrypi][PATCH v3] linux-raspberrypi.inc: use SRCPV instead of SRCREV for PV
Date: Sun, 4 Oct 2015 22:14:06 +1100 [thread overview]
Message-ID: <561109FE.3080807@gmail.com> (raw)
In-Reply-To: <CALbNGRT3tdQfngPbCxdt+rQZV-e1jeTVKfG6Yxz8EZqwCdaWoQ@mail.gmail.com>
On 4/10/2015 9:50 PM, Andreas Müller wrote:
> On Sun, Oct 4, 2015 at 4:15 AM, Jonathan Liu <net147@gmail.com> wrote:
>> SRCPV is intended to be used by PV. Using SRCREV for PV is incorrect.
>>
>> Signed-off-by: Jonathan Liu <net147@gmail.com>
>> ---
>> recipes-kernel/linux/linux-raspberrypi.inc | 3 ++-
>> 1 file changed, 2 insertions(+), 1 deletion(-)
>>
>> diff --git a/recipes-kernel/linux/linux-raspberrypi.inc b/recipes-kernel/linux/linux-raspberrypi.inc
>> index d60a3e9..70e8bfe 100644
>> --- a/recipes-kernel/linux/linux-raspberrypi.inc
>> +++ b/recipes-kernel/linux/linux-raspberrypi.inc
>> @@ -12,7 +12,8 @@ SRC_URI += " \
>>
>> COMPATIBLE_MACHINE = "raspberrypi"
>>
>> -PV = "${LINUX_VERSION}+git${SRCREV}"
>> +PE = "1"
>> +PV = "${LINUX_VERSION}+git${SRCPV}"
>>
> Doesn't PRServer takes care for things like these?
>
> Andreas
The version goes backwards because the the revision is shortened. It
does rebuild the package though when the version changes because of
PRServer but it breaks package feeds when the version goes backwards.
Upgrading using package manager on the target device would not detect a
newer version.
Regards,
Jonathan
next prev parent reply other threads:[~2015-10-04 11:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-04 2:15 [meta-raspberrypi][PATCH v3] linux-raspberrypi.inc: use SRCPV instead of SRCREV for PV Jonathan Liu
2015-10-04 10:50 ` Andreas Müller
2015-10-04 11:14 ` Jonathan Liu [this message]
2015-10-13 17:46 ` Andrei Gherzan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=561109FE.3080807@gmail.com \
--to=net147@gmail.com \
--cc=schnitzeltony@googlemail.com \
--cc=yocto@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.