diff mbox series

package/libnss: bump version to 3.67

Message ID 20210612173513.2253959-1-giulio.benetti@benettiengineering.com
State Changes Requested
Headers show
Series package/libnss: bump version to 3.67 | expand

Commit Message

Giulio Benetti June 12, 2021, 5:35 p.m. UTC
Note: NSS 3.67(like NSS 3.66) requires NSPR 4.31.
Release Notes (not yet available, but should eventually land):
https://developer.mozilla.org/en-US/docs/Mozilla/Projects/NSS/NSS_3.67_release_notes

Signed-off-by: Giulio Benetti <giulio.benetti@benettiengineering.com>
---
 package/libnss/libnss.hash | 4 ++--
 package/libnss/libnss.mk   | 2 +-
 2 files changed, 3 insertions(+), 3 deletions(-)

Comments

Giulio Benetti June 12, 2021, 5:38 p.m. UTC | #1
Hello All,

this patch superseeds the one which bumps to 3.66 [1], but the one which 
updates libnspr to 4.31 [2] is needed.


[1]: 
https://patchwork.ozlabs.org/project/buildroot/patch/20210531102947.7501-3-giulio.benetti@benettiengineering.com/
[2]: 
https://patchwork.ozlabs.org/project/buildroot/patch/20210531102947.7501-2-giulio.benetti@benettiengineering.com/

Best regards
Thomas Petazzoni July 20, 2021, 8:44 p.m. UTC | #2
Hello Giulio,

On Sat, 12 Jun 2021 19:35:13 +0200
Giulio Benetti <giulio.benetti@benettiengineering.com> wrote:

> Note: NSS 3.67(like NSS 3.66) requires NSPR 4.31.
> Release Notes (not yet available, but should eventually land):
> https://developer.mozilla.org/en-US/docs/Mozilla/Projects/NSS/NSS_3.67_release_notes
> 
> Signed-off-by: Giulio Benetti <giulio.benetti@benettiengineering.com>

This patch doesn't apply in master: master has libnss 3.65, and your
patch assumes a code base that has libnss 3.66.

Also, according to your reply to this e-mail, libnspr 4.31 is needed as
a requirement for this bump of libnss, so you should always resend both
in a single series.

Could you resend the libnspr and libnss version bumps in a single patch
series, rebased on master ?

Thanks a lot!

Thomas
Giulio Benetti July 20, 2021, 9:09 p.m. UTC | #3
Hello Thomas,

On 7/20/21 10:44 PM, Thomas Petazzoni wrote:
> Hello Giulio,
> 
> On Sat, 12 Jun 2021 19:35:13 +0200
> Giulio Benetti <giulio.benetti@benettiengineering.com> wrote:
> 
>> Note: NSS 3.67(like NSS 3.66) requires NSPR 4.31.
>> Release Notes (not yet available, but should eventually land):
>> https://developer.mozilla.org/en-US/docs/Mozilla/Projects/NSS/NSS_3.67_release_notes
>>
>> Signed-off-by: Giulio Benetti <giulio.benetti@benettiengineering.com>
> 
> This patch doesn't apply in master: master has libnss 3.65, and your
> patch assumes a code base that has libnss 3.66.
> 
> Also, according to your reply to this e-mail, libnspr 4.31 is needed as
> a requirement for this bump of libnss, so you should always resend both
> in a single series.

Ah sorry, you're right.

> Could you resend the libnspr and libnss version bumps in a single patch
> series, rebased on master ?


Sure I can. Here there is a "problem" if we can call it that way. It's 
from some month that they release very very fast. Now they are at NSS 
3.68 and NSPR 4.32 [1], but very soon there will be version 3.69. Even 
if I send version bumps, they will release another version before you 
apply for sure. Let's see if it gets slower.
They also stopped emitting the Release Notes that doesn't help[2].

What can I do? Do I send the latest I see in the moment I bump and 
that's it, right?

[1]: https://hg.mozilla.org/projects/nss
[2]: 
https://developer.mozilla.org/en-US/docs/Mozilla/Projects/NSS/NSS_Releases

Best regards
Thomas Petazzoni July 20, 2021, 9:33 p.m. UTC | #4
On Tue, 20 Jul 2021 23:09:05 +0200
Giulio Benetti <giulio.benetti@benettiengineering.com> wrote:

> Sure I can. Here there is a "problem" if we can call it that way. It's 
> from some month that they release very very fast. Now they are at NSS 
> 3.68 and NSPR 4.32 [1], but very soon there will be version 3.69. Even 
> if I send version bumps, they will release another version before you 
> apply for sure. Let's see if it gets slower.
> They also stopped emitting the Release Notes that doesn't help[2].
> 
> What can I do? Do I send the latest I see in the moment I bump and 
> that's it, right?

Correct. Whenever you see a new version, send a new patch series which
is based on the latest master, and mark your previous patches in
patchwork as "Superseded".

Thanks!

Thomas
diff mbox series

Patch

diff --git a/package/libnss/libnss.hash b/package/libnss/libnss.hash
index 7b27d859b2..3fdb0af6ca 100644
--- a/package/libnss/libnss.hash
+++ b/package/libnss/libnss.hash
@@ -1,4 +1,4 @@ 
-# From https://ftp.mozilla.org/pub/security/nss/releases/NSS_3_66_RTM/src/SHA256SUMS
-sha256  89a79e3a756cf0ac9ba645f4d4c0fc58d4133134401fb0b6c8a74c420bb4cdc9  nss-3.66.tar.gz
+# From https://ftp.mozilla.org/pub/security/nss/releases/NSS_3_67_RTM/src/SHA256SUMS
+sha256  f6549a9148cd27b394b40c77fa73111d5ea23cdb51d796665de1b7458f88ce7f  nss-3.67.tar.gz
 # Locally calculated
 sha256  a20c1a32d1f8102432360b42e932869f7c11c7cdbacf9cac554c422132af47f4  nss/COPYING
diff --git a/package/libnss/libnss.mk b/package/libnss/libnss.mk
index c5398c2959..32b4c379c7 100644
--- a/package/libnss/libnss.mk
+++ b/package/libnss/libnss.mk
@@ -4,7 +4,7 @@ 
 #
 ################################################################################
 
-LIBNSS_VERSION = 3.66
+LIBNSS_VERSION = 3.67
 LIBNSS_SOURCE = nss-$(LIBNSS_VERSION).tar.gz
 LIBNSS_SITE = https://ftp.mozilla.org/pub/mozilla.org/security/nss/releases/NSS_$(subst .,_,$(LIBNSS_VERSION))_RTM/src
 LIBNSS_DISTDIR = dist