unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: Pierre Neidhardt <mail@ambrevar.xyz>
Cc: 39798@debbugs.gnu.org
Subject: [bug#39798] [PATCH 00/13] Update Pandoc.
Date: Wed, 26 Feb 2020 19:04:05 +0100	[thread overview]
Message-ID: <87r1yhi5t6.fsf@elephly.net> (raw)
In-Reply-To: <20200226113442.9798-1-mail@ambrevar.xyz>


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

  parent reply	other threads:[~2020-02-26 18:05 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-26 11:34 [bug#39798] [PATCH 00/13] Update Pandoc Pierre Neidhardt
2020-02-26 11:45 ` [bug#39798] [PATCH 01/13] gnu: ghc-hsyaml: Update to 0.2.1.0 Pierre Neidhardt
2020-02-26 11:45   ` [bug#39798] [PATCH 02/13] gnu: ghc-doctemplates: Update to 0.8.1 Pierre Neidhardt
2020-02-26 11:45   ` [bug#39798] [PATCH 03/13] gnu: Add ghc-regex-base-0.94 Pierre Neidhardt
2020-02-26 11:45   ` [bug#39798] [PATCH 05/13] gnu: ghc-skylighting-core: Update to 0.8.3.2 Pierre Neidhardt
2020-02-26 11:45   ` [bug#39798] [PATCH 06/13] gnu: ghc-skylighting: " Pierre Neidhardt
2020-02-26 11:45   ` [bug#39798] [PATCH 07/13] gnu: ghc-pandoc-types: Update to 1.20 Pierre Neidhardt
2020-02-26 11:46   ` [bug#39798] [PATCH 08/13] gnu: ghc-texmath: Update to 0.12.0.1 Pierre Neidhardt
2020-02-26 11:46   ` [bug#39798] [PATCH 09/13] gnu: Add ghc-base-compat-0.11 Pierre Neidhardt
2020-02-26 11:46   ` [bug#39798] [PATCH 10/13] gnu: Add ghc-optparse-applicative-0.15 Pierre Neidhardt
2020-02-26 11:46   ` [bug#39798] [PATCH 11/13] gnu: ghc-haddock-library: Update to 1.8.0 Pierre Neidhardt
2020-02-26 11:46   ` [bug#39798] [PATCH 12/13] gnu: ghc-pandoc: Update to 2.9.2 Pierre Neidhardt
2020-02-26 11:46   ` [bug#39798] [PATCH 13/13] gnu: ghc-pandoc: Rename to pandoc Pierre Neidhardt
2020-02-26 18:04 ` Ricardo Wurmus [this message]
2020-02-27  7:51   ` [bug#39798] [PATCH 00/13] Update Pandoc Pierre Neidhardt
2020-03-02  8:45     ` zimoun
2020-03-02  8:56       ` Pierre Neidhardt
2020-05-27 14:24 ` Ricardo Wurmus
2020-05-27 14:38   ` Pierre Neidhardt
2020-09-09 16:39 ` zimoun
2020-09-09 17:02   ` Ricardo Wurmus
2020-09-14 17:49     ` zimoun
2020-10-07 15:32 ` bug#39798: " zimoun

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=87r1yhi5t6.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=39798@debbugs.gnu.org \
    --cc=mail@ambrevar.xyz \
    /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).