ripe-atlas-software-probe
ripe-atlas-software-probe copied to clipboard
RIPE-NCC
Feature Request: for every tagged release, provide pre-compiled binaries of atlasswprobe
Feature Request
Provide downloadable installer files when a new release is tagged
I.e. when a release is tagged for a git commit, upload pre-compiled .deb and/or .rpm files available on RIPE-NCC/ripe-atlas-software-probe/releases (e.g. release 5010)
- File: atlasswprobe-5010-1-amd64.deb.zip
- Checksum: atlasswprobe-5010-1-amd64.deb.zip - sha256:
565963DC6A78E2AA90CE18C106684F5BABAC8AC51F80A907A647DDB79ED20FEC - Checksum: atlasswprobe-5010-1-amd64.deb - sha256:
D2621E8A7076A7FE4D97E2FFD59A14612FCA03CB2006C95B2BE437E34E94268F
You mean like this? https://github.com/Knight1/ripe-atlas_packages-test/releases
I don't think so. They made clear that they only provide the Software and CentOS Tools.
You mean like this? https://github.com/Knight1/ripe-atlas_packages-test/releases
Yep.
Currently only the Debian Build system includes support for amd64, arm64, and armhf.
Is there a public discussion about why this is a problem atm. ?
Somewhere publicly would be prefered.
Or even if RIPE NCC has considered to host a repo?
E.g. https://deb.ripe.net/ (similar to how FRR has https://deb.frrouting.org/)
@netravnen i've created an automated workflow for building the sw probe with github actions.
Currently the files are only stored as artifacts, i still need to figure out how i can add them as release in my fork. But i would be happy if someone would try the built packages. I built them for Debian x64, aarch64 and armv7 (armhf). I've tried armv7 as upgrade on my raspberry from v5020 to v5040 and it works fine.
Currently i also don't have a mechanism, that creates a release when a new tag was created here in this repo.
The Workflows called build do have the packages as zipped artifacts attached. https://github.com/Zeik0s/ripe-atlas-software-probe/actions/workflows/build.yml
Hi guys,
Good ideas!
As it happens, we are currently refactoring our repository to support automated builds. The CentOS packages are copied to a CentOS 7/8 repository at the moment, which is something I would love to do automatically. I have no objections against pushing them here as well, can you tell me how this would be easier than a repo?
Regarding Debian, this is currently not officially supported. I do get the question a lot, so it is something that I will bring up for discussion.
Regards,
Michel
