From: Benjamin Orthen <benjamin@orthen.net>
To: Stefan Monnier <monnier@iro.umontreal.ca>,
Philip Kaludercic <philipk@posteo.net>
Cc: 63916@debbugs.gnu.org
Subject: bug#63916: 30.0.50; use-package: changes do not propagate to elpa-devel
Date: Sun, 11 Jun 2023 19:32:09 +0200 [thread overview]
Message-ID: <bd9414ec73ab925cd081e4ed333ebd95310aabd7.camel@orthen.net> (raw)
In-Reply-To: <jwvmt16ueib.fsf-monnier+emacs@gnu.org>
Hi,
I think I figured out why elpa does not build a new version of use-
package.
To determine the devel version, it looks only at the git log of `(elpa-
-main-file pkg-spec)`, which in this case turns out to be use-
package.el. However, use-package.el has not been changed since
20230115, I suppose this is why no new version is built.
Best, Benjamin
On Sun, 2023-06-11 at 12:55 -0400, Stefan Monnier wrote:
> > > I agree that these kinds of problems are annoying to debug. It
> > > would be
> > > nice to offer a "debug mode" where the user can see what's going
> > > on
> > > within the sandbox. Maybe we could do that by opening an
> > > interactive
> > > shell with a message saying "this is the command that we want to
> > > run"
> > > and then let the user run that command?
> > Shouldn't just invoking bash do that?
>
> Yes, it should be fairly easy to do.
>
> > But returning to the initial issue (hoping I did not miss
> > anything), if
> > the issue is not what I mentioned, then why is use-package not
> > building?
>
> You did not miss anything: it's not building simply because the
> process
> run within the sandbox cannot read the target of the `use-
> package.texi`
> symlink because the sandbox does not expose this target.
>
>
> Stefan
>
next prev parent reply other threads:[~2023-06-11 17:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-05 21:21 bug#63916: 30.0.50; use-package: changes do not propagate to elpa-devel Benjamin Orthen
2023-06-10 9:03 ` Philip Kaludercic
2023-06-10 16:01 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-11 10:34 ` Philip Kaludercic
2023-06-11 15:55 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-11 16:37 ` Philip Kaludercic
2023-06-11 16:55 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-11 17:32 ` Benjamin Orthen [this message]
2023-09-08 10:55 ` Benjamin Orthen
2023-09-08 17:14 ` Philip Kaludercic
2023-09-08 19:35 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-11 9:58 ` Benjamin Orthen
2023-09-27 10:53 ` Benjamin Orthen
2023-09-28 19:52 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=bd9414ec73ab925cd081e4ed333ebd95310aabd7.camel@orthen.net \
--to=benjamin@orthen.net \
--cc=63916@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
--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 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.