[U-Boot] [ANNOUNCEMENT] Switching to gitlab.denx.de
Hello everybody,
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 new URLs for cloning will become
https://gitlab.denx.de/u-boot/u-boot
for the master repository and
https://gitlab.denx.de/u-boot/custodians/u-boot-XXX
for the XXX custodian repo.
Note:
a) These are the Web URLs, from where you also can clone. Feel free to add a ".git" to these URLs. b) SSH access for the custodians is available under git@gitlab.denx.de:u-boot/custodians/u-boot-XXX.git c) git:// access is not available yet; this depends on the URL rewrite rules and DNS changes and will be added later - ASAP, see below.
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 :-)
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.
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.
6. Everybody is happy.
Hopefully.
OK, at least that's the theory. If there are problems please let us know (me and Harald hws@denx.de) and we will do our best to fix the issues as fast as possible.
Thanks, and please keep your finger's crossed.
Best regards,
Wolfgang Denk
-----Original Message----- From: U-Boot-Custodians u-boot-custodians-bounces@lists.denx.de On Behalf Of Wolfgang Denk Sent: Monday, June 17, 2019 8:12 PM To: u-boot-custodians@lists.denx.de Cc: u-boot@lists.denx.de; hws@denx.de Subject: [U-Boot-Custodians] [ANNOUNCEMENT] Switching to gitlab.denx.de
Hello everybody,
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 new URLs for cloning will become
https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fg itlab.denx.de%2Fu-boot%2Fu- boot&data=02%7C01%7Cprabhakar.kushwaha%40nxp.com%7C785a421de 9484244e28608d6f3320075%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7 C0%7C636963793415718080&sdata=IVw37sZDqzUfs6SFnjNqLMmAX6TCP %2BhbhcAm%2Fj2UeAY%3D&reserved=0
for the master repository and
https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fg itlab.denx.de%2Fu-boot%2Fcustodians%2Fu-boot- XXX&data=02%7C01%7Cprabhakar.kushwaha%40nxp.com%7C785a421de9 484244e28608d6f3320075%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C 0%7C636963793415728075&sdata=ix1jVdvV0WVpH%2BFO%2FeLwcrjlLwL 5HcyEv3AXg0UhmVQ%3D&reserved=0
for the XXX custodian repo.
Note:
a) These are the Web URLs, from where you also can clone. Feel free to add a ".git" to these URLs. b) SSH access for the custodians is available under git@gitlab.denx.de:u-boot/custodians/u-boot-XXX.git c) git:// access is not available yet; this depends on the URL rewrite rules and DNS changes and will be added later - ASAP, see below.
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.
I still not received any e-mail notification related to custodian account on gitlab.denx.de
Or
I am asking too early.
--pk
Hi Wolfgang
On 6/17/19 4:42 PM, Wolfgang Denk wrote:
Hello everybody,
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 new URLs for cloning will become
https://gitlab.denx.de/u-boot/u-boot
for the master repository and
https://gitlab.denx.de/u-boot/custodians/u-boot-XXX
for the XXX custodian repo.
Note:
a) These are the Web URLs, from where you also can clone. Feel free to add a ".git" to these URLs. b) SSH access for the custodians is available under git@gitlab.denx.de:u-boot/custodians/u-boot-XXX.git c) git:// access is not available yet; this depends on the URL rewrite rules and DNS changes and will be added later - ASAP, see below.
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.
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.
Everybody is happy.
Hopefully.
OK, at least that's the theory. If there are problems please let us know (me and Harald hws@denx.de) and we will do our best to fix the issues as fast as possible.
Thanks, and please keep your finger's crossed.
Best regards,
Wolfgang Denk
Patrick Delaunay and i are the STM32 MCU/MPU's U-Boot Maintainers.
Recently Tom let us managed STM32 pull requests from our github temporary waiting for the gitlab migration.
Previously STM-U-boot custodian tree was used but inactive since 2013.
If this repo has been migrated on gitlab, could we get access to it and use it for STM32 ?
Thanks
Patrice
Dear Patrice,
In message 561e5fe4-3b32-e45f-ed5d-100c51a7f5b3@st.com you wrote:
Patrick Delaunay and i are the STM32 MCU/MPU's U-Boot Maintainers.
The MAINTAINERS file lists also Christophe Kerello; is he also still active?
Previously STM-U-boot custodian tree was used but inactive since 2013.
Why?
If this repo has been migrated on gitlab, could we get access to it and use it for STM32 ?
Yes, of course. Just the two of you, or also Christophe Kerello?
And please be so kind and update the custodian web page htat it lists the correct names and addresses.
[I will update re repository URLs globally ASAP.]
Best regards,
Wolfgang Denk
On 6/18/19 9:46 AM, Wolfgang Denk wrote:
Dear Patrice,
In message 561e5fe4-3b32-e45f-ed5d-100c51a7f5b3@st.com you wrote:
Patrick Delaunay and i are the STM32 MCU/MPU's U-Boot Maintainers.
The MAINTAINERS file lists also Christophe Kerello; is he also still active?
Christophe will not have maintainer activities. We will remove its name from
MAINTAINERS file.
Previously STM-U-boot custodian tree was used but inactive since 2013.
Why?
Vipin Kumar left the company and no upstream activity was continued.
When we start to upstream STM32 U-boot 2 years ago, we asked to Tom if we can reused this repo and
managed this custodian, but he preferred to managed itself.
But recently, the amount of STM32 patches increased and Tom accepted to rely on us and on our pull request.
If this repo has been migrated on gitlab, could we get access to it and use it for STM32 ?
Yes, of course. Just the two of you, or also Christophe Kerello?
Just Patrick Delaunay and me.
And please be so kind and update the custodian web page htat it lists the correct names and addresses.
Yes of course. when we will get access we will update the custodian description.
Thanks
Patrice
[I will update re repository URLs globally ASAP.]
Best regards,
Wolfgang Denk
On Tue, Jun 18, 2019 at 08:49:57AM +0000, Patrice CHOTARD wrote:
On 6/18/19 9:46 AM, Wolfgang Denk wrote:
Dear Patrice,
In message 561e5fe4-3b32-e45f-ed5d-100c51a7f5b3@st.com you wrote:
Patrick Delaunay and i are the STM32 MCU/MPU's U-Boot Maintainers.
The MAINTAINERS file lists also Christophe Kerello; is he also still active?
Christophe will not have maintainer activities. We will remove its name from
MAINTAINERS file.
Previously STM-U-boot custodian tree was used but inactive since 2013.
Why?
Vipin Kumar left the company and no upstream activity was continued.
When we start to upstream STM32 U-boot 2 years ago, we asked to Tom if we can reused this repo and
managed this custodian, but he preferred to managed itself.
But recently, the amount of STM32 patches increased and Tom accepted to rely on us and on our pull request.
If this repo has been migrated on gitlab, could we get access to it and use it for STM32 ?
Yes, of course. Just the two of you, or also Christophe Kerello?
Just Patrick Delaunay and me.
And please be so kind and update the custodian web page htat it lists the correct names and addresses.
Yes of course. when we will get access we will update the custodian description.
For the record, I endorse Patrice's request, thanks!
On 6/18/19 2:00 PM, Tom Rini wrote:
On Tue, Jun 18, 2019 at 08:49:57AM +0000, Patrice CHOTARD wrote:
On 6/18/19 9:46 AM, Wolfgang Denk wrote:
Dear Patrice,
In message 561e5fe4-3b32-e45f-ed5d-100c51a7f5b3@st.com you wrote:
Patrick Delaunay and i are the STM32 MCU/MPU's U-Boot Maintainers.
The MAINTAINERS file lists also Christophe Kerello; is he also still active?
Christophe will not have maintainer activities. We will remove its name from
MAINTAINERS file.
Previously STM-U-boot custodian tree was used but inactive since 2013.
Why?
Vipin Kumar left the company and no upstream activity was continued.
When we start to upstream STM32 U-boot 2 years ago, we asked to Tom if we can reused this repo and
managed this custodian, but he preferred to managed itself.
But recently, the amount of STM32 patches increased and Tom accepted to rely on us and on our pull request.
If this repo has been migrated on gitlab, could we get access to it and use it for STM32 ?
Yes, of course. Just the two of you, or also Christophe Kerello?
Just Patrick Delaunay and me.
And please be so kind and update the custodian web page htat it lists the correct names and addresses.
Yes of course. when we will get access we will update the custodian description.
For the record, I endorse Patrice's request, thanks!
ACK
On Mon, Jun 17, 2019 at 04:42:09PM +0200, Wolfgang Denk wrote:
Hello everybody,
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 new URLs for cloning will become
https://gitlab.denx.de/u-boot/u-boot
for the master repository and
https://gitlab.denx.de/u-boot/custodians/u-boot-XXX
for the XXX custodian repo.
On a related note, where do we go for a new repository? I'd like to get "u-boot-gitlab-ci-runner" configured so I can more easily publish the Dockerfile (and license, etc) for the gitlab-ci runner container. Thanks!
On Tue, 2019-06-18 at 12:58 -0400, Tom Rini wrote:
On a related note, where do we go for a new repository? I'd like to get "u-boot-gitlab-ci-runner" configured so I can more easily publish the Dockerfile (and license, etc) for the gitlab-ci runner container. Thanks!
I created a repo for you: https://gitlab.denx.de/u-boot/gitlab-ci-runner
On Wed, Jun 19, 2019 at 03:14:42PM +0200, Harald Seiler wrote:
On Tue, 2019-06-18 at 12:58 -0400, Tom Rini wrote:
On a related note, where do we go for a new repository? I'd like to get "u-boot-gitlab-ci-runner" configured so I can more easily publish the Dockerfile (and license, etc) for the gitlab-ci runner container. Thanks!
I created a repo for you: https://gitlab.denx.de/u-boot/gitlab-ci-runner
Thanks!
Hi Wolfgang,
-----Original Message----- From: U-Boot [mailto:u-boot-bounces@lists.denx.de] On Behalf Of Wolfgang Denk Sent: 2019年6月17日 22:42 To: u-boot-custodians@lists.denx.de Cc: u-boot@lists.denx.de; Tom Rini trini@konsulko.com Subject: [U-Boot] [ANNOUNCEMENT] Switching to gitlab.denx.de
Hello everybody,
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 new URLs for cloning will become
https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgi tlab.denx.de%2Fu-boot%2Fu-boot&data=02%7C01%7CPeng.Fan%40nxp .com%7C88eabcbc2b404ad26f7808d6f3320a40%7C686ea1d3bc2b4c6fa92cd 99c5c301635%7C0%7C0%7C636963793613197298&sdata=viFBHEPBrkx 3akygAqknCC0tkkgr%2BCn%2Bz6hwrr1wDuk%3D&reserved=0
for the master repository and
https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgi tlab.denx.de%2Fu-boot%2Fcustodians%2Fu-boot-XXX&data=02%7C01% 7CPeng.Fan%40nxp.com%7C88eabcbc2b404ad26f7808d6f3320a40%7C686e a1d3bc2b4c6fa92cd99c5c301635%7C0%7C0%7C636963793613197298&am p;sdata=LSKpzUlxyG1ESfw0OlLe%2FuSxUzO7KQsgUzcdfnlWvuc%3D&re served=0
for the XXX custodian repo.
Note:
a) These are the Web URLs, from where you also can clone. Feel free to add a ".git" to these URLs. b) SSH access for the custodians is available under git@gitlab.denx.de:u-boot/custodians/u-boot-XXX.git c) git:// access is not available yet; this depends on the URL rewrite rules and DNS changes and will be added later - ASAP, see below.
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.
I did not receive email, could you please check?
Thanks, Peng.
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.
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.
Everybody is happy.
Hopefully.
OK, at least that's the theory. If there are problems please let us know (me and Harald hws@denx.de) and we will do our best to fix the issues as fast as possible.
Thanks, and please keep your finger's crossed.
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 When choosing between two evils, I always like to take the one I've never tried before. -- Mae West, "Klondike Annie" _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.d enx.de%2Flistinfo%2Fu-boot&data=02%7C01%7CPeng.Fan%40nxp.com %7C88eabcbc2b404ad26f7808d6f3320a40%7C686ea1d3bc2b4c6fa92cd99c5 c301635%7C0%7C0%7C636963793613197298&sdata=70p3de%2F4J1O sXGKG8yiMGOKjfZBbernEstne%2Freg0Ss%3D&reserved=0
Hello Peng,
On Thu, 2019-06-20 at 06:42 +0000, Peng Fan wrote:
Hi Wolfgang,
[...]
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.
I did not receive email, could you please check?
You are not listed as custodian for any of the trees in either the wiki or MAINTAINERS. Can you please verify to me which trees you should have access to?
Thanks, Peng.
On Mon, Jun 24, 2019 at 03:04:41PM +0200, Harald Seiler wrote:
Hello Peng,
On Thu, 2019-06-20 at 06:42 +0000, Peng Fan wrote:
Hi Wolfgang,
[...]
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.
I did not receive email, could you please check?
You are not listed as custodian for any of the trees in either the wiki or MAINTAINERS. Can you please verify to me which trees you should have access to?
Hey now: MMC M: Peng Fan peng.fan@nxp.com S: Maintained T: git https://gitlab.denx.de/u-boot/custodians/u-boot-mmc.git F: drivers/mmc/
is in MAINTAINERS currently, btw. Maybe a few others got missed too? Thanks!
Hi Wolfgang,
On Mon, Jun 17, 2019 at 8:12 PM Wolfgang Denk wd@denx.de wrote:
Hello everybody,
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 new URLs for cloning will become
https://gitlab.denx.de/u-boot/u-bootfor the master repository and
https://gitlab.denx.de/u-boot/custodians/u-boot-XXXfor the XXX custodian repo.
Note:
a) These are the Web URLs, from where you also can clone. Feel free to add a ".git" to these URLs. b) SSH access for the custodians is available under git@gitlab.denx.de:u-boot/custodians/u-boot-XXX.git c) git:// access is not available yet; this depends on the URL rewrite rules and DNS changes and will be added later - ASAP, see below.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.
Sorry for late response. I have seen u-boot-spi/sunxi were crated on new gitlab but I wouldn't receive any mail on this notification about SSH keys move. Any help on this?
Jagan.
Hi Jagan,
On Mon, Jun 24, 2019 at 5:35 PM Jagan Teki jagan@amarulasolutions.com wrote:
Hi Wolfgang,
On Mon, Jun 17, 2019 at 8:12 PM Wolfgang Denk wd@denx.de wrote:
Hello everybody,
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 new URLs for cloning will become
https://gitlab.denx.de/u-boot/u-bootfor the master repository and
https://gitlab.denx.de/u-boot/custodians/u-boot-XXXfor the XXX custodian repo.
Note:
a) These are the Web URLs, from where you also can clone. Feel free to add a ".git" to these URLs. b) SSH access for the custodians is available under git@gitlab.denx.de:u-boot/custodians/u-boot-XXX.git c) git:// access is not available yet; this depends on the URL rewrite rules and DNS changes and will be added later - ASAP, see below.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.
Sorry for late response. I have seen u-boot-spi/sunxi were crated on new gitlab but I wouldn't receive any mail on this notification about SSH keys move. Any help on this?
I am not sure what email notification about SSH keys move as you mentioned. But you can add your own SSH keys in gitlab by yourself.
Regards, Bin
participants (9)
-
Bin Meng -
Harald Seiler -
Jagan Teki -
Marek Vasut -
Patrice CHOTARD -
Peng Fan -
Prabhakar Kushwaha -
Tom Rini -
Wolfgang Denk