We are now using GIT

[Martin_fr]

Lazarus has moved

The new official repository is now available at
     https://gitlab.com/freepascal.org/lazarus/lazarus

All bug-reports have been moved to Gitlab too, and the new tracker can be found at the above address.


Mirrors for Git read access are at
  https://github.com/fpc
  https://sourceforge.net/p/lazarus/git/ci/main/tree/

EDIT:
Couple of notes/rules.

• Mirrors are read only. If you find a way to post a note/issue/pull-request, be prepared to see it ignored. We are not checking for them
• GITHUB: the svn mirror is a side-effect. Use it at your own risk, if needs must. There is no support. Revisions there will likely not match the old/original svn. Revisions from that mirror can not be used for issue reports or anything, as we do not know (nor check) whatever Github hands out to you.

FPC has moved

FPC bugs has also moved.

[Edited to indicate move complete]

[del]

Very cool.

[Artlav]

Was FPC issue tracker fully moved over? I can't find any of the recent issues, i.e. https://bugs.freepascal.org/view.php?id=39275
At least some of the old ones as well, actually.

Also, any plans for redirects? The old links are giving rather unhelpful 403 messages.

[lucamar]

Artlav, this announcement is only for Lazarus. FPC will have its own repository, tracker, etc. (that is, if I understood correctly; I'm not a core developer in any of the projects )

[korba812]

I see the Lazarus bugtracker has been moved. But where do I find reports from the "CCR" section of the old bugtraker?

[Martin_fr]

Was FPC issue tracker fully moved over? I can't find any of the recent issues, i.e. https://bugs.freepascal.org/view.php?id=39275
At least some of the old ones as well, actually.

Also, any plans for redirects? The old links are giving rather unhelpful 403 messages.

FPC is still moving

They will have an issue tracker in the same gitlab account, but in their sub group.

[ccrause]

Anyone knows how to move a branch with commit history from Github to GitLab and preserve commit history?  Work started as a branch of a fork of Martin's Lazarus Github mirror.  Would like to move this branch across to a fork of the official GitLab Lazarus project if possible.

I can recreate the branch from scratch and copy the changes across, but this would not have the commit history.

[Martin_fr]

yep.
Checkout both repositories.

It your github clone, add a new remote, as url use the path to your gitlab checkout.
  git remote update.

now you have both in the same local repro.

Code: Text  [Select][+][-]

1. git rebase --reapply-cherry-picks --onto  <commit_in_new_local_gitlab>   <upstream_in_old_githup_e_g_master>  <branch_in_old_github>

Then push the rebased branch to your local gitlab clone.

Unfortunately some files in the conversion are checked in with wrong line endings.
This can, if you switch to older commits, lead to files showing as modified, and blocking rebase. In that case make sure you are on "main" head, before starting rebase.

You can also temporary create a file .git/info/gitattributes  and put the affected files in there as binary (IIRC  /path/file -text )
Or disable core.autocrlf

[DonAlfredo]

Another alternative way. Export all commits your are interested in as a patch. Followed by an import all patches into your new repo.
Example of export:

Code: Pascal  [Select][+][-]

1. git format-patch --output-directory "../patches" --root origin --since="Dec 25, 2020"

[Martin_fr]

Gitlab has been working fine for me all the time. Both webpage and repro access.
Maybe some routing on the way.
Or maybe your IP was in the same range as that of someone doing malicious stuff?

 btw.
   What do I need to do change my SVN URL in the existing trunk I have ? I am using the windows desk top version of it.

   I know where the URL properties are, do I need only to change that or do I need to do a complete checkout again ?

The url is on the github site. Just drop down the "clone" button. (as if you wanted the git link / svn is the same link)

Since github reverse translates git to svn, all the revision numbers will have changed. I doubt you can simply change the url in your client. (But I have not tested, maybe it does something useful, or at least recoverable...)
I guess remove the current checkout, and do a new checkout.

And again, while the choice to use this is there, the svn revision numbers will be useless in conversations about what works and what does not.
No one in the team (afaik) has that checkout. So we will have no idea what any rev number actually points to.

[Martin_fr]

Gitlab has been working fine for me all the time. Both webpage and repro access.
Maybe some routing on the way.
Or maybe your IP was in the same range as that of someone doing malicious stuff?

Ah, well yes. Actually.

Just recalling, there was/is some more maintenance. So we have/had to temporarily make the repro private. That explains the 404.
Sorry about that.

I have to get the exact feedback, but I estimate it should be done by tomorrow.

[dsiders]

Gitlab has been working fine for me all the time. Both webpage and repro access.
Maybe some routing on the way.
Or maybe your IP was in the same range as that of someone doing malicious stuff?

Not working here. 
https://gitlab.com/freepascal.org/lazarus/lazarus returns 404.

CLI git pull returns:
remote: The project you were looking for could not be found or you don't have permission to view it.
fatal: repository 'https://gitlab.com/freepascal.org/lazarus/lazarus.git/' not found

[Martin_fr]

See my 2nd post.

We "forgot" to move some bug from mantis to gitlab. We are doing that now.

But in order to be able to do that, we need to disable access.

----------
Should have been better communicated. But it was just realized maybe an hour ago. I even forgot when I made the first reply earlier....

[dsiders]

See my 2nd post.

We "forgot" to move some bug from mantis to gitlab. We are doing that now.

But in order to be able to do that, we need to disable access.

----------
Should have been better communicated. But it was just realized maybe an hour ago. I even forgot when I made the first reply earlier....

Sorry. I overlooked that one.

[LacaK]

When migration will be done can be "bugs.freepascal.org" redirected to new location on GitLab?