[Bro-Dev] Bro nightly packages for .dev and .rpm based distributions
johanna at icir.org
Fri Apr 10 12:57:31 PDT 2015
the bro package on the Opensuse Build Service just moved to its final
location in network:bro. So - the obs interface for is now available at
https://build.opensuse.org/project/show/network:bro and builds for
bro-nightly will be available at
(currently it still is a 404; should hopefully be available within the
next few hours).
The binaries at the old location will no longer be updated.
On Thu, Feb 12, 2015 at 12:53:51PM -0800, Johanna Amann wrote:
> we are considering to provide packages for a number of different
> .deb and .rpm based distributions starting with Bro 2.4, using the
> OpenSuse build service.
> As a first step, I have created a repository that contains nightly Bro
> builds for CentOs, Debian, Fedora, Suse Linux, Scientific Linux,
> Univention as well as Ubuntu.
> At the moment, Bro is installed into /opt/bro and broctl needs root
> permissions to run. Users in the Bro group (which is automatically created
> on installation) should be able to modify configuration files like
> local.bro, or the broctl configuration, and read the log files that Bro
> The package is called bro-nightly which is a metapackage which pulls in
> the sub-packages
> bro-core-nightly, containing only bro without broctl or libbroccoli
> broctl-nightly, containing broctl
> libbroccoli-nightly, containing libbroccoli
> and libbroccoli-devel-nightly, containing the header files for libbroccoli
> The obs interface showing the status and sources is available at
> https://build.opensuse.org/package/show/home:0xxon:bro/bro-nightly and
> downloads are available at
> (locations will change in the future).
> If you add the repositories to your distribution, new nightly builds
> should automatically be installed each time bro is updated.
> Additionally, Bro 2.3.2 packages are available at
> At the moment, this is in an early stage and I would be happy to receive
> any kind of feedback or problems that you encounter when using these
> packages. Please note that the packages have not gone through a lot of
> testing and that you should not use them in a production environment :)
> bro-dev mailing list
> bro-dev at bro.org
More information about the bro-dev