Re: [update] security/wapiti: update to 3.2.0, new deps

2024-10-30 Thread Kirill A . Korinsky
On Wed, 30 Oct 2024 19:11:03 +0100, Stuart Henderson wrote: > > > I think I would probably drop Remi as maintainer unless there are > objections, the port is pretty outdated as it is, so it's not really > maintained (if he was around more then I'd say wait and check first, > but there's a good c

Re: [update] security/wapiti: update to 3.2.0, new deps

2024-10-30 Thread Stuart Henderson
On 2024/10/30 17:50, Kirill A. Korinsky wrote: > On Wed, 30 Oct 2024 12:40:51 +0100, > Stuart Henderson wrote: > > > > Those are OK sthen with the above changes. The other deps are > > OK sthen as-is. > > > > Thanks, dependencies are imported. > > > I haven't tested wapiti itself yet. Are the de

Re: [update] security/wapiti: update to 3.2.0, new deps

2024-10-30 Thread Klemens Nanni
30.10.2024 19:50, Kirill A. Korinsky пишет: > I just re-tested and I can rebuild it without this block. > > As far as I recall this block / patch was required at begining, but I assume > that I did something wrong and because it was a few months ago I can't > recall it. > > So, here the updated d

Re: [update] security/wapiti: update to 3.2.0, new deps

2024-10-30 Thread Kirill A . Korinsky
On Wed, 30 Oct 2024 12:40:51 +0100, Stuart Henderson wrote: > > Those are OK sthen with the above changes. The other deps are > OK sthen as-is. > Thanks, dependencies are imported. > I haven't tested wapiti itself yet. Are the dep changes (to remove > ==$VERSION) in pyproject.yaml actually neede

Re: [update] security/wapiti: update to 3.2.0, new deps

2024-10-30 Thread Stuart Henderson
On 2024/10/30 10:09, Kirill A. Korinsky wrote: > ports@, > > Here the same archive with deps and updated version for wapiti diff which > includes regenerated PLIST to avoid merge conflicts which was noticed by tb@ Looking at the deps. devel/py-aiocache: - this looks like a better HOMEPAGE https:

Re: [update] security/wapiti: update to 3.2.0, new deps

2024-10-30 Thread Kirill A . Korinsky
ports@, Here the same archive with deps and updated version for wapiti diff which includes regenerated PLIST to avoid merge conflicts which was noticed by tb@ On Wed, 23 Oct 2024 18:05:26 +0200, Kirill A. Korinsky wrote: > > On Sat, 19 Oct 2024 20:56:25 +0200, > Klemens Nanni wrote: > > > > >

Re: [update] security/wapiti: update to 3.2.0, new deps

2024-10-23 Thread Kirill A . Korinsky
On Sat, 19 Oct 2024 20:56:25 +0200, Klemens Nanni wrote: > > >> ports@, Remi, > > Still no maintainer response, I suggest we remove Remi as maintainer. I willing to take care of wapiti and replace Remi if he doesn't interested in it anymore. > >> > >> Here an update of security/wapiti to the l

Re: [update] security/wapiti: update to 3.2.0, new deps

2024-10-19 Thread Klemens Nanni
05.10.2024 00:51, Kirill A. Korinsky пишет: > > ping > > On Thu, 05 Sep 2024 01:25:36 +0200, > Kirill A. Korinsky wrote: >> >> ports@, Remi, Still no maintainer response, I suggest we remove Remi as maintainer. >> >> Here an update of security/wapiti to the last version 3.2.0 from 3.0.1 which

Re: [update] security/wapiti: update to 3.2.0, new deps

2024-10-04 Thread Kirill A . Korinsky
ping On Thu, 05 Sep 2024 01:25:36 +0200, Kirill A. Korinsky wrote: > > ports@, Remi, > > Here an update of security/wapiti to the last version 3.2.0 from 3.0.1 which > was released in May of 2018. > > To this email I've attached new ports: > > - databases/py-aiosqlite > - devel/py-ai

Re: [update] security/wapiti: update to 3.2.0, new deps

2024-09-06 Thread Klemens Nanni
05.09.2024 23:20, Kirill A. Korinsky пишет: > They simple had nuked internalization because it's pain to support: > https://github.com/wapiti-scanner/wapiti/issues/324 > > Anyway, it is a good point and allows to make a 7.6 with working wapiti. > > So, here the diff to fix this issue. I had brifl

Re: [update] security/wapiti: update to 3.2.0, new deps

2024-09-05 Thread Kirill A . Korinsky
On Thu, 05 Sep 2024 21:06:15 +0200, Klemens Nanni wrote: > > > +# Tests installs specified version via netowrk, disable it > > +NO_TEST= Yes > > Doesn't match bsd.port.mk(5) for NO_TEST. > Porters should be able to run tests if they exist; they may enable network > or do not use PORTS

Re: [update] security/wapiti: update to 3.2.0, new deps

2024-09-05 Thread Kirill A . Korinsky
On Thu, 05 Sep 2024 21:06:15 +0200, Klemens Nanni wrote: > > 05.09.2024 02:25, Kirill A. Korinsky пишет: > > ports@, Remi, > > > > Here an update of security/wapiti to the last version 3.2.0 from 3.0.1 which > > was released in May of 2018. > > > > So, time pasts, and it needs new dependencies

Re: [update] security/wapiti: update to 3.2.0, new deps

2024-09-05 Thread Klemens Nanni
05.09.2024 02:25, Kirill A. Korinsky пишет: > ports@, Remi, > > Here an update of security/wapiti to the last version 3.2.0 from 3.0.1 which > was released in May of 2018. > > So, time pasts, and it needs new dependencies which I ported as well. > > Thus, right now wapiti fails as: > > Fi

[update] security/wapiti: update to 3.2.0, new deps

2024-09-04 Thread Kirill A . Korinsky
ports@, Remi, Here an update of security/wapiti to the last version 3.2.0 from 3.0.1 which was released in May of 2018. So, time pasts, and it needs new dependencies which I ported as well. Thus, right now wapiti fails as: File "/usr/local/lib/python3.11/site-packages/wapitiCore/main/wapi