-
Notifications
You must be signed in to change notification settings - Fork 85
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
Fix package uploads for Windows MSI and MacOSX #340
Comments
Receive error on the latest release:
|
You forgot to also copy the masonry executable. Hence the error that you are getting. |
On 3/9/19 10:16 AM, Gabe Alford wrote:
Receive error on the latest release:
|./compliance-masonry 76 19:24:15 2019/03/08 19:24:17
Error: cannot find the 'masonry' executable |
You forgot to also copy the masonry executable. Hence the error that
you are getting. |compliance-masonry| calls the masonry executable for
backwards compatibility. Might just need to remove the
|compliance-masonry| executable.
Didn't "forget" -- that's not documented anywhere, for any platform:
https://github.com/opencontrol/compliance-masonry/blob/master/docs/install.md
Will send a PR.
|
Travis has been fixed. Now just need to fix Appveyor which the issue. |
@afeld @geramirez @gregelin can any of you guys create an OpenControl organization in Appveyor and add yourselves, @shawndwells, and @redhatrises as co-admins? Need the ability to upload MSIs built from Appveyor to GitHub when a new release is tagged. |
On 3/12/19 12:04 PM, Gabe Alford wrote:
@afeld <https://github.com/afeld> @geramirez
<https://github.com/geramirez> @gregelin <https://github.com/gregelin>
can any of you guys create an OpenControl organization in Appveyor and
add yourselves, @shawndwells <https://github.com/shawndwells>, and
@redhatrises <https://github.com/redhatrises> as co-admins? Need the
ability to upload MSIs built from Appveyor to GitHub when a new
release is tagged.
Alternatively (and ideally), could y'all also add Gabe (@redhatrises) to
the OpenControl org admins on GitHub? We're frequently running into
situations where we can't perform releases, setup CI/CD, etc. Believe
the historical maintainers have moved into new jobs/roles and this is
becoming problematic.
|
The text was updated successfully, but these errors were encountered: