From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/3] Opkg patch upstreaming and SIGSEGV fix
Date: Wed, 19 Sep 2012 19:16:28 +0200 [thread overview]
Message-ID: <cover.1348074403.git.Martin.Jansa@gmail.com> (raw)
This depends on
http://patchwork.openembedded.org/patch/36893/
otherwise warning about missing SRC_URI entries will be shown
The following changes since commit f06097f4581e4c728c2950a86e025384e4bdcdf0:
eglibc: Do not use fsqrt in libm when building for fsl ppc with fpu (2012-09-18 07:44:13 -0700)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib jansa/opkg
http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=jansa/opkg
Martin Jansa (3):
opkg: replace local patches with git patches submitted upstream
opkg: add patch to fix SIGSEGV when printing status file
opkg-nogpg: drop SRCREV
meta/recipes-devtools/opkg/opkg-nogpg_svn.bb | 2 -
.../0001-add-opkg_compare_versions-function.patch | 51 ++++++++++++++
...e-the-uname-gname-fields-when-extracting.patch} | 30 +++++---
...ix-dependency-issues-for-preinst-scripts.patch} | 65 ++++++++++--------
...nst-script-is-not-fatal-with-conf-offlin.patch} | 75 +++++++++++---------
...ot-read-etc-opkg-.conf-if-f-is-specified.patch} | 11 ++-
...tch => 0006-detect-circular-dependencies.patch} | 79 +++++++++++++---------
...g-provides-even-when-oldpkg-provides-exis.patch | 46 +++++++++++++
meta/recipes-devtools/opkg/opkg/add_vercmp.patch | 36 ----------
meta/recipes-devtools/opkg/opkg_svn.bb | 15 ++--
10 files changed, 258 insertions(+), 152 deletions(-)
create mode 100644 meta/recipes-devtools/opkg/opkg/0001-add-opkg_compare_versions-function.patch
rename meta/recipes-devtools/opkg/opkg/{add_uname_support.patch => 0002-Ensure-we-use-the-uname-gname-fields-when-extracting.patch} (71%)
rename meta/recipes-devtools/opkg/opkg/{fix_installorder.patch => 0003-Fix-dependency-issues-for-preinst-scripts.patch} (82%)
rename meta/recipes-devtools/opkg/opkg/{offline_postinstall.patch => 0004-Failed-postinst-script-is-not-fatal-with-conf-offlin.patch} (52%)
rename meta/recipes-devtools/opkg/opkg/{conf_override.patch => 0005-Do-not-read-etc-opkg-.conf-if-f-is-specified.patch} (91%)
rename meta/recipes-devtools/opkg/opkg/{track_parents.patch => 0006-detect-circular-dependencies.patch} (59%)
create mode 100644 meta/recipes-devtools/opkg/opkg/0007-merge-newpkg-provides-even-when-oldpkg-provides-exis.patch
delete mode 100644 meta/recipes-devtools/opkg/opkg/add_vercmp.patch
--
1.7.12
next reply other threads:[~2012-09-19 17:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-19 17:16 Martin Jansa [this message]
2012-09-19 17:16 ` [PATCH 1/3] opkg: replace local patches with git patches submitted upstream Martin Jansa
2012-09-19 17:16 ` [PATCH 2/3] opkg: add patch to fix SIGSEGV when printing status file Martin Jansa
[not found] ` <cover.1348076271.git.Martin.Jansa@gmail.com>
2012-09-19 17:40 ` [PATCHv2 " Martin Jansa
2012-09-19 17:41 ` [PATCHv2 1/3] opkg: replace local patches with git patches submitted upstream Martin Jansa
2012-09-19 17:16 ` [PATCH 3/3] opkg-nogpg: drop SRCREV Martin Jansa
2012-09-19 17:29 ` [PATCH 0/3] Opkg patch upstreaming and SIGSEGV fix Saul Wold
2012-09-19 17:33 ` Martin Jansa
2012-09-21 22:25 ` Saul Wold
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.1348074403.git.Martin.Jansa@gmail.com \
--to=martin.jansa@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 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.