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++).

tags 793244 + confirmed
thanks

I've confirmed that git-crypt is affected.  However, are you sure that
rebuilding is a sufficient workaround?  When I tried building with g++
5.2.1-11 from experimental, I had to use -D_GLIBCXX_USE_CXX11_ABI=0 in
order to successfully catch std::ios_base::failure.  Should I modify
git-crypt to build with this flag?

Thanks,
Andrew

no, that was an omission in libstdc++6, now fixed in 5.2.1-12.

Control: found 793244 0.5.0-1
Control: fixed 793244 0.7.0-0.1
Control: close 793244
X-Debbugs-CC: agwa@andrewayer.name doko@debian.org
https://wiki.debian.org/GCC5#libstdc.2B-.2B-_c.2B-.2B-11_incompatibilities_.284.9_and_5.29

With the GCC 5 transition completed long long ago, I believe at least the
most recent upload in Sid is not affected by GCC's change. Closing this bug
accordingly. If there are anything that I'm missing, please feel free to
make corrections.

Thanks,
Boyuan Yang