On 2017-03-14 09:36, Matthias Klose wrote: > On 14.03.2017 00:53, Mattia Rizzolo wrote: > > On Thu, Dec 15, 2016 at 10:35:16AM +0100, Matthias Klose wrote: > >> remaining issues: > >> https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=gcc-5-legacy;users=debian-...@lists.debian.org > > > > All the actionable ones are done (apart from llvm-toolchain-snapshot, > > which doesn't seem to explictly be using any fixed version of gcc to > > me). > > > >> gcc-5-cross and gcc-5-cross-ports should be removed from testing at the > >> same > >> time. llvm-toolchain-snapshot is only in unstable. #835940 is asking for > >> gcc-5 > >> to stay in unstable, which should be fine. > > > > According to `dak rm -Rn gcc-5 gnat-5 gcc-5-cross gcc-5-cross-ports` > > nothing (build-)depends on them anymore¹. Do you think it can be > > removed from unstable too now, or does it have a particular purpose? > > The cuda maintainers asked to keep it still in unstable. Also I'd like to see > the next upstream release 5.5.0 in the snapshot archive.
Note that the latest version of nvidia-cuda-toolkit which is in testing and unstable, now depends on g++-6 instead of g++-5. -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net