Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] package/python-crontab: bump to version 2.4.2
Date: Tue, 28 Apr 2020 21:11:18 +0200	[thread overview]
Message-ID: <20200428191118.GH11346@scaer> (raw)
In-Reply-To: <20200428130748.459546-1-grzegorz@blach.pl>

Grzegorz, All,

On 2020-04-28 15:07 +0200, Grzegorz Blach spake thusly:
> Signed-off-by: Grzegorz Blach <grzegorz@blach.pl>

Both patches applied to master, thanks.

Regards,
Yann E. MORIN.

> ---
>  package/python-crontab/python-crontab.hash | 4 ++--
>  package/python-crontab/python-crontab.mk   | 4 ++--
>  2 files changed, 4 insertions(+), 4 deletions(-)
> 
> diff --git a/package/python-crontab/python-crontab.hash b/package/python-crontab/python-crontab.hash
> index f22e782a69..d0e5725708 100644
> --- a/package/python-crontab/python-crontab.hash
> +++ b/package/python-crontab/python-crontab.hash
> @@ -1,5 +1,5 @@
>  # md5, sha256 from https://pypi.org/pypi/python-crontab/json
> -md5  663bd09882c7caaa18be3c0cc0c7e716  python-crontab-2.4.1.tar.gz
> -sha256  2366c7aa373118315de7c082401907bacd28e8b1e4e0a6d702334d17b89e71aa  python-crontab-2.4.1.tar.gz
> +md5  65fe16d44568de2671d334a637e64a3b  python-crontab-2.4.2.tar.gz
> +sha256  ed9583cff430715d9560cbad28309429ac13f3fdb13051ac2288050e05abc392  python-crontab-2.4.2.tar.gz
>  # Locally computed sha256 checksums
>  sha256  da7eabb7bafdf7d3ae5e9f223aa5bdc1eece45ac569dc21b3b037520b4464768  COPYING
> diff --git a/package/python-crontab/python-crontab.mk b/package/python-crontab/python-crontab.mk
> index 2abb4eed74..0c6109dd7f 100644
> --- a/package/python-crontab/python-crontab.mk
> +++ b/package/python-crontab/python-crontab.mk
> @@ -4,8 +4,8 @@
>  #
>  ################################################################################
>  
> -PYTHON_CRONTAB_VERSION = 2.4.1
> -PYTHON_CRONTAB_SITE = https://files.pythonhosted.org/packages/09/b1/31d3ccf2ad3d4f7727b325ad7ea77d042e1939c5cacbf1d7478e391cca51
> +PYTHON_CRONTAB_VERSION = 2.4.2
> +PYTHON_CRONTAB_SITE = https://files.pythonhosted.org/packages/d1/c2/e92e801a0c504e62899d574a6d281d6e598861797c6798a664556d2bca8c
>  PYTHON_CRONTAB_SETUP_TYPE = setuptools
>  PYTHON_CRONTAB_LICENSE = LGPL-3.0+
>  PYTHON_CRONTAB_LICENSE_FILES = COPYING
> -- 
> 2.26.2
> 
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 561 099 427 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

      parent reply	other threads:[~2020-04-28 19:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-28 13:07 [Buildroot] [PATCH 1/2] package/python-crontab: bump to version 2.4.2 Grzegorz Blach
2020-04-28 13:07 ` [Buildroot] [PATCH 2/2] package/python-wtforms: bump to version 2.3.1 Grzegorz Blach
2020-04-28 19:11 ` Yann E. MORIN [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=20200428191118.GH11346@scaer \
    --to=yann.morin.1998@free.fr \
    --cc=buildroot@busybox.net \
    /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