Skip to content
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

Change cddlib to GitHub tarball #73

Closed
wants to merge 3 commits into from
Closed

Conversation

wxmerkt
Copy link
Collaborator

@wxmerkt wxmerkt commented Jun 27, 2018

The Cloudfront one is blocked from the UK. cddlib recently started to host their project on GitHub instead of the old FTP server, so changing it to GitHub tag tarball.

Resolves #72

wxmerkt and others added 2 commits June 27, 2018 14:34
@wxmerkt
Copy link
Collaborator Author

wxmerkt commented Jun 27, 2018

Actually, this tarball is different from the one that used to be on CloudFront and the patch fails. Do you have a copy of it or could change the CloudFront to allow the UK? 🇬🇧

…a while back when the original FTP went down.
@rdeits
Copy link
Owner

rdeits commented Jun 27, 2018

I can send you a copy of the tarball from the cloudfront server, but I have no control over that server whatsoever and no idea why it's not working. Maybe some GDPR thing?

Would you like a copy from cloudfront, or is the new terminator link the right one now?

@rdeits
Copy link
Owner

rdeits commented Jun 27, 2018

Also @wxmerkt I just marked you as a collaborator on this repo, so you should now be able to push branches to the main repo instead of your fork. That will let the CI actually run properly on your pull requests, since otherwise the encrypted Mosek license file can't be used.

@wxmerkt
Copy link
Collaborator Author

wxmerkt commented Jun 27, 2018

Hi Robin,
Thanks for the quick response and invitation, I will push it against here to runt he CI.

I have the correct tarball and it's the one on terminator - unfortunately the upstream @cddlib/cddlib repository tarball is not the same. Happy to close this PR and leave it on CloudFront as is - it worked wonderfully about 1-2 weeks ago and we just noticed today that it's blocked. Do you know who runs the CloudFront (Drake?). If so, could they open it up again then we can leave it as is?

@rdeits
Copy link
Owner

rdeits commented Jun 27, 2018

@jamiesnape it looks like you made the switch from aws to cloudfront: wxmerkt@22935c6 Do you know why it's no longer accessible?

@jamiesnape
Copy link
Contributor

I will check the settings.

@jamiesnape
Copy link
Contributor

@wxmerkt
Copy link
Collaborator Author

wxmerkt commented Jun 27, 2018

@jamiesnape That one is good and accessible.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants