Control: tags 797755 + wontfix On 02/09/15 13:05, Steve M. Robbins wrote: > On September 2, 2015 10:55:01 AM you wrote: >> In the case of insighttoolkit, std::string appears in installed headers, >> so it seems very likely that a transition is needed. > > Do note that this packge is requested for removal (#795019) so there will be > no work done to transition it.
Marking this as wontfix on that basis. However, I notice that the removal bug is marked moreinfo, because the ftp-masters will not remove insighttoolkit 3 while packages still depend on it, unless those packages are also removed. Please tell that bug how you plan to deal with this. Does insighttoolkit4 still have a C++ ABI involving std::string, std::list or other affected symbols? If it does, it will need a similar bug. The transition can be done either by moving from one SONAME to another (libinsighttoolkit4.7 -> libinsighttoolkit4.8), or by adding a v5 suffix to 4.7. The people who have already spent a month fighting with this transition would really prefer the short-term answer to be "whichever is quicker and lower-risk", which seems likely to be the v5 suffix; you can still do the 4.7 -> 4.8 transition later, after unstable is a usable suite for development again. Leaving insighttoolkit4 built with g++-4 is not a valid solution, because it already needs to be rebuilt with g++-5 for the dcmtk2v5 sub-transition (although it FTBFS right now - I'll open a bug). S