firehol / packages Goto Github PK

Pre-built packages for distributions that do not provide them

Shell 68.57% Makefile 31.43%

packages's Introduction

FireHOL packages

This repository is intended to provide pre-built packages for distributions that do not have them as standard.

Current status:

Package	Architecture	Installs	Runs	Works
FireHOL OpenWRT 22.03 ipk	all	?	?	?
FireHOL CentOS/RHEL 8 rpm	all (noarch)	?	?	?
FireHOL CentOS/RHEL 9 rpm	all (noarch)	?	?	?
iprange OpenWRT 22.03 ipk	bcm47xx	?	?	?
iprange OpenWRT 22.03 ipk	ipq806x	?	?	?
iprange CentOS/RHEL 8 rpm	amd64	?	?	?
iprange CentOS/RHEL 9 rpm	amd64	?	?	?

Basically: I run the builds but don't check them personally. I update this table when people report success/failure.

It is all something of a best-effort basis, so pull requests to add new packaging formats, architectures, or updated versions are always welcome.

Old packages

CentOS7/RHEL 7 package build no longer works. Last built RPMs are here.

CentOS6/RHEL 6 package build no longer works. Last built RPMs are here.

Last builds for OpenWRT 19.07 (and last ar71xx build) are here.

Last builds for OpenWRT 18.06 are here.

Releases

Everything gets built by Github Actions; tags are created after a package update or new output is added which automatically puts all the binaries into github releases:

git push
# wait...
git tag YYYY-MM-DD-hhmm
git push --tags

Building outside Github

Clone the repository and run the common setup script:

git clone https://github.com/firehol/packages.git firehol-packages
cd firehol-packages
./setup.sh

Then run any individual (build-PLATFORM.sh) scripts you are interested in e.g.:

./build-openwrt.sh

Provided everything works, the outputs all go to outputs/packages. If something goes wrong you most likely need to install a dependency on your build host.

Github Actions runs each build-*.sh script in order and provided everything builds OK, it builds checksums in outputs/checksums.

Dependencies

The OpenWRT builds need ccache and basic build tools (make etc.) installed
The CentOS/Redhat builds need docker (docker.io on Ubuntu) installed and to be able to run sudo

packages's People

Contributors

Stargazers

Watchers

Forkers

alexxnica universal-it-systems royaflash klaast ktsaou ols3er arovietnam johnramsden thecheatah dheckl shawnhank kylemaas virtualinterconnect lizhengdao

packages's Issues

OpenWRT 18.06.0 Build

Create a build for the latest release of OpenWRT 18.06.0.

update-ipsets

It appears the "update-ipsets" script is not included in this package:
https://github.com/firehol/packages/releases/download/2017-10-14-1440/firehol-3.1.5-1.el7.centos.noarch.rpm

I have both the latest packages for CentOS7 iprange and firehol installed. I tried to just copy over the
update-ipsets.sh script, but it complains that iprange is not installed. Iprange and firehol working great, but can't get the update-ipsets working.

Is there a way I could get manually install the "update-ipsets" script for CentOS?
And could you please include it in the next packages.
Thank you.

Error: Nothing provides iptables-ipv6 needed by firehol

Just by looking at the documentation I'm very excited to use FireHOL
Thanks for this great piece of software!

Unfortunately I have trouble installing FireHOL on CentOS 8
yum --nogpgcheck localinstall firehol-x.y.z-1.el7.centos.noarch.rpm
gives error
Nothing provides iptables-ipv6 needed by firehol

I tried firehol-3.1.5-1.el7.centos.noarch.rpm and firehol-3.1.6-1.el7.noarch.rpm without success

Can you please help? Thanks!

Please Update Package Releases

Please create the latest packages for files at this location:
https://github.com/firehol/packages/releases/latest

I was specifically looking for the new netdata 1.9 for el7.centos.
The new features in 1.9 are amazing, great work.

Firehol release version in RPM package is concatenating a 1

The package.conf has RPM_FIREHOL_RELEASE=2 but the files came out as e.g. firehol-3.1.6-12.el6.noarch.rpm.

See here: https://github.com/firehol/packages/releases/tag/2020-02-18-0552

Malformed package file?

Model MikroTik RBM33G
Architecture MediaTek MT7621 ver:1 eco:3
Firmware Version OpenWrt 18.06.2 r7676-cddd7b4c77 / LuCI openwrt-18.06 branch (git-19.020.41695-6f6641d)
Kernel Version 4.14.95
Local Time Tue Feb 26 01:43:12 2019

Push RPM and DEB Packages to Packagecloud

Now that package build are here, about about pushing them to packagecloud.io or any other RPM and/or DEB hoster? Should be quite easy to do so via travis: https://docs.travis-ci.com/user/deployment/packagecloud/

opkg install

Hi I've not understand if I iprange_1.0.3-1_ar71xx_chaos_calmer.ipk will work out of the box.
I can login to openwrt with ssh and next wget the .ipk file for install with opkg?
Thanks.

I would like to have a single dashboard with my multiple openwrt devices.

RPM Fusion

Similar to #3, it would be nice if firehol packages could be made available via RPM Fusion.

https://rpmfusion.org/Contributors

Static x86_64 builds

I have added a static x86_64 build using alpine and linux in commit 05f7bcb which can be the foundation for some generic packaging.

@ktsaou I will not have any more time to work on this until next week at the earliest but the binaries are built statically and appear to run as expected.

If you follow the readme instructions you should be able to get the build-x86_64-static.sh to run without much trouble.

The result of make install currently goes to build/x86_64-static/netdata/opt on the host, given the prefix used for configure and the DESTDIR for make install within the container.

What is left to do:

Update x86_64-static/netdata/docker-build.sh to make a package of some kind and settle any options to ./configure.
Update build-x86_64-static.sh to copy the packages from under build/x86_64-static/netdata on the to the output/packages folder.
Wait until a master build succeeds on travis
Create a tag and watch the results appear in a github release!

Of these, 1 is almost all of the work, of course...

Support for OpenWrt 19.07.x

Do the 18.06 packages support openwrt 19.07?

Packages for CentOS 8

Is it possible the build system could be updated to include packages for CentOS 8?