Date: Wed, 6 Jan 2016 00:54:08 +1100 From: Kubilay Kocak <koobs@FreeBSD.org> To: Graham Menhennitt <graham@menhennitt.com.au>, freebsd-ports@freebsd.org Cc: Ruslan Mahmatkhanov <rm@freebsd.org> Subject: Re: portupgrade fails possibly due to py27-asn1 rename to py-pyasn1 Message-ID: <568BCB00.4040202@FreeBSD.org> In-Reply-To: <568BAE94.30304@menhennitt.com.au> References: <568BAE94.30304@menhennitt.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
On 5/01/2016 10:52 PM, Graham Menhennitt wrote: > Hi all, > > I updated my ports collection the other day and ran portupgrade. It > fails on the devel/py-pyasn1 port with the error: > > ===> Installing for py27-pyasn1-0.1.9 > ===> py27-pyasn1-0.1.9 depends on package: py27-setuptools27>0 - found > ===> py27-pyasn1-0.1.9 depends on file: /usr/local/bin/python2.7 - found > ===> Checking if py27-pyasn1 already installed > ===> Registering installation for py27-pyasn1-0.1.9 as automatic > Installing py27-pyasn1-0.1.9... > pkg-static: py27-pyasn1-0.1.9 conflicts with py27-asn1-0.1.8,1 (installs > files into the same place). Problematic file: > /usr/local/lib/python2.7/site-packages/pyasn1/__init__.py > *** Error code 70 > > Stop. > > I suspect it's because this port was recently renamed from > devel/py27-asn1 (see > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204567). I can't see > any message in UPDATING that's relevant. > > Any clues please? > > Thanks, > Graham Had their been an UPDATING entry, it would have said please delete py-asn, then reinstall py-pyasn. At least portmaster users would have been affected by a move like this I believe, not sure about portupgrade. I was under the impression it handled moves OK. CC'ing committer. Thanks for letting us know Graham
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?568BCB00.4040202>