Gentoo Package - Include Failure of CAF

Zeek
1

Good morning,

The CAF ebuild looks good to me. The deprecation warnings arise because
of the combination of Broker 0.4 with CAF >= 0.14.

This was a misunderstanding; I meant the internal deprecation warnings
that arise when compiling CAF 0.14.4. CAF's 0.13.2 build.log is
completely devoid of that.

If you want a stable
release, you would have to use the following combination:

    Bro 2.4.1 + Broker 0.4 + CAF 0.13.2

I've created a 0.13.2 CAF ebuild and something's going wrong with
Swig/Python. See attached bro-swig-python-failure.log.

And as mentioned in an earlier email, for the next release Bro 2.5, it
would be Broker 0.5 and CAF 0.15.

I don't have a gentoo installation handy so that I could further debug
the issue with the symlinked .sh file. Would you mind giving us a bit
more insight in to that error?

Sure. It's an automated QA warning by portage:
Symbolic link /usr/share/broctl/scripts/broctl-config.sh points to
/var/spool/bro/broctl-config.sh which does not exist.

The install phase is listed in attached bro-warning.log. The QA warning
is at the very end. Please ignore the warnings in the middle; they are
coming from a bug in portage.

With kind regards,
Markus

bro-swig-python-failure.log.xz (6.41 KB)

bro-warning.log.xz (8.17 KB)

2

This was a misunderstanding; I meant the internal deprecation warnings
that arise when compiling CAF 0.14.4. CAF's 0.13.2 build.log is
completely devoid of that.

Ah, okay. Thanks for clarifying.

See attached bro-swig-python-failure.log.
[..]
The install phase is listed in attached bro-warning.log.

I cannot uncompress what you have attached. Various combinations of tar
switches seem to fail [1]. Feel free to send the relevant part of the
log file inline. As long as we're not talking multiple MBs, you can also
send plain text attachments to the list.

    Matthias

[1] xkcd: tar

3

Ah.. this has come up before. The target of the symlink is auto created the first time bro runs.

https://bro-tracker.atlassian.net/browse/BIT-1437 is somewhat related..

Homebrew ran into this as well, they fixed it by moving spool and logs under var/ which actually makes more sense.

https://github.com/Homebrew/homebrew/commit/3591e099860b00a57b7f9f67ef69d5e6eac0fa47

https://github.com/Homebrew/homebrew/pull/42179

4

Hello Matthias,

See attached bro-swig-python-failure.log.
[..]
The install phase is listed in attached bro-warning.log.

I cannot uncompress what you have attached. Various combinations of tar
switches seem to fail [1]. Feel free to send the relevant part of the
log file inline. As long as we're not talking multiple MBs, you can also
send plain text attachments to the list.

    Matthias

[1] xkcd: tar

The attached files are compressed with xz; `xz -d` should do the trick
if installed. Tar can only handle files which are additionally tar'd.
Mails to the list are capped at 100KBytes (including the e-mail itself),
which is easily exceeded with MIME encoded stuff. That's why I
compressed them.

With kind regards,
tomboy64

5

Hello again,

I managed to resolve most issues with Bro and submitted the .ebuild via
PR. If someone would like to review and comment on it, feel free to do so.
https://github.com/gentoo/gentoo/pull/1069/

Otherwise, I'm positive it will hit the tree within a week or so.

With kind regards,
tomboy64