Your message dated Fri, 29 Jul 2005 00:47:08 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#320376: fixed in nntp 1.5.12.1-19
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)

--------------------------------------
Received: (at submit) by bugs.debian.org; 28 Jul 2005 22:15:54 +0000
>From [EMAIL PROTECTED] Thu Jul 28 15:15:54 2005
Return-path: <[EMAIL PROTECTED]>
Received: from apate.telenet-ops.be [195.130.132.57] 
        by spohr.debian.org with esmtp (Exim 3.36 1 (Debian))
        id 1DyGfR-0006Fx-00; Thu, 28 Jul 2005 15:15:54 -0700
Received: from localhost (localhost.localdomain [127.0.0.1])
        by apate.telenet-ops.be (Postfix) with SMTP id DCEF838146
        for <[EMAIL PROTECTED]>; Fri, 29 Jul 2005 00:15:32 +0200 (CEST)
Received: from Q.roeckx.be (dD5775FD9.access.telenet.be [213.119.95.217])
        by apate.telenet-ops.be (Postfix) with ESMTP id C105338108
        for <[EMAIL PROTECTED]>; Fri, 29 Jul 2005 00:15:32 +0200 (CEST)
Received: by Q.roeckx.be (Postfix, from userid 501)
        id 6A21726136; Fri, 29 Jul 2005 00:15:32 +0200 (CEST)
Date: Fri, 29 Jul 2005 00:15:32 +0200
From: Kurt Roeckx <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: nntp: FTBFS: errno: TLS definition in /lib/libc.so.6 section .tbss 
mismatches non-TLS reference in get_tcp_conn.o
Message-ID: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4.2.1i
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
        (1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level: 
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE 
        autolearn=no version=2.60-bugs.debian.org_2005_01_02

Package: nntp
Version: 1.5.12.1-18
Severity: serious
Tags: patch

Hi,

When building your on some arches (ia64 and amd64) you get the
following error:
cc -O2 -s -I../libdbz -o nntpxmit nntpxmit.o remote.o llist.o get_tcp_conn.o 
xmitauth.o fakesyslog.o strcasecmp.o ../libdbz/dbz.o ../libdbz/dbzdbm.o -lpam
/usr/bin/ld: errno: TLS definition in /lib/libc.so.6 section .tbss mismatches
non-TLS reference in get_tcp_conn.o
/lib/libc.so.6: could not read symbols: Bad value

(You probably get the same on i686 with a 2.6 kernel, didn't check.)

The problem is that xmit/get_tcp_conn.c has:
extern  int     errno;

Instead of including <errno.h> which has the proper defenition of
errno.

Simple patch:
--- xmit/get_tcp_conn.c.old     2005-07-29 00:12:25.065680088 +0200
+++ xmit/get_tcp_conn.c 2005-07-29 00:14:05.195458048 +0200
@@ -29,7 +29,7 @@
 #include <netdb.h>
 #endif /* NONETDB */

-extern int     errno;
+#include <errno.h>
 extern char    *Pname;
 extern char    *errmsg();
 #ifndef BSD_44


---------------------------------------
Received: (at 320376-close) by bugs.debian.org; 29 Jul 2005 07:54:59 +0000
>From [EMAIL PROTECTED] Fri Jul 29 00:54:59 2005
Return-path: <[EMAIL PROTECTED]>
Received: from katie by spohr.debian.org with local (Exim 3.36 1 (Debian))
        id 1DyPaG-0002Lx-00; Fri, 29 Jul 2005 00:47:08 -0700
From: Blars Blarson <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.56 $
Subject: Bug#320376: fixed in nntp 1.5.12.1-19
Message-Id: <[EMAIL PROTECTED]>
Sender: Archive Administrator <[EMAIL PROTECTED]>
Date: Fri, 29 Jul 2005 00:47:08 -0700
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
        (1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level: 
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER 
        autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-CrossAssassin-Score: 2

Source: nntp
Source-Version: 1.5.12.1-19

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

nntp_1.5.12.1-19.diff.gz
  to pool/main/n/nntp/nntp_1.5.12.1-19.diff.gz
nntp_1.5.12.1-19.dsc
  to pool/main/n/nntp/nntp_1.5.12.1-19.dsc
nntp_1.5.12.1-19_sparc.deb
  to pool/main/n/nntp/nntp_1.5.12.1-19_sparc.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.
Blars Blarson <[EMAIL PROTECTED]> (supplier of updated nntp 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: Thu, 28 Jul 2005 23:40:35 -0700
Source: nntp
Binary: nntp
Architecture: source sparc
Version: 1.5.12.1-19
Distribution: unstable
Urgency: low
Maintainer: Blars Blarson <[EMAIL PROTECTED]>
Changed-By: Blars Blarson <[EMAIL PROTECTED]>
Description: 
 nntp       - An NNTP server for use with C News
Closes: 320146 320376
Changes: 
 nntp (1.5.12.1-19) unstable; urgency=low
 .
   * another errno fix (closes: #320376)
   * Don't use vfork on sparc (closes: #320146)
   * use includes to get rid of some warnings
Files: 
 d320c93680a6cbf9baeab38f340111f4 614 news extra nntp_1.5.12.1-19.dsc
 6c2c4f34c0ad177794d808ec03d29580 33781 news extra nntp_1.5.12.1-19.diff.gz
 08925f2ee1e11edd6de411cfc7db763e 76610 news extra nntp_1.5.12.1-19_sparc.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQFC6dyzg1HDwmisV0YRAtQlAJ4ozeJ0Y7l5pkGaS4sIoaGvS/GIrwCcDK6S
uAO92HuSfwopUopg76G2SsE=
=s1Rl
-----END PGP SIGNATURE-----


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to