How to migrate from PRINC to PR_SERVER?
Attempting to move to the current OE-head now yields about a hundred messages like this:
WARNING: Use of PRINC 7 was detected in the recipe ...
The https://wiki.yoctoproject.org/wiki/PR_Service page tells what the PR server is.
However, it does not tell what to do with the recipes. Just removing PRINC from the recipes will break the upgrade path.
What are we supposed to do now?
Signature · 1 line
Mike Looijmans
Quoted 7 lines · Mike Looijmans
Attempting to move to the current OE-head now yields about a hundred messages like this:
WARNING: Use of PRINC 7 was detected in the recipe ...
The https://wiki.yoctoproject.org/wiki/PR_Service page tells what the PR server is.
PR_Service doesn't help with PRINC removal, because PRINC is applied on first number in PR and AUTOPR is appended as extra number after dot.
Quoted 2 lines
However, it does not tell what to do with the recipes. Just removing PRINC from the recipes will break the upgrade path.
You were supposed to send corresponding PR bumps to upper layers when removing PRINCs, like:
http://git.openembedded.org/openembedded-core/commit?id=c6825ec6e92e20bb64a051d1576f363c16e98d68
but it's probably too late for daisy.
Quoted 1 line
What are we supposed to do now?
You can wait for PV/PE upgrades in upper layers or in worse case break upgrade path and remove PRINCs without replacement (e.g. if it's in your private layer and company doesn't care about upgrade path).
Signature · 1 line
Martin 'JaMa' Jansa jabber: [email protected]
Quoted 11 lines · Martin Jansa
Quoted 7 lines · Mike Looijmans
Attempting to move to the current OE-head now yields about a hundred messages like this:
WARNING: Use of PRINC 7 was detected in the recipe ...
The https://wiki.yoctoproject.org/wiki/PR_Service page tells what the PR server is.
PR_Servicedoesn't help with PRINC removal, because PRINC is applied on first number in PR and AUTOPR is appended as extra number after dot.
So what is the relation then? Why is PRINC now suddenly declared obsolete, without providing anything to replace it?
Quoted 7 lines
Quoted 2 lines
However, it does not tell what to do with the recipes. Just removing PRINC from the recipes will break the upgrade path.
You were supposed to send corresponding PR bumps to upper layers when removing PRINCs, like:
http://git.openembedded.org/openembedded-core/commit?id=c6825ec6e92e20bb64a051d1576f363c16e98d68
Quoted 7 lines
but it's probably too late for daisy.
Quoted 1 line
What are we supposed to do now?
You can wait for PV/PE upgrades in upper layers or in worse case break upgrade path and remove PRINCs without replacement (e.g. if it's in your private layer and company doesn't care about upgrade path).
That would also mean hand-crafting several dozen of PR numbers. And for a project like OpenPLi for which there are something like a million embedded boxes running and upgrading it in the field, I'd definitely want to keep the upgrade path clean...
Would a patch that bumps PRs for so many packages be accepted?
Signature · 1 line
Mike Looijmans