-
Notifications
You must be signed in to change notification settings - Fork 13
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
#35: everything broken. #48
Comments
Leamas, I believe I speak for Jon and Mauro too, I am certain it is unintentional, we are very much in support of the Plugin Installer and trying have Plugin Installer work alongside the current git deployment to release tab system. What do you think broke it? However in mauroc/squiddio_pi branch "test_dep" I see your PR #35 and PR #38 and that branch does not seem to be showing the ci builds. Perhaps there are other service configuration needed to build these and Mauro may need some guidance. |
In mauroc/squiddio_pi "master" branch debian
I find ci/control.trusty and ci/control.xenian. No ci/control or ci/control.debian fedora
mingw
flatpak
Did not find wxWidgets_LIBRARIES wxWidgets_INCLUDE_DIRS |
the test_dep branch was just me messing around with the code,
unsuccessfully. It should be ignored
…On Fri, Oct 11, 2019 at 10:45 AM Rick Gleason ***@***.***> wrote:
Alec,
On mauroc/squiddio_pi "test_dep" branch, where I can see your merged PR's
#35 <#35> & #38
<#38>, I do not see any
ci/builds at any stage.
Perhaps this will take a bit more work? Figuring out why?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#48?email_source=notifications&email_token=AAGRYLQWJJ2TXNLIAASSR2DQOC3S7A5CNFSM4I73DUZ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEBAW7CQ#issuecomment-541159306>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAGRYLRYGSZ6IH7ZIKYHONLQOC3S7ANCNFSM4I73DUZQ>
.
|
I think we need to do the following:
|
When #35 was merged all circleci builder worked (although the deployment wasn't completely configured). Current master does not build any of the plugin loader artifacts, several files are removed or completely reset to another version without any visible attempt to merge the changes done.
I don't really understand the situation. Are these changes on purpose with the goal to get rid of any changes aiming to provide the artifacts required by the plugin installer? Or is it just some mistakes?
"Mystified"
The text was updated successfully, but these errors were encountered: