From owner-freebsd-pkg@FreeBSD.ORG Tue Oct 7 09:11:02 2014 Return-Path: Delivered-To: pkg@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 5F5CA30F; Tue, 7 Oct 2014 09:11:02 +0000 (UTC) Received: from mail-la0-x229.google.com (mail-la0-x229.google.com [IPv6:2a00:1450:4010:c03::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 73319F28; Tue, 7 Oct 2014 09:11:01 +0000 (UTC) Received: by mail-la0-f41.google.com with SMTP id pn19so5994526lab.0 for ; Tue, 07 Oct 2014 02:10:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=DH9aMJFxzTABm6CzICo95MEslkgXUPMYtoT1Jkis/zk=; b=WFj3LiFYPll3DlssoW8CZAoXFswm3zD0SOwyOsJl83iDRMV2ZVW2ylzXigXBvJmTBB /rFUzF/QBIUQr1ZEF00KDglkN2mWd3NcVhezmrvW+vrrCNSz7mz9WuvjV4gm1iD/F2cm 9hsuUYB62UCjkn99OvZGl0Gjs560cg7BGZ4JWvgSIvYot9miGoH65Y6RpeMOUqKufmwv HqgrtlD+MA6MtT8s4K5tCv87l9q34KPkPKYwUeX9zmhIKzkce6QvB90O8AG4KVp3iIFL KIykRw+3adNhTP6R7KsAv9xIw8Awnj4ePH7PZOJnf96mdyujB68nHeo5J38ZFR6utgxN AnUw== X-Received: by 10.152.121.8 with SMTP id lg8mr1679566lab.98.1412673059286; Tue, 07 Oct 2014 02:10:59 -0700 (PDT) Received: from [10.0.1.14] (broadband-5-228-253-252.nationalcablenetworks.ru. [5.228.253.252]) by mx.google.com with ESMTPSA id li3sm6522193lab.25.2014.10.07.02.10.57 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 07 Oct 2014 02:10:58 -0700 (PDT) Sender: Dmitry Sivachenko Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Subject: Re: incorrect dependency registration? From: Dmitry Sivachenko In-Reply-To: <20140929080109.GI40373@ivaldir.etoilebsd.net> Date: Tue, 7 Oct 2014 13:10:56 +0400 Content-Transfer-Encoding: quoted-printable Message-Id: References: <15E556C8-EEB6-4218-93F3-F76BFA2E4F29@FreeBSD.org> <20140929080109.GI40373@ivaldir.etoilebsd.net> To: Baptiste Daroussin X-Mailer: Apple Mail (2.1878.6) Cc: pkg@FreeBSD.org, python@FreeBSD.org X-BeenThere: freebsd-pkg@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Binary package management and package tools discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Oct 2014 09:11:02 -0000 On 29 =D1=81=D0=B5=D0=BD=D1=82. 2014 =D0=B3., at 12:01, Baptiste = Daroussin wrote: > On Mon, Sep 29, 2014 at 11:52:50AM +0400, Dmitry Sivachenko wrote: >> Hello, >>=20 >> I am using FreeBSD-10/stable and pkg-1.3.8. >>=20 >> Consider py-dateutil port, it depends on py-six. >>=20 >> First, I installed py33-dateutil (with py33-six), for python3. >>=20 >> Now I install py-dateutil for python2. Upon installation, I get the = following waring: >> =3D=3D=3D> Installing for py27-dateutil-2.2 >> =3D=3D=3D> py27-dateutil-2.2 depends on package: py27-six>0 - found >> =3D=3D=3D> py27-dateutil-2.2 depends on package: = py27-setuptools27>0 - found >> =3D=3D=3D> py27-dateutil-2.2 depends on file: = /usr/local/bin/python2.7 - found >> =3D=3D=3D> Checking if py27-dateutil already installed >> =3D=3D=3D> Registering installation for py27-dateutil-2.2 >> pkg-static: py27-dateutil-2.2: duplicate dependency listing: = py33-six-1.5.2, ignoring >>=20 >> When I try to deinstall py27-six, I get: >>=20 >> # pkg delete py27-six >> Checking integrity... done (0 conflicting) >> Deinstallation has been requested for the following 3 packages (of 0 = packages in the universe): >>=20 >> Installed packages to be REMOVED: >> py27-six-1.8.0 >> py33-dateutil-2.1_3 (depends on py27-six-1.8.0) >> py27-dateutil-2.2 (depends on py27-six-1.8.0) >>=20 >> The operation will free 1 MB. >>=20 >> Proceed with deinstalling packages? [y/N]:=20 >>=20 >> (it wants to deinstall both versions of py-dateutil). >>=20 >> Something looks broken here. >>=20 >> Some time ago it did not let to install the same port for different = python version, now it is possible but deps registration looks broken. >=20 > I do not have time for this right now, I'll see in a couple of days, = but CCing > parties that should be interested :) >=20 Can you reproduce this or is this a problem on my side? Thanks.=