Your message dated Mon, 10 Mar 2008 21:02:50 +0000
with message-id <[EMAIL PROTECTED]>
and subject line Bug#470247: fixed in timps 0.25-2
has caused the Debian Bug report #470247,
regarding timps: FTBFS: conn.c:1118: error: too few arguments to function 
'nbio_sfd_newlistener'
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.)


-- 
470247: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=470247
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: timps
Version: 0.25-1
Severity: serious
User: [EMAIL PROTECTED]
Usertags: qa-ftbfs-20080308 qa-ftbfs
Justification: FTBFS on i386

Hi,

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

Relevant part:
> gcc -DHAVE_CONFIG_H -I. -I. -I../include -I. -I../libmx/include -I../include 
> -I/usr/local/include/libnbio -I/usr/include/libnbio    -fno-strict-aliasing 
> -Wall -g -DNOXML -c conn.c
> conn.c: In function 'listenestablish':
> conn.c:1118: warning: passing argument 2 of 'nbio_sfd_newlistener' makes 
> pointer from integer without a cast
> conn.c:1118: error: too few arguments to function 'nbio_sfd_newlistener'
> make[3]: *** [conn.o] Error 1

The full build log is available from:
   http://people.debian.org/~lucas/logs/2008/03/08

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 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 ---
Source: timps
Source-Version: 0.25-2

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

timps_0.25-2.diff.gz
  to pool/main/t/timps/timps_0.25-2.diff.gz
timps_0.25-2.dsc
  to pool/main/t/timps/timps_0.25-2.dsc
timps_0.25-2_i386.deb
  to pool/main/t/timps/timps_0.25-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.
Eric Warmenhoven <[EMAIL PROTECTED]> (supplier of updated timps 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: Mon, 10 Mar 2008 12:27:49 -0700
Source: timps
Binary: timps
Architecture: source i386
Version: 0.25-2
Distribution: unstable
Urgency: low
Maintainer: Eric Warmenhoven <[EMAIL PROTECTED]>
Changed-By: Eric Warmenhoven <[EMAIL PROTECTED]>
Description: 
 timps      - Transparent Instant Messaging Proxy Server
Closes: 470247
Changes: 
 timps (0.25-2) unstable; urgency=low
 .
   * Fix build with conn.c fix from timps cvs. Closes: #470247.
   * Fix lintian warnings (standards version, ignore make clean failure)
Files: 
 ae35b625f0a201b158b608ef53cdeddc 641 net extra timps_0.25-2.dsc
 3b58525adc1c28c117947919961dd282 3949 net extra timps_0.25-2.diff.gz
 7be187f1c6373be804c570712766ba20 56364 net extra timps_0.25-2_i386.deb

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

iD8DBQFH1YxNBLcxcFStIbURAhCeAJ9cdRQ6JBXB+UP1e5LRpVqoo6LYKACeMd0D
/XMHZB/TO2LnQk2O62bd0pU=
=1/fn
-----END PGP SIGNATURE-----



--- End Message ---

Reply via email to