Hi Joachim,
Joachim Breitner a écrit :
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.
Yes, that's somehow an accident. I actually got trapped by the
pkg-haskell-uupdate tool which I did not expect would also commit to the
darcs repo and push the commit without even asking for confirmation.
I am aware that build dependencies need update and do plan to work this
later on. I will check the plan before moving forward as you suggested.
Regards,
Denis
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
Archive: https://lists.debian.org/[email protected]
