Disappearing sources of packages when Inria gforge is shut down end 2020 #1298
Comments
|
Hi. The sources of coq-color are on https://github.com/fblanqui/color/ for some time now. However, the targz are on gforge. I will try to move them to github as well by the end of the year. |
|
Hi @CohenCyril, thanks for your message. The sources of coq-high-school-geometry have moved on https://github.com/coq-contribs/high-school-geometry for some time now (though, unfortunately, I renounced to adapt high-school-geometry to Coq 8.7: the |
|
Note that the coqprime dev sources live at https://github.com/thery/coqprime, so it should be possible to migrate the 8.5b tag to there, and to change the bugtracker and homepage links to the GitHub ones |
|
I moved gforge/coqprime to https://thery.gitlabpages.inria.fr/coqprime/ |
|
What is the difference between https://github.com/thery/coqprime and https://gitlab.inria.fr/thery/coqprime? They both have relatively recent commits. |
|
github is the current development. |
|
OK thanks for the explanations. |
|
@thery could you please advertise this in the readme of each repo, each one pointing to the other, and the frozen copy being flaged as such within |
|
Subsidiary question: have the two repos diverged so much that they are irreconcilable? Could we have a simple automatic hook synchronizing them with github, so that inria's one is simply a mirror? |
this is done in https://thery.gitlabpages.inria.fr/coqprime/ and https://github.com/thery/coqprime/blob/master/README.md. |
this was my initial mistake. Some one asked me to put a copy of coqprime on github and |
|
The gitlab repo is missing tags for the files available at https://gforge.inria.fr/frs/?group_id=163 (in particular, there's a link to https://gforge.inria.fr/frs/download.php/file/35520/coqprime_8.5b.zip for coqprime.1.0.0 in ) As far as the repos go, I've pushed the gitlab master branch to https://github.com/JasonGross/coqprime/tree/gitlab/master, and while GitHub informs me that "[t]his branch is 149 commits ahead, 245 commits behind thery:master", when I rebase the GitLab master branch atop the GitHub master branch, the only commits remaining are There are a number of commits on the GitHub master branch that did not make it to the GitLab master branch. So I think it's safe to get rid of the GitLab one (though you may wish to make tags for the old versions?). Btw, if you want to get the GitLab version on GitHub, you can run these commands: git clone [email protected]:thery/coqprime.git coqprime-temp
cd coqprime-temp
git remote add gitlab https://gitlab.inria.fr/thery/coqprime.git
git remote update
git checkout -b gforge/master gitlab/master
git push origin gforge/master
git push origin --tagsThis will not get rid of any history on the GitHub repo, but will just add a new branch |
|
@JasonGross Thanks. My memory was wrong : github/coqprime contains all the history. |
If you go to https://github.com/thery/coqprime/releases/new you can select a particular commit to target the release at. Alternatively, in your local clone of the repo, you can run |
|
Inria is launching an "impact assessment" of the closure of the gforge (see the internal link: https://intranet.inria.fr/Actualite/Nouvelles-concernant-l-arret-de-la-gforge). To contribute, we can open a ticket on their Helpdesk service. There's also an e-mail address: [email protected]. I don't plan on writing myself, but if @palmskog or someone else wish to prepare something, I can certainly forward to this Helpdesk. |
|
@fajb @vbgl the only package on the Coq opam archive using gforge that we have no confirmation about is ppsimpl. Even though the package may have been obsoleted by So, could you please move the repo (https://scm.gforge.inria.fr/anonscm/git/ppsimpl/ppsimpl.git) to a new canonical location, such as GitHub? |
|
We now have confirmation from all relevant projects that they will move or have already moved to a new location. Let's follow up in late November again for final checkup. |
|
The shutdown has been pushed back to summer 2021. |
Inria recently announced that they will shut down gforge project hosting by the end of 2020. Everyone who uses gforge will have to take manual action to migrate their repositories elsewhere, since hosted files will simply disappear.
Quite a few packages in the archive will be affected by this, a full list can be obtained by running the following command in the root:
However, the number of projects affected are far fewer, and can be obtained with the following command (thanks @CohenCyril):
The output list is currently as follows:
We should try to work with the authors of these packages to make sure (1) that all files related to the projects and packages are preserved and (2) if necessary, projects become hosted permanently elsewhere.
The text was updated successfully, but these errors were encountered: