Package Details: zeek 7.0.3-1

Git Clone URL: https://aur.archlinux.org/zeek.git (read-only, click to copy)
Package Base: zeek
Description: A network analysis framework
Upstream URL: https://zeek.org
Licenses: BSD
Submitter: synnick
Maintainer: dllcoolj
Last Packager: dllcoolj
Votes: 5
Popularity: 0.000000
First Submitted: 2019-06-04 11:57 (UTC)
Last Updated: 2024-10-15 01:15 (UTC)

Latest Comments

1 2 3 Next › Last »

cbhihe commented on 2024-11-02 21:37 (UTC) (edited on 2024-11-02 21:38 (UTC) by cbhihe)

@dllcoolj : Thank you, that did it.
Testing passed with flying colors, while building CXX objects for the first time was very slow.

The following warnings and loud complaints popped up multiple times during the build process:

  • "scheduled_actor.cpp" and "middleman.cpp" both raised warning during build.
  • for ( const auto& n : visitor::range(visitor::PreOrder(), _root.get(), {}) ) {...}
  • cc1: warning: command-line option ‘-Wno-changes-meaning’ is valid for C++/ObjC++ but not for C
  • zeek/src/zeek-7.0.3/auxil/spicy/hilti/toolchain/src/compiler/optimizer.cc:92:10: warning: ‘virtual void hilti::OptimizerVisitor::operator()(hilti::declaration::Module)’ was hidden [-Woverloaded-virtual=]
    92 | void operator()(declaration::Module     n) final { _current_module = n; }

Will test blocking various packets using a zeek script with ufw tomorrow.

dllcoolj commented on 2024-11-02 00:30 (UTC)

@cbhihe, gpg key for zeek is available here.

After downloading the file, you can import the key via:

gpg --import 962FD2187ED5A1DD82FC478A33F15EAEF8CB8019.asc

cbhihe commented on 2024-11-01 19:01 (UTC) (edited on 2024-11-01 19:03 (UTC) by cbhihe)

Despite passing on the sha256sums and b2sums tests, the package won't build because of a PGP signature issue for the zeek-7-0-3 tarball.

...
==> Verifying source file signatures with gpg...
zeek-7.0.3.tar.gz ... FAILED (unknown public key C68B494DF56ACC7E)
==> ERROR: One or more PGP signatures could not be verified!
==> Removing installed dependencies
...

This is blocking. Can the PGP public key be updated somehow ? Tx.

<deleted-account> commented on 2023-07-15 20:14 (UTC)

Bumped to 6.0.0 LTS version of Zeek. I'll be uploading a -git version later this week for those interested in bleed edge options.

enemyleft commented on 2022-09-16 21:08 (UTC)

Hi, Looks like the patch "0001-Fix-default-build-with-disable-cpp-tests.patch" was already applied to the source in the latest version (5.0.1)? - I am getting an error that the patch was already applied. When I skip the patch in prepare() it works.

bennyboersma commented on 2022-05-04 22:05 (UTC)

Hi,

I cannot seem to find the configuration files like node.cfg, networks.cfg and zeekctl.cfg when using this package. Can someone point me in the right direction?

boogy commented on 2020-09-17 11:11 (UTC)

You need to change the path to the patch file as it's not installing due to a wrong path.

Replace ../../ with ../patchfile.diff

Best, Boogy

synnick commented on 2020-05-14 12:46 (UTC)

I've rolled the version back to 3.0.6 due to compilation errors encountered on an up to date arch system and gcc 10.1.0.

https://github.com/zeek/zeek/issues/970

It's possible a 3.1.x will address the issue.

synnick commented on 2020-05-14 09:04 (UTC)

Hi Erik, Pierre

Ok, I accept the arguments. I've changed the prefix to /usr, removed the (incorrect) peg to git to prefer 3.1.3 and disabled what I could of optional pieces of the build.

The package now unpacks its ~2000 files into the following directories:

  • /usr/bin/ (9 binaries 3 soft-links)
  • /usr/include/<binpac, broker, caf, paraglob, zeek>
  • /usr/lib/zeek <- libbroker and libcaf are here
  • /usr/share/man
  • /usr/share/zeek <- .zeek scripts

eschwartz commented on 2020-05-13 20:57 (UTC)

Please convert this package to build from the latest stable release, and optionally create a second package named zeek-git which builds the latest development version from git master.

P.S. Upstream being strange and installing outside of /usr isn't a good reason to do so ourselves, furthermore, ignore their OBS package and look at the project README which doesn't list any --prefix to use.

P.P.S. Arch also does not do gratuitous split packaging, while debian as a matter of policy does. Therefore certainly don't emulate upstream's respect for debian packaging standards in their debian package by introducing debian packaging standards to archlinux.

1 2 3 Next › Last »