[OE-core] [PATCH] initramfs-framework: bump PR and fix install-efi and setup-live modules

[Martin Jansa]

> Changing arch on a package resets the incrementing PR?  Isn't that a bug?

Arch is part of the key in PR server database.

It's not a bug, because when you have MACHINE_ARCH recipe then it's normal
that different MACHINEs (with different bbappends in BSP layers) have
different EXTENDPRAUTO, without the arch in the key, the EXTENDPRAUTO would
be incremented in PR server database every time you change MACHINE
variable. It's not ideal but better than the alternative.

On Tue, Sep 12, 2017 at 12:03 AM, Burton, Ross <ross.burton at intel.com>
wrote:

> On 11 September 2017 at 23:01, Otavio Salvador <otavio.salvador at ossystems.
> com.br> wrote:
>
>> On Mon, Sep 11, 2017 at 6:59 PM, Burton, Ross <ross.burton at intel.com>
>> wrote:
>> > On 11 September 2017 at 22:58, Otavio Salvador
>> > <otavio.salvador at ossystems.com.br> wrote:
>> >>
>> >> On Mon, Sep 11, 2017 at 6:49 PM, Burton, Ross <ross.burton at intel.com>
>> >> wrote:
>> >> > On 11 September 2017 at 22:33, California Sullivan
>> >> > <california.l.sullivan at intel.com> wrote:
>> >> >>
>> >> >> Bump initramfs-framework PR, as it was missed in the previous
>> >> >> initramfs-framework patch.
>> >> >
>> >> >
>> >> > There's no need to bump PR.  In the ideal world, the PR isn't
>> assigned
>> >> > at
>> >> > all.
>> >>
>> >> there is, the package moved across arches so adding the PR makes sure
>> >> it is upgraded.
>> >
>> >
>> > Surely the PR service handles this if you're running a feed.  If you're
>> not
>> > running a feed then this isn't a problem.
>>
>> It does not; it goes back to r0.
>
>
> Changing arch on a package resets the incrementing PR?  Isn't that a bug?
>
> Ross
>
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core at lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openembedded.org/pipermail/openembedded-core/attachments/20170912/4fd10c7b/attachment-0002.html>