@TrevorBramble I've got fixing the SSL bits in hab on the backburner. For now using the statically compiled binary should be fine as a workaround until we can get it to compile on the latest openssl.
Search Criteria
Package Details: habitat-bin 1.6.139-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/habitat-bin.git (read-only, click to copy) |
---|---|
Package Base: | habitat-bin |
Description: | Application automation framework that allows you to build applications that have automation built-in |
Upstream URL: | https://www.habitat.sh/ |
Keywords: | automation cloud containers packaging |
Licenses: | Apache |
Conflicts: | habitat, habitat-git |
Provides: | habitat |
Submitter: | dmp1ce |
Maintainer: | marcparadise (jaym) |
Last Packager: | ryancragun |
Votes: | 2 |
Popularity: | 0.000000 |
First Submitted: | 2017-04-16 15:22 (UTC) |
Last Updated: | 2020-09-04 17:37 (UTC) |
Dependencies (0)
Required by (0)
Sources (1)
Latest Comments
ryancragun commented on 2019-02-21 00:23 (UTC)
dmp1ce commented on 2019-02-20 23:53 (UTC)
Maybe it would be better to package up habitat as a Snap, Flatpak or AppImage until the issue gets resolved.
TrevorBramble commented on 2019-02-20 23:48 (UTC)
@dmp1ce: Great question. Fletcher and I decided it was unwise to distribute Hab binaries built against OpenSSL 1.0 to OpenSSL 1.1 systems.
@ryancragun: I'm adding you as a maintainer of the three packages. I'd appreciate your help resolving the issue as the two solutions Fletcher proposed, updating the Rust dependencies or complete removal of the SSL bits (which apparently weren't even used anymore) haven't happened.
dmp1ce commented on 2019-02-20 19:59 (UTC)
@TrevorBramble I see why that issue effects habitat and habitat-git but why would that cause habitat-bin not to build?
TrevorBramble commented on 2019-02-20 18:29 (UTC)
@ryancragun: There hasn't been a new release because there hasn't been any movement on the issue in the pinned comment. I'd be happy to build a new release if we can compile on Arch again.
dmp1ce commented on 2019-02-20 18:17 (UTC)
@ryancragun, It is fine with me. Can you contact the maintainers?
ryancragun commented on 2019-02-20 16:17 (UTC)
I'd be happy to take over maintainership of this package. It's been out of date for a while now.
Pinned Comments