From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Artur Malabarba Newsgroups: gmane.emacs.devel Subject: Re: Async package.el Date: Sun, 12 Apr 2015 02:38:32 +0100 Message-ID: References: <55228FD2.3080501@yandex.ru> <552330A2.1090406@yandex.ru> <55249033.6050301@yandex.ru> <55255129.4030002@yandex.ru> <5525DFA1.5040307@yandex.ru> <552671D0.8020205@yandex.ru> Reply-To: bruce.connor.am@gmail.com NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 X-Trace: ger.gmane.org 1428802809 8510 80.91.229.3 (12 Apr 2015 01:40:09 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 12 Apr 2015 01:40:09 +0000 (UTC) Cc: emacs-devel To: Dmitry Gutov Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Apr 12 03:40:09 2015 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1Yh6sa-0003p8-0k for ged-emacs-devel@m.gmane.org; Sun, 12 Apr 2015 03:40:08 +0200 Original-Received: from localhost ([::1]:44216 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Yh6sY-0005Zh-Od for ged-emacs-devel@m.gmane.org; Sat, 11 Apr 2015 21:40:06 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:49035) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Yh6sL-0005ZG-3x for emacs-devel@gnu.org; Sat, 11 Apr 2015 21:39:53 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Yh6r3-0001tC-KN for emacs-devel@gnu.org; Sat, 11 Apr 2015 21:38:34 -0400 Original-Received: from mail-lb0-x233.google.com ([2a00:1450:4010:c04::233]:33309) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Yh6r3-0001ri-Cn for emacs-devel@gnu.org; Sat, 11 Apr 2015 21:38:33 -0400 Original-Received: by lbbzk7 with SMTP id zk7so36827816lbb.0 for ; Sat, 11 Apr 2015 18:38:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:sender:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=DQHOpuhveU/rIuIQ5v88I5+iH3xXrOV4jzjFXLnDnCo=; b=AqjDN182JdOIg4VEn/i1PT1tCDl6uUyyiRgm3s5Bt2DZaf7i+3XazLjF9c6cqCl9xD OyNfpgdtuJNmlUJsheoySjrXYfXua64n5x9+y2Gz+VR/jOY5B4ZNqxGbSj+pyhSo/94e oTSI+fssD8lQxl7EviaHVxa7ERvDzDLKaZiotP4k0IdjzUmmFo4CxEcveRtnPMx6m7vj y4awQ7ZpcjPRAjQkL7s9Wpt7h0xF9C45EMvE2ckiDC6yg+/+dO6qYJMCyAqGHORRElt4 Z5VnWPohJsCM81+sEppx6hDmiPoHQbuvNeSiqTDDIKZxRV0YUQngl1OtM94kTwHsXqyz zF4w== X-Received: by 10.152.2.105 with SMTP id 9mr5787393lat.16.1428802712496; Sat, 11 Apr 2015 18:38:32 -0700 (PDT) Original-Received: by 10.25.150.131 with HTTP; Sat, 11 Apr 2015 18:38:32 -0700 (PDT) In-Reply-To: <552671D0.8020205@yandex.ru> X-Google-Sender-Auth: Ln8byF5G-CNFQhtn3aYVu21ncHk X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2a00:1450:4010:c04::233 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:185310 Archived-At: 2015-04-09 13:34 GMT+01:00 Dmitry Gutov >> I don't get that bevahiour from emacs -Q, but there was a problem with >> the incompatible table a few days ago. Maybe your elc file is outdated? > > > 'emacs -Q' won't let you reproduce this, because (I think) it won't load > ~/.emacs.d/elpa/archives/melpa/archive-contents during `package-initilize'. > > I've pulled the latest changes, re-bootstrapped Emacs, removed > ~/.emacs.d/elpa/archives, but after restarting Emacs, the problem persists. Found it. The compatibility table was being initialize before the list of built-in packages. Should be fixed now. > Indeed, that should be rare. I don't have a scarier scenario to offer right > now, so maybe we can ignore this downside (but preferably handle the > possibility with care; and not move the "to install" mark to the > now-incompatible package). Yup