From mboxrd@z Thu Jan  1 00:00:00 1970
From: Chong Yidong <cyd@gnu.org>
Subject: Re: ELPA syncing cronjob stopped running
Date: Fri, 23 Mar 2012 00:12:43 +0800
Message-ID: <877gyclimc.fsf@gnu.org>
References: <87vclzp082.fsf@thinkpad.tsdh.de>
	<20120320191927.E29641FE45@saturn.ch.ristopher.com>
	<20120320193229.A37AA1FE45@saturn.ch.ristopher.com>
	<87obrrox44.fsf_-_@thinkpad.tsdh.de> <873991hxwt.fsf@gnu.org>
	<878vit2cnw.fsf@thinkpad.tsdh.de>
Mime-Version: 1.0
Content-Type: text/plain
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([208.118.235.92]:33320)
	by lists.gnu.org with esmtp (Exim 4.71) (envelope-from <cyd@gnu.org>)
	id 1SAkdC-0000MT-QX
	for emacs-orgmode@gnu.org; Thu, 22 Mar 2012 12:13:00 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <cyd@gnu.org>) id 1SAkdA-0007jI-LR
	for emacs-orgmode@gnu.org; Thu, 22 Mar 2012 12:12:54 -0400
In-Reply-To: <878vit2cnw.fsf@thinkpad.tsdh.de> (Tassilo Horn's message of
	"Thu, 22 Mar 2012 10:44:03 +0100")
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/emacs-orgmode>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=subscribe>
Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
To: Tassilo Horn <tassilo@member.fsf.org>
Cc: emacs-orgmode@gnu.org, emacs-devel@gnu.org

Tassilo Horn <tassilo@member.fsf.org> writes:

>>> on irc some user reported that the current org-mode version listed
>>> in `M-x package-list-packages' cannot be downloaded anymore.  It
>>> seems that this is caused by some cronjob that stopped running on
>>> February, 14th.
>>
>> Looks like some kind of firewall snafu when the machine moved to the
>> new location last month.  On it.

The FSF sysadmin has now fixed it.  Thanks for the heads up.