Your message dated Wed, 05 Sep 2007 22:39:40 +0000
with message-id <[EMAIL PROTECTED]>
and subject line Bug#430250: fixed in libfcgi 2.4.0-7
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: libfcgi-dev
Severity: serious
User: [EMAIL PROTECTED]
Usertags: goal-ldbl128
Discussed in http://lists.debian.org/debian-devel/2007/05/msg01173.html
With glibc-2.5 and gcc-4.1.2 (and gcc-4.2), the 'long double'
data type did change from a 64bit representation to a 128bit
representation on alpha, powerpc, sparc, s390. To allow
partial upgrades of packages, we will need to rename all
packages holding libraries with the long double data type in
their API. Both libc and libstdc++ do not need to be renamed,
because they support both representations. We rename the library
packages on all architectures to avoid name mismatches between
architectures (you can avoid the renaming by supporting both
datatype representations in the library as done in glibc and
libstdc++, but unless a library is prepared for that, it does not
seem to be worth the effort).
It is suggested to rename a package libfoo1 to libfoo1ldbl;
please wait with the renaming if the package depends on
another library package which needs renaming.
This package has been indentified as one with header files in
/usr/include matching 'long *double'. Please close this bug report
if it is a false positive, or rename the package accordingly.
--- End Message ---
--- Begin Message ---
Source: libfcgi
Source-Version: 2.4.0-7
We believe that the bug you reported is fixed in the latest version of
libfcgi, which is due to be installed in the Debian FTP archive:
libfcgi-dev_2.4.0-7_amd64.deb
to pool/main/libf/libfcgi/libfcgi-dev_2.4.0-7_amd64.deb
libfcgi0ldbl_2.4.0-7_amd64.deb
to pool/main/libf/libfcgi/libfcgi0ldbl_2.4.0-7_amd64.deb
libfcgi_2.4.0-7.diff.gz
to pool/main/libf/libfcgi/libfcgi_2.4.0-7.diff.gz
libfcgi_2.4.0-7.dsc
to pool/main/libf/libfcgi/libfcgi_2.4.0-7.dsc
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.
Tatsuki Sugiura <[EMAIL PROTECTED]> (supplier of updated libfcgi 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, 5 Sep 2006 18:11:06 +0900
Source: libfcgi
Binary: libfcgi0ldbl libfcgi-dev
Architecture: source amd64
Version: 2.4.0-7
Distribution: unstable
Urgency: low
Maintainer: Taku YASUI <[EMAIL PROTECTED]>
Changed-By: Tatsuki Sugiura <[EMAIL PROTECTED]>
Description:
libfcgi-dev - Header files of FastCGI
libfcgi0ldbl - Shared library of FastCGI
Closes: 430250
Changes:
libfcgi (2.4.0-7) unstable; urgency=low
.
* rebuild for long double 128bit transition. (Closes: #430250)
* update autotools scripts
Files:
7e86e5f6489c20a033ace1617b03589e 580 - optional libfcgi_2.4.0-7.dsc
9235bb595535a4a907b1260acfa3cc03 415800 - optional libfcgi_2.4.0-7.diff.gz
215da477f96ff7511f4163ad57081207 36950 libdevel optional
libfcgi-dev_2.4.0-7_amd64.deb
e72781a111a504bc16ae0f30176633b1 281782 libs optional
libfcgi0ldbl_2.4.0-7_amd64.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFG2nO1FwU5DuZsm7ARAmf/AJ0ZIli3VsLw1LNovWkRPZw8B+SmPgCgmZdf
DfPToFIr3SKidLIxkmsNgQg=
=FkZ0
-----END PGP SIGNATURE-----
--- End Message ---
