If you see a spurious rebuild, you should investigate with
bitbake-diffsigs, rather that trying to outsmart the build system,
else you're likely to shoot yourself in the foot :)
2019-10-10 17:32 UTC+02:00, Mauro Ziliani :
> I find the solution.
>
> I know that I have not modified the packages rebu
I find the solution.
I know that I have not modified the packages rebuilded (i.e the kernel)
So I see in prserv.sqlite3.
The table PRMAIN_nohist contains the history of buildhistory for each
pkg/recipe.
I deleted the line which the field value i bigger or equal the value I need
The package
The PR server takes care not to reuse those versions.
Apart from making sure your recipe's signature matches the one for
0.13, you probably can't (assuming you don't want to mess with your
PR's database).
2019-10-10 10:27 UTC+02:00, Mauro Ziliani :
> Hi all
>
> I need to change the build number o
Hi all
I need to change the build number of a package.
That is: i have the package
kernel-4.1.15-2.0.1_4.1.15-r0.*17*_armhf.deb, but in need to turn back
to kernel-4.1.15-2.0.1_4.1.15-r0.*13*_armhf.deb
Can I setup manually the 17 value to 13?
Mauro
--
___
