From: Martin Jansa <martin.jansa@gmail.com>
To: Mike Looijmans <mike.looijmans@topic.nl>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: How to migrate from PRINC to PR_SERVER?
Date: Sat, 19 Apr 2014 12:59:04 +0200 [thread overview]
Message-ID: <20140419105904.GI2486@jama> (raw)
In-Reply-To: <53523CF6.2040208@topic.nl>
[-- Attachment #1: Type: text/plain, Size: 1138 bytes --]
On Sat, Apr 19, 2014 at 11:08:06AM +0200, Mike Looijmans wrote:
> 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.
> 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.
> 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).
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
next prev parent reply other threads:[~2014-04-19 10:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-19 9:08 How to migrate from PRINC to PR_SERVER? Mike Looijmans
2014-04-19 10:59 ` Martin Jansa [this message]
2014-04-19 13:35 ` Mike Looijmans
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140419105904.GI2486@jama \
--to=martin.jansa@gmail.com \
--cc=mike.looijmans@topic.nl \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.