[bug#51401] [PATCH] gnu: bitcoin-core@0.20: Update to 0.20.2

[bug#51401] [PATCH] gnu: bitcoin-core@0.20: Update to 0.20.2

[Michael Ford]

[-- Attachment #1: Type: text/plain, Size: 940 bytes --]

---
 gnu/packages/finance.scm | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/gnu/packages/finance.scm b/gnu/packages/finance.scm
index f0093ba635..df430bbe6e 100644
--- a/gnu/packages/finance.scm
+++ b/gnu/packages/finance.scm
@@ -193,7 +193,7 @@ (define-public bitcoin-core-0.21
 (define-public bitcoin-core-0.20
   (package
     (inherit bitcoin-core-0.21)
-    (version "0.20.1")
+    (version "0.20.2")
     (source (origin
               (method url-fetch)
               (uri
@@ -201,7 +201,7 @@ (define-public bitcoin-core-0.20
                               version "/bitcoin-" version ".tar.gz"))
               (sha256
                (base32
-
 "0y5rad68b398arh0abr2wgiwybdw0i5a4dxz9s3fk9fgdbyn5gab"))))))
+
 "14smp5vmh7baabl856wlg7w7y5910jhx6c02mlkm4hkywf3yylky"))))))

 ;; The support lifetimes for bitcoin-core versions can be found in
 ;; <https://bitcoincore.org/en/lifecycle/#schedule>.
-- 
2.33.1

[-- Attachment #2: Type: text/html, Size: 1281 bytes --]

[bug#51401] [PATCH] gnu: bitcoin-core@0.20: Update to 0.20.2

[Michael Ford]

[-- Attachment #1: Type: text/plain, Size: 139 bytes --]

Hi,

Just wanted to follow up and check whether there was anything blocking this
for merge, or if it's just stuck in the backlog?

Thanks,

[-- Attachment #2: Type: text/html, Size: 231 bytes --]

bug#51401: [PATCH] gnu: bitcoin-core@0.20: Update to 0.20.2

[Guillaume Le Vaillant]

[-- Attachment #1: Type: text/plain, Size: 644 bytes --]

Michael Ford <fanquake@gmail.com> skribis:

> Hi,
>
> Just wanted to follow up and check whether there was anything blocking this
> for merge, or if it's just stuck in the backlog?
>
> Thanks,

Hi,

The long delay in processing patches is indeed because there is a lot of
things in the backlog.

It looks like your email client mangled the patch (cutting long lines,
removing spaces). Could configure your client so that it doesn't do
that? If that's not possible you can also put patches in attachment.

I fixed the patch, added the changelog-style part of the commit message
and pushed it as 3d1c984ad857d9fd56b1ae068adf81cd8e05f83b.
Thanks.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]