svn commit: r451109 - in head: . sysutils sysutils/iocage sysutils/py3-iocage

[Marcelo Araujo]

2017-10-03 13:11 GMT+08:00 Jan Beich <jbeich at freebsd.org>:

> Marcelo Araujo <araujobsdport at gmail.com> writes:
>
> > 2017-10-03 12:01 GMT+08:00 Jan Beich <jbeich at freebsd.org>:
> >
> >> Marcelo Araujo <araujo at FreeBSD.org> 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.

Best,
-- 

-- 
Marcelo Araujo            (__)araujo at FreeBSD.org
\\\'',)http://www.FreeBSD.org <http://www.freebsd.org/>   \/  \ ^
Power To Server.         .\. /_)