From: zimoun <zimon.toutoune@gmail.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: simon <simon@pfiuh02.univ-paris-diderot.fr>,
"Ludovic Courtès" <ludo@gnu.org>,
43330@debbugs.gnu.org
Subject: [bug#43330] [PATCH 0/6] Use pandoc instead of ghc-pandoc
Date: Mon, 14 Sep 2020 09:59:07 +0200 [thread overview]
Message-ID: <CAJ3okZ3Bob3YvvOHF19jcCTw51QkxxwY1p3J2zXJotC7ezaDmA@mail.gmail.com> (raw)
In-Reply-To: <87bli9z79e.fsf@elephly.net>
Thank you for the quick review.
On Sun, 13 Sep 2020 at 23:38, Ricardo Wurmus <rekado@elephly.net> wrote:
> Ludovic Courtès <ludo@gnu.org> writes:
> > zimoun <zimon.toutoune@gmail.com> skribis:
> >> Note that rapicorn does not build, independently of {ghc-,}pandoc. See:
> >>
> >> https://data.guix.gnu.org/repository/1/branch/master/package/rapicorn/output-history
> >
> > Uh.
>
> Rapicorn was only ever used for Beast, which we will likely not be able
> to include going forward as they plan to depend on npm things.
The home-page URL <https://rapicorn.testbit.org/> is "Not found", as
the source <https://testbit.eu/pub/dists/rapicorn/rapicorn-16.0.0.tar.xz>.
And Github <https://github.com/tim-janik/rapicorn> says that the last
commit is 2017 (I do not know if it is the main upstream repo).
The package beast does not build either, but that's another story.
Well, I suggest removing both.
And this asks how to detect automatically and report broken packages.
Another story (Data Service or Cuirass). :-)
Cheers,
simon
next prev parent reply other threads:[~2020-09-14 8:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-11 10:41 [bug#43330] [PATCH 0/6] Use pandoc instead of ghc-pandoc zimoun
2020-09-11 10:43 ` [bug#43330] [PATCH 1/6] gnu: ruby-pandoc-ruby: " zimoun
2020-09-11 10:43 ` [bug#43330] [PATCH 2/6] gnu: emacs-ox-pandoc: " zimoun
2020-09-11 10:43 ` [bug#43330] [PATCH 3/6] gnu: emacs-org-web-tools: " zimoun
2020-09-11 10:43 ` [bug#43330] [PATCH 4/6] gnu: manuskript: " zimoun
2020-09-11 10:43 ` [bug#43330] [PATCH 5/6] gnu: ganeti: " zimoun
2020-09-11 10:43 ` [bug#43330] [PATCH 6/6] gnu: rapicorn: " zimoun
2020-09-13 21:27 ` [bug#43330] [PATCH 0/6] " Ludovic Courtès
2020-09-13 21:39 ` Ricardo Wurmus
2020-09-14 7:59 ` zimoun [this message]
2020-09-14 8:03 ` bug#43330: " Ludovic Courtès
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAJ3okZ3Bob3YvvOHF19jcCTw51QkxxwY1p3J2zXJotC7ezaDmA@mail.gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=43330@debbugs.gnu.org \
--cc=ludo@gnu.org \
--cc=rekado@elephly.net \
--cc=simon@pfiuh02.univ-paris-diderot.fr \
/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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).