On 07/18/2015 11:29 PM, Manuel A. Fernandez Montecelo wrote: > Anyway, aptitude with GCC-5 and -std=c++98 also suffers the same problem as > cwidget, because it fails to compile the cwidget header, if nothing else. But > if cwidget goes C++11, it forces aptitude to go C++11, and it doesn't work for > other reasons (that I am working to fix), so we are between a rock and a hard > place. > > Even if I can fix things in time before the deadline, maybe subtle changes > like > the ABI problems make aptitude fail in catastrophic ways, there is not much > time > to expose it and be tested before the deadline in experimental or similar. > > I am thinking that the best solution is to force them to stay with gcc-4.9 for > the time being, it looks the safest bet. After that or in parallel, as soon > as > I get things working, I can upload to experimental the changes that allow them > to work with C++11, and keep it there for a while before moving to unstable.
no, this is definitely *not* an option. cwidget and aptitude b-d on libsigc++-2, and this will be built using GCC 5. There will be neither g++-4.9 nor g++-4.8 in the archive once we finish this transition. Maintainers don't have the choice to fall-back to an older version this time. Matthias -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
