Package Details: gitit 0.15.0.0-1

Git Clone URL: https://aur.archlinux.org/gitit.git (read-only, click to copy)
Package Base: gitit
Description: A wiki backed by a git, darcs, or mercurial filestore
Upstream URL: https://hackage.haskell.org/package/gitit
Keywords: darcs git gitit haskell mercurial wiki
Licenses: GPL
Submitter: Rufflewind
Maintainer: Rufflewind
Last Packager: Rufflewind
Votes: 7
Popularity: 0.000000
First Submitted: 2015-09-09 08:23 (UTC)
Last Updated: 2021-09-16 17:43 (UTC)

Dependencies (8)

Required by (0)

Sources (214)

Latest Comments

« First ‹ Previous 1 2 3 4 Next › Last »

Repentinus commented on 2021-05-28 03:08 (UTC)

Rufflewind, could you please rewrite this PKGBUILD to conform to the Haskell package guidelines?

Rufflewind commented on 2019-01-13 08:18 (UTC)

@houbaron: I tried fixing the plugin issue. For rather complicated reasons, it's not really possible to make this work as an AUR package, so I'm disabling plugins entirely. If you wish to use plugins, I suggest building gitit directly using cabal + ghc-pristine, as outlined here.

houbaron commented on 2019-01-11 10:59 (UTC) (edited on 2019-01-11 10:59 (UTC) by houbaron)

@Rufflewind Another problem: The program want to load plugin from the temp build directory. Logs:

$ gitit -f .config/gitit/default.conf
Loading plugin '/usr/share/gitit/x86_64-linux-ghc-8.6.3/gitit-0.12.3.1/plugins/Interwiki.hs'...
gitit: /var/tmp/pamac-build-houbaron/gitit/src/.local/lib/ghc-8.6.3/settings: openFile: does not exist (No such file or directory)

While I can find this settings in /usr/lib/ghc-8.6.3.

houbaron commented on 2019-01-11 09:15 (UTC)

Thank you, @Rufflewind

Rufflewind commented on 2018-12-21 20:05 (UTC)

@houbaron: I made a temporary fix to the PKGBUILD so that gitit can be built while https://github.com/jgm/gitit/issues/625 is being resolved.

Rufflewind commented on 2018-12-19 18:23 (UTC)

@houbaron: Sorry, gitit is not compatible with the latest Haskell compiler in Arch Linux: https://github.com/jgm/gitit/issues/625

Until that issue resolved, this package is going to be broken.

houbaron commented on 2018-12-19 12:19 (UTC) (edited on 2018-12-19 12:28 (UTC) by houbaron)

Hi there, I met such warnings after installation, what should I do?

Resolving dependencies...
cabal: Could not resolve dependencies:
[__0] trying: gitit-0.12.3 (user goal)
[__1] trying: xml-conduit-1.8.0.1 (dependency of gitit)
[__2] trying: resourcet-1.2.1 (dependency of xml-conduit)
[__3] trying: exceptions-0.8.3 (dependency of resourcet)
[__4] next goal: template-haskell (dependency of exceptions)
[__4] rejecting: template-haskell-2.14.0.0/installed-2.1... (conflict:
exceptions => template-haskell>=2.2 && <2.14)
[__4] fail (backjumping, conflict set: exceptions, template-haskell)
After searching the rest of the dependency tree exhaustively, these were the
goals I've had most trouble fulfilling: exceptions, gitit, resourcet,
template-haskell, xml-conduit
Note: when using a sandbox, all packages are required to have consistent
dependencies. Try reinstalling/unregistering the offending packages or
recreating the sandbox.

guygma commented on 2018-09-28 19:06 (UTC)

@Rufflewind: Ah, I see. Well, way to track that subtle issue down; +1 for good maintenance. For what it is worth stack does install gitit just fine (that is how I have done it), but I imagine the same issue that 3e4 saw is what would come up using that method in the PKGBUILD since you ideally wouldn't want to bring the whole stack root over onto the actual arch system in addition to just the gitit binary.

Rufflewind commented on 2018-09-28 04:21 (UTC)

@guygma: I switched back to Cabal a year ago because of this: https://aur.archlinux.org/cgit/aur.git/commit/PKGBUILD?h=gitit&id=c2b9a66c0e65

The dependencies are tracked automatically by a script.

guygma commented on 2018-09-28 03:28 (UTC)

I do not understand the state of this PKGBUILD. You say you switched to stack, but you have not. It would almost certainly be easier than having to manually keep track of the bajillion haskell modules to pull in by hand... Maybe I am missing something, but a stack build in a clean chroot and installing the binary a la all packages seems like the way to go.

« First ‹ Previous 1 2 3 4 Next › Last »