FS#57272 - [pypy3] Add dependency on ncurses

Attached to Project: Community Packages
Opened by raphael (rca) - Monday, 29 January 2018, 13:49 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Monday, 29 January 2018, 17:27 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Sven-Hendrik Haase (Svenstaro)
Architecture All
Severity Very Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
Missing dependency on ncurses

ldd /usr/bin/pypy3 :

...
libncursesw.so.6 => /usr/lib/libncursesw.so.6 (0x00007f4cee7f7000)
libtinfo.so.6 => /usr/lib/libtinfo.so.6 (0x00007f4cee5cb000)
...
This task depends upon

Closed by  Sven-Hendrik Haase (Svenstaro)
Monday, 29 January 2018, 17:27 GMT
Reason for closing:  Fixed
Additional comments about closing:  Added to deps even though it's not necessary strictly speaking.
Comment by Doug Newgard (Scimmia) - Monday, 29 January 2018, 16:00 GMT
Both bzip2 and gdbm depend on 'sh', which happens to be provided by bash and pulls in ncurses. If something else provided sh, it could break. Of course, an Arch system without bash means no pacman, so...
Comment by raphael (rca) - Monday, 29 January 2018, 16:07 GMT
Ah yes, you're right.
I reported it because it didn't pull in ncurses 6 when i updated it. Which makes sense since the transitive dependency doesn't have a hard version requirement. Is it possible to indicate that it needs ncurses6 ? Otherwise never mind, it's not a huge deal to update ncurses separately.
Comment by Doug Newgard (Scimmia) - Monday, 29 January 2018, 16:12 GMT
"didn't pull in ncurses 6 when i updated it"

That's a partial update, and is unsupported.
Comment by Sven-Hendrik Haase (Svenstaro) - Monday, 29 January 2018, 16:18 GMT
It's probably prudent to directly depend on ncurses which is what many other packages are doing as well. I'll add that.
Comment by Eli Schwartz (eschwartz) - Monday, 29 January 2018, 16:32 GMT
Yeah, we don't have any policy on packages in the base group, but OTOH indirect dependencies are another question entirely. Lots of packages explicitly depend on their own dependencies even if they are eventually pulled in by some package in base, so it could go either way. It seems like it wouldn't be unreasonable to add it to svn for the future.

Loading...