Your message dated Mon, 9 Jul 2007 21:40:12 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#432364: xdemineur: FTBFS: No rule to make target `clean'.
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: xdemineur
version: 2.1.1-9
Severity: serious
User: [EMAIL PROTECTED]
Usertags: qa-ftbfs-20070708
Justification: FTBFS on i386
Hi,
During a rebuild of all packages in sid, your package failed to build on i386.
Relevant part:
/usr/bin/fakeroot debian/rules clean
dpatch deapply-all
03_optionmines not applied to ./ .
02_manpage_section not applied to ./ .
01_endgame not applied to ./ .
rm -rf patch-stamp patch-stampT debian/patched
dh_testdir
dh_testroot
/usr/bin/make clean
make[1]: Entering directory `/build/user/xdemineur-2.1.1'
make[1]: *** No rule to make target `clean'. Stop.
make[1]: Leaving directory `/build/user/xdemineur-2.1.1'
make: *** [clean] Error 2
The full build log is available from
http://people.debian.org/~lucas/logs/2007/07/08/
About the archive rebuild: The rebuild was done on about 50 AMD64 nodes
of the Grid'5000 platform, using a clean chroot containing a sid i386
environment. Internet was not accessible from the build systems.
--
| Lucas Nussbaum
| [EMAIL PROTECTED] http://www.lucas-nussbaum.net/ |
| jabber: [EMAIL PROTECTED] GPG: 1024D/023B3F4F |
--- End Message ---
--- Begin Message ---
Version: 2.1.1-10
On Mon, Jul 09, 2007 at 05:28:25PM +0000, Lucas Nussbaum wrote:
> /usr/bin/make clean
> make[1]: Entering directory `/build/user/xdemineur-2.1.1'
> make[1]: *** No rule to make target `clean'. Stop.
This had already been fixed in version 2.1.1-10. -Ralf.
--- End Message ---
