Your message dated Sat, 5 Sep 2015 08:42:44 +0100
with message-id <20150905074244.ge3...@rano.org>
and subject line Re: libcolpack0v5: built with g++-4.9 on arm64 and sparc64
has caused the Debian Bug report #797758,
regarding libcolpack0v5: built with g++-4.9 on arm64 and sparc64
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.)
--
797758: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797758
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libcolpack0v5
Version: 1.0.9-3.2
Severity: important
https://packages.debian.org/sid/libcolpack0v5 says:
dep: libstdc++6 (>= 4.9) [arm64, sparc64]
GNU Standard C++ Library v3
dep: libstdc++6 (>= 5.2) [not arm64, hurd-i386, sparc64]
I think the recent shogun build failure on arm64 was caused by this:
https://buildd.debian.org/status/package.php?p=shogun&suite=sid
On arm64 this happened because arm-arm-03 failed to regenerate its
chroot on Aug 2; a binNMU would presumably make the problem go away.
But perhaps you'd prefer to update the source to make sure that g++-5
is used for the "v5" package.
--- End Message ---
--- Begin Message ---
Wookey binNMU-ed it.
--- End Message ---
--
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
