mbox series

[bug#43330,0/6] Use pandoc instead of ghc-pandoc

Message ID 20200911104101.1805-1-zimon.toutoune@gmail.com
Headers show
Series Use pandoc instead of ghc-pandoc | expand

Message

zimoun Sept. 11, 2020, 10:41 a.m. UTC
From: simon <simon@pfiuh02.univ-paris-diderot.fr>

Dear,

These patches close #33844 <http://issues.guix.gnu.org/issue/33844>.
However, the bug number is not mentioned in the commit messages, mimicking
previous commit messages doing the same.

Note that rapicorn does not build, independently of {ghc-,}pandoc.  See:

https://data.guix.gnu.org/repository/1/branch/master/package/rapicorn/output-history

All the best,
simon


zimoun (6):
  gnu: ruby-pandoc-ruby: Use pandoc instead of ghc-pandoc.
  gnu: emacs-ox-pandoc: Use pandoc instead of ghc-pandoc.
  gnu: emacs-org-web-tools: Use pandoc instead of ghc-pandoc.
  gnu: manuskript: Use pandoc instead of ghc-pandoc.
  gnu: ganeti: Use pandoc instead of ghc-pandoc.
  gnu: rapicorn: Use pandoc instead of ghc-pandoc.

 gnu/packages/emacs-xyz.scm      | 4 ++--
 gnu/packages/graphics.scm       | 2 +-
 gnu/packages/ruby.scm           | 4 ++--
 gnu/packages/text-editors.scm   | 2 +-
 gnu/packages/virtualization.scm | 2 +-
 5 files changed, 7 insertions(+), 7 deletions(-)


base-commit: 0574446be82ef54b925441e4283bf754a86918a9

Comments

Ludovic Courtès Sept. 13, 2020, 9:27 p.m. UTC | #1
Hi,

zimoun <zimon.toutoune@gmail.com> skribis:

> These patches close #33844 <http://issues.guix.gnu.org/issue/33844>.
> However, the bug number is not mentioned in the commit messages, mimicking
> previous commit messages doing the same.
>
> 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.

[...]

>   gnu: ruby-pandoc-ruby: Use pandoc instead of ghc-pandoc.
>   gnu: emacs-ox-pandoc: Use pandoc instead of ghc-pandoc.
>   gnu: emacs-org-web-tools: Use pandoc instead of ghc-pandoc.
>   gnu: manuskript: Use pandoc instead of ghc-pandoc.
>   gnu: ganeti: Use pandoc instead of ghc-pandoc.
>   gnu: rapicorn: Use pandoc instead of ghc-pandoc.

It all LGTM; Ricardo, could you confirm this is as intended?

Thanks,
Ludo’.
Ricardo Wurmus Sept. 13, 2020, 9:39 p.m. UTC | #2
Ludovic Courtès <ludo@gnu.org> writes:

> Hi,
>
> zimoun <zimon.toutoune@gmail.com> skribis:
>
>> These patches close #33844 <http://issues.guix.gnu.org/issue/33844>.
>> However, the bug number is not mentioned in the commit messages, mimicking
>> previous commit messages doing the same.
>>
>> 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.

>>   gnu: ruby-pandoc-ruby: Use pandoc instead of ghc-pandoc.
>>   gnu: emacs-ox-pandoc: Use pandoc instead of ghc-pandoc.
>>   gnu: emacs-org-web-tools: Use pandoc instead of ghc-pandoc.
>>   gnu: manuskript: Use pandoc instead of ghc-pandoc.
>>   gnu: ganeti: Use pandoc instead of ghc-pandoc.
>>   gnu: rapicorn: Use pandoc instead of ghc-pandoc.
>
> It all LGTM; Ricardo, could you confirm this is as intended?

Yes, this looks all fine to me.
zimoun Sept. 14, 2020, 7:59 a.m. UTC | #3
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
Ludovic Courtès Sept. 14, 2020, 8:03 a.m. UTC | #4
Hi,

Ricardo Wurmus <rekado@elephly.net> skribis:

> Yes, this looks all fine to me.

Applied’em all, thanks!

Ludo’.