Hi Jonas, On Sun, 2022-06-05 at 17:31 +0200, Jonas Smedegaard wrote: > Quoting Jonas Smedegaard (2022-05-30 15:40:57) > > Quoting Robert Greener (2022-05-30 15:20:34) > > > On Sat, 2022-05-07 at 19:09 +0100, Robert Greener wrote: > > > > > I would like to update some packages so that pandoc can be > > > > > updated. > > > > > > > > > > /Lots/ of packages would need to be updated to update pandoc > > > > > to its > > > > > latest upstream (2.18). It is currently on 2.9.2.1. > > > > > > > > > > To make the task simpler, I intend to update the dependencies > > > > > so that > > > > > it can be bumped to 2.10.1, and then keep working up. > > > Jonas - Once haskell-commonmark-pandoc has been uploaded by Scott > > > & > > > gone through the NEW queue, you should have enough to upgrade > > > pandoc to > > > 2.10.1. Could you put this in experimental & I will update hakyll > > > and > > > patch patat & then everything can be moved to unstable. > > > > Yes, sounds like I have plenty to work with now. > > Pandoc 2.10 is now succesfully built in experimental. Excellent -- thanks! > Feel free to release dependency updates for that to unstable, then I > will release pandoc 2.10 to unstable as well. > > When haskell-commonmark-pandoc enters experimental I will look into > upgrading pandoc to 2.10.1. > > When haskell-pandoc-types is upgraded to 1.23 then I will look into > upgrading pandoc to 2.11 or newer... I'm away for the next few weeks. When I'm back I'll upgrade the few things that depend on pandoc and then it can all be moved. Hopefully, haskell-commonmark-pandoc will be in experimental by the time I'm back. You may want to follow the ITP bug (#1011459) so you get notified when it's in experimental. > Please note that if you choose to upgrade pandoc-types *before* > releasing current updates to unstable, then risk is higher that we > end > in a more complicated situation. Your choice. I'll leave it until its in unstable. -- Robert
Attachment:
signature.asc
Description: This is a digitally signed message part