Your message dated Mon, 4 Feb 2008 12:09:28 -0600
with message-id <[EMAIL PROTECTED]>
and subject line Bug#464013: libghc6-missingh-dev: Fails to install.
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: libghc6-missingh-dev
Version: 1.0.0.0
Severity: serious
Hi,
Your package is failing to install with the following error:
Setting up libghc6-missingh-dev (1.0.0.0) ...
Reading package info from
"/usr/lib/haskell-packages/ghc6/lib/MissingH-1.0.0/installed-pkg-config" ...
done.
ghc-pkg: dependency regex-compat-0.91 doesn't exist (use --force to override)
dpkg: error processing libghc6-missingh-dev (--configure):
subprocess post-installation script returned error exit status 1
Errors were encountered while processing:
libghc6-missingh-dev
E: Sub-process /usr/bin/dpkg returned an error code (1)
And then fail to remove with:
Removing libghc6-missingh-dev ...
ghc-pkg: cannot find package MissingH-1.0.0
dpkg: error processing libghc6-missingh-dev (--purge):
subprocess pre-removal script returned error exit status 1
Reading package info from
"/usr/lib/haskell-packages/ghc6/lib/MissingH-1.0.0/installed-pkg-config" ...
done.
ghc-pkg: dependency regex-compat-0.91 doesn't exist (use --force to override)
dpkg: error while cleaning up:
subprocess post-installation script returned error exit status 1
Pretty please make some kind of policy to avoid such errors in the
future. I had to file too many bugs for such problems.
Kurt
--- End Message ---
--- Begin Message ---
On Mon February 4 2008 11:53:34 am Kurt Roeckx wrote:
> Package: libghc6-missingh-dev
> Version: 1.0.0.0
> Severity: serious
I just minutes before getting this uploaded 1.0.0.1, which fixes this issue.
-- John
--- End Message ---
