mbox

[bug#39798,00/13] Update Pandoc.

Message ID 20200226113442.9798-1-mail@ambrevar.xyz
Headers show

Message

Pierre Neidhardt Feb. 26, 2020, 11:34 a.m. UTC
Update ghc-pandoc to 2.92 and rename it to pandoc.
This closes bug 33844.

Questions:

- Should this go on staging?  It rebuilds a few hundred packages, maybe less
than 300.
- I'm not 100% sure that updating the Haskell libraries didn't break
anything.  I guess the continuous integration will tell us.
- 3-4 libraries seemed to have many dependents and updating them would break
  stuff, so instead I created a versioned package, e.g. ghc-regex-base-0.94.
  Is this OK?  Is there a best practice here?

Pierre Neidhardt (13):
  gnu: ghc-hsyaml: Update to 0.2.1.0.
  gnu: ghc-doctemplates: Update to 0.8.1.
  gnu: Add ghc-regex-base-0.94.
  gnu: ghc-regex-pcre-builtin: Update to 0.95.1.1.8.43.
  gnu: ghc-skylighting-core: Update to 0.8.3.2.
  gnu: ghc-skylighting: Update to 0.8.3.2.
  gnu: ghc-pandoc-types: Update to 1.20.
  gnu: ghc-texmath: Update to 0.12.0.1.
  gnu: Add ghc-base-compat-0.11.
  gnu: Add ghc-optparse-applicative-0.15.
  gnu: ghc-haddock-library: Update to 1.8.0.
  gnu: ghc-pandoc: Update to 2.9.2.
  gnu: ghc-pandoc: Rename to pandoc.

 gnu/local.mk                                  |   2 -
 gnu/packages/haskell-xyz.scm                  | 130 ++++++++++++------
 .../patches/ghc-pandoc-fix-html-tests.patch   |  92 -------------
 .../patches/ghc-pandoc-fix-latex-test.patch   |  31 -----
 4 files changed, 89 insertions(+), 166 deletions(-)
 delete mode 100644 gnu/packages/patches/ghc-pandoc-fix-html-tests.patch
 delete mode 100644 gnu/packages/patches/ghc-pandoc-fix-latex-test.patch

Comments

Ricardo Wurmus Feb. 26, 2020, 6:04 p.m. UTC | #1
Pierre Neidhardt <mail@ambrevar.xyz> writes:

> Update ghc-pandoc to 2.92 and rename it to pandoc.
> This closes bug 33844.
>
> Questions:
>
> - Should this go on staging?  It rebuilds a few hundred packages, maybe less
> than 300.
> - I'm not 100% sure that updating the Haskell libraries didn't break
> anything.  I guess the continuous integration will tell us.
> - 3-4 libraries seemed to have many dependents and updating them would break
>   stuff, so instead I created a versioned package, e.g. ghc-regex-base-0.94.
>   Is this OK?  Is there a best practice here?

I would prefer to untangle upgrading any packages from renaming
ghc-pandoc to pandoc.

Haskell package upgrades need to be consistent according to the current
LTS.  We can’t just upgrade some Haskell packages without upgrading them
all.  They also cannot be upgraded to the latest version as that may be
higher than the LTS version.

--
Ricardo
Pierre Neidhardt Feb. 27, 2020, 7:51 a.m. UTC | #2
Ricardo Wurmus <rekado@elephly.net> writes:

>> - Should this go on staging?  It rebuilds a few hundred packages, maybe less
>> than 300.
>> - I'm not 100% sure that updating the Haskell libraries didn't break
>> anything.  I guess the continuous integration will tell us.
>> - 3-4 libraries seemed to have many dependents and updating them would break
>>   stuff, so instead I created a versioned package, e.g. ghc-regex-base-0.94.
>>   Is this OK?  Is there a best practice here?
>
> I would prefer to untangle upgrading any packages from renaming
> ghc-pandoc to pandoc.

No problem.

> Haskell package upgrades need to be consistent according to the current
> LTS.  We can’t just upgrade some Haskell packages without upgrading them
> all.  They also cannot be upgraded to the latest version as that may be
> higher than the LTS version.

I'm new to Haskell packaging.  Where do I find the LTS versions?
Can we update pandoc then?
Simon Tournier March 2, 2020, 8:45 a.m. UTC | #3
Hi Pierre,

On Thu, 27 Feb 2020 at 08:52, Pierre Neidhardt <mail@ambrevar.xyz> wrote:
> Ricardo Wurmus <rekado@elephly.net> writes:

> > Haskell package upgrades need to be consistent according to the current
> > LTS.  We can’t just upgrade some Haskell packages without upgrading them
> > all.  They also cannot be upgraded to the latest version as that may be
> > higher than the LTS version.
>
> I'm new to Haskell packaging.  Where do I find the LTS versions?
> Can we update pandoc then?

I am not closely following the Haskell packaging in Guix, but you
should find the LTS versions there:
https://www.stackage.org/
It is better to upgrade all the Haskell packages (compiler included)
to stay compliant with the LTS, otherwise it should become a mess
falling in the Cabal Hell.

https://en.wikipedia.org/wiki/Cabal_(software)#Criticism


Hope that helps.
simon
Pierre Neidhardt March 2, 2020, 8:56 a.m. UTC | #4
Makes sense, thanks!
Ricardo Wurmus May 27, 2020, 2:24 p.m. UTC | #5
Hi Pierre,

> Update ghc-pandoc to 2.92 and rename it to pandoc.
> This closes bug 33844.

We have a stackage importer that can help here.  We should update to the
latest LTS Haskell release of 15.14.

The version of Pandoc in that LTS Haskell release is 2.9.1.1.

We will also need a new GHC (8.8.3), and all other Haskell packages need
to upgraded together.

This could then go to a new branch that we can have ci.guix.gnu.org
build for us.

I’m about to finish a few changes to the haskell-build-system and our
current GHC package to reduce the closure size; that could also go to
the same branch.

Would you like to help with the update or should we close this issue?
Pierre Neidhardt May 27, 2020, 2:38 p.m. UTC | #6
Hi Ricardo,

Thanks for the update, looks great!

I originally sent this patch because I needed pandoc 2.9.* at some
point, but I no longer use it (at least for now) and I'm no Haskeller so
my motivation is a bit low to be honest :D

If no one else gets to it, I may give this a shot in a while (don't hold
your breat) :p

I suggest you let know guix-devel, hopefully someone will chime in!
Simon Tournier Sept. 9, 2020, 4:39 p.m. UTC | #7
Dear,

On Wed, 26 Feb 2020 at 12:34, Pierre Neidhardt <mail@ambrevar.xyz> wrote:

> Update ghc-pandoc to 2.92 and rename it to pandoc.

Does this patch set [1] still make sense?
Especially after the merge [2] of wip-haskell and since the patches are
not consistent with LTS, AFAICT.

> This closes bug 33844.

Almost close by commit d4e4a3824d380e576b56a74aa714db205fcc59a4.


[1] http://issues.guix.gnu.org/issue/39798
[2] https://lists.gnu.org/archive/html/guix-devel/2020-08/msg00017.html

All the best,
simon
Ricardo Wurmus Sept. 9, 2020, 5:02 p.m. UTC | #8
zimoun <zimon.toutoune@gmail.com> writes:
>
> On Wed, 26 Feb 2020 at 12:34, Pierre Neidhardt <mail@ambrevar.xyz> wrote:
>
>> Update ghc-pandoc to 2.92 and rename it to pandoc.
>
> Does this patch set [1] still make sense?
> Especially after the merge [2] of wip-haskell and since the patches are
> not consistent with LTS, AFAICT.

The lack of consistency is the biggest problem.  Since Pierre has no
motivation to continue working on these patches I’d say we should close
this issue.
Simon Tournier Sept. 14, 2020, 5:49 p.m. UTC | #9
Dear,

>>> Update ghc-pandoc to 2.92 and rename it to pandoc.

Commit d4e4a3824d380e576b56a74aa714db205fcc59a4 adds the package
pandoc.  Then couples of commits rename all the dependencies.

Moreover, updating to 2.92 without consistency with Haskell LTS packages
is a problem.

Therefore, I am closing.  Feel free to reopen if there is motivation to
continue working on these patches.

All the best,
simon
Simon Tournier Oct. 7, 2020, 3:32 p.m. UTC | #10
Closing with the explanations here:

    <http://issues.guix.gnu.org/issue/39798#21>

Thanks,
simon