From owner-svn-ports-all@freebsd.org Tue Oct 3 05:27:51 2017 Return-Path: Delivered-To: svn-ports-all@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 51635E31002; Tue, 3 Oct 2017 05:27:51 +0000 (UTC) (envelope-from jbeich@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [96.47.72.132]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 30C4564CBB; Tue, 3 Oct 2017 05:27:51 +0000 (UTC) (envelope-from jbeich@freebsd.org) Received: by freefall.freebsd.org (Postfix, from userid 1354) id 879EB6B1; Tue, 3 Oct 2017 05:27:50 +0000 (UTC) From: Jan Beich To: Marcelo Araujo Cc: araujo@freebsd.org, "svn-ports-head\@freebsd.org" , "svn-ports-all\@freebsd.org" , ports-committers Subject: Re: svn commit: r451109 - in head: . sysutils sysutils/iocage sysutils/py3-iocage References: <201710030241.v932fWjX078115@repo.freebsd.org> <8tgs-khgn-wny@FreeBSD.org> <60bw-iznr-wny@FreeBSD.org> Date: Tue, 03 Oct 2017 07:27:35 +0200 In-Reply-To: (Marcelo Araujo's message of "Tue, 3 Oct 2017 13:17:01 +0800") Message-ID: <8tgs-g5rs-wny@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: svn-ports-all@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: SVN commit messages for the ports tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Oct 2017 05:27:51 -0000 Marcelo Araujo writes: > 2017-10-03 13:11 GMT+08:00 Jan Beich : > >> Marcelo Araujo writes: >> >> > 2017-10-03 12:01 GMT+08:00 Jan Beich : >> > >> >> Marcelo Araujo writes: >> >> >> >> > Author: araujo >> >> > Date: Tue Oct 3 02:41:32 2017 >> >> > New Revision: 451109 >> >> > URL: https://svnweb.freebsd.org/changeset/ports/451109 >> >> > >> >> > Log: >> >> > Rename py3-iocage to iocage as by now we don't have more conflicts >> with >> >> > the old iocage version >> >> >> >> If you mean CONFLICTS = py-iocage-[0-9]* then it never worked as package >> >> comparison failed on underspecificed pyXY- prefix. >> >> >> > >> > We used to have py-iocage, here the CONFLICTS isn't for checking pyXY. >> > >> > sysutils/iocage-devel||2017-04-10|Has expired: Outdated version. Please >> use >> > sysutils/py-iocage instead >> > sysutils/iocage||2017-04-10|Has expired: Outdated version. Please use >> > sysutils/py-iocage instead >> >> What is the CONFLICTS line for then? Try installing sysutils/py-iocage >> then proceed to install sysutils/iocage and notice CONFLICTS doesn't >> abort early but proceeds to install dependencies and iocage itself until >> a file conflict occurs. >> > > We don't have sysutils/py-iocage anymore in the portstree. > sysutils/py-iocage|sysutils/py3-iocage|2017-07-10|Has expired: obsoleted by > sysutils/py3-iocage port using Python 3 instead of Python 2 > > But I can't avoid that maybe some legacy systems might still ran py-iocage. Have you actually tested such a scenario? The CONFLICTS line is currently a nop. Here's how to make it work. $ svn up -qr445458 sysutils/py-iocage $ make install -C sysutils/py-iocage [...] $ make install -C sysutils/iocage ===> py36-iocage-0.9.9.2 conflicts with installed package(s): py27-iocage-0.9.5_1 They install files into the same place. You may want to stop build with Ctrl + C. Index: sysutils/iocage/Makefile =================================================================== --- sysutils/iocage/Makefile (revision 451112) +++ sysutils/iocage/Makefile (working copy) @@ -29,6 +29,6 @@ NO_ARCH= yes USES= python:3.6 USE_PYTHON= autoplist distutils -CONFLICTS= py-iocage-[0-9]* +CONFLICTS= py27-iocage-[0-9]* .include