The `git svn` repos we published on GitHub are going to be deleted once we get proper 1st class git support in Arch.
...and sorry again, I slightly misread what was said, I should've replied:
WRT the concerns expressed in post #1 I don't think gitlab.com is much better than github.com.
Arch currently uses svn for its packaging repos. These svn repos are converted by `git svn` to a git repo which was until recently published on the same box that hosted the svn repos. The box is the oldest box in Arch and was beginning to struggle under the load and so we had to move the git repo hosting somewhere else.
Why did we put it on GitHub and not our GitLab? We tested that but we saw GitLab struggling mightily under the load of the massive repos as well (combined 1M commits!). We decided to not spend too much time on it as there are ongoing efforts to convert our packaging repos to direct git but this a slow process.
Make no mistake: No one ever commits directly to the git repos currently. They are read-only mirrors that we provide solely for user and tooling convenience. The `git svn` repos we published on GitHub are going to be deleted once we get proper 1st class git support in Arch. There wasn't news on this because this isn't newsworthy. No conspiracy here, move along.
Remember, you guys can help, we're a do-ocracy.
Follow us along: https://gitlab.archlinux.org/archlinux/ … -/issues/4
]]>Actually I like the interface from Gitlab more. The source is available and you can host it on your own. It is understandable that Archlinux prefers to keep costs low and use the offered service from Gitlab. I prefer to be self-reliant when it is important and if not choose what fits better.
Maybe tomorrow Apple buys GitLab? Or more seriously IBM to add it with RedHat. Slack would be also funny. Who knows?
]]>Gitlab sounds actually much better, self-hosted or external.
WRT the concerns exprssed in post #1 I don't think gitlab is much better than github.
Sorry.
It's a read-only mirror: https://lists.archlinux.org/pipermail/a … 29971.html
On more goal we had is automatic github.com mirroring in some fashion.
We looked at creating a two-way github.com <-> GitLab mirror but that
setup can break easily in the case of force pushes and race conditions
and also would have us looking at both places for pull requests. It
seems simpler to us for the time being to have one-way mirroring from
our GitLab to github.com only and then allow github.com users to easily
collaborate on our GitLab via github.com social login. It's a little bit
more hassle for the users than collaborating directly on github.com but
it's a lot less hassle for us so it's perhaps the best compromise.
Thanks. It is Gitlab
But why we don't get the direct link to the upstream Gitlab repositories?
It is shielding us away
It's a read-only mirror: https://lists.archlinux.org/pipermail/a … 29971.html
On more goal we had is automatic github.com mirroring in some fashion.
We looked at creating a two-way github.com <-> GitLab mirror but that
setup can break easily in the case of force pushes and race conditions
and also would have us looking at both places for pull requests. It
seems simpler to us for the time being to have one-way mirroring from
our GitLab to github.com only and then allow github.com users to easily
collaborate on our GitLab via github.com social login. It's a little bit
more hassle for the users than collaborating directly on github.com but
it's a lot less hassle for us so it's perhaps the best compromise.
I think the issue is with "View Changes" on archlinux.org/packages now linking to the GitHub site (which struggles under the load). Anyhow great work by the Arch Team!
]]>On more goal we had is automatic github.com mirroring in some fashion.
We looked at creating a two-way github.com <-> GitLab mirror but that
setup can break easily in the case of force pushes and race conditions
and also would have us looking at both places for pull requests. It
seems simpler to us for the time being to have one-way mirroring from
our GitLab to github.com only and then allow github.com users to easily
collaborate on our GitLab via github.com social login. It's a little bit
more hassle for the users than collaborating directly on github.com but
it's a lot less hassle for us so it's perhaps the best compromise.
I will link the image
]]>I'm sorry. I'm not able to find any news regarding this. Neither on archlinux.org, planet.archlinux.org, the forum and probably I'm looking at the wrong mailinglists. Is there a link or something which is explaining what is actually going on? Looks like I missed important news. Are the PKGBUILDs and so on no longer hosted on self-reliant/self-hosted servers? For example 0ad:
https://github.com/archlinux/svntogit-c … /0ad/trunk # doesn't load at all
Honestly. I'm feeling rather uncomfortable depending completely on external infrastructure. In this case it is Microsoft. I hope this doesn't sound like a blame. I've only noticed this, because the "view changes" to packages doesn't load anywhere. I'm checking the history often for what and why something was changed. That's why I recognized that in first place.
Thank you
PS: I expected a link to some kind of super secret and public mailing list explaining a long strategic change. Likely within seconds
// edit
Example of gnome-terminal's changes not loading.