similar to: elpa-ess fails to initialize after update to 18.10 on ubuntu bionic

Hi Chris, On 22 October 2018 at 22:22, Chris Sims wrote: | The latest ess and elpa-ess 18.10-1bionic0 packages for ubuntu leave | ess unable to find initialization files when it is invoked from R via | M-x R. I've found a workaround by creating a soft link: | | cd /usr/share | sudo ln -s /usr/share/emacs/site-lisp/elpa-src/ess-18.10 ess | | but this may be a widespread problem. It

Chris, For what it is worth, I made two more tests: - on my system 'M-x R' as well as the suggested-in-the-ESS-documentation 'M-x ess-version' both work whether or not I have my ~/.emacs -- so somehow system path must work - I have the .el files in the default directory: /usr/share/emacs/site-lisp/elpa-src/ess-18.10 - They are also symlinked each into

Updates to Linux Mint included an update to ESS. After the update, M-x R produces: load ESSR: + + + Error in file(filename, "r", encoding = encoding) : ? cannot open the connection In addition: Warning message: In file(filename, "r", encoding = encoding) : ? cannot open file ?/usr/share/ess/etc/ESSR/R/.load.R?: No such file or directory Any guesses? Thanks, Steve

On Wed, Oct 24, 2018 at 12:13 PM Dirk Eddelbuettel <edd at debian.org> wrote: > > It's just a directory, not an apt repo, so you need to download eg > http://dirk.eddelbuettel.com/tmp/ess/elpa-ess_18.10-1-2_all.deb > and then install it. > > These "work for me" but then I also did not have that recent issue. > Testing feedback (on list or off-list) would

Hi Paul, On 24 October 2018 at 14:49, Paul Johnson wrote: | It looks OK from my end. | | On my Ubuntu 18.1 system, I did not see the problem described above. Yes, my Ubuntu 18.04 is fine as well. | However, today I saw some other wrinkles and I have installed your | package and it works as well. M-R does cause an R session to open. (I guess you meant M-x R, presumably ? ) The (updated,

On Mon, Aug 20, 2018 at 10:43:52AM -0500, Dirk Eddelbuettel wrote: > > On 20 August 2018 at 15:29, Eva Myers wrote: > | Hello, > | Attempting to install ess (17.11-3xenial0) on our Ubuntu 16.04 systems > | is failing with an error message. > > This can happen. I (with my Debian hat on) had to make 17.11-3 because the > ess package did not behave with Debian untable and

Hi Dirk, On 2018-08-20 17:43, Dirk Eddelbuettel wrote: > > On 20 August 2018 at 15:29, Eva Myers wrote: > | Hello, > | Attempting to install ess (17.11-3xenial0) on our Ubuntu 16.04 systems > | is failing with an error message. > > This can happen. I (with my Debian hat on) had to make 17.11-3 because the > ess package did not behave with Debian untable and Emacs 26.2.

Michael, ESS broke again on my laptop after I upgraded to Ubuntu 18.10. The elpa-ess package seems to be provided multiple times, sadly the one with xenial (16.04) in its name wins ... and breaks the setup. I one for cosmic, I had one from bionic (18.04), but because the names 'wrapped' the 'x' wins over 'b' and 'c'. We had talked about that in the past, it

Hello, Attempting to install ess (17.11-3xenial0) on our Ubuntu 16.04 systems is failing with an error message. root at kore:/home/eva# apt-get install ess [...] Install ess for emacs24 install/ess: Handling install for emacsen flavor emacs24 ERROR: install script from ess package failed dpkg: error processing package ess (--configure): subprocess installed post-installation script returned

On 20 August 2018 at 15:29, Eva Myers wrote: | Hello, | Attempting to install ess (17.11-3xenial0) on our Ubuntu 16.04 systems | is failing with an error message. This can happen. I (with my Debian hat on) had to make 17.11-3 because the ess package did not behave with Debian untable and Emacs 26.2. It does now. Changes can have side effects. Turn out that in this case 16.04 is affected. Your

> On 20 August 2018 at 15:29, Eva Myers wrote: > | Hello, > | Attempting to install ess (17.11-3xenial0) on our Ubuntu 16.04 systems > | is failing with an error message. > > This can happen. I (with my Debian hat on) had to make 17.11-3 because the > ess package did not behave with Debian untable and Emacs 26.2. It does now. > > Changes can have side effects. Turn out

Hello, I appear to have a similar issue as?Willem Ligtenberg (Disco Dingo repository issues,?Thu May 2 19:01:04 CEST 2019), except on a completely fresh installation of Ubuntu?18.04 LTS (Bionic Beaver). After updating and upgrading packages and adding the repo "deb https://cloud.r-project.org/bin/linux/ubuntu bionic-cran35/" and associated key, attempting to install r-base fails due to

Hello llvm devs, Melpa[1] is pretty much the most common package manager for emacs and very recently the llvm-mode got removed from it[2] due to performance issues. This issue is not unique to llvm-mode, but affects a bunch of projects with very large git repositories[3]. Will it be possible to split this into a new separate git repo? This should make it easier for the emacs community to work

Modern Emacs uses a standard set of repos for managing emacs mode packages, so that all users need to add syntax highlighting for llvm-mode would be M-x package-install RET llvm-mode RET. Could we package llvm-mode for these repos? * MELPA <http://melpa.milkbox.net/> * Marmalade <http://marmalade-repo.org/> -- Cheers, Andrew Pennebaker www.yellosoft.us -------------- next part

Jaseem Abid via llvm-dev <llvm-dev at lists.llvm.org> writes: > Hello llvm devs, > > Melpa[1] is pretty much the most common package manager for emacs and very > recently the llvm-mode got removed from it[2] due to performance issues. > This issue is not unique to llvm-mode, but affects a bunch of projects with > very large git repositories[3]. > > Will it be possible

I can't tell what you did wrong as I can't see your setup -- and your email is not really readable on my screen (next time please try text mode if you can). Bionic beaver works for other people, see eg this blog post, support slides and (primarily) video http://dirk.eddelbuettel.com/blog/2019/06/09#022_rocker_and_ppas http://dirk.eddelbuettel.com/papers/r4_rocker_and_ppas.pdf

As far as I can see, melpa dropped svn support some time ago.... https://github.com/melpa/melpa/pull/4802 On Thu, May 10, 2018 at 11:51 AM, Tim Northover via llvm-dev <llvm-dev at lists.llvm.org> wrote: > On 10 May 2018 at 06:07, Jaseem Abid via llvm-dev > <llvm-dev at lists.llvm.org> wrote: >> Melpa[1] is pretty much the most common package manager for emacs and very

On 10 May 2018 at 06:07, Jaseem Abid via llvm-dev <llvm-dev at lists.llvm.org> wrote: > Melpa[1] is pretty much the most common package manager for emacs and very > recently the llvm-mode got removed from it[2] due to performance issues. Wouldn't svn be better here? It ought to allow you to checkout just the utils/emacs directory (or not even that with "svn cat").

btw, do you have commit access or should I commit it? On 6 January 2015 at 11:22, Rafael Espíndola <rafael.espindola at gmail.com> wrote: > LGTM, thanks! > > On 4 January 2015 at 19:08, Wilfred Hughes <me at wilfred.me.uk> wrote: >> Hi >> >> I'd like users to be able to install the LLVM major modes from >> MELPA[1], the most popular Emacs package

Hi I'd like users to be able to install the LLVM major modes from MELPA[1], the most popular Emacs package repository. However, these files are not well-formed packages. I've made the following changes: * Both files have valid package headers and footers (you can verify with M-x checkdoc). * Fixed style warnings generated by checkdoc. * Fixed a byte-compiler warning in llvm-mode.el. *