Your message dated Sun, 23 Aug 2009 12:47:19 +0000
with message-id <e1mfctf-0001ns...@ries.debian.org>
and subject line Bug#543050: fixed in libdumbnet 1.12-3
has caused the Debian Bug report #543050,
regarding labrea: FTBFS: configure: error: libdnet not found
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 ow...@bugs.debian.org
immediately.)


-- 
543050: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=543050
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: labrea
Version: 2.5-stable-3
Severity: serious
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20090822 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
>  /usr/bin/fakeroot debian/rules clean
> dh_testdir
> dh_testroot
> rm -f build-stamp
> [ ! -f Makefile ] || /usr/bin/make distclean
> rm -f config.guess config.sub
> dh_clean
> QUILT_PATCHES=debian/patches quilt --quiltrc /dev/null pop -a -R || test $? = 
> 2 
> No patch removed
> rm -rf .pc debian/stamp-patched
>  dpkg-source -b labrea-2.5-stable
> dpkg-source: info: using source format `1.0'
> dpkg-source: info: building labrea using existing 
> labrea_2.5-stable.orig.tar.gz
> dpkg-source: info: building labrea in labrea_2.5-stable-3.diff.gz
> dpkg-source: warning: ignoring deletion of file config.guess
> dpkg-source: warning: ignoring deletion of file config.sub
> dpkg-source: info: building labrea in labrea_2.5-stable-3.dsc
>  debian/rules build
> QUILT_PATCHES=debian/patches quilt --quiltrc /dev/null push -a || test $? = 2
> Applying patch use-dumbnet.patch
> patching file inc/ctl.h
> patching file inc/utils.h
> patching file inc/pkt.h
> patching file src/pkt_handler.c
> 
> Applying patch manpages-fix.patch
> patching file misc/labrea.1
> patching file misc/labrea.conf.5
> 
> Now at patch manpages-fix.patch
> touch debian/stamp-patched
> dh_testdir
> ln -sf /usr/share/misc/config.guess /usr/share/misc/config.sub .
> ./configure --prefix=/usr --mandir=/usr/share/man --sysconfdir=/etc/labrea 
> --build=x86_64-linux-gnu
> checking build system type... x86_64-pc-linux-gnu
> checking host system type... x86_64-pc-linux-gnu
> checking for a BSD-compatible install... /usr/bin/install -c
> checking whether build environment is sane... yes
> checking for gawk... no
> checking for mawk... mawk
> checking whether make sets $(MAKE)... yes
> checking for target os... linux-gnu
> checking whether make sets $(MAKE)... (cached) yes
> checking for gcc... gcc
> checking for C compiler default output... a.out
> checking whether the C compiler works... yes
> checking whether we are cross compiling... no
> checking for suffix of executables... 
> checking for suffix of object files... o
> checking whether we are using the GNU C compiler... yes
> checking whether gcc accepts -g... yes
> checking for gcc option to accept ANSI C... none needed
> checking for style of include used by make... GNU
> checking dependency style of gcc... gcc3
> configure: error: libdnet not found
> checking for a BSD-compatible install... /usr/bin/install -c
> checking whether ln -s works... yes
> checking for ranlib... ranlib
> checking for libpcap... yes
> checking for libdnet... no
> make: *** [build-stamp] Error 1

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2009/08/22/labrea_2.5-stable-3_lsid64.buildlog

A list of current common problems and possible solutions is available at 
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on about 50 AMD64 nodes
of the Grid'5000 platform, using a clean chroot.  Internet was not
accessible from the build systems.

-- 
| Lucas Nussbaum
| lu...@lucas-nussbaum.net   http://www.lucas-nussbaum.net/ |
| jabber: lu...@nussbaum.fr             GPG: 1024D/023B3F4F |



--- End Message ---
--- Begin Message ---
Source: libdumbnet
Source-Version: 1.12-3

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

libdumbnet-dev_1.12-3_amd64.deb
  to pool/main/libd/libdumbnet/libdumbnet-dev_1.12-3_amd64.deb
libdumbnet1_1.12-3_amd64.deb
  to pool/main/libd/libdumbnet/libdumbnet1_1.12-3_amd64.deb
libdumbnet_1.12-3.diff.gz
  to pool/main/libd/libdumbnet/libdumbnet_1.12-3.diff.gz
libdumbnet_1.12-3.dsc
  to pool/main/libd/libdumbnet/libdumbnet_1.12-3.dsc
python-dumbnet_1.12-3_amd64.deb
  to pool/main/libd/libdumbnet/python-dumbnet_1.12-3_amd64.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 543...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jan Christoph Nordholz <he...@pool.math.tu-berlin.de> (supplier of updated 
libdumbnet 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 ftpmas...@debian.org)


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

Format: 1.8
Date: Sun, 23 Aug 2009 00:09:20 +0200
Source: libdumbnet
Binary: libdumbnet1 libdumbnet-dev python-dumbnet
Architecture: source amd64
Version: 1.12-3
Distribution: unstable
Urgency: low
Maintainer: Jan Christoph Nordholz <he...@pool.math.tu-berlin.de>
Changed-By: Jan Christoph Nordholz <he...@pool.math.tu-berlin.de>
Description: 
 libdumbnet-dev - A dumb, portable networking library -- development files
 libdumbnet1 - A dumb, portable networking library -- shared library
 python-dumbnet - A dumb, portable networking library -- python bindings
Closes: 542972 543050
Changes: 
 libdumbnet (1.12-3) unstable; urgency=low
 .
   * Restore lost libdumbnet.so symlink in the -dev package.
     Closes: #542972.
   * Provide dumbnet-config again, provide the old name 'dnet-config'
     as a symlink, and make it print the correct -l parameter (i.e.
     include it into the changed files of the 01rename_library patch).
     Closes: #543050.
   * Write a terse manpage for dumbnet-config.
   * Bump Standards Version to 3.8.3.
     * Add a README.source file.
Checksums-Sha1: 
 d3d82a36cd747ff37294f048f40520cd8f4512f5 1183 libdumbnet_1.12-3.dsc
 94ab8a12e8f5c79fc3ee1a8016fa049e76e87a58 10343 libdumbnet_1.12-3.diff.gz
 eb1d4f0bd38789b040abf998070c41da10da43b6 31328 libdumbnet1_1.12-3_amd64.deb
 41e79a0a24d05a9018df65fe6ff4f253604de65c 64764 libdumbnet-dev_1.12-3_amd64.deb
 92d75b2793ca06aaf895cd3fae5409c4d2e86a05 149690 python-dumbnet_1.12-3_amd64.deb
Checksums-Sha256: 
 68bf397f4f68c8ea8b4fd73edfe2195a7226685480654ef49386ef5d12c8333a 1183 
libdumbnet_1.12-3.dsc
 ade0538d4b88d7ef7fbf8c85247d441796fbaab506683c1be68e0e215e72de51 10343 
libdumbnet_1.12-3.diff.gz
 09716475fd5bc45b7c7c675fc1454f1c2fbe56e17ddbc9dafe5f5e96bda1594d 31328 
libdumbnet1_1.12-3_amd64.deb
 c1d3f0397f8d01c5f9b85e40d01197b9268df3fef84b45e64736ebf9bae5c9d6 64764 
libdumbnet-dev_1.12-3_amd64.deb
 4284c590a64ed4c1e0ff0c8e5c4feeb69b5da604d2d4251be83538355850bb6e 149690 
python-dumbnet_1.12-3_amd64.deb
Files: 
 07da8c0114b4aae28fe087efb92f2783 1183 libs optional libdumbnet_1.12-3.dsc
 ebdfd379c9afb1b4169c54ff6d436463 10343 libs optional libdumbnet_1.12-3.diff.gz
 8a1163f672cc4b6301d92387fa3d8525 31328 libs optional 
libdumbnet1_1.12-3_amd64.deb
 3000dc87cfd444927f4dca01907ee7c0 64764 libdevel optional 
libdumbnet-dev_1.12-3_amd64.deb
 3b72c4e648db12e8ed5fec8e06ead538 149690 python optional 
python-dumbnet_1.12-3_amd64.deb

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

iEYEARECAAYFAkqRNPYACgkQHYflSXNkfP8xNQCgqij9s0SnNPcgMG3mUGDgqday
ch4AoJyFJ6nAlPOyBVmzwponzwSMuqlz
=vTRx
-----END PGP SIGNATURE-----



--- End Message ---

Reply via email to