All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Kanavin <alex.kanavin@gmail.com>
To: Wang Mingyu <wangmy@cn.fujitsu.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] python3-pycairo: upgrade 1.18.2 -> 1.19.0
Date: Fri, 14 Feb 2020 18:46:35 +0100	[thread overview]
Message-ID: <CANNYZj_xy7G5ejCfOXYwJpE_=AvwWjnEvOjfdkKADx6troHbrg@mail.gmail.com> (raw)
In-Reply-To: <1581723869-21232-4-git-send-email-wangmy@cn.fujitsu.com>

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

Thanks Wang, the recipe upgrade work is very appreciated, particularly
because it doesn't fit very well into commercial product development and
its typical incentives.

Do you want to be the official maintainer for any of the oe-core recipes?
In the sense that you would be listed for them in
meta/conf/distro/include/maintainers.inc

The benefits are - you can place the 'official' bit into your CV; you will
also get monthly upgrade patches by email from AUH, so you don't have to
create them yourself.

Alex


On Fri, 14 Feb 2020 at 17:12, Wang Mingyu <wangmy@cn.fujitsu.com> wrote:

> -License-Update: "PDX-License-Identifier: LGPL-2.1-only OR MPL-1.1"
> is added
>
> Signed-off-by: Wang Mingyu <wangmy@cn.fujitsu.com>
> ---
>  ...{python3-pycairo_1.18.2.bb => python3-pycairo_1.19.0.bb} | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
>  rename meta/recipes-devtools/python/{python3-pycairo_1.18.2.bb =>
> python3-pycairo_1.19.0.bb} (77%)
>
> diff --git a/meta/recipes-devtools/python/python3-pycairo_1.18.2.bb
> b/meta/recipes-devtools/python/python3-pycairo_1.19.0.bb
> similarity index 77%
> rename from meta/recipes-devtools/python/python3-pycairo_1.18.2.bb
> rename to meta/recipes-devtools/python/python3-pycairo_1.19.0.bb
> index 3aedf3d142..8f60834c17 100644
> --- a/meta/recipes-devtools/python/python3-pycairo_1.18.2.bb
> +++ b/meta/recipes-devtools/python/python3-pycairo_1.19.0.bb
> @@ -3,7 +3,7 @@ HOMEPAGE = "http://cairographics.org/pycairo"
>  BUGTRACKER = "http://bugs.freedesktop.org"
>  SECTION = "python-devel"
>  LICENSE = "LGPLv2.1 & MPLv1.1"
> -LIC_FILES_CHKSUM = "file://COPYING;md5=f2e071ab72978431b294a0d696327421 \
> +LIC_FILES_CHKSUM = "file://COPYING;md5=f3713ca2c28d9312ad718520b6dc3eee \
>
>  file://COPYING-LGPL-2.1;md5=fad9b3332be894bab9bc501572864b29 \
>
>  file://COPYING-MPL-1.1;md5=bfe1f75d606912a4111c90743d6c7325"
>
> @@ -13,8 +13,8 @@ DEPENDS = "cairo python3"
>  SRC_URI = "
> https://github.com/pygobject/pycairo/releases/download/v${PV}/pycairo-${PV}.tar.gz
> "
>  UPSTREAM_CHECK_URI = "https://github.com/pygobject/pycairo/releases/"
>
> -SRC_URI[md5sum] = "be2ba51f234270dec340f28f1695a95e"
> -SRC_URI[sha256sum] =
> "dcb853fd020729516e8828ad364084e752327d4cff8505d20b13504b32b16531"
> +SRC_URI[md5sum] = "38b84416021640b01250c8f8ec4c52d4"
> +SRC_URI[sha256sum] =
> "4f5ba9374a46c98729dd3727d993f5e17ed0286fd6738ed464fe4efa0612d19c"
>
>  S = "${WORKDIR}/pycairo-${PV}"
>
> --
> 2.17.1
>
>
>
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>

[-- Attachment #2: Type: text/html, Size: 4856 bytes --]

  reply	other threads:[~2020-02-14 17:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-14 23:44 [PATCH] ell: upgrade 0.27 -> 0.28 Wang Mingyu
2020-02-14 23:44 ` [PATCH] icu: upgrade 64.2 -> 65.1 Wang Mingyu
2020-02-15 10:19   ` Richard Purdie
2020-02-15 16:10     ` Alexander Kanavin
2020-02-14 23:44 ` [PATCH] libgpg-error: upgrade 1.36 -> 1.37 Wang Mingyu
2020-02-15  8:03   ` Richard Purdie
2020-02-14 23:44 ` [PATCH] python3-pycairo: upgrade 1.18.2 -> 1.19.0 Wang Mingyu
2020-02-14 17:46   ` Alexander Kanavin [this message]
2020-02-16  3:51   ` Peter Kjellerstedt

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='CANNYZj_xy7G5ejCfOXYwJpE_=AvwWjnEvOjfdkKADx6troHbrg@mail.gmail.com' \
    --to=alex.kanavin@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=wangmy@cn.fujitsu.com \
    /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.