all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: pooh@aikipooh.name (Юрий Пухальский)
Cc: 35959@debbugs.gnu.org
Subject: bug#35959: IPv6 for elpa.gnu.org
Date: Wed, 12 Jun 2019 10:27:11 -0400	[thread overview]
Message-ID: <jwvzhmmubz1.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <m2imtbvvsw.fsf@gmail.com> (Robert Pluim's message of "Wed, 12 Jun 2019 14:21:19 +0200")

>     Юрий> I'm using EMACS and would like to use elpa on one of my hosts, which
>     Юрий> is IPv6 only. But unlike gnu.org elpa.gnu.org has only IPv4 address.
>     Юрий> I believe it's not hard IPv6 there as well.

This was requested a little while ago, but indeed currently elpa.gnu.org
is IPv4-only.  To make it IPv6, it needs an IPv6 entry in the DNS, it
needs its network interface to acquire this IPv6 address, and it requires
the rest of the FSF's network to propagate the corresponding IPv6
packets to that host.

When we (an FSF sysadmin and myself) looked at it earlier this year, there
was a problem in the FSF's infrastructure (the 3rd part).  I can't quite
remember what it was, but I have the vague impression that it had to do
with the VM host being currently itself limited to IPv4.

> That host is not managed by the Emacs team.  Iʼm not sure who *does*
> manage it, and itʼs not obvious from the website.  Stefan, is this
> one yours?

The maintenance is done in part by myself (the one within the VM, mostly
limited to the part directly relevant to the GNU ELPA archive) and in
part by some of the FSF sysadmins (the part outside the VM).  For this
specific issue, it's best to send the request to sysadmin@gnu.org (and
put me in Cc).


        Stefan






  reply	other threads:[~2019-06-12 14:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-28  8:14 bug#35959: IPv6 for elpa.gnu.org Юрий Пухальский
2019-06-12 12:21 ` Robert Pluim
2019-06-12 14:27   ` Stefan Monnier [this message]
2020-08-15 14:34     ` Stefan Kangas
2020-08-17 21:21       ` Stefan Kangas
2020-08-17 21:58         ` Stefan Monnier

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=jwvzhmmubz1.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=35959@debbugs.gnu.org \
    --cc=pooh@aikipooh.name \
    /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.