incorrect dependency registration?

[Dmitry Sivachenko]

On 07 окт. 2014 г., at 13:12, Baptiste Daroussin <bapt at FreeBSD.org> wrote:

> On Tue, Oct 07, 2014 at 01:10:56PM +0400, Dmitry Sivachenko wrote:
>> 
>> On 29 сент. 2014 г., at 12:01, Baptiste Daroussin <bapt at FreeBSD.org> wrote:
>> 
>>> On Mon, Sep 29, 2014 at 11:52:50AM +0400, Dmitry Sivachenko wrote:
>>>> Hello,
>>>> 
>>>> I am using FreeBSD-10/stable and pkg-1.3.8.
>>>> 
>>>> Consider py-dateutil port, it depends on py-six.
>>>> 
>>>> First, I installed py33-dateutil (with py33-six), for python3.
>>>> 
>>>> Now I install py-dateutil for python2.  Upon installation, I get the following waring:
>>>> ===>  Installing for py27-dateutil-2.2
>>>> ===>   py27-dateutil-2.2 depends on package: py27-six>0 - found
>>>> ===>   py27-dateutil-2.2 depends on package: py27-setuptools27>0 - found
>>>> ===>   py27-dateutil-2.2 depends on file: /usr/local/bin/python2.7 - found
>>>> ===>  Checking if py27-dateutil already installed
>>>> ===>   Registering installation for py27-dateutil-2.2
>>>> pkg-static: py27-dateutil-2.2: duplicate dependency listing: py33-six-1.5.2, ignoring
>>>> 
>>>> When I try to deinstall py27-six, I get:
>>>> 
>>>> # pkg delete py27-six
>>>> Checking integrity... done (0 conflicting)
>>>> Deinstallation has been requested for the following 3 packages (of 0 packages in the universe):
>>>> 
>>>> 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)
>>>> 
>>>> The operation will free 1 MB.
>>>> 
>>>> Proceed with deinstalling packages? [y/N]: 
>>>> 
>>>> (it wants to deinstall both versions of py-dateutil).
>>>> 
>>>> Something looks broken here.
>>>> 
>>>> 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.
>>> 
>>> I do not have time for this right now, I'll see in a couple of days, but CCing
>>> parties that should be interested :)
>>> 
>> 
>> 
>> Can you reproduce this or is this a problem on my side?
> 
> Bryan has fixed it iirc, this was a port bug.
> 


What commit do you mean?  I just updated ports tree, installed pkg-1.3.8_3, and I see the same issue.