Re: [Fink-users] Troubles Compiling pandoc

2014-10-03 Thread Brendan Cully
Yes, if sedding info files sounds scary, then you should probably wait (or use the bindist). On Friday, 03 October 2014 at 18:06, Lowell Tacconi-Garman wrote: > Sounds to me like I'm better off waiting a bit, right? Maybe coming back to > things next week some time? > >Oh boy. I really need to fi

Re: [Fink-users] Troubles Compiling pandoc

2014-10-03 Thread Brendan Cully
Oh boy. I really need to fix this in the source packages. It is possible to recover here, but it requires poking under the covers of dpkg a bit. You'd want to find ghc-* in /sw/var/lib/dpkg/info and for each of those files, comment out or delete the line "set -e". At that point, recursive remove sh

Re: [Fink-users] Troubles Compiling pandoc

2014-10-03 Thread Brendan Cully
There's a bug in the packaging. The ghc-mods need to depend on the exact point release of the compiler that built them in order to remain known to the ghc package system on upgrade. In this case, you'd have to I think remove ghc-text, then rebuild it so that it registered against current ghc. On

Re: [Fink-users] Troubles Compiling pandoc

2014-10-03 Thread Peter Dyballa
Am 03.10.2014 um 03:01 schrieb Lowell Tacconi-Garman: >> pandoc >> The following 28 additional packages will be installed: >> ghc-aeson ghc-attoparsec ghc-conduit ghc-digest ghc-exceptions >> ghc-hashable >> ghc-hslua ghc-lifted-base ghc-mmorph ghc-monad-control ghc-pandoc-types >> ghc-primitive

[Fink-users] Troubles Compiling pandoc

2014-10-02 Thread Lowell Tacconi-Garman
Hello, I am having problems compiling/installing pandoc, even after having run the recommended fink selfupdate. The log file is shown below. Can you please help? Thanks in advance, Lowell Tacconi-Garman Here follows the log... > The following package will be installed or updated: > pandoc