Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Fix #593: Remove snaps #649

Merged
merged 1 commit into from
Feb 9, 2019
Merged

Fix #593: Remove snaps #649

merged 1 commit into from
Feb 9, 2019

Conversation

hsanjuan
Copy link
Collaborator

Snap builds have broken again. It seems the credentials have expired without
warning, even though they were not so old anyways. As promised,
next time snaps would break, they would be removed.

License: MIT
Signed-off-by: Hector Sanjuan code@hector.link

Snap builds have broken again. It seems the credentials have expired without
warning, even though they were not so old anyways. As promised,
next time snaps would break, they would be removed.

License: MIT
Signed-off-by: Hector Sanjuan <code@hector.link>
@hsanjuan hsanjuan self-assigned this Jan 18, 2019
@ghost ghost added the status/in-progress In progress label Jan 18, 2019
@hsanjuan
Copy link
Collaborator Author

This should fix master builds, but the only way to test it is after merging.

@hsanjuan hsanjuan mentioned this pull request Jan 18, 2019
@coveralls
Copy link

Coverage Status

Coverage decreased (-0.02%) to 65.604% when pulling 6e43d27 on remove/snaps into a244af9 on master.

@hsanjuan hsanjuan added RFM Ready for Merge and removed status/in-progress In progress labels Jan 23, 2019
@lanzafame lanzafame merged commit ecef9ea into master Feb 9, 2019
@lidel lidel mentioned this pull request Aug 30, 2022
2 tasks
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
RFM Ready for Merge
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants