Re: UPDATE: security/sn0int

2024-05-07 Thread Theo Buehler
Committed, with a few tweaks, thanks. > -REVISION = 6 > +GH_TAGNAME = v0.26.0 > +REVISION = 0 Remove REVISION rather than setting it to 0 > +MAINTAINER = Purple Rain Thanks. > Index: crates.mk I took the liberty of renaming that to crates.inc, as is done in most other rust-based ports.

Re: UPDATE: security/sn0int

2024-05-07 Thread Theo Buehler
On Tue, May 07, 2024 at 10:23:05AM -0600, Purple Rain wrote: > Hello, > > This update sn0int from 0.24.1 to 0.26.0. > > Tested on amd64, works fine. Ok? If you use this, could you ask upstream if they could not update their ring dependency? This would allow using sn0int with better asm on more

Re: update security/sn0int

2020-03-16 Thread kpcyrd
hey! thanks for pointing this out. The project does explicitly enable the `use-pkg-config` feature to enforce dynamic linking, I just forgot to add it to WANTLIB as well. I've attached a new patch. Thanks! On Mon, Mar 16, 2020 at 11:58:54AM +0100, Sebastien Marie wrote: > On Mon, Mar 16, 2020

Re: update security/sn0int

2020-03-16 Thread Sebastien Marie
On Mon, Mar 16, 2020 at 03:49:11AM +, kpcyrd wrote: > hi! > > this patch imports the latest version and drops the patches that have > been upstreamed (patch follows). I will take a look. > Index: Makefile > === > RCS file:

update security/sn0int

2020-03-15 Thread kpcyrd
hi! this patch imports the latest version and drops the patches that have been upstreamed (patch follows). Thanks! Index: Makefile === RCS file: /cvs/ports/security/sn0int/Makefile,v retrieving revision 1.6 diff -u -p -r1.6

Re: update security/sn0int

2019-09-12 Thread Sebastien Marie
On Mon, Sep 09, 2019 at 10:02:51PM +, kpcyrd wrote: > I've tried to track down these issues (unfortunatly I only have an amd64 > testsystem right now): > > ## i386 > > It seems the issue was in typenum and also showed up in librsvg in > debian[1], where it was fixed by cherry-picking a

Re: update security/sn0int

2019-09-09 Thread kpcyrd
I've tried to track down these issues (unfortunatly I only have an amd64 testsystem right now): ## i386 It seems the issue was in typenum and also showed up in librsvg in debian[1], where it was fixed by cherry-picking a patch[2] from upstream. This commit was part of the typenum 1.11.0 release,

Re: update security/sn0int

2019-09-09 Thread Sebastien Marie
On Mon, Sep 09, 2019 at 08:31:35AM +0200, Gonzalo L. Rodriguez wrote: > Hello, > > I have a similar diff, if no one complain I will commit this tomorrow. o/ I am complaining :) First, a general remark: I strongly want that such Rust port to have a maintainer. Else, it means I will have to do

Re: update security/sn0int

2019-09-09 Thread Gonzalo L. Rodriguez
Hello, I have a similar diff, if no one complain I will commit this tomorrow. Thanks Cheers.- On Mon, 09 Sep 2019 at 03:09:51 +, kpcyrd wrote: > Hi, > > this patch imports the latest version and drops the patches that have > been upstreamed in the meantime. > > (long diff follows) > >

update security/sn0int

2019-09-08 Thread kpcyrd
Hi, this patch imports the latest version and drops the patches that have been upstreamed in the meantime. (long diff follows) Thanks! Index: Makefile === RCS file: /cvs/ports/security/sn0int/Makefile,v retrieving revision 1.4