Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Andreas Ziegler <br015@umbiko.net>
Cc: Fabrice Fontaine <fontaine.fabrice@gmail.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/libnpupnp: update version to 4.2.2
Date: Sun, 24 Apr 2022 16:24:30 +0200	[thread overview]
Message-ID: <20220424142430.GU2730@scaer> (raw)
In-Reply-To: <20220424090931.268434-1-br015@umbiko.net>

Andreas, All,

On 2022-04-24 11:09 +0200, Andreas Ziegler spake thusly:
> Bugfix release for:
> http://autobuild.buildroot.net/results/a87/a8754431aad8808ae2d67e32d4a7973b00eda1c1/
> 
> Technical discussion:
> https://github.com/MusicPlayerDaemon/MPD/pull/1513
> 
> Signed-off-by: Andreas Ziegler <br015@umbiko.net>

Applied to master, thanks.

Regards,
Yann E. MORIN.

> ---
>  package/libnpupnp/libnpupnp.hash | 2 +-
>  package/libnpupnp/libnpupnp.mk   | 2 +-
>  2 files changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/package/libnpupnp/libnpupnp.hash b/package/libnpupnp/libnpupnp.hash
> index 276bf93c99..79c2bbdc26 100644
> --- a/package/libnpupnp/libnpupnp.hash
> +++ b/package/libnpupnp/libnpupnp.hash
> @@ -1,5 +1,5 @@
>  # Hash from: http://www.lesbonscomptes.com/upmpdcli/downloads/libnpupnp-4.2.1.tar.gz.sha256
> -sha256  e0e59eb2d3d024e827050428e0e7eb228355912a38c85eb30bfeb2f0926eca4c  libnpupnp-4.2.1.tar.gz
> +sha256  cb3968773d30e2bfc765547df514fdc8927b9a37ecccca2e260ee8b612e756bc  libnpupnp-4.2.2.tar.gz
>  
>  # Hash for license file:
>  sha256  c8b99423cad48bb44e2cf52a496361404290865eac259a82da6d1e4331ececb3  COPYING
> diff --git a/package/libnpupnp/libnpupnp.mk b/package/libnpupnp/libnpupnp.mk
> index 09bfa34b87..d7192ec3f1 100644
> --- a/package/libnpupnp/libnpupnp.mk
> +++ b/package/libnpupnp/libnpupnp.mk
> @@ -4,7 +4,7 @@
>  #
>  ################################################################################
>  
> -LIBNPUPNP_VERSION = 4.2.1
> +LIBNPUPNP_VERSION = 4.2.2
>  LIBNPUPNP_SITE = http://www.lesbonscomptes.com/upmpdcli/downloads
>  LIBNPUPNP_LICENSE = BSD-3-Clause
>  LIBNPUPNP_LICENSE_FILES = COPYING
> -- 
> 2.34.1
> 
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/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.  |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      parent reply	other threads:[~2022-04-24 14:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-24  9:09 [Buildroot] [PATCH 1/1] package/libnpupnp: update version to 4.2.2 Andreas Ziegler
2022-04-24  9:32 ` [Buildroot] [PATCH v2 " Andreas Ziegler
2022-05-26 20:06   ` Peter Korsgaard
2022-04-24 14:24 ` 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=20220424142430.GU2730@scaer \
    --to=yann.morin.1998@free.fr \
    --cc=br015@umbiko.net \
    --cc=buildroot@buildroot.org \
    --cc=fontaine.fabrice@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox