Re: svn commit: r456182 - in head/devel: . py-bullet3 py-bullet3/files

2017-12-15 Thread Kubilay Kocak
On 13/12/2017 6:13 am, Yuri Victorovich wrote:
> Author: yuri
> Date: Tue Dec 12 19:13:30 2017
> New Revision: 456182
> URL: https://svnweb.freebsd.org/changeset/ports/456182
> 
> Log:
>   New port: devel/py-bullet3: Python version of 3D collision detection 
> library Bullet
>   
>   Approved by:tcberner (mentor)



> +# $FreeBSD$
> +
> +PORTNAME=bullet3
> +DISTVERSION= 2.87
> +CATEGORIES=  devel
> +PKGNAMEPREFIX=   ${PYTHON_PKGNAMEPREFIX}
> +
> +MAINTAINER=  y...@freebsd.org
> +COMMENT= Python version of 3D collision detection library Bullet
> +
> +LICENSE= ZLIB
> +LICENSE_FILE=${WRKSRC}/LICENSE.txt
> +
> +USES=compiler:c++11-lang localbase python
> +USE_GITHUB=  yes
> +GH_ACCOUNT=  bulletphysics
> +USE_PYTHON=  autoplist distutils
> +USE_GL=  gl glew

Hi Yuri,

This appears to be 'pybullet' on PyPI with version 1.7.5 (released
yesterday)

https://pypi.python.org/pypi/pybullet/1.7.5

Github tags do not appear to match.

If it is pybullet, and there is no compelling reason not to use the
registered name/versioning, please rename to the official/registered
name and version. This will require a PORTEPOCH bump

It's probably worth checking what the 'internal version' of the package
is before deciding that the git tags are more or less canonical.

For all intents and purposes, users/programs will depend on (*_requires)
pybullet by the pybullet PyPI name, and by that internal version.


./koobs
___
freebsd-python@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-python
To unsubscribe, send any mail to "freebsd-python-unsubscr...@freebsd.org"


Re: new portmaster fails to build devel/py-libzfs@py36 because of failing cython

2017-12-15 Thread Kubilay Kocak
On 15/12/2017 8:50 pm, Johan Hendriks wrote:
> Hello all.

Hi Johan

> First of all thank you for the update of portmaster, much appreciated.
> 
> When i am updating my ports, portmaster fails with the following error.
> 
> > Compressing man pages (compress-man)
> ===>>> Starting check for runtime dependencies
> ===>>> Gathering dependency list for lang/cython@py36 from ports
> ===>>> Dependency check complete for lang/cython@py36
> 
> ===>>> devel/py-libzfs@py36 1/10 >> lang/cython@py36 (1/1)
> 
> ===>  Installing for py36-cython-0.26
> ===>  Checking if py36-cython already installed
> ===>   Registering installation for py36-cython-0.26 as automatic
> Installing py36-cython-0.26...
> pkg-static: py36-cython-0.26 conflicts with cython3-0.26 (installs files

notice the reference to cython3 here ---^

lang/cython and lang/cython3 use to both exist, one for python2, the
other for python3.

lang/cython3 was recently deleted, since lang/cython now supports
multiple concurrent installations with different python versions.

pkg delete cython3, then go again.

Let us know how it goes

> into the same place).  Problematic file: /usr/local/bin/cygdb-3.6
> *** Error code 70
> 
> Stop.
> make: stopped in /usr/ports/lang/cython
> 
> ===>>> Installation of py36-cython-0.26 (lang/cython@py36) failed
> ===>>> Aborting update
> 
> ===>>> Update for lang/cython@py36 failed
> ===>>> Aborting update
> 
> ===>>> Update for devel/py-libzfs@py36 failed
> ===>>> Aborting update
> 
> 
> Is there someting i can try or do?




> regards
> 
> Johan
> 

___
freebsd-python@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-python
To unsubscribe, send any mail to "freebsd-python-unsubscr...@freebsd.org"


[Bug 220214] Try to handle man files for USE_PYTHON=concurrent

2017-12-15 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220214

--- Comment #7 from Fukang Chen  ---
Thanks mat@ and antoine@ :)

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-python@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-python
To unsubscribe, send any mail to "freebsd-python-unsubscr...@freebsd.org"


Re: new portmaster fails to build devel/py-libzfs@py36 because of failing cython

2017-12-15 Thread Stefan Esser
Am 15.12.17 um 11:21 schrieb Kubilay Kocak:
> On 15/12/2017 8:50 pm, Johan Hendriks wrote:
>> Hello all.
> 
> Hi Johan
> 
>> First of all thank you for the update of portmaster, much appreciated.
>>
>> When i am updating my ports, portmaster fails with the following error.
>>
>> > Compressing man pages (compress-man)
>> ===>>> Starting check for runtime dependencies
>> ===>>> Gathering dependency list for lang/cython@py36 from ports
>> ===>>> Dependency check complete for lang/cython@py36
>>
>> ===>>> devel/py-libzfs@py36 1/10 >> lang/cython@py36 (1/1)
>>
>> ===>  Installing for py36-cython-0.26
>> ===>  Checking if py36-cython already installed
>> ===>   Registering installation for py36-cython-0.26 as automatic
>> Installing py36-cython-0.26...
>> pkg-static: py36-cython-0.26 conflicts with cython3-0.26 (installs files
> 
> notice the reference to cython3 here ---^
> 
> lang/cython and lang/cython3 use to both exist, one for python2, the
> other for python3.
> 
> lang/cython3 was recently deleted, since lang/cython now supports
> multiple concurrent installations with different python versions.
> 
> pkg delete cython3, then go again.
> 
> Let us know how it goes

Well, actually portmaster is expected to deal with that conversion of the
cython3 port.

I have tested the upgrade of individual ports and of all ports that are
either back-level or where the ORIGIN changed (as in the case of this
particular port).

Hmmm, now I see what's the problem: The package name seems to have been
changed during the conversion to a flavored port (from "cython3-0.26.tbz"
to "py36-cython-0.26.tar.bz"). This is not typical of ports that use
flavors now, in general they generate packages under the same name as the
non-flavored port did.

I have to see, whether I can easily detect this case - the current logic
that distinguishes between fresh installs and re-installs does not see
that the old version needs to be deleted before installing the new one.

For now the advice to manually delete the cython3 port is right and will
let you install the new version.

Regards, STefan
___
freebsd-python@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-python
To unsubscribe, send any mail to "freebsd-python-unsubscr...@freebsd.org"


[Bug 224324] lang/python* fails to install for wrongfully requiring yp/nis

2017-12-15 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224324

Chris Hutchinson  changed:

   What|Removed |Added

 Status|New |Closed
 Resolution|--- |FIXED

--- Comment #5 from Chris Hutchinson  ---
(In reply to Chris Hutchinson from comment #4)
> (In reply to w.schwarzenfeld from comment #3)
> > Chris you missunderstood my post.
> > 
> > .if !exists(/usr/bin/ypcat) || defined(WITHOUT_NIS)
> >  @${REINPLACE_CMD} -e 's/disabled_module_list =[^]]*/&, "nis"/' \
> >  ${WRKSRC}/setup.py
> > .endif
> > 
> > is part of the existing python Makefile.
> > 
> > My first attempt was to comment out the lines with .if and .endif (but this
> > did not work).
> > 
> > Later I found the simpler way with WITHOUT_NIS=yes.
> 
> Sigh... it's been a l-o-o-n-g tough day for me, I'm afraid.
> Now taking a closer look. I can see what you mean.
> Sorry. :(
> 
> Thank you again, Walter, for helping me out. :-)
> 
> --Chris

OK I just realized that I forgot to run make delete-old
after completing the instllworld. Which left the old copies.
This may have contributed to the cause of this. As such, I'm
going to close this pr(1). If I find later that this is still
an issue, I'll just re-open this.

Thanks again, for all your time, and help on this!

--Chris

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-python@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-python
To unsubscribe, send any mail to "freebsd-python-unsubscr...@freebsd.org"


Re: new portmaster fails to build devel/py-libzfs@py36 because of failing cython

2017-12-15 Thread Stefan Esser
Am 15.12.17 um 14:25 schrieb Stefan Esser> Hmmm, now I see what's the problem:
The package name seems to have been
> changed during the conversion to a flavored port (from "cython3-0.26.tbz"
> to "py36-cython-0.26.tar.bz"). This is not typical of ports that use
> flavors now, in general they generate packages under the same name as the
> non-flavored port did.
> 
> I have to see, whether I can easily detect this case - the current logic
> that distinguishes between fresh installs and re-installs does not see
> that the old version needs to be deleted before installing the new one.
> 
> For now the advice to manually delete the cython3 port is right and will
> let you install the new version.

I'm sorry, but fixing this problem will take quite some effort ...

The problem is, that portmaster operates in phases and recursively
invokes itself with an always smaller set of options. While knows
that the port origin has moved in one invocation, it then goes on
and just calls itself to build and install with only the new origin
(in this case "lang/cython@py36").

It is not possible to derive the old package name from that information,
portmaster must assume, that the package name (sans version) did not
change, it can then lookup the nane of the package to be replaced in
the package DB. But in the case of this port, the origin changed and
the package name changed at the same time, and I'd need to have at
least one of these parameters unchanged to lookup the old package name
to de-install it before installing the new version.

I have plans to refactor portmaster and completely rewrite the logic
that builds and installs packages, but this is a major undertaking and
earlier maintainers have given up after trying.

So please accept that it may be necessary to manually remove a package
in case both port directory (origin) and package name change at the
same time. All information is there at a point, but the structure of
the program does not allow to easily access it when actually needed.

Regards, STefan
___
freebsd-python@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-python
To unsubscribe, send any mail to "freebsd-python-unsubscr...@freebsd.org"