From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: ulf@emagii.com
Cc: openembedded-core@lists.openembedded.org
Subject: Re: Change in "openembedded-core/meta/files/common-licenses/LGPL-2.0" breaks opie-image
Date: Fri, 09 Dec 2011 10:24:37 +0000 [thread overview]
Message-ID: <1426848.m8dnn0MDvm@helios> (raw)
In-Reply-To: <4EE1DE55.1040303@emagii.com>
On Friday 09 December 2011 11:09:25 Ulf Samuelsson wrote:
> NOTE: package libopie2-1.2.5-r16.0: task do_configure: Started
> ERROR: libopie2: md5 data is not matching for
> file:///home/ulf/projects/OE_2011-12-08/sources/openembedded-core/meta/files
> /common-licenses/LGPL-2.0;md5=03f2b9deed35802bc1aae2ae3dc6d9ed ERROR:
> libopie2: The new md5 checksum is 9427b8ccf5cf3df47c29110424c9641a ERROR:
> libopie2: Check if the license information has changed in
> ERROR: Licensing Error: LIC_FILES_CHKSUM does not match, please fix
Argh. I guess this is one reason why pointing to those files in your recipes is
not a good idea. FYI I basically bypassed LIC_FILES_CHKSUM in meta-opie
because the opie-* recipes build parts of a single source tree and not all of
those split parts contains a license file. For 1.2.6 I plan to make the
splitting script add a license file where it is not present and once the
recipes are updated this will never be a problem again.
For now I guess we will have to correct the checksums :/ I will try to do this
soon.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2011-12-09 10:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-09 10:09 Change in "openembedded-core/meta/files/common-licenses/LGPL-2.0" breaks opie-image Ulf Samuelsson
2011-12-09 10:17 ` Ulf Samuelsson
2011-12-09 10:24 ` Paul Eggleton [this message]
2011-12-09 10:30 ` Ulf Samuelsson
2011-12-09 10:40 ` Paul Eggleton
2011-12-09 19:03 ` Flanagan, Elizabeth
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=1426848.m8dnn0MDvm@helios \
--to=paul.eggleton@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ulf@emagii.com \
/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.