Koen has raised the problem of how to handle a release when there is PR server enabled. The requirement is that a given release must be rebuildable and correspond to what was released. A way to dump the database and fix the PR values based on the contents of the PR server's current set of values would seem to be the best way to do this, perhaps in the form of a generated conf file of the form: PR_pn-PACKAGEA = "r1" PR_pn-PACKAGEB = "r5"
Patches being review: http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=llu/PRService_bitbake&id=4b7c60fcff831d944abc7bffda05a2daedfb55a7 http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=llu/PRService_oecore&id=6ad22f9852cfd011244b3e511f5e563007f7ac5c
new patch being review: http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=llu/PRService_bitbake&id=4b7c60fcff831d944abc7bffda05a2daedfb55a7 http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=llu/PRService_oecore&id=03140960a07a85cb0549d0cb8fab4ee09281ba6a
Fixed in commits: http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=30a9bc6c92a8920d6e9c4a4b93b83bdbe5d48e78 http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=a05e3a57c6f567578faeb31fae89b20e22850af4
Typical usage scenario of the export/import is: 1. bitbake-prserv-tool export <file> to export the AUTOPR values from the current PR service into an exported .inc file. 2. Others may use that exported .inc file(to be included in the local.conf) to lockdown and reproduce the same AUTOPR when generating package feeds. 3. Others may "bitbake-prserv-tool import <file>" to import the AUTOPR values into their own PR service and the AUTOPR values will be incremented from there.
For PR service, since there is a bug with gcc, we could not verify the feature and have to pend it to M3.
The bitbake-prserv could run well with lockdown mode in 1.2 M3 RC1 testing. Mark the bug as VERIFIED FIXED.