Date: Mon, 13 May 2019 21:13:06 +1000 From: Kubilay Kocak <koobs@FreeBSD.org> To: "Luis Espinoza Jr." <ljejr@hotmail.com>, "freebsd-ports@freebsd.org" <freebsd-ports@freebsd.org> Cc: python <python@FreeBSD.org>, Dan Langille <dvl@freebsd.org> Subject: Re: audio/lv2 and textproc/py-rdflib have py36 vs. py27 conflict Message-ID: <3c24b6f9-ce0c-3137-5ef0-13256fedd2e0@FreeBSD.org> In-Reply-To: <MWHPR02MB27028CD6E937DEEC2C54E725B40F0@MWHPR02MB2702.namprd02.prod.outlook.com> References: <MWHPR02MB27028CD6E937DEEC2C54E725B40F0@MWHPR02MB2702.namprd02.prod.outlook.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 13/05/2019 8:12 pm, Luis Espinoza Jr. wrote: > Hello all. > > > My system is FreeBSD 11.2-RELEASE-p9 AMD64. I update my ports tree with > portsnap and build my ports with portmaster. For several days I have been > trying to resolve a problem updating ffmpeg. > > ffmpeg requires audio/lv2 > lv2 requires textproc/py-rdflib > > According to the data in the Freshports site, lv2 has a runtime dependency > on py36-rdflib but py-rdflib has build- and runtime dependencies on > lang/python27, and its package name is py27-rdflib. Hi Luis, I *think* the latter case (rdflib looking like it depends on python27 at freshports) is an artifact of the port not having been updated since June 2018, which was before the Python default version switch this year, and freshports not having regenerated/refreshed the page/information for the port. > Portmaster emits the following error compiling py-rdflib: > pkg-static: py36-rdflib-4.2.2 conflicts with py27-rdflib-4.2.2 > (installs files into the same place). Problematic file: /usr/local/bin/csv2rdf > *** Error code 70 It's likely the case that you have py27-rdflib installed at the moment, and since the default version of Python has switched to 3.6, it now conflicts. See: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=226634#c10 for the details explanation (it applies to any python package, not just setuptools) What do you currently have set in /etc/make.conf for DEFAULT_VERSIONS ? > > I have checked the UPDATING file and found no answer. Is there some standard > method for dealing with python27 vs. python36 conflicts, or is this a bug in the > lv2 dependencies that must be fixed by the maintainer? Python ports/packages that install things in LOCALBASE/bin should be made concurrent safe, and the py-rdflib isn't. I'll sort that out shortly, which will address the conflict, where only the *default version of the port/package will have the version-suffixless name.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3c24b6f9-ce0c-3137-5ef0-13256fedd2e0>