Control: tags -1 pending
On 1 December 2016 at 22:52, Sascha Steinbiss wrote:
>
> Done, see
> https://anonscm.debian.org/cgit/users/satta/suricata.git/log/?h=hyperscan
>
Ok, thanks Sascha.
Just pushed the patch to the unstable-next branch of pkg-suricata git repo :-)
Hi Arturo,
[…]
>> Beware that your current branch contains a lot of changes we don't
>> need (ie, cleanups of your own commits).
>> Please, push only the changes we are talking about (may require you to
>> manually merge some commits before pushing to pkg-suricata)
>> If you want, I can myself mig
Hi Arturo,
>> Yes, I see your point and agree that having 3.2 in testing in time for
>> the freeze is a priority. What do you think about the following course
>> of action: get 3.2 into testing now, and after the (soft? full?) stretch
>> freeze we upload a split-hyperscan package for the version t
On 1 December 2016 at 17:13, Sascha Steinbiss wrote:
>
> Yes, I see your point and agree that having 3.2 in testing in time for
> the freeze is a priority. What do you think about the following course
> of action: get 3.2 into testing now, and after the (soft? full?) stretch
> freeze we upload a s
Hi Arturo,
thanks for your comments.
[...]
>> Done. Please see my 'hyperscan-with-alternatives' branch [1] for a
>> version using alternatives.
>
> Ok.
>
> I think this is the way to go, thanks Sascha.
Sure, no problem.
> One more thing: do you think it's time for us to introduce the change
>
On 30 November 2016 at 18:28, Sascha Steinbiss wrote:
> Hi Arturo,
>
> [...]
>> I think the alternatives method discussed at debian-devel seems like
>> the way to go.
>>
>> @Sascha, would you handle the change or should I work on it?
>
> Done. Please see my 'hyperscan-with-alternatives' branch [1]
Hi Arturo,
[...]
> I think the alternatives method discussed at debian-devel seems like
> the way to go.
>
> @Sascha, would you handle the change or should I work on it?
Done. Please see my 'hyperscan-with-alternatives' branch [1] for a
version using alternatives. I'm now installing
'/usr/bin/su
Hi Arturo,
[...]
>>> Just posted to debian-devel to give a bit of visibility to our issue.
>>> I, as well, would like to get a bit of feedback from other fellow
>>> developers to know if there is a better approach.
>>
>> Great, many thanks for this. Reading the post I'm not sure there may
>> have
On 29 November 2016 at 15:13, Sascha Steinbiss wrote:
> Hi Arturo,
>
> [...]
>>> I would be curious to learn what the maintainers' and community thoughts
>>> are,
>>> and would appreciate any comments you might have.
>>>
>>
>> Just posted to debian-devel to give a bit of visibility to our issue.
Hi Arturo,
[...]
>> I would be curious to learn what the maintainers' and community thoughts are,
>> and would appreciate any comments you might have.
>>
>
> Just posted to debian-devel to give a bit of visibility to our issue.
> I, as well, would like to get a bit of feedback from other fellow
>
On 28 November 2016 at 17:30, Sascha Steinbiss wrote:
>
> I spent some time last week to assess how much effort it would be to enable
> Hyperscan support for Debian's suricata packages. Robert Haist has been so
> kind
> to provide a package for Hyperscan, available on the currently supported
> ar
Package: suricata
Version: 3.1.3-3
Severity: wishlist
Dear Suricata maintainers,
I spent some time last week to assess how much effort it would be to enable
Hyperscan support for Debian's suricata packages. Robert Haist has been so kind
to provide a package for Hyperscan, available on the current
12 matches
Mail list logo
