Your message dated Mon, 26 Sep 2016 00:54:22 -0500 with message-id <1938133.RXGOqWVyq1@riemann> and subject line status unshure [change of type in system_error might break with GCC-5] has caused the Debian Bug report #793232, regarding digikam: change of type in system_error might break with GCC-5 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.) -- 793232: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793232 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: src:digikam Severity: important Tags: sid stretch User: debian-...@lists.debian.org Usertags: gcc-pr66145 GCC PR libstdc++/66145 is a regression in GCC 5 which won't be fixed upstream in time for the GCC defaults change. The work around is to rebuild the affected packages after GCC 5 is the default compiler. Please look at the code and decide, if the package is affected. If not, please just close the issue. If it's a real issue, I'll add the packages affected to libstdc++6's Breaks attributes, with the version of the package at the time of the defaults change. See https://wiki.debian.org/GCC5#libstdc.2B-.2B-_c.2B-.2B-11_incompatibilities_.284.9_and_5.29 for further information. To build with GCC 5,install the gcc, g++, gfortran, ... packages from experimental (apt-get -t experimental install g++).
--- End Message ---
--- Begin Message ---The analysis for this issues was never done, but we've already rebuilt with GCC 5 and now GCC 6 so I'm sure this is a non-issue at this point. -S
Description: This is a digitally signed message part.
--- End Message ---