Sign in Join

Live chat for Free Pascal, Lazarus, Delphi and every Pascal programmer.

Mailing lists / fpc-devel / 2021-07

Moving to gitlab.

18 messages · 8 people · –

Reply by email Subscribe to this list Your subscription

Read-only archive. Use j and k to move between messages.

Michael Van Canneyt

Hello,

Some of you may have seen this on the lazarus list: During the upcoming weekend we will be moving to GitLab.

During this time, there may be interruptions to 2 of our services:

- SVN will become unavailable permanently.

- Mantis/Bugtracker will become unavailable.
  * It will be taken offline.
  * A forwarder to the GitLab issue tracker will be installed after all was reworked, so old 'view' links will continue to work.

The forum and mailing lists should not be affected and continue to work as normal.

The list of new Urls will be posted when the move has been done.

We plan a read-only GitHub mirror.

GitHub advertises that the repositories can be read with an svn client too. So for those needing read only access, there will be an svn link.

Michael.

Reply by email

J. Gareth Moreton
to Michael Van Canneyt

For those who connect to the SVN repository through a command-line terminal to update the trunk, can we have instructions on how to connect to the new GitHub repository this way?  The instructions aren't yet on https://www.freepascal.org/develop.html, presumably because it's not yet live or at least ready.

Gareth aka. Kit

Michael Van Canneyt wrote 31 lines
Hello, Some of you may have seen this on the lazarus list: During the upcoming weekend we will be moving to GitLab. During this time, there may be interruptions to 2 of our services: - SVN will become unavailable permanently. - Mantis/Bugtracker will become unavailable.   * It will be taken offline.   * A forwarder to the GitLab issue tracker will be installed after all was reworked,     so old 'view' links will continue to work. The forum and mailing lists should not be affected and continue to work as normal. The list of new Urls will be posted when the move has been done. We plan a read-only GitHub mirror. GitHub advertises that the repositories can be read with an svn client too. So for those needing read only access, there will be an svn link. Michael. _______________________________________________ fpc-devel maillist - https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel
This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus

Reply by email

Christo Crause
to J. Gareth Moreton

A document discussing the SVN support of github, just for reference: https://docs.github.com/en/github/importing-your-projects-to-github/working-with-subversion-on-github/support-for-subversion-clients

On Thu, 22 Jul 2021, 15:56 J. Gareth Moreton via fpc-devel, <

Show quoted text 10 lines
wrote: For those who connect to the SVN repository through a command-line terminal to update the trunk, can we have instructions on how to connect to the new GitHub repository this way? The instructions aren't yet on https://www.freepascal.org/develop.html, presumably because it's not yet live or at least ready. Gareth aka. Kit

Reply by email

Michael Van Canneyt
to J. Gareth Moreton: For those who connect to the SVN repository through a command-line terminal to update the…
J. Gareth Moreton wrote 5 lines
For those who connect to the SVN repository through a command-line terminal to update the trunk, can we have instructions on how to connect to the new GitHub repository this way?  The instructions aren't yet on https://www.freepascal.org/develop.html, presumably because it's not yet live or at least ready.

I don't plan to put instructions for svn online.

It's 2021 meanwhile, please move to git.

Michael.

Reply by email

Martin Frb
to J. Gareth Moreton: For those who connect to the SVN repository through a command-line terminal to update the…
J. Gareth Moreton wrote 5 lines
For those who connect to the SVN repository through a command-line terminal to update the trunk, can we have instructions on how to connect to the new GitHub repository this way?  The ins

git (gitlab or github):
both pages have full explanations. They are alternatives, choose one. https://wiki.lazarus.freepascal.org/FPC_git
https://wiki.lazarus.freepascal.org/SVN_to_GIT_Cheatsheet

svn
just change the URL?

Reply by email

Martin Frb
to Martin Frb
Martin Frb wrote 7 lines
On 22/07/2021 15:55, J. Gareth Moreton via fpc-devel wrote: > > For those who connect to the SVN repository through a command-line > terminal to update the trunk, can we have instructions on how to > connect to the new GitHub repository this way?  The ins svn just change the URL?

Actually, you probably need to delete the current svn dir, and do a new checkout.

Mind, that there will be zero support on the revision numbers handed out by github's svn.
If you have issues, you need the git sha.

Reply by email

John Lee
to Michael Van Canneyt: Some of you may have seen this on the lazarus list: During the upcoming weekend we will…

I use viewvc to look at repository - is there an equivalent when everyting is on gitlaB? tia john

On Thu, 22 Jul 2021 at 13:32, Michael Van Canneyt via fpc-pascal <

Show quoted text 32 lines
wrote: Hello, Some of you may have seen this on the lazarus list: During the upcoming weekend we will be moving to GitLab. During this time, there may be interruptions to 2 of our services: - SVN will become unavailable permanently. - Mantis/Bugtracker will become unavailable. * It will be taken offline. * A forwarder to the GitLab issue tracker will be installed after all was reworked, so old 'view' links will continue to work. The forum and mailing lists should not be affected and continue to work as normal. The list of new Urls will be posted when the move has been done. We plan a read-only GitHub mirror. GitHub advertises that the repositories can be read with an svn client too. So for those needing read only access, there will be an svn link. Michael._______________________________________________ fpc-pascal maillist - https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal

Reply by email

J. Gareth Moreton
to Michael Van Canneyt: I don't plan to put instructions for svn online. It's 2021 meanwhile, please move to git.…

I didn't actually mean to support SVN, but just to connect to the Github repository instead (via git I presume).

I'll probably have to do a lot of reading up on git, since I have a lot of local branches for individual changes that I test and develop.

Gareth aka. Kit

Michael Van Canneyt wrote 19 lines
On Thu, 22 Jul 2021, J. Gareth Moreton via fpc-devel wrote: > For those who connect to the SVN repository through a command-line > terminal to update the trunk, can we have instructions on how to > connect to the new GitHub repository this way?  The instructions > aren't yet on https://www.freepascal.org/develop.html, presumably > because it's not yet live or at least ready. I don't plan to put instructions for svn online. It's 2021 meanwhile, please move to git. Michael. _______________________________________________ fpc-devel maillist - https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel
This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus

Reply by email

Michael Van Canneyt
to J. Gareth Moreton: I didn't actually mean to support SVN, but just to connect to the Github repository…
J. Gareth Moreton wrote
I didn't actually mean to support SVN, but just to connect to the Github repository instead (via git I presume).

You presume right :-)

I'll probably have to do a lot of reading up on git, since I have a lot of local branches for individual changes that I test and develop.

I think you'll find that this becomes a lot easier with git...

Although I think all git related questions have answers on stackoverflow or the git site; don't hesitate to ask for help if you get stuck anyway...

Michael.

Reply by email

Michael Van Canneyt
to Ryan Joseph
Ryan Joseph wrote
I see the old bug reporter has been taken down now. Can anyone explain how to see my old bug reports now? I went to https://gitlab.com/groups/freepascal.org/fpc/-/issues and filtered by my username "genericptr" but nothing came up.

That's normal. The conversion is delayed.

Only the lazarus project and all other repositories have been converted, but the FPC one not yet. (it's BIG, so the conversion has some issues)

Michael.

Reply by email

Denis Kozlov
to Michael Van Canneyt

Regarding the old bug tracker. Can you please keep it online, perhaps making it accessible in read-only mode?

There are many references to issues in the old bug tracker across many code bases and discussions, at it would be a real shame to loose that link so abruptly.

If keeping the old bug tracker alive (in read-only mode) is not feasible, a good alternative is to set up redirects to the newly generated issues in gitlab.

Regards,
Denis

Michael Van Canneyt wrote 19 lines
On Tue, 27 Jul 2021, Ryan Joseph via fpc-devel wrote: > I see the old bug reporter has been taken down now.  Can anyone explain > how to see my old bug reports now?  I went to > https://gitlab.com/groups/freepascal.org/fpc/-/issues and filtered by my > username "genericptr" but nothing came up. That's normal. The conversion is delayed. Only the lazarus project and all other repositories have been converted, but the FPC one not yet. (it's BIG, so the conversion has some issues) Michael. _______________________________________________ fpc-devel maillist  -  https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel

Reply by email

Michael Van Canneyt
to Denis Kozlov
Denis Kozlov wrote 7 lines
Regarding the old bug tracker. Can you please keep it online, perhaps making it accessible in read-only mode? There are many references to issues in the old bug tracker across many code bases and discussions, at it would be a real shame to loose that link so abruptly.

The links will not be dead.

If keeping the old bug tracker alive (in read-only mode) is not feasible.

No, because for security reasons I would need to maintain it (security updates etc) and this is exactly why we move to gitlab, to get rid of the release burden.

a good alternative is to set up redirects to the newly generated issues in gitlab.

The redirects to gitlab are already in place. if the script cannot determine the page to go to, you get the choice to select a bugtracker.

Note that the old bug ID is used in the new bugtracker, so if a bug was transferred (and they should all be transferred) you can just search for the old bug ID.

Michael.

Reply by email

Michael Van Canneyt
to Michael Van Canneyt
Michael Van Canneyt wrote 32 lines
On Thu, 29 Jul 2021, Denis Kozlov via fpc-devel wrote: > > Regarding the old bug tracker. Can you please keep it online, perhaps > making it accessible in read-only mode? > > There are many references to issues in the old bug tracker across many > code bases and discussions, at it would be a real shame to loose that > link so abruptly. The links will not be dead. > > If keeping the old bug tracker alive (in read-only mode) is not > feasible. No, because for security reasons I would need to maintain it (security updates etc) and this is exactly why we move to gitlab, to get rid of the release burden. > a good alternative is to set up redirects to the newly > generated issues in gitlab. The redirects to gitlab are already in place. if the script cannot determine the page to go to, you get the choice to select a bugtracker. Note that the old bug ID is used in the new bugtracker, so if a bug was transferred (and they should all be transferred) you can just search for the old bug ID.

For clarity: the lazarus issues have already been transferred, the FPC ones not yet; there is an issue with the svn -> git conversion. (we need the git conversion to be done first)

Michael.

Reply by email

Luca Olivetti
to Michael Van Canneyt

El 29/7/21 a les 17:52, Michael Van Canneyt via fpc-devel ha escrit:

For clarity: the lazarus issues have already been transferred, the FPC ones not yet; there is an issue with the svn -> git conversion. (we need the git conversion to be done first)

I tried some links to lazarus issues I had in my mail archive and none of them worked, e.g.

http://bugs.freepascal.org/view.php?id=21318
https://bugs.freepascal.org/view.php?id=33850
https://bugs.freepascal.org/view.php?id=38666

they are redirected to
https://gitlab.com/freepascal.org/lazarus/lazarus/-/issues/38666 (the last one) and it's a "404 page not found".

Bye

Luca

Reply by email

Martin Frb
to Luca Olivetti
Luca Olivetti wrote 18 lines
El 29/7/21 a les 17:52, Michael Van Canneyt via fpc-devel ha escrit: > For clarity: the lazarus issues have already been transferred, the > FPC ones > not yet; there is an issue with the svn -> git conversion. > (we need the git conversion to be done first) I tried some links to lazarus issues I had in my mail archive and none of them worked, e.g. http://bugs.freepascal.org/view.php?id=21318 https://bugs.freepascal.org/view.php?id=33850 https://bugs.freepascal.org/view.php?id=38666 they are redirected to https://gitlab.com/freepascal.org/lazarus/lazarus/-/issues/38666 (the last one) and it's a "404 page not found".

The project is currently hidden. Because we had to sort some issues with the conversion.

If all goes well, it should work tomorrow or the day after.

Reply by email