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: 104
Popularity: 0.001512
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 .. 27 28 29 30 31 32 33 34 35 36 37 38 Next › Last »

eliasson commented on 2012-12-18 12:34 (UTC)

Please add imagemagick, libotf and m17n-lib to the depends. Reason: $ emacs emacs: error while loading shared libraries: libMagickWand.so.6: cannot open shared object file: No such file or directory # pacman -S imagemagick $ emacs emacs: error while loading shared libraries: libotf.so.0: cannot open shared object file: No such file or directory # pacman -S libotf $ emacs emacs: error while loading shared libraries: libm17n-flt.so.0: cannot open shared object file: No such file or directory Using x86_64.

nsantos commented on 2012-11-10 12:24 (UTC)

@aurelien Weird issue. Maybe Savannah was down when you tried?

aurelien commented on 2012-11-06 07:55 (UTC)

trouble for me during the build. Stop after Connecting to Savannah Optional dependencies for bzr python2-paramiko: for sftp support ==> Retrieving Sources... ==> Extracting Sources... ==> Entering fakeroot environment... ==> Determining latest bzr revision... -> Version found: 110811 ==> Starting build()... ==> Connecting to Savannah...

nsantos commented on 2012-10-06 08:52 (UTC)

Put "make bootstrap" back in. This should fix most those intermittent build failures that mostly don't make sense, judging from the thrown error messages. This *won't*, however, facilitate building a package in those instances wherein the repo itself is in a broken state. Also added a new option _opt_puresize. Raised the default from about 1.68 megs to about 2 megs. (This isn't the final value; there're still other calculations applied to this to get the final value. See src/puresize.h for details.) This should help those who've encountered error messages regarding Pure Storage for Emacs Lisp, and noticed Emacs leaking like a sieve. If you've never had this error message pop up on you, don't worry about the increased memory--in my experience, it doesn't really add much of an overhead (am using a 6+ year old, 32-bit laptop with 2gigs of RAM). If you're truly concerned, you can just comment out the call-out to sed about halfway through the recipe.

nsantos commented on 2012-09-28 00:22 (UTC)

LOL, yeah. Fixed now.

<deleted-account> commented on 2012-09-27 17:54 (UTC)

@nsantos: NP :-). You still have a little error in your PKGBUILD, regarding the dependency resolution: if [[ $_opt_use_gtk3 = "y" ]]; then depends=('dbus-core' 'desktop-file-utils' 'libpng' 'libtiff' 'librsvg' 'giflib' 'gtk3' 'libxpm' 'libjpeg>=7' 'hicolor-icon-theme') else depends=('dbus-core' 'desktop-file-utils' 'libpng' 'libtiff' 'librsvg' 'giflib' 'gtk2' 'libxpm' 'libjpeg>=7' 'hicolor-icon-theme') fi You should change the $_opt_use_gtk3 there to $_opt_use_gtk2 and exchange the gtk3 and gtk2 dependencies. Vale, Quintus

nsantos commented on 2012-09-25 07:40 (UTC)

@Quintus Thanks for the head's up. Since 3.x is now the default, I did just as you suggested.

<deleted-account> commented on 2012-09-14 22:04 (UTC)

The PKGBUILD always builds the GTK3 version of emacs, this option is useless: # Don't compile against Gtk+ 3.x by default; stick with Gtk+ 2.x _opt_use_gtk3="n" To correct this, further down replace --with-x-toolkit=gtk with --with-x-toolkit=gtk2 Emacs now builds GTK3 by default if GTK2 is not requested specifically. Instead you could of course change the option to "_opt_use_gtk2" :-) Vale, Quintus

eschulte commented on 2012-07-30 18:07 (UTC)

WRT the info.info.gz conflicts, adding the following to the "cleaning up..." section of PKGBUILD allows me to sucessfully install this package, although I do get a "error: command failed to execute correctly" warning printed after instillation. rm /usr/share/info/info.info.gz || return 1 I don't know if this is a desirable or general solution.

eschulte commented on 2012-07-30 16:03 (UTC)

I'm getting the following conflict when installing with pacman -U error: failed to commit transaction (conflicting files) emacs-bzr: /usr/share/info/info.info.gz exists in filesystem Errors occurred, no packages were upgraded. I see this mentioned in the comments below, but see no solution posted. Thanks,

« First ‹ Previous 1 .. 27 28 29 30 31 32 33 34 35 36 37 38 Next › Last »