poudriere 12.0R amd64 & 13.0-CURRENT amd64 OK, waiting on the
rest
Details
Details
- Reviewers
jrm olgeni trociny - Commits
- rP518609: databases/leofs: move to a supported OTP release
Diff Detail
Diff Detail
- Lint
No Lint Coverage - Unit
No Test Coverage - Build Status
Buildable 27693 Build 25893: arc lint + arc unit
Event Timeline
Comment Actions
I would suggest to use lang/erlang-runtime21 so that lang/erlang stays free for upgrades as the "user facing" Erlang, just in case..
Comment Actions
bump PORTREVISION to force a rebuild and therefore ensure everybody gets
a warning message
Comment Actions
I don't think users will get a warning when installing the package. I also don't think there is any change in the package, so bumping PORTREVISION is probably not necessary. @olgeni's suggestion?
Comment Actions
I still think it's worth bumping the PORTREVISION to ensure everything
is rebuilt correctly. Erlang is picky about this, as explicit versions
are bound into the runtime configuration.
The original intent was to get this change sorted out before 2019Q3
starts which maximises time for users to get their stuff sorted.
Comment Actions
I was referring to the PORTREVISION bump on lang/erlang-runtime.
Did I miss that you addressed @olgeni's suggestion? I would suggest to use lang/erlang-runtime21 so that lang/erlang stays free for upgrades as the "user facing" Erlang, just in case..
Comment Actions
Ooops.. I did not mean to accept this before addressing @olgeni's suggestion about the dependency.
Comment Actions
Port builds fine for me, and I wombled my way through node startup without issue, but couldn't get auth working. I think the port is working fine, I just lack the leofs expertise. Mikolaj can you check it please before we push out the changes?
Looks like the port could do with a short pkg-message to explain how to set up your first node?
Comment Actions
@dch the patch works for me.
I was creating a user for test with the commands:
leofs-adm create-user ${user} ''
leofs-adm update-user-role ${user} 9And was using access-key-id and secret-access-key (outputed when leofs-adm create-user was run) in a s3 tool (s3cmd in my case).