[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#636277: marked as done (gcc-3.3: should be multiarch'ified)



Your message dated Mon, 10 Oct 2011 21:17:15 +0000
with message-id <E1RDNDn-0002iv-1O@franck.debian.org>
and subject line Bug#636277: fixed in gcc-3.3 1:3.3.6ds1-25
has caused the Debian Bug report #636277,
regarding gcc-3.3: should be multiarch'ified
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 owner@bugs.debian.org
immediately.)


-- 
636277: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=636277
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: libstdc++5
Version: 1:3.3.6-24

libstdc++5 should be multiarch'ified to support legacy applications
cross-architecture.

Kind regards,
Philipp Kern
-- 
 .''`.  Philipp Kern                        Debian Developer
: :' :  http://philkern.de                         Stable Release Manager
`. `'   xmpp:phil@0x539.de                         Wanna-Build Admin
  `-    finger pkern/key@db.debian.org

Attachment: signature.asc
Description: Digital signature


--- End Message ---
--- Begin Message ---
Source: gcc-3.3
Source-Version: 1:3.3.6ds1-25

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

gcc-3.3_3.3.6ds1-25.diff.gz
  to main/g/gcc-3.3/gcc-3.3_3.3.6ds1-25.diff.gz
gcc-3.3_3.3.6ds1-25.dsc
  to main/g/gcc-3.3/gcc-3.3_3.3.6ds1-25.dsc
libstdc++5_3.3.6-25_amd64.deb
  to main/g/gcc-3.3/libstdc++5_3.3.6-25_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 636277@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Philipp Kern <pkern@debian.org> (supplier of updated gcc-3.3 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 ftpmaster@debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Mon, 10 Oct 2011 22:26:38 +0200
Source: gcc-3.3
Binary: libstdc++5
Architecture: source amd64
Version: 1:3.3.6ds1-25
Distribution: unstable
Urgency: low
Maintainer: Philipp Kern <pkern@debian.org>
Changed-By: Philipp Kern <pkern@debian.org>
Description: 
 libstdc++5 - The GNU Standard C++ Library v3
Closes: 636277
Changes: 
 gcc-3.3 (1:3.3.6ds1-25) unstable; urgency=low
 .
   * Multiarch'ify libstdc++5.
     Thanks to Felix Geyer <debfx-pkg@fobos.de> for the full patch!
     (Closes: #636277)
   * Drop lpia everywhere.
Checksums-Sha1: 
 d307f61885e1ac039e3fb57cedb641f63eea4f79 1886 gcc-3.3_3.3.6ds1-25.dsc
 91bf78d221889322c5483f287da007d6e0287853 382945 gcc-3.3_3.3.6ds1-25.diff.gz
 181c35d8ca3f5644b3f5d6fc531e9ac489e8528b 308680 libstdc++5_3.3.6-25_amd64.deb
Checksums-Sha256: 
 bdb7ce074668563f5c2b1591662f6f062932b7bca30e79283f6a9f1a8f4fbbe4 1886 gcc-3.3_3.3.6ds1-25.dsc
 45a7d3bc953410706f9f8441e0e72fd9b1349210577af56eb5b65f9ea8c53cfb 382945 gcc-3.3_3.3.6ds1-25.diff.gz
 0d0c3347bbf0ea8ea77d568503c1c52ce4c98f2522e73fa37d94797183832abe 308680 libstdc++5_3.3.6-25_amd64.deb
Files: 
 36dbe756e784422506bb0d9492b0b879 1886 devel optional gcc-3.3_3.3.6ds1-25.dsc
 17538b2ff0019eca64be41a8ae2afdd3 382945 devel optional gcc-3.3_3.3.6ds1-25.diff.gz
 c1397cf1767b142d81d3471ffc2c8deb 308680 libs optional libstdc++5_3.3.6-25_amd64.deb

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

iEYEAREIAAYFAk6TXq0ACgkQ7Ro5M7LPzdjn8ACg4YDcnIilOXgetidVoEH4aEfx
qHEAn2ZTJ/67yQifpMfIh5UF5HVt5PfY
=Zone
-----END PGP SIGNATURE-----



--- End Message ---

Reply to: