Package Base Details: libc++

Git Clone URL: https://aur.archlinux.org/libc++.git (read-only, click to copy)
Submitter: WoefulDerelict
Maintainer: WoefulDerelict
Last Packager: WoefulDerelict
Votes: 248
Popularity: 2.49
First Submitted: 2017-02-04 16:09
Last Updated: 2020-05-07 18:42

Pinned Comments

eschwartz commented on 2019-01-21 03:57

PSA: Due to repeated abuse, this package is now a ZERO-TOLERANCE ZONE for rules violations.

Hi people, sorry for the interruption if you're the majority of users just innocently doing your thing, if so, feel free to just move on. For the rest of you, this is your final reminder regarding the following points, which shall now be grounds for having your account suspended:

  • Thou shalt not complain about makepkg's validpgpkeys feature.

  • Thou shalt not complain about makepkg's check() feature.

  • Thou shalt not under any circumstances ever insult the maintainer for implementing said features.

This package is doing the correct thing, and there has been a great deal of pointless moaning and whining about it despite the pinned comments explaining why these complaints are not only null and void, but also ridiculous because they can already be disabled. This nagging stops now.

The banhammer is ready and waiting in case you still want to ignore all this on top of the Trusted User warning(s).

Alad commented on 2018-08-22 12:58

Holy shit guys. What's unclear about "AUR helpers are not supported"? Stop this incessant spam and learn how to use makepkg.

https://wiki.archlinux.org/index.php/Makepkg https://wiki.archlinux.org/index.php/Arch_User_Repository

Any comments on AUR helper issues will be deleted from now on. Repeat offenders will have their accounts suspended.

WoefulDerelict commented on 2018-07-21 11:45

If you experience issues when using an AUR helper please try again using makepkg. AUR helpers are not supported here. The AUR article in the ArchWiki documents the prerequisites and supported process. https://wiki.archlinux.org/index.php/Arch_User_Repository

The test suite contains tests for multiple locales including: en_US.UTF-8, fr_FR.UTF-8, ru_RU.UTF-8, zh_CN.UTF-8, fr_CA.ISO8859-1 and cs_CZ.ISO8859-2. If a locale isn't present on the system the related tests will be marked as unsupported and skipped.

If you encounter issues when building with makepkg please attempt to build this in a clean chroot using using the appropriate devtools script. The Arch Linux DeveloperWiki has an article focused around building packages in a clean chroot which contains information on the devtools scripts and explains the process of building in a clean chroot: https://wiki.archlinux.org/index.php/DeveloperWiki:Building_in_a_Clean_Chroot

There is an active community of users on IRC along with a vibrant Discord server and Forums should you require assistance.

Picking a fight with one of the Trusted Users is a terrible idea.

WoefulDerelict commented on 2017-02-05 03:42

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.

The libc++ test suite can be skipped by passing --nocheck to makepkg.

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

WoefulDerelict commented on 2017-02-09 07:27

MrLinuxFish: No, no, no a thousand times NO! This package is not out of date nor is there anything wrong with it. Flagging a package out of date is not the way to report issues with source signature verification.

The problem here is your failure to RTFM and understand what is going on and what you need to do in order to successfully build and install this package. There is a pinned comment with background and instructions for fetching the keys necessary to verify the integrity of the signed sources BEFORE you attempt to build this. Go read the documentation and try again.

WoefulDerelict commented on 2017-02-05 22:37

I've gone ahead and merged this into a split package built inside the LLVM source tree as it can be bootstrapped with clang from [Extra] and all the dependencies are currently in the core binary repos. If you've already built this there is very little difference in the output so it is not necessary to rebuild and reinstall. Aside from the ordeal of ensuring the keys are available to verify the sources this should be relatively easy to build. Haven't really tested it against the AUR helpers but it should be less confusing for them.

pepper_chico commented on 2017-02-05 03:54

@WoefulDerelict ok, I do it manually in general, it's just that it's really a quite rare thing to do.

WoefulDerelict commented on 2017-02-05 03:47

pepper_chico: The wiki article on GnuPG should explain how to configure GPG and fetch keys to verify the sources. If you don't fancy adding three keys manually or manually adding the keys in general pay special attention to the tip on configuring GPG to fetch the keys for you automatically.

WoefulDerelict commented on 2017-02-05 03:42

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.

The libc++ test suite can be skipped by passing --nocheck to makepkg.

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

pepper_chico commented on 2017-02-05 03:13

I'm a user of libc++ in Arch a long time. Have emailed the original maintainer regarding a necessary update before because an older version didn't even work with the clang that was being shipped on Arch.

The previous version was working, but now this update is failing PGP verification.

WoefulDerelict commented on 2017-02-05 01:38

skystrife: I'd had these floating around so when I saw that they had been dropped from the AUR instead of being adopted by a new TU and updated I pushed out what I had. I'd considered doing a split package and avoiding many of the little warnings thrown when building them as separate packages. Unfortunately not being able to toss in checks as an added bonus to go along with signed sources minimized any arguable benefit. There is a general distaste for split packages even when it is more efficient and effective in the long run so I hadn't gone that route yet.

I'm not against a split package if users find that easier or more convenient. I suspect migrating to a split package at this point would require a merge request. If you're familiar with this software and would like to assist as a co-maintainer I can add you. You can find one's mock up of the split package here: https://gist.github.com/WoefulDerelict/0f0d248eb12c2d0d826965a7ca29b728

If one tosses the example you provided at the tooling used to build, test and deploy packages to the AUR it reveals a few flaws you should be aware of. First and foremost, while makepkg will tolerate a pkgdesc with an escaped newline mksrcinfo will not. BSD, MIT, zlib/png, Python and custom licences need to be copied into the package. In this case the license is broken into two pieces which need to be included in each package. Everything else checked out.

skystrife commented on 2017-02-05 01:01

@WoefulDerelict I think you can avoid the bootstrapping issue by using a split-package PKGBUILD. libc++ and libc++abi can be built simultaneously without having either pre-installed if you build them in-tree with an LLVM checkout.

For example: http://pastebin.com/y3cpKGkv

I was going to submit this package, after having a discussion on the mailing list[1], but it seems like you beat me to the punch.

[1]: https://lists.archlinux.org/pipermail/aur-general/2017-February/033185.html

WoefulDerelict commented on 2017-02-04 22:47

doskoi: I don't know why this package was dropped from [Community]. I suspect it has to do with it being out of date, lacking a TU to maintain it and that it has no dependencies in the core repositories or [Community].

doskoi commented on 2017-02-04 22:39

Ok ;) And do you know why this package was removed from community?