From mboxrd@z Thu Jan  1 00:00:00 1970
From: Leo Famulari <leo@famulari.name>
Subject: Re: [PATCH] gnu: beets: Update to 1.3.19.
Date: Fri, 29 Jul 2016 19:24:20 -0400
Message-ID: <20160729232420.GA16663@jasmine>
References: <1469831979.401650.680828161.4A5CCB9D@webmail.messagingengine.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Return-path: <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:56958)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <leo@famulari.name>) id 1bTH8t-0000TF-Uz
	for guix-devel@gnu.org; Fri, 29 Jul 2016 19:24:36 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <leo@famulari.name>) id 1bTH8p-0004Kd-L2
	for guix-devel@gnu.org; Fri, 29 Jul 2016 19:24:34 -0400
Received: from out5-smtp.messagingengine.com ([66.111.4.29]:59395)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <leo@famulari.name>) id 1bTH8n-0004K4-Bx
	for guix-devel@gnu.org; Fri, 29 Jul 2016 19:24:31 -0400
Content-Disposition: inline
In-Reply-To: <1469831979.401650.680828161.4A5CCB9D@webmail.messagingengine.com>
List-Id: "Development of GNU Guix and the GNU System distribution."
	<guix-devel.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/guix-devel/>
List-Post: <mailto:guix-devel@gnu.org>
List-Help: <mailto:guix-devel-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=subscribe>
Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org
Sender: "Guix-devel" <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
To: Alex Griffin <a@ajgrf.com>
Cc: guix-devel@gnu.org

On Fri, Jul 29, 2016 at 05:39:39PM -0500, Alex Griffin wrote:
> This patch just updates beets to 1.3.19.

Awesome, thank you for paying attention :)

> With the new pypi URLs, are we updating the long hash portion? I did in
> this patch, but it seemed to work either way.

I changed it to use pypi-uri, and pushed as 23319ed674. The "long hash" URLs
were a temporary workaround when PyPi changed their URL schema.

> (I'm also working on a few more patches to enable more beets plugins.
> They'll probably be ready sometime this weekend.)

Doubly awesome!

By the way, Beets says that the next version will be compatible with
Python 3:
https://twitter.com/b33ts/status/746871072436289537

When that release comes, let's take the opportunity to update Beets's
entire dependency graph.