Package Details: emacs-lucid 26.1-2

Git Clone URL: (read-only)
Package Base: emacs-lucid
Description: The extensible, customizable, self-documenting real-time display editor (Lucid toolkit version)
Upstream URL:
Licenses: GPL3
Conflicts: emacs
Provides: emacs=26
Submitter: favadi
Maintainer: jpkotta
Last Packager: jpkotta
Votes: 21
Popularity: 0.557707
First Submitted: 2012-07-23 16:07
Last Updated: 2018-06-04 22:39

Required by (274)

Sources (2)

Latest Comments

jpkotta commented on 2018-06-14 17:29

@tychoish Yeah I've noticed that. The main emacs PKGBUILD in extra also has that warning. I don't think it's a big deal. If I get some time, I'll try to make that warning go away.

tychoish commented on 2018-06-14 14:52

==> Checking for packaging issues... ==> WARNING: Package contains reference to $srcdir usr/bin/emacs-26.1

It looks like there's an issue in packaging?

CyberShadow commented on 2018-02-19 15:22

Hi, would you mind updating the /var/games permissions fix as it is in the extra/emacs PKGBUILD?

Currently core/filesystem says the mode is 775, but this package says it's 755.

Edit: thanks!

eigengrau commented on 2017-09-11 18:28

Looks like they will be doing 25.3 as an emergency release.

eigengrau commented on 2017-09-11 18:12

Emacs 25.2 suffers from a trivially exploitable remote-code-execution vulnerability [1]. I’m not sure how fast things like this are backported (if at all), but since this is a rather concerning issue, maybe it might make sense to apply the patch [2] in the PKGBUILD to get this shipped to folks who don’t know about this and who haven’t applied any mitigation in their init.el.

[1] <>
[2] <>

jpkotta commented on 2017-07-20 17:11

You can just do a rebuild (`makepkg -f && pacman -U emacs-lucid...`), but yes bumping pkgrel forces it for everyone, which is convenient.

CyberShadow commented on 2017-07-20 08:02

Please bump pkgrel to fix "emacs: error while loading shared libraries: cannot open shared object file: No such file or directory" ?

eigengrau commented on 2017-04-19 05:59

When installing cask I just noticed some packages actually do use versioned requirements, so it might be convenient to have this «provides=emacs=$pkgver». For repo packages this seems to be the standard, so we should probably do this for our packages as well.

jpkotta commented on 2016-11-30 18:57

I don't really like building differently than the user expects (assuming they installed `hardening-wrapper` and configured it as they like), but it seems like Emacs just doesn't build with PIE, and their solution on other platforms (where PIE is the default) is to explicitly disable PIE with linker flags. So I added `HARDENING_PIE=0`.

eigengrau commented on 2016-11-29 21:45

Unfortunately, the build currently seems to segfault when hardening-wrapper is installed (this will causet the build to segfault). Do you think it’s sensible to «export HARDENING_PIE=0» in the PKGBUILD for the time being?

Apparently this has been an issue before:

Though, for some reason, this only turned up with 25.1-4 for me.

All comments