unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Glenn Morris <rgm@gnu.org>
To: Stefan Kangas <stefan@marxist.se>
Cc: marmot-te@riseup.net, 46236@debbugs.gnu.org
Subject: bug#46236: 26.1; explicit the info files installation
Date: Wed, 21 Apr 2021 11:32:37 -0400	[thread overview]
Message-ID: <db8s5b4pre.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <CADwFkmmEa6GSDc095bEGQ_eMhTviX6JeoQooOOqXb9qx2_sjUQ@mail.gmail.com> (Stefan Kangas's message of "Wed, 21 Apr 2021 07:40:00 -0500")


IMO it's obviously Debian's responsibility to fix this.
If they want to remove an info file, they should replace it with a stub that
says that they did so, and explains how to get the original.
It would seem simple to do so.
But given that this has not happened in 15 years, it seems unlikely to.

See eg https://bugs.debian.org/961593
(But I'm sure this must have been discussed before that.)

(This problem is of course not specific to Emacs info files.)





  reply	other threads:[~2021-04-21 15:32 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-01 14:10 bug#46236: 26.1; explicit the info files installation marmot-te
2021-02-03  5:48 ` Richard Stallman
2021-04-21  3:20   ` Stefan Kangas
2021-04-21  9:02     ` Eli Zaretskii
2021-04-21 12:06       ` Stefan Kangas
2021-04-21 12:16         ` Eli Zaretskii
2021-04-21 12:40           ` Stefan Kangas
2021-04-21 15:32             ` Glenn Morris [this message]
2021-04-21 16:34               ` Stefan Kangas
2021-04-21 12:32         ` Gregory Heytings
2021-04-21 13:00           ` Eli Zaretskii
2021-04-21 13:47             ` Gregory Heytings
2021-04-21 13:11           ` Stefan Kangas
2021-04-21 13:54             ` Gregory Heytings
2021-04-21 14:13               ` Stefan Kangas
2021-03-06 14:25 ` Tomas Nordin
2021-03-07  6:11   ` Richard Stallman

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=db8s5b4pre.fsf@fencepost.gnu.org \
    --to=rgm@gnu.org \
    --cc=46236@debbugs.gnu.org \
    --cc=marmot-te@riseup.net \
    --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 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).