Re: [U-Boot] [ANNOUNCEMENT] Switching to gitlab.denx.de
Hello everybody,
I wrote:
as discussed before, we want to switch from the old git server to more powerful soft- and hardware. We will move the U-Boot master repository and all custodian repositories to gitlab.
...
The switch will take place as follows:
We will create user accounts for all custodians at gitlab.denx.de You will receive an e-mail notification with your login credentials. We will start with this this afternoon (CEST), so if you have not received such an e-mail by tomorrow morning, please let us know.
We will block your SSH keys on the old git server, thus effectively turning the custodian repositories into read-only mode. Custodians will not be able to push any new stuff to the old repositories any more.
This phase will start when all custodian repositories have been created, but in no case before 12:00 p. m. (noon) CEST. the next steps will follow as quickly as possible, ideally only a few minutes later.
The old repository will be cloned to the new gitlab server. This should not take long. We don't expect any long interruption. You wanted to have another cup of coffee anyway :-)
The custodian can resume work using the gitlab server, as soon as he can "see" his repository there. Tom should already be prepared to pull from the gitlab repos.
All these steps have been completed by now. All custodians should be able to access the new repositories now, and use all teh gitlab features that are enabled for this project (including CI runners).
The U-Boot web pages (especially the source code links and the custodian page) have been updated to reference the new gitlab repositories.
By now, the gitlab repos represent the official and active mainline / custodian repositories.
After all custodians have been moved, URL rewrite rules will be activated, and the DNS will be changed, so that the old URLs will still be working, though only for read-only access.
Note: this last step is the most error-prone one. It is likely that the rewrite roles are incomplete at the beginning, and/or incorrect for a few special cases. Please be patient and report such errors with enough detail to reproduce, then we will fix them.
This is what we will be working on now.
Thanks for your patience!
Best regards,
Wolfgang Denk
On Tue, Jun 18, 2019 at 3:47 PM Wolfgang Denk wd@denx.de wrote:
...
- The custodian can resume work using the gitlab server, as soon as he can "see" his repository there. Tom should already be prepared to pull from the gitlab repos.
All these steps have been completed by now. All custodians should be able to access the new repositories now, and use all teh gitlab features that are enabled for this project (including CI runners).
works for me and the MIPS repository, thanks.
The U-Boot web pages (especially the source code links and the custodian page) have been updated to reference the new gitlab repositories.
By now, the gitlab repos represent the official and active mainline / custodian repositories.
should we update the source links in MAINTAINERS file as well?
Dear Daniel,
In message CACUy__U=Xn5+RJ=Z5HRFDZYpbyQf0Ffow3NW_71RQpyyu54SXA@mail.gmail.com you wrote:
All these steps have been completed by now. All custodians should be able to access the new repositories now, and use all teh gitlab features that are enabled for this project (including CI runners).
works for me and the MIPS repository, thanks.
Thanks for the confirmation.
should we update the source links in MAINTAINERS file as well?
Yes, of coure. Volunteers welcome :-)
Best regards,
Wolfgang Denk
On Tue, Jun 18, 2019 at 10:50 PM Wolfgang Denk wd@denx.de wrote:
Dear Daniel,
In message CACUy__U=Xn5+RJ=Z5HRFDZYpbyQf0Ffow3NW_71RQpyyu54SXA@mail.gmail.com you wrote:
All these steps have been completed by now. All custodians should be able to access the new repositories now, and use all teh gitlab features that are enabled for this project (including CI runners).
works for me and the MIPS repository, thanks.
Thanks for the confirmation.
should we update the source links in MAINTAINERS file as well?
Yes, of coure. Volunteers welcome :-)
Here we go :) http://patchwork.ozlabs.org/patch/1118071/
Regards, Bin
Hi Wolfgang
On 6/18/19 4:04 PM, Daniel Schwierzeck wrote:
On Tue, Jun 18, 2019 at 3:47 PM Wolfgang Denk wd@denx.de wrote: ...
- The custodian can resume work using the gitlab server, as soon as he can "see" his repository there. Tom should already be prepared to pull from the gitlab repos.
All these steps have been completed by now. All custodians should be able to access the new repositories now, and use all teh gitlab features that are enabled for this project (including CI runners).
works for me and the MIPS repository, thanks.
It works also for STM custodian.
Thanks
Patrice
The U-Boot web pages (especially the source code links and the custodian page) have been updated to reference the new gitlab repositories.
By now, the gitlab repos represent the official and active mainline / custodian repositories.
should we update the source links in MAINTAINERS file as well?
On Tue, Jun 18, 2019 at 8:47 AM Wolfgang Denk wd@denx.de wrote:
Hello everybody,
I wrote:
as discussed before, we want to switch from the old git server to more powerful soft- and hardware. We will move the U-Boot master repository and all custodian repositories to gitlab.
...
The switch will take place as follows:
We will create user accounts for all custodians at gitlab.denx.de You will receive an e-mail notification with your login credentials. We will start with this this afternoon (CEST), so if you have not received such an e-mail by tomorrow morning, please let us know.
We will block your SSH keys on the old git server, thus effectively turning the custodian repositories into read-only mode. Custodians will not be able to push any new stuff to the old repositories any more.
This phase will start when all custodian repositories have been created, but in no case before 12:00 p. m. (noon) CEST. the next steps will follow as quickly as possible, ideally only a few minutes later.
The old repository will be cloned to the new gitlab server. This should not take long. We don't expect any long interruption. You wanted to have another cup of coffee anyway :-)
The custodian can resume work using the gitlab server, as soon as he can "see" his repository there. Tom should already be prepared to pull from the gitlab repos.
All these steps have been completed by now. All custodians should be able to access the new repositories now, and use all teh gitlab features that are enabled for this project (including CI runners).
I tried to push to u-boot-net an got this...
------8<------
$ git push -u -v net-push master Pushing to git@gitlab.denx.de:u-boot/custodians/u-boot-net.git gitaly-receive-pack: fatal: error: %v fatal: Could not read from remote repository.
Please make sure you have the correct access rights and the repository exists.
------>8-------
SSH seems to be fine, but something about the path is no good. Can someone check this on the server?
Thanks, -Joe
The U-Boot web pages (especially the source code links and the custodian page) have been updated to reference the new gitlab repositories.
By now, the gitlab repos represent the official and active mainline / custodian repositories.
After all custodians have been moved, URL rewrite rules will be activated, and the DNS will be changed, so that the old URLs will still be working, though only for read-only access.
Note: this last step is the most error-prone one. It is likely that the rewrite roles are incomplete at the beginning, and/or incorrect for a few special cases. Please be patient and report such errors with enough detail to reproduce, then we will fix them.
This is what we will be working on now.
Thanks for your patience!
Best regards,
Wolfgang Denk
-- DENX Software Engineering GmbH, Managing Director: Wolfgang Denk HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de Living on Earth may be expensive, but it includes an annual free trip around the Sun. _______________________________________________ U-Boot-Custodians mailing list U-Boot-Custodians@lists.denx.de https://lists.denx.de/listinfo/u-boot-custodians
On 6/18/19 10:08 PM, Joe Hershberger wrote:
On Tue, Jun 18, 2019 at 8:47 AM Wolfgang Denk wd@denx.de wrote:
Hello everybody,
I wrote:
as discussed before, we want to switch from the old git server to more powerful soft- and hardware. We will move the U-Boot master repository and all custodian repositories to gitlab.
...
The switch will take place as follows:
We will create user accounts for all custodians at gitlab.denx.de You will receive an e-mail notification with your login credentials. We will start with this this afternoon (CEST), so if you have not received such an e-mail by tomorrow morning, please let us know.
We will block your SSH keys on the old git server, thus effectively turning the custodian repositories into read-only mode. Custodians will not be able to push any new stuff to the old repositories any more.
This phase will start when all custodian repositories have been created, but in no case before 12:00 p. m. (noon) CEST. the next steps will follow as quickly as possible, ideally only a few minutes later.
The old repository will be cloned to the new gitlab server. This should not take long. We don't expect any long interruption. You wanted to have another cup of coffee anyway :-)
The custodian can resume work using the gitlab server, as soon as he can "see" his repository there. Tom should already be prepared to pull from the gitlab repos.
All these steps have been completed by now. All custodians should be able to access the new repositories now, and use all teh gitlab features that are enabled for this project (including CI runners).
I tried to push to u-boot-net an got this...
------8<------
$ git push -u -v net-push master Pushing to git@gitlab.denx.de:u-boot/custodians/u-boot-net.git
Just use https, e.g
git remote set-url net \ https://gitlab.denx.de/u-boot/custodians/u-boot-net.git
And in .gitconfig put your email address:
[credential "https://gitlab.denx.de"] username = joe.hershberger@gmail.com
At least this setup worked for EFI.
Best reards
Heinrich
gitaly-receive-pack: fatal: error: %v fatal: Could not read from remote repository.
Please make sure you have the correct access rights and the repository exists.
------>8-------
SSH seems to be fine, but something about the path is no good. Can someone check this on the server?
Thanks, -Joe
The U-Boot web pages (especially the source code links and the custodian page) have been updated to reference the new gitlab repositories.
By now, the gitlab repos represent the official and active mainline / custodian repositories.
After all custodians have been moved, URL rewrite rules will be activated, and the DNS will be changed, so that the old URLs will still be working, though only for read-only access.
Note: this last step is the most error-prone one. It is likely that the rewrite roles are incomplete at the beginning, and/or incorrect for a few special cases. Please be patient and report such errors with enough detail to reproduce, then we will fix them.
This is what we will be working on now.
Thanks for your patience!
Best regards,
Wolfgang Denk
-- DENX Software Engineering GmbH, Managing Director: Wolfgang Denk HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de Living on Earth may be expensive, but it includes an annual free trip around the Sun. _______________________________________________ U-Boot-Custodians mailing list U-Boot-Custodians@lists.denx.de https://lists.denx.de/listinfo/u-boot-custodians
U-Boot-Custodians mailing list U-Boot-Custodians@lists.denx.de https://lists.denx.de/listinfo/u-boot-custodians
On Tue, 18 Jun 2019 22:49:44 +0200 Heinrich Schuchardt xypron.glpk@gmx.de wrote: ...
I tried to push to u-boot-net an got this...
------8<------
$ git push -u -v net-push master Pushing to git@gitlab.denx.de:u-boot/custodians/u-boot-net.git
Just use https, e.g
git remote set-url net \ https://gitlab.denx.de/u-boot/custodians/u-boot-net.git
Something went wrong when importing u-boot-net repository, this repository is empty on gitlab server. This might be the reason. Cloning via https doesn't work, too.
@Harald: could you please have a look?
Thanks, Anatolij
On Tue, 2019-06-18 at 22:49 +0200, Heinrich Schuchardt wrote:
Just use https, e.g
git remote set-url net \ https://gitlab.denx.de/u-boot/custodians/u-boot-net.git
And in .gitconfig put your email address:
[credential "https://gitlab.denx.de"] username = joe.hershberger@gmail.com
At least this setup worked for EFI.
SSH should work just fine as well if you add your SSH key to your account. You can do so at https://gitlab.denx.de/profile/keys.
The issue for Joe was that my script did not import his tree correctly for some reason. I have fixed it now.
On Wed, Jun 19, 2019 at 8:33 AM Harald Seiler hws@denx.de wrote:
On Tue, 2019-06-18 at 22:49 +0200, Heinrich Schuchardt wrote:
Just use https, e.g
git remote set-url net \ https://gitlab.denx.de/u-boot/custodians/u-boot-net.git
And in .gitconfig put your email address:
[credential "https://gitlab.denx.de"] username = joe.hershberger@gmail.com
At least this setup worked for EFI.
SSH should work just fine as well if you add your SSH key to your account. You can do so at https://gitlab.denx.de/profile/keys.
The issue for Joe was that my script did not import his tree correctly for some reason. I have fixed it now.
Working for me now. Thanks Harald!
-Joe
-- Harald
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: +49-8142-66989-62 Fax: +49-8142-66989-80 Email: hws@denx.de
Hi Joe,
On Tue, 2019-06-18 at 15:08 -0500, Joe Hershberger wrote:
I tried to push to u-boot-net an got this...
------8<------
$ git push -u -v net-push master Pushing to git@gitlab.denx.de:u-boot/custodians/u-boot-net.git gitaly-receive-pack: fatal: error: %v fatal: Could not read from remote repository.
Please make sure you have the correct access rights and the repository exists.
------>8-------
SSH seems to be fine, but something about the path is no good. Can someone check this on the server?
Sorry, there were some issues with the import. It should be fixed now. If you added your SSH key, you should be able to access it.
Thanks, -Joe
Hi Wolfgang,
On Tue, Jun 18, 2019 at 3:46 PM Wolfgang Denk wd@denx.de wrote:
Hello everybody,
I wrote:
as discussed before, we want to switch from the old git server to more powerful soft- and hardware. We will move the U-Boot master repository and all custodian repositories to gitlab.
...
The switch will take place as follows:
We will create user accounts for all custodians at gitlab.denx.de You will receive an e-mail notification with your login credentials. We will start with this this afternoon (CEST), so if you have not received such an e-mail by tomorrow morning, please let us know.
We will block your SSH keys on the old git server, thus effectively turning the custodian repositories into read-only mode. Custodians will not be able to push any new stuff to the old repositories any more.
This phase will start when all custodian repositories have been created, but in no case before 12:00 p. m. (noon) CEST. the next steps will follow as quickly as possible, ideally only a few minutes later.
The old repository will be cloned to the new gitlab server. This should not take long. We don't expect any long interruption. You wanted to have another cup of coffee anyway :-)
The custodian can resume work using the gitlab server, as soon as he can "see" his repository there. Tom should already be prepared to pull from the gitlab repos.
All these steps have been completed by now. All custodians should be able to access the new repositories now, and use all teh gitlab features that are enabled for this project (including CI runners).
The U-Boot web pages (especially the source code links and the custodian page) have been updated to reference the new gitlab repositories.
By now, the gitlab repos represent the official and active mainline / custodian repositories.
I have not received an e-mail about the MPC83xx repository yet, so I think something did not quite work as expected. Could you have a look?
After all custodians have been moved, URL rewrite rules will be activated, and the DNS will be changed, so that the old URLs will still be working, though only for read-only access.
Note: this last step is the most error-prone one. It is likely that the rewrite roles are incomplete at the beginning, and/or incorrect for a few special cases. Please be patient and report such errors with enough detail to reproduce, then we will fix them.
This is what we will be working on now.
Thanks for your patience!
Best regards,
Wolfgang Denk
Best regards, Mario
Hi Wolfgang,
On Tue, Jun 18, 2019 at 03:46:56PM +0200, Wolfgang Denk wrote:
Hello everybody,
I wrote:
as discussed before, we want to switch from the old git server to more powerful soft- and hardware. We will move the U-Boot master repository and all custodian repositories to gitlab.
...
The switch will take place as follows:
We will create user accounts for all custodians at gitlab.denx.de You will receive an e-mail notification with your login credentials. We will start with this this afternoon (CEST), so if you have not received such an e-mail by tomorrow morning, please let us know.
We will block your SSH keys on the old git server, thus effectively turning the custodian repositories into read-only mode. Custodians will not be able to push any new stuff to the old repositories any more.
This phase will start when all custodian repositories have been created, but in no case before 12:00 p. m. (noon) CEST. the next steps will follow as quickly as possible, ideally only a few minutes later.
The old repository will be cloned to the new gitlab server. This should not take long. We don't expect any long interruption. You wanted to have another cup of coffee anyway :-)
The custodian can resume work using the gitlab server, as soon as he can "see" his repository there. Tom should already be prepared to pull from the gitlab repos.
All these steps have been completed by now. All custodians should be able to access the new repositories now, and use all teh gitlab features that are enabled for this project (including CI runners).
The U-Boot web pages (especially the source code links and the custodian page) have been updated to reference the new gitlab repositories.
By now, the gitlab repos represent the official and active mainline / custodian repositories.
After all custodians have been moved, URL rewrite rules will be activated, and the DNS will be changed, so that the old URLs will still be working, though only for read-only access.
Note: this last step is the most error-prone one. It is likely that the rewrite roles are incomplete at the beginning, and/or incorrect for a few special cases. Please be patient and report such errors with enough detail to reproduce, then we will fix them.
This is what we will be working on now.
Thanks for your patience!
Ack ! Many thanks !
Angelo Dureghello (m68k)
Best regards,
Wolfgang Denk
-- DENX Software Engineering GmbH, Managing Director: Wolfgang Denk HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de Living on Earth may be expensive, but it includes an annual free trip around the Sun. _______________________________________________ U-Boot-Custodians mailing list U-Boot-Custodians@lists.denx.de https://lists.denx.de/listinfo/u-boot-custodians
participants (10)
-
Anatolij Gustschin -
Angelo Dureghello -
Bin Meng -
Daniel Schwierzeck -
Harald Seiler -
Heinrich Schuchardt -
Joe Hershberger -
Mario Six -
Patrice CHOTARD -
Wolfgang Denk