Hi. I tried the haskell-pkg-debcheck script (the updated one is the one written in Haskell, is it?). Maybe we should put a warning about the large memory consumption, the first time it froze my system! :-) Then, I'd like to know more about the output it produces, that I'm attaching to this email. I'm ok with the first two lines, obviously (in fact, I'd like Joachim to actually apply them, as haskell-hsx is uninstallable in my system right now and I need it to finish happstack). Then, what do all the other dw lines do? They're there just to be sure that next build won't be done against old dependencies, or are there other reasons? BTW, I never found an answer to this question: is it nowadays acceptable in cases like this (I want to install a package that needs to be rebuilt) for a DD to build the package and then manually binNMU it? I don't think I wouldn't do either (I prefer when official packages are built under clean buildd and logs are publicly kept for reference), just out of curiosity. In my understanding, when there were no buildd around all the porting work was done just like this. Thanks, Giovanni. -- Giovanni Mascellani <mascellani@poisson.phc.unipi.it> Pisa, Italy Web: http://poisson.phc.unipi.it/~mascellani Jabber: g.mascellani@jabber.org / giovanni@elabor.homelinux.org
Attachment:
signature.asc
Description: OpenPGP digital signature