On Fri, 30 Oct 2020, Kurt Mosiejczuk wrote:
> Ping. I've added py-packaging to TEST_DEPENDS to fix the issue daniel@ saw.
> (I don't see it because the tests using py-packaging don't run when using
> PORTS_PRIVSEP).
>
> So this went throught a sparc64 bulk without issues.
>
> ok?
>
seems li
On Fri, Oct 23, 2020 at 01:20:09PM -0400, Kurt Mosiejczuk wrote:
> On Fri, Oct 23, 2020 at 12:41:49PM -0400, Daniel Dickman wrote:
> > I tried running "make test" under both of the python2 and python3 flavors.
> > Neither worked, but very possible could be something local on my end as my
> > tree
On Fri, Oct 23, 2020 at 12:41:49PM -0400, Daniel Dickman wrote:
> I tried running "make test" under both of the python2 and python3 flavors.
> Neither worked, but very possible could be something local on my end as my
> tree has lots of local changes.
> Under python2 it said it needed py-futures
I tried running "make test" under both of the python2 and python3 flavors.
Neither worked, but very possible could be something local on my end as my
tree has lots of local changes.
Under python2 it said it needed py-futures so I put this into the Makefile
.if !${FLAVOR:Mpython3}
TEST_DEPEN
This updates py-setuptools to the last version that still supports python
2.7, 44.1.1.
I've run a bulk build on my sparc64 test cluster and didn't have any failures
due to the update. That was a shorter build though because of the
spidermonkey update, so I wouldn't be opposed if someone wants to
On Thu, Oct 06, 2016 at 10:47:29PM +0200, frantisek holop wrote:
> Daniel Jakots, 30 Sep 2016 08:52:
> > Which ports did you test, and how did you test them?
>
> well..
>
> i tested _a_ setuptools inside pyvenv-3.5
> pip (8.1.1)
> setuptools (20.10.1)
>
> then another one inside virtualenv:
> pi
Daniel Jakots, 30 Sep 2016 08:52:
> Which ports did you test, and how did you test them?
well..
i tested _a_ setuptools inside pyvenv-3.5
pip (8.1.1)
setuptools (20.10.1)
then another one inside virtualenv:
pip (8.1.2)
setuptools (28.2.0)
and as py-virtualenv-15.0.3 is supposed to come with
set
On Thu, 29 Sep 2016 23:44:01 +0200, frantisek holop
wrote:
> please test and commit.
>
> -f
Which ports did you test, and how did you test them?
please test and commit.
-f
--
no generalization is wholly true, not even this one.
Index: Makefile
===
RCS file: /cvs/ports/devel/py-setuptools/Makefile,v
retrieving revision 1.28
diff -u -p -r1.28 Makefile
--- Makefile29 Sep 201
On Fri, Sep 20, 2013 at 9:38 AM, Remi Pointel wrote:
> On Thu, 19 Sep 2013 21:42:25 +0100
> Edd Barrett wrote:
>> Hi,
>>
>> I noticed that our py-setuptools ports is quite lagging. The following
>> diff brings it up to date.
>>
>> Presumably setuptools is mostly used for building/installing pytho
On Thu, 19 Sep 2013 21:42:25 +0100
Edd Barrett wrote:
> Hi,
>
> I noticed that our py-setuptools ports is quite lagging. The following
> diff brings it up to date.
>
> Presumably setuptools is mostly used for building/installing python
> packages, so to test I have checked that every port depend
Hi,
I noticed that our py-setuptools ports is quite lagging. The following
diff brings it up to date.
Presumably setuptools is mostly used for building/installing python
packages, so to test I have checked that every port depending upon this
still packages. I did this on a fresh install using a S
12 matches
Mail list logo
