From: Giulio Benetti <giulio.benetti@benettiengineering.com> To: buildroot@busybox.net Subject: [Buildroot] [PATCH] package/libnss: bump version to 3.67 Date: Tue, 20 Jul 2021 23:09:05 +0200 [thread overview] Message-ID: <900065c9-8832-df20-35ac-ea69cbfe72e4@benettiengineering.com> (raw) In-Reply-To: <20210720224443.24edcd0f@windsurf> 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 -- Giulio Benetti Benetti Engineering sas
WARNING: multiple messages have this Message-ID (diff)
From: Giulio Benetti <giulio.benetti@benettiengineering.com> To: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Cc: Joseph Kogut <joseph.kogut@gmail.com>, buildroot@buildroot.org Subject: Re: [Buildroot] [PATCH] package/libnss: bump version to 3.67 Date: Tue, 20 Jul 2021 23:09:05 +0200 [thread overview] Message-ID: <900065c9-8832-df20-35ac-ea69cbfe72e4@benettiengineering.com> (raw) Message-ID: <20210720210905.5ykLz-ChYGiGQr1mxcQ0x__RsELnVxGgqGURxcaWCik@z> (raw) In-Reply-To: <20210720224443.24edcd0f@windsurf> 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 -- Giulio Benetti Benetti Engineering sas _______________________________________________ buildroot mailing list buildroot@busybox.net http://lists.busybox.net/mailman/listinfo/buildroot
next prev parent reply other threads:[~2021-07-20 21:09 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-06-12 17:35 [Buildroot] [PATCH] package/libnss: bump version to 3.67 Giulio Benetti 2021-06-12 17:38 ` Giulio Benetti 2021-07-20 20:44 ` Thomas Petazzoni 2021-07-20 20:44 ` Thomas Petazzoni 2021-07-20 21:09 ` Giulio Benetti [this message] 2021-07-20 21:09 ` Giulio Benetti 2021-07-20 21:33 ` Thomas Petazzoni 2021-07-20 21:33 ` Thomas Petazzoni 2021-07-22 23:35 ` [Buildroot] [PATCH 0/2] Bump NSS and NSPR Giulio Benetti 2021-07-22 23:35 ` [Buildroot] [PATCH 1/2] package/libnspr: bump to version 4.32 Giulio Benetti 2021-07-22 23:35 ` [Buildroot] [PATCH 2/2] package/libnss: bump to version 3.68 Giulio Benetti 2021-07-25 13:09 ` [Buildroot] [PATCH 0/2] Bump NSS and NSPR Thomas Petazzoni
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=900065c9-8832-df20-35ac-ea69cbfe72e4@benettiengineering.com \ --to=giulio.benetti@benettiengineering.com \ --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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.