From: Uwe Brauer <oub@mat.ucm.es>
To: Stefan Kangas <stefan@marxist.se>
Cc: Uwe Brauer <oub@mat.ucm.es>, 38324@debbugs.gnu.org
Subject: bug#38324: 27.0.50; package corruption? cannot de install packages
Date: Sat, 25 Jan 2020 23:15:10 +0100 [thread overview]
Message-ID: <87h80jdvyp.fsf@mat.ucm.es> (raw)
In-Reply-To: <87wobrizae.fsf@mat.ucm.es>
[-- Attachment #1: Type: text/plain, Size: 2590 bytes --]
>>> "SK" == Stefan Kangas <stefan@marxist.se> writes:
Hi
>> 4. I type ? Because I want to understand the dependency but I
>> obtain an error (debug-on-error t) which I attach.
> (I'm only addressing everything up to step 4 below.)
> matlab-mode is a dependency of the org-babel-eval-in-repl on MELPA.
> So I installed the org-babel-eval-in-repl package, and tried your
> recipe. And I got a backtrace on current master.
> But I'm getting a different backtrace than you did:
> Now, the above happens because, when there is no README file,
> `package--get-description' expects there to be a (format "%s.el"
> package-name) file where we can read the information for installed
> packages.
Ah I did not know thanks, for pointing this. I did not know about it.
> But that's not a convention that the "matlab-mode" package follows for
> some reason. (This requirement/convention does not seem to be
> documented in the manual; see (info "(elisp)Multi-file Packages").)
> Maybe we need to think a bit about what we can do in these cases. For
> example, there is a matlab.el file that we could have been using
> instead. But the question is if we want to start adding heuristics
> here, and if so, which.
> Or should we just document the requirement and tell package authors
> that they just have to follow it? Does anyone else have an opinion
> here?
> (NOTE: There is a README.org in the matlab-mode git repository[1]
> but it is not included in the MELPA package. That should probably
> be fixed, presumably by updating the MELPA recipe.)
Ok, I should add that I am the current matlab repository maintainer at
sourceforge, github is mirror (I rarely provide matlab code, do more
testing and all the repository stuff, like merging etc)
A short while ago I updated the MELPA recipe.
Question, is it sufficient to add the README.org file, or should I,
even, rename the file to README before adding it to the recipe?
> ---
> That said, I don't think I understand the below backtrace:
> In any case, could you please try this again on current master and see
> if you are still seeing the above backtrace, or if you are now seeing
> the same as me. Thanks in advance.
I am currently, using Ubuntu 16.04, unable to compile Emacs master, I
already started a discussion on emacs devel, the problem seems some
bizarre unresolved png library dependency, after I upgraded my png
library.
Regards
Uwe Brauer
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5673 bytes --]
next prev parent reply other threads:[~2020-01-25 22:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-22 17:41 bug#38324: 27.0.50; package corruption? cannot de install packages Uwe Brauer
2020-01-25 5:01 ` Stefan Kangas
2020-01-25 22:15 ` Uwe Brauer [this message]
2020-01-26 3:33 ` Stefan Kangas
2020-01-26 9:03 ` Uwe Brauer
2021-08-31 2:08 ` Lars Ingebrigtsen
2021-08-31 6:53 ` Uwe Brauer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h80jdvyp.fsf@mat.ucm.es \
--to=oub@mat.ucm.es \
--cc=38324@debbugs.gnu.org \
--cc=stefan@marxist.se \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.