From: Ihor Radchenko <yantar92@posteo.net>
To: Philip Kaludercic <philipk@posteo.net>
Cc: 65286@debbugs.gnu.org
Subject: bug#65286: 30.0.50; package-install-file for built-in package
Date: Mon, 14 Aug 2023 14:02:48 +0000 [thread overview]
Message-ID: <87fs4lpvqv.fsf@localhost> (raw)
In-Reply-To: <87fs4livaf.fsf@posteo.net>
Philip Kaludercic <philipk@posteo.net> writes:
>> Also, keeping elpa directory around between the tests triggers various failures.
>
> Are you sure that this is not an issue related to org-mode?
It might be. But the difference between package-install-file w/without
built-in Org loaded is unlikely Org's fault in any case.
> Could you create a minimal working example to reproduce this issue, by
> removing as much as possible from the repository while retaining the
> issue, and then send us a tarball with the remaining files?
Sorry, but the issue is triggered by interaction between built-in and
non-built-in Org. I have no idea if it is possible at all to create more
minimal reproducer.
To be clear, I have no clue at all what is going on. I made some
relatively innocent changes in Org that added a couple of provide
statements. I could see things breaking completely, but not __only__
when built-in Org is loaded. So, any attempt to reduce the reproducer
steps will be me trying random things - not very productive unless you
absolutely cannot use the reproducer I provided.
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
next prev parent reply other threads:[~2023-08-14 14:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-14 11:55 bug#65286: 30.0.50; package-install-file for built-in package Ihor Radchenko
2023-08-14 13:54 ` Philip Kaludercic
2023-08-14 14:02 ` Ihor Radchenko [this message]
2023-08-14 14:15 ` Philip Kaludercic
2023-08-14 15:09 ` Ihor Radchenko
2023-08-18 10:43 ` Max Nikulin
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87fs4lpvqv.fsf@localhost \
--to=yantar92@posteo.net \
--cc=65286@debbugs.gnu.org \
--cc=philipk@posteo.net \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).