unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Ulrich Mueller <ulm@gentoo.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 66721@debbugs.gnu.org
Subject: bug#66721: 29.1; make sanity-check fails
Date: Tue, 24 Oct 2023 13:51:03 +0200	[thread overview]
Message-ID: <uv8aw44t4@gentoo.org> (raw)
In-Reply-To: <83jzrcmg5x.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 24 Oct 2023 14:08:26 +0300")

>>>>> On Tue, 24 Oct 2023, Eli Zaretskii wrote:

> One could argue (although I personally will not necessarily agree)
> that making sure site-lisp loads fine _is_ part of the sanity check,
> since a failure to load that is not necessarily due to problem in
> site-lisp, it could be a problem with the built Emacs.

From a (source-based) distro point of view, the user must first update
Emacs, followed by updating any add-on packages. It's a logical dilemma
if the first step can fail because of outdated add-on packages.

>> I propose the trivial patch below, preferably for the emacs-29 branch.

> Thanks, but I don't think it's trivial, so please install it on
> master, as I don't want any changes in the build at this late stage of
> Emacs 29 release cycle.

I fail to see any potential for breakage there, but whatever.

> Also, please use -Q, not --quick, as I think the former is more
> familiar.

Done.





      reply	other threads:[~2023-10-24 11:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-24  6:24 bug#66721: 29.1; make sanity-check fails Ulrich Mueller
2023-10-24 11:08 ` Eli Zaretskii
2023-10-24 11:51   ` Ulrich Mueller [this message]

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=uv8aw44t4@gentoo.org \
    --to=ulm@gentoo.org \
    --cc=66721@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    /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).