Comment 10 for bug 229489

Hi Duncan,

thanks for the info. However I'm still unsure why this situation can happen in the first place. Imho the old version should have been removed (and hence the postinst run) before ghc6 is getting upgraded, since it has a versioned dependency on ghc6. I've also just dist-upgraded a gutsy chroot to hardy, and that worked as expected.

One thing that's definitely wrong in the postinst is, that it doesn't support rollback/recovery (i.e. the postinst of the new version, which gets tried if the old one fails, cannot work).

I'll forward this to the debian maintainers.

Cheers,
   Stefan.