On Tue, Mar 15, 2016 at 08:32:09PM -0400, Justin Geibel wrote: > I'm really new to haskell, so this is probably a bit beyond my depth.
That's okay; we've fixed it now. The armel http2 doctest failure is still a problem. > I've started by packaging http-media 0.6.3. I cloned DHG_packages and used > http2 as a starting point (since it seemed to be recently packaged). I now > have a build of the package working locally. I've requested membership on > the alioth group, is that the best place to push a branch for review or is > there some other preferred workflow? You can push it to master and we'll take a look. > The only issues I ran into where: > * I don't know how to include both a lower and upper bound on dependencies, > as was done in the upstream cabal file. For now I've only included the > lower bounds in the control file. We would translate something like base16-bytestring >= 0.1.1.6 && < 0.2 to libghc-base16-bytestring-dev (>= 0.1.1.6), libghc-base16-bytestring-dev (<< 0.2), > * I had to add a few -prof packages to get it to build. I'm not sure how > to determine that in advance, other than attempt a build and see what fails. You'll need -prof packages matching each -dev dependency corresponding to a library (and not if it's just used in a binary or a testsuite). > * I noticed things like libghc-base-dev and libghc-bytestring-dev are > virtual packages provided by ghc, so didn't explicitly include them in the > control file. Correct. You may wish to install the pkg-haskell-tools package (which will pull in cabal-debian as a dependency) so you need to do less by hand. This looks like it's partially out of date, but https://wiki.debian.org/Haskell/CollabMaint/GettingStarted
