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

CheckForUpdates fails #45

Closed
laurentbartholdi opened this issue Jan 13, 2017 · 8 comments
Closed

CheckForUpdates fails #45

laurentbartholdi opened this issue Jan 13, 2017 · 8 comments

Comments

@laurentbartholdi
Copy link

Due to a change on the gap website, that gap-system.org does not accept anymore http requests, the command "CheckForUpdates" does not work anymore.

In fact, it would also be nice to implement an https client, since http seems to be less and less used.

@ChrisJefferson
Copy link
Member

While we should look for this, unfortunately https is a massive undertaking compared to http (it's easy to write a http client, and basically impossible to write a https client). We will have to pull in an external https library (I have no idea how hard that would be..)

@ChrisJefferson
Copy link
Member

This should work again now. However, long term we need a new plan, as it won't work forever.

@ChrisJefferson
Copy link
Member

I should say, this is because we re-enable http access to gap-system, but I'm told we can only have it for a year or so, then it needs turning off.

@olexandr-konovalov
Copy link
Member

The switch to https also has an impact on UnitLib (gap-packages/unitlib#3). It may also eventually have some impact on AtlasRep, which now uses IO or wget to retrieve remote data.

@markuspf
Copy link
Member

markuspf commented Oct 8, 2018

@fingolfin
Copy link
Member

It might be best to remove CheckForUpdates, or at least make it print a big fat deprecation message. And perhaps add a similar command to @mtorpey's https://github.com/gap-packages/PackageManager

@mtorpey
Copy link

mtorpey commented Oct 30, 2018

I've added an issue to PackageManager: gap-packages/PackageManager#33

@fingolfin
Copy link
Member

the issue @mtorpey mentioned was resolved in the meantime, nice. But it asked for something slightly different. I've now also submitted this issue: gap-packages/PackageManager#46

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

No branches or pull requests

6 participants