Date: Wed, 20 Nov 2019 19:02:14 +0100 From: Antoine Brodin <antoine@freebsd.org> To: Dmitry Marakasov <amdmi3@amdmi3.ru> 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: <CAALwa8mOQOcFpiv3faWQC8kN9caAPyz71uqV1CKMeUPdO031WQ@mail.gmail.com> In-Reply-To: <20191120172307.GA24348@hades.panopticon> References: <201911201440.xAKEeWZ7011143@repo.freebsd.org> <20191120172307.GA24348@hades.panopticon>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Nov 20, 2019 at 6:33 PM Dmitry Marakasov <amdmi3@amdmi3.ru> wrote: > > * 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. 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. Antoine
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAALwa8mOQOcFpiv3faWQC8kN9caAPyz71uqV1CKMeUPdO031WQ>