From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark H Weaver Subject: Re: [PATCH 1/1] gnu: python-libxml2: Don't use as replacement for libxml2. Date: Wed, 25 May 2016 13:55:56 -0400 Message-ID: <8760u2vx77.fsf@netris.org> References: <62ac43add157952dca3a1a478b774b65d859b31c.1464146347.git.leo@famulari.name> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:53939) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1b5d3h-0003tK-Ts for guix-devel@gnu.org; Wed, 25 May 2016 13:57:30 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1b5d3d-0000y9-1j for guix-devel@gnu.org; Wed, 25 May 2016 13:57:28 -0400 Received: from world.peace.net ([50.252.239.5]:34300) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1b5d3c-0000y1-UB for guix-devel@gnu.org; Wed, 25 May 2016 13:57:24 -0400 In-Reply-To: <62ac43add157952dca3a1a478b774b65d859b31c.1464146347.git.leo@famulari.name> (Leo Famulari's message of "Tue, 24 May 2016 23:24:20 -0400") List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Leo Famulari Cc: guix-devel@gnu.org Hi, Leo Famulari writes: > This is a followup to commit 493e9a5a8f613764cfa396c33ee6cb381b0dbbef. > > * gnu/packages/xml.scm (python-libxml2, python2-libxml2)[replacement]: > New field. > --- > gnu/packages/xml.scm | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/gnu/packages/xml.scm b/gnu/packages/xml.scm > index 96bb8b7..782e356 100644 > --- a/gnu/packages/xml.scm > +++ b/gnu/packages/xml.scm > @@ -115,6 +115,7 @@ project (but it is usable outside of the Gnome platform).") > (define-public python-libxml2 > (package (inherit libxml2) > (name "python-libxml2") > + (replacement #f) > (build-system python-build-system) > (arguments > `(;; XXX: Tests are specified in 'Makefile.am', but not in 'setup.py'. I noticed the same problem, and pushed the same fix, before seeing this message. Thanks anyway! Mark