On 2019/09/15 07:29, Klemens Nanni wrote:
> CVSROOT:      /cvs
> Module name:  ports
> Changes by:   k...@cvs.openbsd.org    2019/09/15 07:29:50
> 
> Modified files:
>       devel/angr     : Makefile.inc 
>       devel/angr/py-ailment: distinfo 
>       devel/angr/py-ailment/pkg: PLIST 
>       devel/angr/py-angr: Makefile distinfo 
>       devel/angr/py-angr/patches: 
>                                   
> patch-angr_knowledge_plugins_functions_function_py 
>                                   patch-setup_py 
>       devel/angr/py-angr/pkg: PLIST 
>       devel/angr/py-archinfo: distinfo 
>       devel/angr/py-claripy: distinfo 
>       devel/angr/py-claripy/pkg: PLIST 
>       devel/angr/py-cle: distinfo 
>       devel/angr/py-cle/pkg: PLIST 
>       devel/angr/py-pyvex: distinfo 
>       security/angrop: Makefile distinfo 
> Removed files:
>       devel/angr/py-cle/patches: patch-setup_py 
> 
> Log message:
> Update angr to 8.19.7.25
> 
> Mostly just bugfixes;  there is no changelog, so please have a look at
> https://github.com/angr/angr/commits/master/
> 
> "Go ahead" jasper
> 

I had a weird error in my i386 bulk with this, py-ailment built a package but
reported as failed in dpb, tail of the log looks like this:

-----------------
running install_scripts
===>  Building package for py3-ailment-8.19.7.25
Create /mnt/packages/i386/all/py3-ailment-8.19.7.25.tgz
Creating package py3-ailment-8.19.7.25
Link to /mnt/packages/i386/ftp/py3-ailment-8.19.7.25.tgz                       
>>> Running clean in devel/angr/py-ailment at 1569586230
===> devel/angr/py-ailment
===>  Cleaning for py3-ailment-8.19.7.25
>>> Building on i386-3 under devel/angr/py-ailment
         FULLPKGNAME = stub_name
>>> Running build in devel/angr/py-ailment at 1569634549
===> devel/angr/py-ailment
===> py3-ailment-8.19.7.25 depends on: python->=3.7,<3.8 - not found
Dependency check failed
*** Error 1 in devel/angr/py-ailment 
(/usr/ports/infrastructure/mk/bsd.port.mk:2131 
'/pobj/py-ailment-8.19.7.25/.dep-lang-python-3.7')
-----------------

I haven't seen it before and don't see anything in the commit that would
have triggered this, but I see that devel/angr/vex is ONLY_FOR_ARCHS=amd64,
and most of the other ports have a RUN_DEPENDS on this - can we avoid the
chance of build noise and avoid having an uninstallable package by marking
the dependent ports as amd64-only as well? i.e. py-ailment, py-angr,
py-cle, py-pyvex, security/angrop.

Alternatively if the others (py-z3-solver, py-archinfo, py-claripy) are
not really useful without vex/py-angr/etc we could just set ONLY_FOR_ARCHS
in Makefile.inc and security/angrop.

Reply via email to