Switching to gitlab.denx.de
Hello everybody,
Quoted 3 lines · 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.
...
Quoted 18 lines
The switch will take place as follows:
1. 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.
2. 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.
Quoted 7 lines
3. 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 :-)
4. 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.
Quoted 9 lines
5. 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
Signature · 5 lines
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 at denx.de Living on Earth may be expensive, but it includes an annual free trip around the Sun.
Quoted 1 line · Wolfgang Denk
...
Quoted 8 lines
Quoted 4 lines
4. 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.
Quoted 7 lines
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?
Signature · 1 line
- Daniel
Dear Daniel,
Quoted 6 lines · In message <CACUy__U=Xn5+RJ=Z5HRFDZYpbyQf0Ffow3NW_71RQpyyu54SXA@mail.gmail.com>…
Quoted 4 lines
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.
Quoted 1 line
should we update the source links in
MAINTAINERSfile as well?
Yes, of coure. Volunteers welcome :-)
Best regards,
Wolfgang Denk
Signature · 5 lines
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 at denx.de The only thing necessary for the triumph of evil is for good men to do nothing. - Edmund Burke
Quoted 9 lines · Wolfgang Denk
Dear Daniel,
Quoted 5 lines · In message <CACUy__U=Xn5+RJ=Z5HRFDZYpbyQf0Ffow3NW_71RQpyyu54SXA@mail.gmail.com>…
Quoted 4 lines
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).
Quoted 8 lines
Quoted 1 line
works for me and the MIPS repository, thanks.
Thanks for the confirmation.
Quoted 1 line
should we update the source links in
MAINTAINERSfile as well?Yes, of coure. Volunteers welcome :-)
Here we go :)
http://patchwork.ozlabs.org/patch/1118071/
Regards,
Bin
Hi Wolfgang
Quoted 9 lines · Daniel Schwierzeck
On Tue, Jun 18, 2019 at 3:47 PM Wolfgang Denk <[email protected]> wrote:
...Quoted 6 lines
Quoted 3 lines
4. 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
Quoted 9 lines
Quoted 7 lines
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
MAINTAINERSfile as well?
Quoted 31 lines · Wolfgang Denk
Hello everybody,
Quoted 3 lines · 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.
...
Quoted 22 lines
The switch will take place as follows:
1. 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.
2. 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.
3. 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 :-)
Quoted 7 lines
Quoted 3 lines
4. 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 [email protected]: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
Quoted 36 lines
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.
Quoted 9 lines
5. 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 at 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 at lists.denx.de
https://lists.denx.de/listinfo/u-boot-custodians
Quoted 40 lines · Joe Hershberger
Quoted 31 lines · Wolfgang Denk
Hello everybody,
Quoted 3 lines · 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.
...
Quoted 22 lines
The switch will take place as follows:
1. 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.
2. 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.
3. 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 :-)
Quoted 7 lines
Quoted 3 lines
4. 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).
Quoted 6 lines
I tried to push to u-boot-net an got this...
------8<------
$ git push -u -v net-push master Pushing to git at 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 at gmail.com
At least this setup worked for EFI.
Best reards
Heinrich
Quoted 55 lines
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,
-JoeQuoted 26 lines
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.
Quoted 9 lines
5. 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
Quoted 10 lines
--
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 at 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 at lists.denx.de
https://lists.denx.de/listinfo/u-boot-custodians_______________________________________________
U-Boot-Custodians mailing list
U-Boot-Custodians at lists.denx.de
https://lists.denx.de/listinfo/u-boot-custodians
On Tue, 18 Jun 2019 22:49:44 +0200
Heinrich Schuchardt xypron.glpk at gmx.de wrote:
...
Quoted 11 lines
Quoted 6 lines
I tried to push to u-boot-net an got this...
------8<------
$ git push -u -v net-push master Pushing to git at gitlab.denx.de:u-boot/custodians/u-boot-net.gitJust 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
Quoted 11 lines · Heinrich Schuchardt
Just use https, e.g
git remote set-url net \
https://gitlab.denx.de/u-boot/custodians/u-boot-net.gitAnd in .gitconfig put your email address:
[credential "https://gitlab.denx.de"]
username = joe.hershberger at gmail.comAt 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.
Signature · 5 lines
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 at denx.de
Quoted 12 lines · Harald Seiler
Quoted 10 lines · Heinrich Schuchardt
Just use https, e.g
git remote set-url net \
https://gitlab.denx.de/u-boot/custodians/u-boot-net.gitAnd in .gitconfig put your email address:
[credential "https://gitlab.denx.de"]
username = joe.hershberger at gmail.com
Quoted 7 lines
Quoted 1 line
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
Quoted 7 lines
--
HaraldDENX 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 at denx.de
Hi Joe,
Quoted 10 lines · Joe Hershberger
I tried to push to u-boot-net an got this...
------8<------
$ git push -u -v net-push master Pushing to git at gitlab.denx.de:u-boot/custodians/u-boot-net.git gitaly-receive-pack: fatal: error: %v fatal: Could not read from remote repository.
Quoted 7 lines
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.
Quoted 4 lines
Thanks,
-Joe
Signature · 5 lines
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 at denx.de
Hi Wolfgang,
Quoted 39 lines · Wolfgang Denk
Hello everybody,
Quoted 3 lines · 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.
...
Quoted 18 lines
The switch will take place as follows:
1. 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.
2. 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.
Quoted 7 lines
3. 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 :-)
4. 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).
Quoted 7 lines
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?
Quoted 11 lines
Quoted 10 lines
5. 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.
Quoted 8 lines
This is what we will be working on now.
Thanks for your patience!
Best regards,
Wolfgang Denk
Best regards,
Mario
Hi Wolfgang,
Quoted 56 lines · Wolfgang Denk
Hello everybody,
Quoted 3 lines · 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.
...
Quoted 18 lines
The switch will take place as follows:
1. 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.
2. 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.
Quoted 7 lines
3. 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 :-)
4. 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.
Quoted 9 lines
5. 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.
Quoted 4 lines
This is what we will be working on now.
Thanks for your patience!
Ack ! Many thanks !
Angelo Dureghello (m68k)
Quoted 14 lines
Best regards,
Wolfgang Denk
Signature · 9 lines
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 at 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 at lists.denx.de https://lists.denx.de/listinfo/u-boot-custodians
A message that is not in the archive (sent off-list or not yet received): [email protected]
Hi Wolfgang
Quoted 30 lines
Hello everybody,
Quoted 3 lines · 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.
...
Quoted 22 lines
The switch will take place as follows:
1. 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.
2. 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.
3. 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 :-)
Quoted 7 lines
Quoted 3 lines
4. 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).
It works for RISC-V custodian now.
There is another problem may need your help about NDS32 tree. I am responsible for NDS32 repo since 2014. But the maintainer is still Macpaul Lin on the list.
Can you create an account for me to access the U-Boot / Custodians / NDS32 tree project ?
Thanks
Rick