Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Alexander Kanavin <alex.kanavin@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 07/12] createrepo-c: upgrade 0.14.3 -> 0.15.0
Date: Tue, 20 Aug 2019 17:32:14 +0200	[thread overview]
Message-ID: <20190820153219.62435-7-alex.kanavin@gmail.com> (raw)
In-Reply-To: <20190820153219.62435-1-alex.kanavin@gmail.com>

Disable delta-rpm, which oe-core does not use.

Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com>
---
 .../{createrepo-c_0.14.3.bb => createrepo-c_0.15.0.bb}        | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
 rename meta/recipes-devtools/createrepo-c/{createrepo-c_0.14.3.bb => createrepo-c_0.15.0.bb} (91%)

diff --git a/meta/recipes-devtools/createrepo-c/createrepo-c_0.14.3.bb b/meta/recipes-devtools/createrepo-c/createrepo-c_0.15.0.bb
similarity index 91%
rename from meta/recipes-devtools/createrepo-c/createrepo-c_0.14.3.bb
rename to meta/recipes-devtools/createrepo-c/createrepo-c_0.15.0.bb
index 22b9f3d3b14..ae0a35da847 100644
--- a/meta/recipes-devtools/createrepo-c/createrepo-c_0.14.3.bb
+++ b/meta/recipes-devtools/createrepo-c/createrepo-c_0.15.0.bb
@@ -8,7 +8,7 @@ SRC_URI = "git://github.com/rpm-software-management/createrepo_c \
            file://0001-Do-not-set-PYTHON_INSTALL_DIR-by-running-python.patch \
            "
 
-SRCREV = "de9d8337885d953baae501cce75decc11d5468dd"
+SRCREV = "2077ba104eae04bb819e9e0c906c8c835b62e7a6"
 
 S = "${WORKDIR}/git"
 
@@ -17,7 +17,7 @@ DEPENDS_append_class-native = " file-replacement-native"
 
 inherit cmake pkgconfig bash-completion distutils3-base
 
-EXTRA_OECMAKE = " -DPYTHON_INSTALL_DIR=${PYTHON_SITEPACKAGES_DIR} -DPYTHON_DESIRED=3 -DWITH_ZCHUNK=OFF"
+EXTRA_OECMAKE = " -DPYTHON_INSTALL_DIR=${PYTHON_SITEPACKAGES_DIR} -DPYTHON_DESIRED=3 -DWITH_ZCHUNK=OFF -DENABLE_DRPM=OFF"
 
 BBCLASSEXTEND = "native nativesdk"
 
-- 
2.17.1



  parent reply	other threads:[~2019-08-20 15:32 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-20 15:32 [PATCH 01/12] linux-yocto: add drm-bochs support Alexander Kanavin
2019-08-20 15:32 ` [PATCH 02/12] qemu: switch to '-vga std' emulated hardware from vmware/cirrus for x86/mips Alexander Kanavin
2019-08-23  9:13   ` Richard Purdie
2019-08-23 10:34     ` Alexander Kanavin
2019-08-20 15:32 ` [PATCH 03/12] images: use 512M of RAM in qemu if 'opengl" is in DISTRO_FEATURES Alexander Kanavin
2019-08-20 15:32 ` [PATCH 04/12] python3-numpy: update to 1.17.0 Alexander Kanavin
2019-08-22 13:33   ` Richard Purdie
2019-08-22 15:07     ` Alexander Kanavin
2019-08-20 15:32 ` [PATCH 05/12] rt-tests: exclude another development version Alexander Kanavin
2019-08-20 15:32 ` [PATCH 06/12] libmodulemd: depend on target python at build time Alexander Kanavin
2019-08-20 15:32 ` Alexander Kanavin [this message]
2019-08-20 15:32 ` [PATCH 08/12] gtk-doc: upgrade 1.30 -> 1.31 Alexander Kanavin
2019-08-20 15:32 ` [PATCH 09/12] desktop-file-utils: upgrade 0.23 -> 0.24 Alexander Kanavin
2019-08-20 15:32 ` [PATCH 10/12] vala: upgrade 0.44.5 -> 0.44.7 Alexander Kanavin
2019-08-20 15:32 ` [PATCH 11/12] libdazzle: upgrade 3.32.2 -> 3.32.3 Alexander Kanavin
2019-08-20 15:32 ` [PATCH 12/12] epiphany: upgrade 3.32.3 -> 3.32.4 Alexander Kanavin

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=20190820153219.62435-7-alex.kanavin@gmail.com \
    --to=alex.kanavin@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