From: Justin Bronder <jsbronder@cold-front.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: python3-asyncinotify: upgrade 3.0.1 -> 4.0.2
Date: Mon, 17 Jul 2023 13:15:03 -0400 [thread overview]
Message-ID: <ZLV3F0kY2U4JMlSl@ravine.members.linode.com> (raw)
In-Reply-To: <1772B6E959A7EECD.27904@lists.openembedded.org>
Apologies, there is no second patch; I fat-fingered git-send-email.
On 17/07/23 13:11 -0400, Justin Bronder wrote:
> c5590c5 Switch from GitHub to gitlab
> 22b0ed7 make pass all mypy type checks
> abd15f8 add __weakref__ to inotify and watch
> 5e57e0b add slots to all classes
> f907237 restore support to 3.6
> 5269b9d improve documentation
> 2512aa3 Merge branch '16-add-timeout-for-the-sync-version-of-get-sync_get' into 'master'
> 5beff57 add sync_timeout
> c8f8653 fix readthedocs
> 97056b9 remove package rule
> faebfa9 move test after package
> a75f116 version bump
> 6b4921f rework docs
> 35716a4 rework docs
> c51d603 fix test for deprecations
> ddd987c switch to pyproject.toml, test against all supported python versions
>
> Signed-off-by: Justin Bronder <jsbronder@cold-front.org>
> ---
> ...n3-asyncinotify_3.0.1.bb => python3-asyncinotify_4.0.2.bb} | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
> rename meta-python/recipes-devtools/python/{python3-asyncinotify_3.0.1.bb => python3-asyncinotify_4.0.2.bb} (75%)
>
> diff --git a/meta-python/recipes-devtools/python/python3-asyncinotify_3.0.1.bb b/meta-python/recipes-devtools/python/python3-asyncinotify_4.0.2.bb
> similarity index 75%
> rename from meta-python/recipes-devtools/python/python3-asyncinotify_3.0.1.bb
> rename to meta-python/recipes-devtools/python/python3-asyncinotify_4.0.2.bb
> index 2f4adcea7a..08dc77bd17 100644
> --- a/meta-python/recipes-devtools/python/python3-asyncinotify_3.0.1.bb
> +++ b/meta-python/recipes-devtools/python/python3-asyncinotify_4.0.2.bb
> @@ -3,9 +3,9 @@ HOMEPAGE = "https://gitlab.com/Taywee/asyncinotify"
> LICENSE = "MIT"
> LIC_FILES_CHKSUM = "file://LICENSE;md5=6ec941a1cd6616454970d03cb9c9e8f8"
>
> -SRC_URI[sha256sum] = "da812bf2be6a76aac6670b766eec4564d9484da6595d3ce1f9bba8ba78c30445"
> +SRC_URI[sha256sum] = "bcac19425b1b418bbbc4d31193ea3c39e24343cd7ddff2074ae7b599f1a04829"
>
> -inherit pypi setuptools3
> +inherit pypi python_setuptools_build_meta
>
> RDEPENDS:${PN} += " \
> python3-asyncio \
> --
> 2.41.0
>
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#103887): https://lists.openembedded.org/g/openembedded-devel/message/103887
> Mute This Topic: https://lists.openembedded.org/mt/100199246/4454694
> Group Owner: openembedded-devel+owner@lists.openembedded.org
> Unsubscribe: https://lists.openembedded.org/g/openembedded-devel/unsub [jsbronder@cold-front.org]
> -=-=-=-=-=-=-=-=-=-=-=-
>
--
Justin Bronder
parent reply other threads:[~2023-07-17 17:15 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1772B6E959A7EECD.27904@lists.openembedded.org>]
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=ZLV3F0kY2U4JMlSl@ravine.members.linode.com \
--to=jsbronder@cold-front.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox