[Buildroot] [PATCH] package/uacme: bump version to 1.2.3

[Buildroot] [PATCH] package/uacme: bump version to 1.2.3

[Nicola Di Lieto]

This version fixes https://github.com/ndilieto/uacme/issues/22

Signed-off-by: Nicola Di Lieto <nicola.dilieto@gmail.com>
---
 package/uacme/uacme.hash | 2 +-
 package/uacme/uacme.mk   | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/package/uacme/uacme.hash b/package/uacme/uacme.hash
index abc30a7e54..44cff5cf61 100644
--- a/package/uacme/uacme.hash
+++ b/package/uacme/uacme.hash
@@ -1,3 +1,3 @@
 # Locally computed:
-sha256	26fa153118fc895f0961502d644e3606cccb7fb261594c2b7dd293decd0b0174        uacme-1.2.2.tar.gz
+sha256	7e737eadc4495512f4f41e39b6ed4e14476922e26953f1be3446d69c8e63d189        uacme-1.2.3.tar.gz
 sha256	8ceb4b9ee5adedde47b31e975c1d90c73ad27b6b165a1dcd80c7c545eb65b903	COPYING
diff --git a/package/uacme/uacme.mk b/package/uacme/uacme.mk
index 61d3f11ca1..6df13eced6 100644
--- a/package/uacme/uacme.mk
+++ b/package/uacme/uacme.mk
@@ -4,7 +4,7 @@
 #
 ################################################################################
 
-UACME_VERSION = 1.2.2
+UACME_VERSION = 1.2.3
 # Released versions are on branch upstream/latest, tagged as
 # upstream/X.Y.Z Do not use vX.Y.Z tags from master, as they do not
 # include .tarball-version
-- 
2.11.0

[Buildroot] [PATCH] package/uacme: bump version to 1.2.3

[Thomas Petazzoni]

On Thu, 23 Apr 2020 07:51:04 +0200
Nicola Di Lieto <nicola.dilieto@gmail.com> wrote:

> This version fixes https://github.com/ndilieto/uacme/issues/22
> 
> Signed-off-by: Nicola Di Lieto <nicola.dilieto@gmail.com>
> ---
>  package/uacme/uacme.hash | 2 +-
>  package/uacme/uacme.mk   | 2 +-
>  2 files changed, 2 insertions(+), 2 deletions(-)

Applied to master, thanks.

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

[Buildroot] [PATCH] package/uacme: bump version to 1.2.3

[Peter Korsgaard]

>>>>> "Nicola" == Nicola Di Lieto <nicola.dilieto@gmail.com> writes:

 > This version fixes https://github.com/ndilieto/uacme/issues/22
 > Signed-off-by: Nicola Di Lieto <nicola.dilieto@gmail.com>

Does that also affect the 1.0.21 version we have in 2020.02.x? If so,
what is the impact? Do we need to update to 1.2.3 or cherry pick a
patch?

-- 
Bye, Peter Korsgaard

[Buildroot] [PATCH] package/uacme: bump version to 1.2.3

[Nicola Di Lieto]

On Fri, May 08, 2020 at 10:11:00AM +0200, Peter Korsgaard wrote:
>Does that also affect the 1.0.21 version we have in 2020.02.x? If so,
>what is the impact? Do we need to update to 1.2.3 or cherry pick a
>patch?
>

Yes, all versions prior to 1.2.3 are affected. The impact for the moment 
is only with pebble (the non-production standalone let's encrypt testing 
server, https://github.com/letsencrypt/pebble).

The production let's encrypt server runs a different software (boulder) 
which doesn't trigger this bug, however this may change and I have no 
control over whether or when this will happen.

Therefore I recommend updating to a newer version. Also note that I 
released 1.3 about one hour ago which has a few more small fixes and 
enhancements, see https://github.com/ndilieto/uacme/blob/master/NEWS

Kind regards,
Nicola

[Buildroot] [PATCH] package/uacme: bump version to 1.2.3

[Peter Korsgaard]

>>>>> "Nicola" == Nicola Di Lieto <nicola.dilieto@gmail.com> writes:

 > On Fri, May 08, 2020 at 10:11:00AM +0200, Peter Korsgaard wrote:
 >> Does that also affect the 1.0.21 version we have in 2020.02.x? If so,
 >> what is the impact? Do we need to update to 1.2.3 or cherry pick a
 >> patch?
 >> 

 > Yes, all versions prior to 1.2.3 are affected. The impact for the
 > moment is only with pebble (the non-production standalone let's
 > encrypt testing server, https://github.com/letsencrypt/pebble).

 > The production let's encrypt server runs a different software
 > (boulder) which doesn't trigger this bug, however this may change and
 > I have no control over whether or when this will happen.

 > Therefore I recommend updating to a newer version.

Ok, I will bump to 1.2.3 then for 2020.02.x. Is there any backwards
compatibility issues with that?


 > Also note that I released 1.3 about one hour ago which has a few more
 > small fixes and enhancements, see
 > https://github.com/ndilieto/uacme/blob/master/NEWS

Ok, thanks. Will you send a patch to bump the version in Buildroot?

-- 
Bye, Peter Korsgaard

[Buildroot] [PATCH] package/uacme: bump version to 1.2.3

[Nicola Di Lieto]

On Sat, May 09, 2020 at 09:09:18AM +0200, Peter Korsgaard wrote:
>
> > Also note that I released 1.3 about one hour ago which has a few more
> > small fixes and enhancements, see
> > https://github.com/ndilieto/uacme/blob/master/NEWS
>
>Ok, thanks. Will you send a patch to bump the version in Buildroot?

I am preparing it right now. So maybe you want to wait until I post it 
and also update 2020.02.x to it.

Nicola

[Buildroot] [PATCH] package/uacme: bump version to 1.2.3

[Peter Korsgaard]

>>>>> "Nicola" == Nicola Di Lieto <nicola.dilieto@gmail.com> writes:

 > On Fri, May 08, 2020 at 10:11:00AM +0200, Peter Korsgaard wrote:
 >> Does that also affect the 1.0.21 version we have in 2020.02.x? If so,
 >> what is the impact? Do we need to update to 1.2.3 or cherry pick a
 >> patch?
 >> 

 > Yes, all versions prior to 1.2.3 are affected. The impact for the
 > moment is only with pebble (the non-production standalone let's
 > encrypt testing server, https://github.com/letsencrypt/pebble).

 > The production let's encrypt server runs a different software
 > (boulder) which doesn't trigger this bug, however this may change and
 > I have no control over whether or when this will happen.

 > Therefore I recommend updating to a newer version. Also note that I
 > released 1.3 about one hour ago which has a few more small fixes and
 > enhancements, see https://github.com/ndilieto/uacme/blob/master/NEWS

Sorry for the slow reponse, I have now updated 2020.02.x to 1.2.4.

-- 
Bye, Peter Korsgaard