Arch Linux User Repository

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

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

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]

@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.

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.

Could it be possible to add aarch64 architecture?

I can confirm the package builds succesfully and seems to be working properly.

(Might also work on other arm architectures.)

Well the public key worked here and the package built and installed. So I suspect your problem was the keyserver and nothing to do with the package or key. Perhaps you should try again?

Proof ==> Finished making: ncurses5-compat-libs 6.1-1 (Sun 05 Apr 2020 14:07:33 BST) ==> Cleaning up...

Checking keyring... Checking integrity... Loading package files... Checking file conflicts... Checking available disc space... Reinstalling ncurses5-compat-libs (6.1-1)... Transaction successfully finished.

For Signatures I use this

mkdir -p /home/username/.gnupg echo 'keyring /etc/pacman.d/gnupg/pubring.gpg' >> $HOME/.gnupg/gpg.conf chown -R username:username /home/username/.gnupg chmod 700 /home/username/.gnupg chmod 600 /home/username/.gnupg/*

==> Verifying source file signatures with gpg... ncurses-6.1.tar.gz ... FAILED (unknown public key 702353E0F7E48EDB) ==> ERROR: One or more PGP signatures could not be verified! The build failed.

@mirh use this https://gist.githubusercontent.com/florianbegusch/88955f8a86ddd1e45b99f930d5a178f0/raw/e386d3057dc7dfaad627aef9226ec2e48cbeb641/PKGBUILD

I'd really like "--with-versioned-syms" to be added to configure, so that I don't get warning-spammed during compilation of other software.

Also, the last make has problems with spaces in path still.

Updated PKGBUILD and .SRCINFO

Thank you in advance

You may experience the following compilation error on latest gcc:

/usr/include/bits/wchar2.h:448:3: error: #error "Assumed value of MB_LEN_MAX wrong"

Solution: insert the following code to the FIRST line of "src/ncurses-6.1/progs/progs.priv.h", "src/ncurses-6.1/c++/cursesw.h", and "src/ncurses-6.1/ncurses/curses.priv.h".

#include <wchar.h>

Maybe a patch should be added to this repo.