Bug ID 1074600
Summary ncurses 20171216: needs adjustments on yast side
Classification openSUSE
Product openSUSE Tumbleweed
Version Current
Hardware Other
OS Other
Status NEW
Severity Normal
Priority P5 - None
Component YaST2
Assignee yast2-maintainers@suse.de
Reporter dimstar@opensuse.org
QA Contact jsrain@suse.com
Found By ---
Blocker ---

Ncurses 20171216 has been submitted to openSUSE:Factory which in turn causes
build failures in those yast modules:

* libyui-ncurses
* libyui-ncurses-pkg
(more might show up as the staging project progresses)

The build log excerpt from libyui-ncurses:

>[   30s] In file included from /home/abuild/rpmbuild/BUILD/libyui-ncurses-2.49.0/src/NCurses.h:40:0,
>[   30s]                  from /home/abuild/rpmbuild/BUILD/libyui-ncurses-2.49.0/src/NCWidget.h:31,
>[   30s]                  from /home/abuild/rpmbuild/BUILD/libyui-ncurses-2.49.0/src/NCAlignment.h:31,
>[   30s]                  from /home/abuild/rpmbuild/BUILD/libyui-ncurses-2.49.0/src/NCWidgetFactory.h:31,
>[   30s]                  from /home/abuild/rpmbuild/BUILD/libyui-ncurses-2.49.0/src/NCWidgetFactory.cc:26:
>[   30s] /home/abuild/rpmbuild/BUILD/libyui-ncurses-2.49.0/src/ncursesw.h:1613:38: error: macro "is_linetouched" requires 2 arguments, but only 1 given
>[   30s]      bool    is_linetouched( int line ) const


The changelog of ncurses mentions (for patchset 20171125)

>+  + add a macro for is_linetouched() and adjust the function's return
>+    value to make it possible for most applications to check for an
>+    error-return (report by Midolikawa H).


You are receiving this mail because: