On Thu, 2014-03-13 at 04:43 +0000, VanCutsem, Geoffroy wrote:
> ~/gbs.tizen-ivi-3.0.conf so the command-line becomes: gbs -c
> ~/gbs.tizen-ivi-3.0.conf lb -A i586 -P 3.0
Sorry, need more coffee... the command-line should read: gbs -c
~/gbs.tizen-ivi-3.0.conf lb -A i586 -P 3.0-dev
Heads-up too since I guess you'll want to transfer and install this new
kernel on your target image, there are a couple more quirks to be aware
of:
1) The package version of your local build will appear older than what's
in the repo, so use '--oldpackage' when using zypper after having
transferred the binary RPM to the target ('zypper in --oldpackage
<kernel-x86-ivi...rpm>) [1]
2) Zypper will complain that two openavb* packages will be broken by
doing so. You can safely choose to remove those or ignore the breakage.
HTH,
Geoffroy
[1] I have made a suggestion to the tools folks a while back that it
would be better if GBS would automatically assign a release number
higher than the highest from the repo you're building against... but was
told it's not possible (I didn't and still don't understand why...)
Intel Corporation NV/SA
Kings Square, Veldkant 31
2550 Kontich
RPM (Bruxelles) 0415.497.718.
Citibank, Brussels, account 570/1031255/09
This e-mail and any attachments may contain confidential material for the sole
use of the intended recipient(s). Any review or distribution by others is
strictly prohibited. If you are not the intended recipient, please contact the
sender and delete all copies.
_______________________________________________
Dev mailing list
[email protected]
https://lists.tizen.org/listinfo/dev
