Package Details: emacs-pretest 25.2-0.2

Git Clone URL: https://aur.archlinux.org/emacs-pretest.git (read-only)
Package Base: emacs-pretest
Description: The extensible, customizable, self-documenting real-time display editor -- pretest version
Upstream URL: http://www.gnu.org/software/emacs/emacs.html
Licenses: GPL3
Conflicts: emacs
Provides: emacs
Submitter: Schnouki
Maintainer: Schnouki (vorbote)
Last Packager: vorbote
Votes: 7
Popularity: 0.000094
First Submitted: 2011-11-17 16:48
Last Updated: 2017-02-22 20:18

Required by (271)

Sources (2)

Latest Comments

vorbote commented on 2017-10-12 22:38

Version 26.0.90 is broken under arch, so no update yet.

j3thr0 commented on 2016-10-27 16:09

To solve the unknow public key error just do:
-> % gpg --recv-keys 233587A47C207910

oniram commented on 2016-09-14 13:56

@vorbote Thanks. I really don't know anything about PGP key signing.

vorbote commented on 2016-09-14 13:52

@oniram No. Not an error. You need to import the key to the personal gnupg public keyring of the user under which you run makepkg by hand. It doesn't happen by magic. If you don't want PGP signature verification, run makepkg with the "--skippgpcheck" option.

oniram commented on 2016-09-14 13:42

I'm seeing this weird error:
emacs-25.1-rc2.tar.xz ... FAILED (unknown public key 233587A47C207910)

That unknown key is just the last digits of the key given in the PKGBUILD.

vorbote commented on 2016-09-01 17:37

OK, should be fixed now. I promise to start using my reading glasses. Phew!

vorbote commented on 2016-09-01 17:24

Argh! I botched the fix. I'll work on that ASAP.

lizzie commented on 2016-08-31 18:50

Thanks for fixing that, but now the pkgrel is 0.2.1, which doesn't seem to be allowed: "==> ERROR: pkgrel must be a decimal, not 0.2.1.".

lizzie commented on 2016-08-30 18:55

The author has misspelled 'validpgpkeys' as 'validpgkkeys'. This causes the error that jeffles mentioned.

vorbote commented on 2016-04-04 22:32

jeffles, the key is perfectly valid. You should use hkp://keys.gnupg.net as it is more trustworthy and complete.

Keyservers do not work as you think. Once a key is published it cannot be removed, only revoked by uploading a revocation certificate created by the owner of such key (or whoever stole his revocation certificate...). Else, where is the web of trust left?

All comments