FTBFS: unmet dependency for ghc6 << 6.6-999

[Daniel Hahler]

missingpy 0.9.0 fails to build from source.

My guess is that's there's a typo in the Build-Depends:
ghc6 (>= 6.6), ghc6 (<< 6.6-999)
should be:
ghc6 (>= 6.6), ghc6 (<< 6.6.999)

Does this make sense?

pbuilder log:
Installing the build-deps
 -> Attempting to parse the build-deps
 -> Considering build-dep debhelper (>= 5.0.37.2)
   -> Trying debhelper
 -> Considering build-dep ghc6 (>= 6.6)
   -> Trying ghc6
 -> Considering build-dep ghc6 (<< 6.6-999)
      Tried versions: 6.6.1-2ubuntu2
   -> Does not satisfy version, not trying
E: Could not satisfy build-dependency.
E: pbuilder-satisfydepends failed.

[Daniel Hahler (blueyed)]

Adjusting the ghc6 Build-Depends now caused another error.
So I've additionally had to edit the Makefile (inline, because there's no patch system) to use Python 2.5 (instead of 2.5).
I've adjusted the Build-Depends for python-dev accordingly.

I also had to fix the tests (probably because of new error format in Python 2.5).

[Daniel Hahler (blueyed)]

I've updated the debdiff:
- used the build-depends from missingh source package: "ghc6 (>= 6.6.1), ghc6 (<< 6.6.1-999)"
- a dependency on libghc6-anydbm-dev seems to be required for installation
- Standards-Version 3.7.2

[Chuck Short (zulcss)]

uploaded thanks for the patch

[Daniel Hahler (blueyed)]

missingpy (0.9.0ubuntu1) gutsy; urgency=low

  * debian/control: Fixed Build-Depends for ghc6 (LP: #136847)
    "ghc6 (>= 6.6), ghc6 (<< 6.6-999)"
     => "ghc6 (>= 6.6.1), ghc6 (<< 6.6.1-999)"
  * debian/control: DebianMaintainerField
  * debian/control: Build-Depend on python-dev 2.5
    "python-dev (>= 2.4)" => "python-dev (>= 2.5), python-dev (<< 2.6)"
  * debian/control: Depend on libghc6-anydbm-dev, as required during
    installation of the package
  * debian/control: Standards-Version 3.7.2
  * Makefile: use Python 2.5 instead of 2.4
  * testsrc/GZiptest.hs: fixed exception format (for Python 2.5)

 -- dAniel hAhler <email address hidden> Mon, 03 Sep 2007 00:19:38 +0200