Your message dated Sun, 04 Feb 2018 16:06:47 +0000
with message-id <e1eimoz-000cae...@fasolo.debian.org>
and subject line Bug#855851: fixed in gcc-3.3 1:3.3.6ds1-30
has caused the Debian Bug report #855851,
regarding gcc-3.3: still in stretch
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 ow...@bugs.debian.org
immediately.)


-- 
855851: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855851
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:gcc-3.3
Version: 1:3.3.6ds1-28
Severity: serious

Dear maintainer:

Would be possible to get rid of gcc-3.3 in stretch?

We don't have gcc-5 anymore in stretch, so it would be really strange
that we still need gcc-3.3 (even if it's only the source) which is a
lot older.

If we really need gcc-3.3 in stretch, please downgrade and document
the reason here, so that it serves as documentation.

Thanks.

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

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.

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 855...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Philipp Kern <pk...@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 ftpmas...@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Sun, 04 Feb 2018 16:11:34 +0100
Source: gcc-3.3
Binary: libstdc++5
Architecture: source
Version: 1:3.3.6ds1-30
Distribution: unstable
Urgency: medium
Maintainer: Philipp Kern <pk...@debian.org>
Changed-By: Philipp Kern <pk...@debian.org>
Description:
 libstdc++5 - The GNU Standard C++ Library v3
Closes: 855851 887782 887783
Changes:
 gcc-3.3 (1:3.3.6ds1-30) unstable; urgency=medium
 .
   * Use ucontext_t instead of struct ucontext. (Closes: #887782)
   * Clarify that libstdc++5 is only still around for proprietary
     binaries that cannot be recompiled in the package's description.
     (Closes: #887783, #855851)
Checksums-Sha1:
 381a8f1044c5ded958ff942ba4299fd57479c474 2135 gcc-3.3_3.3.6ds1-30.dsc
 4a5134cb42582d02b1fe88fe495745e196d8fb6d 371105 gcc-3.3_3.3.6ds1-30.diff.gz
 95f3f19c4c7e381df5f9044a517169a07a008ae5 6902 
gcc-3.3_3.3.6ds1-30_source.buildinfo
Checksums-Sha256:
 cbb2655bb513dbb603eaeb364d60afd80d21889955e214c1bbb092bfe5c90abd 2135 
gcc-3.3_3.3.6ds1-30.dsc
 32a6d1d53509a50103303926c0aea24bac0f66a16795152bb25602c0a41a05e2 371105 
gcc-3.3_3.3.6ds1-30.diff.gz
 abcbb4557a4b31421973851f0bbee4ac2080c5bfa36bc0e064067c4f75d64330 6902 
gcc-3.3_3.3.6ds1-30_source.buildinfo
Files:
 1849fe7787f07a4f737065ca543b3dfd 2135 devel optional gcc-3.3_3.3.6ds1-30.dsc
 69f666a521068997bdf09c8289b29f88 371105 devel optional 
gcc-3.3_3.3.6ds1-30.diff.gz
 0ec9f2c88f04f8d71e7bdd1768b76fd3 6902 devel optional 
gcc-3.3_3.3.6ds1-30_source.buildinfo

-----BEGIN PGP SIGNATURE-----

iQFFBAEBCgAvFiEEPzuChCNsw7gPxr3/RG4lRTXQVuwFAlp3LGYRHHBrZXJuQGRl
Ymlhbi5vcmcACgkQRG4lRTXQVuxAFAf+KMnlwXNd+r+Ets8jVUWTcpgmg4ZPY0cD
jOLeiyWd+MUmObBncrOks6JC8wCq+Kc2peBvjCWiadPv6cHehnHCCxSHVAg5e/AS
JkIw5vVnNKLp6jOZO4HKEfeodVkfW1n0fhCqbVzh3857s4hBz47FLqlbQpTOnwiU
9yHY3eDGU91QKaP2PTAF4z8CayzKNXb83TU4OgWavMrxtax59CGmTProcOja3nTN
is8hnJRrG/Y3N9auWmI5RuohMnvWpDizijSDCsNtGVFEHjalpQePJQcG8SpPjNLQ
/OBhMfDWNKA8l6ANDpBV79FPWaBlVRIj7u0aYAfefLqihAmRw+CfAQ==
=rhSr
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to