Your message dated Thu, 29 May 2008 17:30:23 +0100
with message-id <[EMAIL PROTECTED]>
and subject line mercury has been removed from Debian, closing #297217
has caused the Debian Bug report #297217,
regarding mercury: FTBFS: cannot stat `./debian/tmp/usr/lib/mercury/bin': No
such file or directory
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
297217: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=297217
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: mercury
Version: 0.11.0.rotd.20040511-5
Severity: serious
Hello,
There was a problem while autobuilding your package:
> Automatic build of mercury_0.11.0.rotd.20040511-5 on avidan by sbuild/i386
> 0.49
> Build started at 20060807-0259
> ******************************************************************************
...
> mercury_deep_copy_body.h: In function 'MR_deep_copy':
> mercury_deep_copy_body.h:387: error: invalid lvalue in assignment
> mercury_deep_copy_body.h:425: error: invalid lvalue in assignment
> mercury_deep_copy_body.h: In function 'MR_deep_copy_type_info':
> mercury_deep_copy_body.h:762: error: invalid lvalue in assignment
> mercury_deep_copy_body.h:771: error: invalid lvalue in assignment
> mercury_deep_copy_body.h: In function 'MR_deep_copy_typeclass_info':
> mercury_deep_copy_body.h:831: error: invalid lvalue in assignment
> make[3]: *** [mercury_deep_copy.o] Error 1
> make[3]: Leaving directory
> `/build/buildd/mercury-0.11.0.rotd.20040511/build/mercury/runtime'
> make[2]: *** [runtime] Error 2
> make[2]: Leaving directory
> `/build/buildd/mercury-0.11.0.rotd.20040511/build/mercury'
> make[1]: Leaving directory
> `/build/buildd/mercury-0.11.0.rotd.20040511/build/mercury'
> cp build/mercury/README build/mercury/README.DotNet \
> build/mercury/README.Java build/mercury/README.Linux* \
> build/mercury/README.gcc-backend build/mercury/RELEASE_NOTES \
> build/mercury/BUGS build/mercury/HISTORY \
> build/mercury/LIMITATIONS \
> build/mercury/NEWS build/mercury/TODO \
> build/mercury/WORK_IN_PROGRESS debian/mercury/usr/share/doc/mercury/
> touch install-stamp
> dh_testdir
> dh_testroot
> dh_installchangelogs -a
> dh_installchangelogs: Compatibility levels before 4 are deprecated.
> dh_installdocs -a
> dh_installdocs: Compatibility levels before 4 are deprecated.
> dh_installexamples -a
> dh_installexamples: Compatibility levels before 4 are deprecated.
> dh_install -a
> dh_install: Compatibility levels before 4 are deprecated.
> cp: cannot stat `./debian/tmp/usr/lib/mercury/bin': No such file or directory
> dh_install: command returned error code 256
> make: *** [binary-arch] Error 1
> ******************************************************************************
> Build finished at 20060807-0303
> FAILED [dpkg-buildpackage died]
--
Julien Danjou
.''`. Debian Developer
: :' : http://julien.danjou.info
`. `' http://people.debian.org/~acid
`- 9A0D 5FD9 EB42 22F6 8974 C95C A462 B51E C2FE E5CD
signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Version: 0.11.0.rotd.20040511-5+rm
The mercury package has been removed from Debian testing, unstable and
experimental, so I am now closing the bugs that were still opened
against it.
For more information about this package's removal, read
http://bugs.debian.org/446665 . That bug might give the reasons why
this package was removed, and suggestions of possible replacements.
Don't hesitate to reply to this mail if you have any question.
Thank you for your contribution to Debian.
--
Marco Rodrigues
http://Marco.Tondela.org
--- End Message ---
