Your message dated Tue, 11 Sep 2007 17:47:03 +0000
with message-id <[EMAIL PROTECTED]>
and subject line Bug#424237: fixed in ssldump 0.9b3-2.2
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: ssldump
Severity: important
Version: 0.9b3-2.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:

#### RUNNING BUILD NO 2 ####
############
dpkg-buildpackage: source package is ssldump
dpkg-buildpackage: source version is 0.9b3-2.1
dpkg-buildpackage: host architecture i386
dpkg-buildpackage: source version without epoch 0.9b3-2.1
 /usr/bin/fakeroot debian/rules clean
dh_testdir
dh_testroot
rm -f build-stamp 
# Add here commands to clean up after the build process.
/usr/bin/make clean
make[1]: Entering directory `/build/user/ssldump-0.9b3'
rm -f  debug.o r_assoc.o r_bitfield.o r_data.o r_errors.o r_list.o r_replace.o 
r_time.o   
rm -f  network.o pcap-snoop.o proto_mod.o tcpconn.o tcppack.o   
rm -f  null_analyze.o   
rm -f  ciphersuites.o ssl.enums.o ssl_analyze.o ssl_rec.o ssldecode.o 
sslprint.o sslxprint.o   
rm -f debug.o r_assoc.o r_bitfield.o r_data.o r_errors.o r_list.o r_replace.o 
r_time.o   network.o pcap-snoop.o proto_mod.o tcpconn.o tcppack.o   
null_analyze.o   ciphersuites.o ssl.enums.o ssl_analyze.o ssl_rec.o ssldecode.o 
sslprint.o sslxprint.o   ssldump config.cache config.status config.log config.h 
config.sub config.guess
make[1]: Leaving directory `/build/user/ssldump-0.9b3'
test -r /usr/share/misc/config.sub && \
          cp -f /usr/share/misc/config.sub config.sub
make: [clean] Error 1 (ignored)
test -r /usr/share/misc/config.guess && \
          cp -f /usr/share/misc/config.guess config.guess
make: [clean] Error 1 (ignored)
rm -f Makefile
dh_clean
dh_clean: Compatibility levels before 4 are deprecated.
 dpkg-source -b ssldump-0.9b3
dpkg-source: building ssldump using existing ssldump_0.9b3.orig.tar.gz
dpkg-source: building ssldump in ssldump_0.9b3-2.1.diff.gz
dpkg-source: warning: ignoring deletion of file config.sub
dpkg-source: warning: ignoring deletion of file config.guess
dpkg-source: building ssldump in ssldump_0.9b3-2.1.dsc
 debian/rules build
dh_testdir
# Add here commands to configure the package.
./configure --host=i486-linux-gnu --build=i486-linux-gnu --prefix=/usr 
--mandir=\${prefix}/share/man
creating cache ./config.cache
configure: error: can not run ./config.sub
make: *** [config.status] Error 1
******************************************************************************
Build finished at 20070515-1718
FAILED [dpkg-buildpackage died]
#### END OF BUILD NO 2 ####


The full build-log can be found at: 
http://people.debian.org/~lucas/logs/2007/05/15/00_Failed_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.



--- End Message ---
--- Begin Message ---
Source: ssldump
Source-Version: 0.9b3-2.2

We believe that the bug you reported is fixed in the latest version of
ssldump, which is due to be installed in the Debian FTP archive:

ssldump_0.9b3-2.2.diff.gz
  to pool/main/s/ssldump/ssldump_0.9b3-2.2.diff.gz
ssldump_0.9b3-2.2.dsc
  to pool/main/s/ssldump/ssldump_0.9b3-2.2.dsc
ssldump_0.9b3-2.2_i386.deb
  to pool/main/s/ssldump/ssldump_0.9b3-2.2_i386.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Margarita Manterola <[EMAIL PROTECTED]> (supplier of updated ssldump package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Tue, 11 Sep 2007 14:18:40 -0300
Source: ssldump
Binary: ssldump
Architecture: source i386
Version: 0.9b3-2.2
Distribution: unstable
Urgency: low
Maintainer: Simon Law <[EMAIL PROTECTED]>
Changed-By: Margarita Manterola <[EMAIL PROTECTED]>
Description: 
 ssldump    - An SSLv3/TLS network protocol analyzer
Closes: 424237 439459
Changes: 
 ssldump (0.9b3-2.2) unstable; urgency=low
 .
   * Non-maintainer upload to fix Failure To Build From Source.
   * Removed the inclusion of <net/bpf.h> since including <pcap.h> is now
     enough, as adviced by Romain Francoise. (Closes: #439459)
   * Removed config.sub and config.guess from the list of files to be erased
     when cleaning, allowing a second build. (Closes: #424237)
Files: 
 0ac5f32fc4438226c38185c037571b55 610 net optional ssldump_0.9b3-2.2.dsc
 df05ece5fea14e90ae44afc1edd97ebc 30595 net optional ssldump_0.9b3-2.2.diff.gz
 b905594abf9704dc7a352c9f7599b0c9 38952 net optional ssldump_0.9b3-2.2_i386.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFG5tK5lAuUx1tI/64RAoLkAJ90DTfriTW+3E9FOOvRyz3KRbcCIACfX8hI
xsu9h/tASvdDSI7D+HwhLhE=
=qrmA
-----END PGP SIGNATURE-----



--- End Message ---

Reply via email to