From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] smart: disable CHANNELSDIR
Date: Mon, 8 Apr 2013 11:05:30 -0500 [thread overview]
Message-ID: <5162EACA.7000905@windriver.com> (raw)
In-Reply-To: <1365433358-29073-1-git-send-email-bogdan.a.marinescu@intel.com>
On 4/8/13 10:02 AM, Bogdan Marinescu wrote:
> Make CHANNELSDIR in smart empty, since this causes host contamination issues
> on some RPM-based hosts on which smart is already installed.
>
> [YOCTO #3881]
>
> Signed-off-by: Bogdan Marinescu <bogdan.a.marinescu@intel.com>
> ---
> .../python/python-smartpm/smart-channelsdir.patch | 24 ++++++++++++++++++++++
> .../python/python-smartpm_1.4.1.bb | 3 ++-
> 2 files changed, 26 insertions(+), 1 deletion(-)
> create mode 100644 meta/recipes-devtools/python/python-smartpm/smart-channelsdir.patch
>
> diff --git a/meta/recipes-devtools/python/python-smartpm/smart-channelsdir.patch b/meta/recipes-devtools/python/python-smartpm/smart-channelsdir.patch
> new file mode 100644
> index 0000000..e621b33
> --- /dev/null
> +++ b/meta/recipes-devtools/python/python-smartpm/smart-channelsdir.patch
> @@ -0,0 +1,24 @@
> +Make CHANNELSDIR in smart empty, since this causes host contamination issues
> +on some RPM-based hosts on which smart is already installed.
> +
> +[YOCTO #3881]
> +
> +Upstream-Status: Inappropriate [embedded specific]
> +
> +diff --git a/smart/plugins/channelsync.py b/smart/plugins/channelsync.py
> +index 3ba95ff..646d696 100644
> +--- a/smart/plugins/channelsync.py
> ++++ b/smart/plugins/channelsync.py
> +@@ -23,7 +23,11 @@ from smart.channel import *
> + from smart import *
> + import os
> +
> +-CHANNELSDIR = "/etc/smart/channels/"
> ++# For now, we leave the definition of CHANNELSDIR empty. This prevents smart
> ++# from erroneously consider the build host's channels while setting up its
> ++# channels [YOCTO #3881]. If this feature will be used in the future, CHANNELSDIR
> ++# should be set to a proper value.
> ++CHANNELSDIR = ""
I don't remember if the channelsdir is used by default on the target or if there
is a different directory.
Did you check if (on the target) you can still add channels and do a remove
install/update of a package?
> +
> + def syncChannels(channelsdir, force=None):
> +
> diff --git a/meta/recipes-devtools/python/python-smartpm_1.4.1.bb b/meta/recipes-devtools/python/python-smartpm_1.4.1.bb
> index d92933f..001d9e4 100644
> --- a/meta/recipes-devtools/python/python-smartpm_1.4.1.bb
> +++ b/meta/recipes-devtools/python/python-smartpm_1.4.1.bb
> @@ -11,7 +11,7 @@ LICENSE = "GPLv2"
> LIC_FILES_CHKSUM = "file://LICENSE;md5=393a5ca445f6965873eca0259a17f833"
>
> DEPENDS = "python rpm"
> -PR = "r8"
> +PR = "r9"
> SRCNAME = "smart"
>
> SRC_URI = "\
> @@ -27,6 +27,7 @@ SRC_URI = "\
> file://smart-improve-error-reporting.patch \
> file://smart-multilib-fixes.patch \
> file://smart-yaml-error.patch \
> + file://smart-channelsdir.patch \
> "
>
> SRC_URI[md5sum] = "573ef32ba177a6b3c4bf7ef04873fcb6"
>
next prev parent reply other threads:[~2013-04-08 16:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-08 15:02 [PATCH] smart: disable CHANNELSDIR Bogdan Marinescu
2013-04-08 16:05 ` Mark Hatle [this message]
[not found] ` <CAMZjud3RpPwm=8h6z87caWireAT5rzVtkfwyJqRF0u7bcvCQ4Q@mail.gmail.com>
2013-04-09 8:13 ` Marinescu, Bogdan A
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=5162EACA.7000905@windriver.com \
--to=mark.hatle@windriver.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