From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: Martin Jansa <martin.jansa@gmail.com>
Subject: Re: [PATCH 1/2] opkg-utils: bump SRCREV
Date: Wed, 20 Jun 2012 19:40:05 -0700 [thread overview]
Message-ID: <4FE28985.1000501@linux.intel.com> (raw)
In-Reply-To: <1340091730-5993-1-git-send-email-Martin.Jansa@gmail.com>
On 06/19/2012 12:42 AM, Martin Jansa wrote:
> * there are 2 small fixes
> python-2.6 compatibility
> missing C option for opkg-build
>
> Signed-off-by: Martin Jansa<Martin.Jansa@gmail.com>
> ---
> .../opkg-utils/opkg-utils/shr.patch | 26 ++++++++++++++++++++
> meta/recipes-devtools/opkg-utils/opkg-utils_git.bb | 2 +-
> 2 files changed, 27 insertions(+), 1 deletions(-)
> create mode 100644 meta/recipes-devtools/opkg-utils/opkg-utils/shr.patch
>
> diff --git a/meta/recipes-devtools/opkg-utils/opkg-utils/shr.patch b/meta/recipes-devtools/opkg-utils/opkg-utils/shr.patch
> new file mode 100644
> index 0000000..29de962
> --- /dev/null
> +++ b/meta/recipes-devtools/opkg-utils/opkg-utils/shr.patch
Martin,
No Upstream-Status or Signed-off-by
Please fix this
Thanks
Sau!
> @@ -0,0 +1,26 @@
> +diff --git a/opkg-build b/opkg-build
> +index 012afd3..485897a 100755
> +--- a/opkg-build
> ++++ b/opkg-build
> +@@ -160,7 +160,7 @@ outer=ar
> + noclean=0
> + opkext=0
> + usage="Usage: $0 [-c] [-C] [-O] [-o owner] [-g group]<pkg_directory> [<destination_directory>]"
> +-while getopts "cg:ho:vO" opt; do
> ++while getopts "cCg:ho:vO" opt; do
> + case $opt in
> + o ) owner=$OPTARG
> + ogargs="--owner=$owner"
> +diff --git a/opkg-make-index b/opkg-make-index
> +index 22393e8..1c3a8e1 100755
> +--- a/opkg-make-index
> ++++ b/opkg-make-index
> +@@ -186,7 +186,7 @@ if packages_filename:
> + gzip_filename = ("%s.gz" % packages_filename)
> + tmp_gzip_filename = ("%s.%d" % (gzip_filename, os.getpid()))
> + gzip_cmd = "gzip -9c< %s> %s" % (tmp_packages_filename, tmp_gzip_filename)
> +- rc = subprocess.check_output(gzip_cmd, shell=True)
> ++ subprocess.call(gzip_cmd, shell=True)
> + os.rename(tmp_packages_filename, packages_filename)
> + os.rename(tmp_gzip_filename, gzip_filename)
> +
> diff --git a/meta/recipes-devtools/opkg-utils/opkg-utils_git.bb b/meta/recipes-devtools/opkg-utils/opkg-utils_git.bb
> index 1996c75..b193ba4 100644
> --- a/meta/recipes-devtools/opkg-utils/opkg-utils_git.bb
> +++ b/meta/recipes-devtools/opkg-utils/opkg-utils_git.bb
> @@ -6,7 +6,7 @@ LIC_FILES_CHKSUM = "file://COPYING;md5=94d55d512a9ba36caa9b7df079bae19f \
> file://opkg.py;beginline=1;endline=18;md5=15917491ad6bf7acc666ca5f7cc1e083"
> RDEPENDS_${PN} = "python"
> RDEPENDS_${PN}_virtclass-native = ""
> -SRCREV = "44df9dd3dc411ca1255cb4b23bde7eb71aed4778"
> +SRCREV = "423ecd36b4782327c16f516885d1248249c7724a"
> PV = "0.1.8+git${SRCPV}"
> PR = "r1"
>
next prev parent reply other threads:[~2012-06-21 2:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-19 7:42 [PATCH 1/2] opkg-utils: bump SRCREV Martin Jansa
2012-06-19 7:42 ` [PATCH 2/2] kernel.bbclass: pass KERNEL_VERSION to depmod calls in postinst Martin Jansa
2012-06-21 2:40 ` Saul Wold [this message]
2012-06-21 5:51 ` [PATCH 1/2] opkg-utils: bump SRCREV Martin Jansa
2012-06-21 5:53 ` [PATCHv2] " Martin Jansa
2012-06-22 17:58 ` 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=4FE28985.1000501@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=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.