[PATCH] gnu: muchsync: Use pandoc instead of ghc-pandoc.

  • Done
  • quality assurance status badge
Details
2 participants
  • Marius Bakke
  • zimoun
Owner
unassigned
Submitted by
zimoun
Severity
normal
Z
Z
zimoun wrote on 7 Oct 2020 17:24
(address . guix-patches@gnu.org)(name . zimoun)(address . zimon.toutoune@gmail.com)
20201007152411.15729-1-zimon.toutoune@gmail.com
* gnu/packages/mail.scm (muchsync)[native-inputs]: Replace ghc-pandoc with
pandoc.
---
gnu/packages/mail.scm | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)

Toggle diff (17 lines)
diff --git a/gnu/packages/mail.scm b/gnu/packages/mail.scm
index 2bab7b4645..dc41bb66ee 100644
--- a/gnu/packages/mail.scm
+++ b/gnu/packages/mail.scm
@@ -1209,7 +1209,7 @@ and search library.")
(base32 "1k2m44pj5i6vfhp9icdqs42chsp208llanc666p3d9nww8ngq2lb"))))
(build-system gnu-build-system)
(native-inputs
- `(("ghc-pandoc" ,ghc-pandoc)
+ `(("pandoc" ,pandoc)
("pkg-config" ,pkg-config)))
(inputs
`(("libcrypto" ,openssl)

base-commit: fb0037af8cecc0ebaa330392b0c54a35b7b8a424
--
2.28.0
M
M
Marius Bakke wrote on 13 Oct 2020 22:41
Re: [bug#43848] [PATCH] gnu: muchsync: Use pandoc instead of ghc-pandoc.
(name . zimoun)(address . zimon.toutoune@gmail.com)
87sgahrh7z.fsf@gnu.org
zimoun <zimon.toutoune@gmail.com> writes:

Toggle quote (3 lines)
> * gnu/packages/mail.scm (muchsync)[native-inputs]: Replace ghc-pandoc with
> pandoc.

Applied, thanks!
-----BEGIN PGP SIGNATURE-----

iQFDBAEBCgAtFiEEu7At3yzq9qgNHeZDoqBt8qM6VPoFAl+GERAPHG1hcml1c0Bn
bnUub3JnAAoJEKKgbfKjOlT6i+EH/iIkHXsVtgMnDViPQA31TeTM22CWB/fgubiA
k3FQy22E67qChPxuKlbVjX8+xMsjj+pKNtOoPzWHqbNGAnouXxG8qdzoVHP6y9MD
5dgZn1SSBnfFieCS5Hclm5JQRt0fr1azK89vxaK2GbedSiYBWheruAukjHZBKwqT
/uAvkDBYDmCtpONAF/odLHNNeSX82Kd1lTc3yLbxZakwUQW1P3XIPaEIHlqZA5Gk
Fs/er/kOXeZevm/d7k5ykZyQjgeNPj5EiN3m4jUPWc4YIUrhyUIwkZoEBM2F1cco
Ec3dXT1P0TDtfZNYfNj8sfkOTcNg8Ok+9aaxt/RovmQ58tcilFU=
=4lc8
-----END PGP SIGNATURE-----

Closed
?
Your comment

This issue is archived.

To comment on this conversation send an email to 43848@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 43848
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch