Installation

unable to connect to github for hotfixes & updates

unable to connect to github for hotfixes & updates

by Murray Eisenberg -
Number of replies: 6

With WeBWorK 2.15 under Ubuntu 20.04 (running in a Parallels Desktop for Mac virtual machine under macOS 12.4), today I am unable to accomplish the usual hotfix/update procedure:

$ cd /opt/webwork/webwork2/

$ git remote show origin

fatal: unable to connect to github.com

github.com[0: 140.82.112.4]: errno-Connection refused

$ cd /opt/webwork/libraries/webwork-open-problem-library

$ show origin

[same error as before]

What's wrong?

Tags:
In reply to Murray Eisenberg

Re: unable to connect to github for hotfixes & updates

by Arnold Pizer -

Hi,

Github no longer allows non secure access.  Do the following

wwadmin@wwserver:~$ cd /opt/webwork/webwork2/

wwadmin@wwserver:/opt/webwork/webwork2$ git remote -v

and you will probably see something like:

origin  git://github.com/openwebwork/webwork2.git (fetch)

origin  git://github.com/openwebwork/webwork2.git (push)

which is no longer allowed.  Change this as follows

wwadmin@wwserver:/opt/webwork/webwork2$ git remote set-url origin https://github.com/openwebwork/webwork2.git

and rerun the command

wwadmin@wwserver:/opt/webwork/webwork2$ git remote -v

and you should see an address with https

origin  https://github.com/openwebwork/webwork2.git (fetch)

origin  https://github.com/openwebwork/webwork2.git (push)

Then you can follow the update instructions for the webwork2 repository. Do the analogous thing for the pg and webwork-open-problem-library repositories.


Arnie




In reply to Arnold Pizer

Re: unable to connect to github for hotfixes & updates

by Murray Eisenberg -

Then I should follow WHICH update instructions? (So many sets of instructions there!).

Do I still execute the following?

 git remote show origin

And then, if output shows current installed version is outdated, execute the following?

git pull origin

If not, please direct me to just which section of which document is relevant. I find locating the appropriate docs somewhat Byzantine with WeBWork!

In reply to Murray Eisenberg

Re: unable to connect to github for hotfixes & updates

by Arnold Pizer -

As is stated in the instructions, if you check the version, you will see the current version of WeBWorK is 2.16 (soon to be 2.17). If you update using git, you will get 2.16 which has some different requirements than your current version which is 2.15.  For details see https://webwork.maa.org/wiki/Release_notes_for_WeBWorK_2.16

For different ways of updating, look at the "Methodology" section in https://webwork.maa.org/wiki/Converting_the_webwork_database_from_the_latin1_to_the_utf8mb4_character_set

You do not have to worry converting the database but the "Methodology" section covers your situation.

Maybe others who have more real world experience than I in updating running systems will give you information on how they do it.


In reply to Arnold Pizer

Re: unable to connect to github for hotfixes & updates

by Murray Eisenberg -

I'm still confused: I'm tnot upgrading from 2.15 to 2.16. I'm just trying to do hotfixes (if there are any) and update the problem library.

Where and what are the instructions to do that for that?

In reply to Murray Eisenberg

Re: unable to connect to github for hotfixes & updates

by Arnold Pizer -
Updating the problem library is straight forward. Follow the instructions to do that.

Unfortunately, the way WeBWorK is distributed there is no way that I know of to apply hot fixes to just webwork2 version 2.15 and pg version 2.15 (if there were any). 

I think it would be a good practice to freeze the final version (with all hot fixes applied) of a major release of WeBWorK (pg and webwork2 version 2.15, 2.16, etc.) before the next release is pushed to main but that is something that has not been done.
In reply to Arnold Pizer

Re: unable to connect to github for hotfixes & updates

by Glenn Rice -
You can obtain WeBWorK 2.15 with all hotfixes by running `git checkout -b WeBWorK-2.15+ WeBWorK-2.15+` in /opt/webwork/webwork2. This checks out the commit tagged with WeBWorK-2.15+ (which is 2.15 with all hotfixes) into the branch named WeBWorK 2.15+.

You can do the same with PG. Run `git checkout -b PG-2.15+ PG-2.15+` in /opt/webwork/pg.