Your message dated Fri, 08 Feb 2008 18:30:15 +0000
with message-id <[EMAIL PROTECTED]>
and subject line Bug#430267: fixed in liblo 0.23-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: liblo0-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: liblo
Source-Version: 0.23-2.2
We believe that the bug you reported is fixed in the latest version of
liblo, which is due to be installed in the Debian FTP archive:
liblo0-dev_0.23-2.2_i386.deb
to pool/main/libl/liblo/liblo0-dev_0.23-2.2_i386.deb
liblo0ldbl_0.23-2.2_i386.deb
to pool/main/libl/liblo/liblo0ldbl_0.23-2.2_i386.deb
liblo_0.23-2.2.diff.gz
to pool/main/libl/liblo/liblo_0.23-2.2.diff.gz
liblo_0.23-2.2.dsc
to pool/main/libl/liblo/liblo_0.23-2.2.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.
Luk Claes <[EMAIL PROTECTED]> (supplier of updated liblo 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: Sat, 02 Feb 2008 14:27:36 +0000
Source: liblo
Binary: liblo0-dev liblo0ldbl
Architecture: source i386
Version: 0.23-2.2
Distribution: unstable
Urgency: medium
Maintainer: Robert Jordens <[EMAIL PROTECTED]>
Changed-By: Luk Claes <[EMAIL PROTECTED]>
Description:
liblo0-dev - Lightweight OSC library -- development files
liblo0ldbl - Lightweight OSC library
Closes: 430267
Changes:
liblo (0.23-2.2) unstable; urgency=medium
.
* Non-maintainer upload.
* Renamed liblo0 for the ldbl128 transition (Closes: #430267).
Files:
0ccfa5a167d15c0023d322bbfb27517e 605 libs optional liblo_0.23-2.2.dsc
829fd295fed2ac1f81bc8999f24bf7db 113716 libs optional liblo_0.23-2.2.diff.gz
51ce1e442e58939d761b83406292b513 80436 libdevel optional
liblo0-dev_0.23-2.2_i386.deb
adba6f1c3fbaccd9de837e559aaf9e8d 25918 libs optional
liblo0ldbl_0.23-2.2_i386.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFHpH8v5UTeB5t8Mo0RAjwhAJ0dLUzDt8O52B1g9VmvoShm9txrBACeMma3
lTzWEq7EEqGF+RlTZuzRxHM=
=Tu1g
-----END PGP SIGNATURE-----
--- End Message ---
