Package Details: ncurses5-compat-libs 6.2-1

Git Clone URL: https://aur.archlinux.org/ncurses5-compat-libs.git (read-only, click to copy)
Package Base: ncurses5-compat-libs
Description: System V Release 4.0 curses emulation library, ABI 5
Upstream URL: http://invisible-island.net/ncurses/ncurses.html
Licenses: MIT
Conflicts: libtinfo5
Provides: libtinfo5
Submitter: Barthalion
Maintainer: Barthalion (invidian)
Last Packager: invidian
Votes: 531
Popularity: 5.55
First Submitted: 2015-09-18 21:03
Last Updated: 2020-04-21 11:54

Required by (136)

Sources (2)

Pinned Comments

Barthalion commented on 2018-01-02 11:53

For the lazy, you can also install ncurses5-compat-libs package from my personal repository.

[bpiotrowski]
Server = https://pkgbuild.com/~bpiotrowski/repo

WoefulDerelict commented on 2016-05-23 19:35

This PKGBUILD verifies the authenticity of the source via PGP signatures which are not part of the Arch Linux keyring. In order to complete the process it is necessary to import the key(s) from the ‘validpgpkeys’ array into the user’s keyring before calling makepkg. There is a helpful article explaining this process by one of Arch Linux's developers located here: http://allanmcrae.com/2015/01/two-pgp-keyrings-for-package-management-in-arch-linux/

Instructions on importing keys from a keyserver and how to automate the retrieval process can be found in the Arch Linux wiki here: https://wiki.archlinux.org/index.php/GnuPG#Use_a_keyserver This article also contains helpful information describing the installation of GnuPG, its configuration and usage.

Execute the following to import keys using gpg:

gpg --recv-keys <KEYID - See 'validpgpkeys' array in PKGBUILD>

The PGP signature check can be skipped by passing --skippgpcheck to makepkg.

Consult the makepkg manual page for a full list of options. [https://www.archlinux.org/pacman/makepkg.8.html]

Latest Comments

1 2 3 4 5 6 ... Next › Last »

3rly commented on 2020-09-28 13:41

@invidian you are most correct Sir, I should have stated the security implications of this approach. I will pull the comment off. Thank you for the guidance.

invidian commented on 2020-09-28 07:23

@3rly please see pinned comment from @WoefulDerelict. What you are suggesting is to disable the authenticity check of the built sources, which is a bad security practice and it shouldn't be copied without understanding it's implications (again explained and mentioned in @WoefulDerelict comment.)

Retro_Gamer commented on 2020-07-26 02:56

There is no such server: "Server = https://pkgbuild.com/~bpiotrowski/repo"

jakuro commented on 2020-07-16 14:01

Any idea that in chroot this build is failing for me on?

configure: error: getopt is required for building programs ==> ERROR: A failure occurred in build(). Aborting...

marfrit commented on 2020-06-28 19:14

Can you please add aarch64 to the architectures?

micronetic commented on 2020-06-28 07:03

Tried to install ceckra1n but I always get the error with the importing of the keys, tried the normal and the git version.

=> PGP keys need importing: -> C52048C0C0748FEE227D47A2702353E0F7E48EDB, required by: ncurses5-compat-libs ==> Import? [Y/n] y :: Importing keys with gpg... gpg: Empfangen vom Schlüsselserver fehlgeschlagen: Keine Berechtigung problem importing keys

gavmanz commented on 2020-05-20 15:45

My build is freezing on the password entry phase, has anyone else experienced that?

EDIT: For anyone else... closing then re-opening a terminal to re-run the package install fixed the issue. Hm.

bickman2k commented on 2020-05-07 18:18

If you are having trouble importing the key, try the following command:

gpg --keyserver keys.gnupg.net --recv-keys 702353E0F7E48EDB

Sven commented on 2020-04-21 15:27

@invidian why are you not also maintaining lib32-ncurses5-compat-libs ? I do the believe that it would be best if the two ncurses-compat packages would be consistent.

invidian commented on 2020-04-21 12:01

I've added "--with-versioned-syms" to configure, *.a files are no longer part of the package and updated to latest version. It was installed for me for couple of weeks and I didn't experience any issues with it.

Regarding aarch64 architecture support, I'm not sure how/where to test it, so I'd rather not add it. Anty0, if you want, I guess you could co-maintain aarch64 support.