From: Marko Lindqvist <cazfi74@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/9] Fix license segment boundaries
Date: Tue, 15 Jan 2013 21:41:54 +0200 [thread overview]
Message-ID: <cover.1358278681.git.cazfi74@gmail.com> (raw)
Found that also "firstline" has been used in several recipes instead
of "beginline". This set fixes those.
It was impossible to fetch affected libidn version at all (for testing
the md5sum change) because of missing SRC checksums so fix for that is
included too.
The following changes since commit 6080d1dc719c38fd97c2abd38e0ad938fbf6f452:
connman: fixed init script so connman can runs over nfs (2013-01-15 08:09:30 +0000)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib cazfi/beginline
http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=cazfi/beginline
Marko Lindqvist (9):
libidn: add checksums to version 0.6.14 recipe
gzip: fix license segment md5sum boundary
iptables: fix license segment md5sum boundary
shadow: fix license segment md5sum boundary
ethtool: fix license segment md5sum boundary
gperf: fix license segment md5sum boundary
libidn: fix license segment md5sum boundary
dbus: fix license segment md5sum boundary
apmd: fix license segment md5sum boundary
meta/recipes-bsp/apmd/apmd_3.2.2-14.bb | 2 +-
meta/recipes-core/dbus/dbus-glib.inc | 2 +-
meta/recipes-core/dbus/dbus-ptest_1.6.4.bb | 2 +-
meta/recipes-core/dbus/dbus.inc | 2 +-
meta/recipes-extended/ethtool/ethtool_3.7.bb | 2 +-
meta/recipes-extended/gperf/gperf.inc | 2 +-
meta/recipes-extended/gperf/gperf_3.0.3.bb | 2 +-
meta/recipes-extended/gzip/gzip.inc | 2 +-
meta/recipes-extended/iptables/iptables_1.4.16.3.bb | 2 +-
meta/recipes-extended/libidn/libidn_0.6.14.bb | 7 +++++--
meta/recipes-extended/shadow/shadow-native_4.1.4.3.bb | 2 +-
meta/recipes-extended/shadow/shadow_4.1.4.3.bb | 2 +-
12 files changed, 16 insertions(+), 13 deletions(-)
--
1.7.10.4
reply other threads:[~2013-01-15 19:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=cover.1358278681.git.cazfi74@gmail.com \
--to=cazfi74@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox