On Sun, Dec 11, 2011 at 11:32:02PM +0000, peter green wrote:
> Pal FTBFS in sid
>
> It turns out that the package depends on and links against ncursesw
> but uses the headers from ncurses.
> This seems wrong to me but I don't know enough details about ncurses
> to know just how bad it is.
A quote from curses.h:
| * NCURSES_CH_T is used in building the library, but not used otherwise in
| * this header file, since that would make the normal/wide-character versions
| * of the header incompatible.
Looks like both header variants are compatible by intention. I did not
adapt the header inclusions to minimize the diff to upstream. Anyway,
now they have to be adapted.
> I have attatched an updated version of
> 51_debian_link_against_ncursesw.patch which changes the
> header includes too.
Great, thanks! I'll upload pal with your fixed patch soonish.
* Martijn van Oosterhout [2011-12-12 22:35 +0100]:
> Now personally I'm not clear about the difference between ncurses and
> ncursesw. All I can find is that with ncursesw you have wide-character
> support?
Indeed, wide character support is as far as I know the only difference
between ncurses and ncursesw.
> But the upstream code just links against ncurses, not the -w version,
> so I'm totally not clear what's going on here...
I just built pal/Sid on Debian Squeeze without the patch that adapts
linking, i.e., I linked against the non-wide ncurses.
If I start the ncurses ui with "LC_ALL=de_DE.UTF-8 ./pal -m", the first
line is displayed as follows:
pal 0.4.3 - 'h' fM-CM-<r Hilfe, 'q' zum Beenden.
Correct would be:
pal 0.4.3 - 'h' für Hilfe, 'q' zum Beenden.
It is displayed properly when linked against ncurses' wide-character
version.
We discussed this in the past and you asked if linking against ncursesw
would be appropriate for upstream too. Back then I wrote that I'm not
sure if other distributions or operating systems also ship different
ncurses variants or if they just use the wide character variant by
default. So I did change the linking for the Debian package and you
didn't alter it upstream.
> That said, I'm just upstream and can't upload anything myself.
This could be changed :) Having a maintainer team instead of just one
maintainer (even if there's a good upstream) is desirable. After some
sponsored uploads you could, as next step, get upload permissions for
specific packages. This would involve answering some questions about
packaging, packaging and so on. Relevant URL's about this process are
http://www.debian.org/devel/join/newmaint and
http://wiki.debian.org/DebianMaintainer
Regards
Carsten
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
