Date: Wed, 20 Nov 2019 21:18:21 +0300 From: Dmitry Marakasov <amdmi3@amdmi3.ru> To: Antoine Brodin <antoine@freebsd.org> Cc: ports-committers <ports-committers@freebsd.org>, svn-ports-all <svn-ports-all@freebsd.org>, svn-ports-head <svn-ports-head@freebsd.org> Subject: Re: svn commit: r518022 - head/devel/py-llfuse Message-ID: <20191120181821.GB24348@hades.panopticon> In-Reply-To: <CAALwa8mOQOcFpiv3faWQC8kN9caAPyz71uqV1CKMeUPdO031WQ@mail.gmail.com> References: <201911201440.xAKEeWZ7011143@repo.freebsd.org> <20191120172307.GA24348@hades.panopticon> <CAALwa8mOQOcFpiv3faWQC8kN9caAPyz71uqV1CKMeUPdO031WQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
* Antoine Brodin (antoine@freebsd.org) wrote: > > > Author: antoine > > > Date: Wed Nov 20 14:40:31 2019 > > > New Revision: 518022 > > > URL: https://svnweb.freebsd.org/changeset/ports/518022 > > > > > > Log: > > > Revert r517286, breaking bulk -a is not covered by portmgr blanket > > > > How exactly and why does specifying the correct python version > > limitation not affecting default python versions, break bulk, and how > > should this be handled? > > This breaks bulk -a with default version of python equal to 3.7 or 3.8 > because of net/s3ql. Isn't it broken in either cases, as the dependency does not support the given python version/flavor? Why does this need to be reverted? > In my opinion the correct way to handle ports that work fine with > python 3.6 but not 3.7 or 3.8 is to mark them BROKEN for these cases. > They may (should?) be fixed upstream or with patches. This seems like a duplication of python:VER we already have. -- Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56 9510 D35A 80DD F9D2 F77D amdmi3@amdmi3.ru ..: https://github.com/AMDmi3
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20191120181821.GB24348>