Hi Denis, thanks for your contributions. But I am bit puzzled about this one: * You upgrade to 0.14.04, but do not update the build dependencies. As you can see in http://hdiff.luite.com/cgit/snap/diff/?id=0.14.0.5&id2=0.13.2.9 there are clearly updates to the meta data that should be reflected in a "New upstream release" commit. * The package plan at http://anonscm.debian.org/gitweb/?p=pkg-haskell/package-plan.git;a=summary still has 0.13.2.9. Before upgrading a packaging in the VCS, you should update the package-plan and make sure there is a clean way forward. Also, we are close to getting our packages in a shape to migrate to testing (or at least I hope so). We should focus on that first. If you pushed that partial commit by accident, simply revert it by pushing the inverse patch. Greetings, Joachim -- Joachim "nomeata" Breitner Debian Developer nomeata@debian.org | ICQ# 74513189 | GPG-Keyid: F0FBF51F JID: nomeata@joachim-breitner.de | http://people.debian.org/~nomeata
Attachment:
signature.asc
Description: This is a digitally signed message part