Yes, PE needs to be restored. (it is package epoch, which is used when
versioning scheme needs to change for whatever reason, with the new version
going backwards. Here the version goes from 0.0 to 20190618 (an improvement
I would say), so we can keep the original PE).
To reproduce, 'bitbake -c cl
PE was dropped, so version definitely went backwards and QA is right to
complain.
On Mon, Aug 12, 2019 at 3:41 PM Oleksandr Kravchuk <
open.sou...@oleksandr-kravchuk.com> wrote:
> Hi Nicola,
>
> How do I reproduce this? It builds fine for me.
>
> On 12/08/2019 15:38, nick83ola wrote:
> > Hi all
>
Hi Nicola,
How do I reproduce this? It builds fine for me.
On 12/08/2019 15:38, nick83ola wrote:
> Hi all
> after this patch I got a ton of errors regarding Package version went
> backwards
>
> Cheers
> Nicola Lunghi
>
> ERROR: linux-firmware-20190618-r0 do_packagedata: QA Issue: Package
> versi
Hi all
after this patch I got a ton of errors regarding Package version went backwards
Cheers
Nicola Lunghi
ERROR: linux-firmware-20190618-r0 do_packagedata: QA Issue: Package
version for package linux-firmware-src went backwards which would
break package feeds from (1:0.0+git0+711d3297ba-r0 to 0