Package Details: emacs-git 30.0.50.169253-1

Git Clone URL: https://aur.archlinux.org/emacs-git.git (read-only, click to copy)
Package Base: emacs-git
Description: GNU Emacs. Development master branch.
Upstream URL: http://www.gnu.org/software/emacs/
Keywords: development editor IDE text
Licenses: GPL3
Conflicts: emacs
Provides: emacs
Submitter: toropisco
Maintainer: toropisco
Last Packager: toropisco
Votes: 107
Popularity: 1.93
First Submitted: 2014-01-05 02:05 (UTC)
Last Updated: 2023-10-14 18:36 (UTC)

Required by (313)

Sources (2)

Pinned Comments

toropisco commented on 2017-06-30 19:14 (UTC) (edited on 2022-05-15 13:26 (UTC) by toropisco)

This PKGBUILD is a work in progress. If you find PACKAGING bugs, please let me know ASAP.

Upstream bugs are to be reported upstream. Check out the emacs-devel archives to confirm if this is an already known bug. In fact... Why are you not subscribed to emacs-devel?. Also check the emacs-bug-tracker archives.

Reporting bugs: Write to the Emacs Bug Tracker and report it there. Or, better yet, use the debbugs client included with the text editor. You will find instructions at https://debbugs.gnu.org/. Good luck!

If you confirm it is a packaging bug, you are welcome to report it here.

Yaourt and other automated tools users BEWARE! This PKGBUILD is written with hand updating in mind and I won't fix bugs arising from such use. Besides, cloning the same repository time and time again from a non-profit such as the GNU Project/FSF gives out a very low image of you.

Latest Comments

« First ‹ Previous 1 .. 20 21 22 23 24 25 26 27 28 29 30 .. 39 Next › Last »

ryuslash commented on 2016-03-04 09:15 (UTC)

If you want to use the latest git version of Emacs you really should be using the "emacs-25" branch, not the "master" branch. At least until Emacs 25 is released.

pandeiro commented on 2016-03-03 17:16 (UTC)

OK vorbote, so this package is "caveat emptor", I get it. I thought I should expect it to be able to build at least. I wonder how else I can get Emacs 25.x on Arch, open to suggestions for a more stable route.

toropisco commented on 2016-03-02 23:56 (UTC) (edited on 2016-03-04 13:38 (UTC) by toropisco)

And back to your scheduled git repo pull. Till Savannah keels over again. ;-)

toropisco commented on 2016-03-02 23:55 (UTC)

@pandeiro then don't use the master branch :-) Seriously though. When you use the master branch you have no guarantee that it will compile at all. If it breaks you get to keep the pieces. Now... Don't you use make bootstrap unless you must; and you'll know if you do. The configuration scripts run make bootstrap if needed and it is only in some corner cases related to unsynced .el .elc files that you really need to run bootstrap. I put forward that if the above is not the case, the problem is somewhere else and may require you reinstall your system; I've had that kind of weirdness arising from filesystem corruption.

pandeiro commented on 2016-03-02 22:22 (UTC)

@verbote Unfortunately none of those suggestions produced a different result than the error I posted below.

toropisco commented on 2016-03-02 17:12 (UTC) (edited on 2016-03-02 17:12 (UTC) by toropisco)

@pandeiro. Delete the src and pkg directories and try again. If trouble persists delete the git repo and download again. Works for me.

pandeiro commented on 2016-03-02 15:35 (UTC)

`makepkg -s` fails for me every time with: ... Dumping under the name emacs Makefile:739: recipe for target 'bootstrap-emacs' failed make[1]: *** [bootstrap-emacs] Segmentation fault (core dumped) make[1]: Leaving directory '/home/mu/emacs-git/src/emacs-git/src' Makefile:398: recipe for target 'src' failed make: *** [src] Error 2 ==> ERROR: A failure occurred in build().

madalu commented on 2016-02-28 16:14 (UTC)

FWIW, the git:// service at Savannah is working at the moment.

toropisco commented on 2016-02-23 13:54 (UTC) (edited on 2016-02-23 13:56 (UTC) by toropisco)

Savannah has been in trouble for the last weeks and the git:// service is gone, who knows for how long. I have switched to use the http interface. I know it is an inconvenience, but a simple edition of the git repo config file fixes it. No need to redownload everything.

zhenya1007 commented on 2015-11-30 16:10 (UTC)

Commit 8e5785c9 introduced a bug: ./configure ${_conf} should instead be ./configure ${_conf[@]} or, equivalently (since the variable expansion isn't inside a double-quoted string) ./configure ${_conf[*]} See: https://www.gnu.org/software/bash/manual/bash.html#Arrays