Your message dated Fri, 23 May 2008 14:08:40 +0100
with message-id <[EMAIL PROTECTED]>
and subject line beepcore-c has been removed from Debian, closing #442507
has caused the Debian Bug report #442507,
regarding beepcore-c: FTBFS if build twice in a row
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.)


-- 
442507: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=442507
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: beepcore-c
Severity: important
Version: 0.2+cvs20030603-1
User: [EMAIL PROTECTED]
Usertags: qa-doublebuild

Hi,                                                                             
                                                                                
                                                              
                                                                                
                                                                                
                                                              
Lucas Nussbaum has rebuilt the whole archive on i386 and your package FTBFS if
built twice in a row with the following error:


dh_clean
  dpkg-source -b beepcore-c-0.2+cvs20030603
 dpkg-source: building beepcore-c using existing 
beepcore-c_0.2+cvs20030603.orig.tar.gz
 dpkg-source: building beepcore-c in beepcore-c_0.2+cvs20030603-1.diff.gz
 dpkg-source: cannot represent change to config.sub:
 dpkg-source:  new version is symlink
 dpkg-source:  old version is something else
 dpkg-source: cannot represent change to config.guess:
 dpkg-source:  new version is symlink
 dpkg-source:  old version is something else
 dpkg-source: warning: executable mode 0755 of 'debian/fix-includes.sh' will 
not be represented in diff
 dpkg-source: warning: executable mode 0755 of 'libtool' will not be 
represented in diff
 dpkg-source: warning: executable mode 0755 of 'config.status' will not be 
represented in diff
 dpkg-source: building beepcore-c in beepcore-c_0.2+cvs20030603-1.dsc
 dpkg-source: unrepresentable changes to source
 ******************************************************************************
 Build finished at 20070906-0308
 #### END OF BUILD NO 2 ####
 FAILED [dpkg-buildpackage died]
 Purging 
/var/lib/schroot/mount/sid32-3e3ff5e6-74b0-47a9-81cb-17f2a027a0e3/build/user/beepcore-c-0.2+cvs20030603
 ------------------------------------------------------------------------------
 Not removing build depends: session managed chroot in use
 ******************************************************************************
 Finished at 20070906-0308
 Build needed 00:00:37, 4020k disk space
 DC-Build-Status: Failed 101.851859s
 mv: cannot stat `*.changes': No such file or directory
 mv: cannot stat `*.dsc': No such file or directory
 mv: cannot stat `*gz': No such file or directory
 mv: cannot stat `*deb': No such file or directory



The full build-log can be found at: 
http://people.debian.org/~lucas/logs/doublebuild-09-05/failed-build-2


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. All
packages have been rebuilt twice in a row, with unpack, build, clean,
build.

Please read the mail of Martin Zobel-Helas on debian-devel [0], for a 
explanation 
for this mass bug filling.


[0]: http://lists.debian.org/debian-devel/2007/05/msg00490.html




--- End Message ---
--- Begin Message ---
Version: 0.2+cvs20030603-1+rm

The beepcore-c 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/476261 . 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 ---

Reply via email to