All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-python][PATCH] python-dateutil: mark as having broken "make clean"
Date: Mon, 1 Feb 2016 16:15:19 +0100	[thread overview]
Message-ID: <20160201151519.GD2639@jama> (raw)
In-Reply-To: <1453116651-11714-1-git-send-email-bob.ham@collabora.com>

[-- Attachment #1: Type: text/plain, Size: 1223 bytes --]

On Mon, Jan 18, 2016 at 11:30:51AM +0000, Bob Ham wrote:
> Set CLEANBROKEN as the Makefile has no "clean" target.
> 
> Signed-off-by: Bob Ham <bob.ham@collabora.com>

Please check if it's still needed for python-dateutil_2.4.2.bb currently
in master.

> ---
>  meta-python/recipes-devtools/python/python-dateutil_1.5.bb | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/meta-python/recipes-devtools/python/python-dateutil_1.5.bb b/meta-python/recipes-devtools/python/python-dateutil_1.5.bb
> index 37f19a8..61d992d 100644
> --- a/meta-python/recipes-devtools/python/python-dateutil_1.5.bb
> +++ b/meta-python/recipes-devtools/python/python-dateutil_1.5.bb
> @@ -8,6 +8,8 @@ SRCNAME = "${BPN}"
>  SRC_URI = "http://labix.org/download/python-dateutil/${SRCNAME}-${PV}.tar.gz"
>  S = "${WORKDIR}/${SRCNAME}-${PV}"
>  
> +CLEANBROKEN = "1"
> +
>  inherit setuptools
>  
>  PACKAGES =+ "${PN}-zoneinfo"
> -- 
> 2.1.4
> 
> -- 
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-devel

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]

      reply	other threads:[~2016-02-01 15:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-18 11:30 [meta-python][PATCH] python-dateutil: mark as having broken "make clean" Bob Ham
2016-02-01 15:15 ` Martin Jansa [this message]

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=20160201151519.GD2639@jama \
    --to=martin.jansa@gmail.com \
    --cc=openembedded-devel@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.