-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adds changes for updated securedrop-log package #133
Conversation
Now that #132 has been merged, this could use a rebase to ensure the built wheel and hashes can be used to build the package. After rebasing on master locally, getting a build error against the 0.0.4 tarball (using freedomofpress/securedrop-log#8). Have you seen this error before? Am I doing something wrong
|
ac6905f
to
7bf28b6
Compare
@emkll I could not reproduce this error. I have also rebased the PR branch. |
Based on freedomofpress/securedrop-log#8 (comment) , should this PR also be rebased to use the latest wheels before review? |
I already did that here. |
7bf28b6
to
749b771
Compare
(CI will pass here for proxy- and client- jobs once rebased on the very latest master that includes #136, log CI failure is expected due to lack of sd-rsyslog on master, will pass when freedomofpress/securedrop-log#8 is merged) |
934c139
to
d31cb54
Compare
Updated and rebased against |
Now also adds the securedrop-log systemd service file.
d31cb54
to
dc10baa
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Diff looks good to me, and CI is passing on 0.0.4 securedrop-log tag
This will not pass till get freedomofpress/securedrop-log#8 and #132 merged.
How to test?