Hi, 2018-03-10 19:37 GMT+01:00 Sven Joachim <svenj...@gmx.de>: > On 2018-02-25 00:55 +0100, Manuel A. Fernandez Montecelo wrote: > >> 2018-02-24 8:54 GMT+01:00 Sven Joachim <svenj...@gmx.de>: >>> >>> So here is a possible plan: >>> >>> - Do *not* fix this bug in unstable now, to exclude the possibility of >>> the above symbol lookup error after a cwidget rebuild when the ncurses >>> transition starts. >>> >>> - After ncurses has been accepted in experimental, upload cwidget there >>> too. Rename the library package again, say to libcwidget3v6, and >>> build-depend on libncurses-dev (>= 6.0+20180210) to ensure that it gets >>> linked against libncursesw6 rather than libncursesw5. >>> >>> - When the ncurses transition starts in unstable, both aptitude and >>> cwidget still FTBFS. Upload the new cwidget package to unstable, get >>> aptitude binNMU'ed, and everyone is happy. >>> >>> Does this sound reasonable? >> >> Yes, with the following comments/caveats (mostly reminders for myself, >> or somebody else if ends up doing this): >> >> - the "v5" suffix was for the GCC5 transition (changes due to C++11 >> ABI), the name should be "libcwidget4" or something. I wanted to >> change a couple of minor things and bump the soversion anyway, just >> never find the time to sort out all of the details, so let's see :) > > Do you think you can finish these changes this month? So far I have > only found one other showstopper[1] for the ncurses transition, and I > intend to file a bug against release.debian.org in 2-3 weeks if nothing > else crops up.
Yes, very busy right now but should be more free in the last week, if that's all right :) Feel free to ping me again, raise the severity of the bug or anything, so I notice and remember. Cheers. -- Manuel A. Fernandez Montecelo <manuel.montez...@gmail.com>
