I have fixed this, for Krita alone.

I would need to write an automation script to fix it for all repos...

--=20
Nicol=C3=A1s

El lun., 15 de jun. de 2020 a la(s) 16:37, L. E. Segovia
(amy@amyspark.me) escribi=C3=B3:
>
> Hi Ben, hi everyone,
>
> I'm writing to let you know that since June 10 the Phabricator copy of
> Krita's repository is broken.
>
> The initialization log from the Manage repository page says:
>
>  > Pull of 'krita' failed: Command failed with error #128! COMMAND git
> ls-remote '********' STDOUT (empty) STDERR fatal: remote error: Please
> use the https: protocol to connect to anongit
>
> so I think this change may have to do with it.
>
> I hope it can be solved soon, as I'm developing my GSoC project and
> cannot bind recent commits to the finished tasks.
>
> cc to the Krita mailing list to let them know as well.
>
> Best regards,
> amyspark
>
> On 11/06/2020 09:11, Ben Cooksley wrote:
> > Hi all,
> >
> > As previously announced by Sysadmin, following the Gitlab migration we
> > would be shutting down a number of services that were part of the old
> > Git infrastructure, as they were replaced with our new Gitlab based
> > infrastructure.
> >
> > This is a change which has now been actioned, and means the following:
> >
> > 1) git:// protocol support has now been discontinued
> >
> > Prior to the move to Gitlab, the anongit network offered access to our
> > repositories over both the git:// protocol as well as https://. This
> > has now been discontinued, and access is now provided solely via https
> > to ensure that connections cannot be intercepted and tampered with
> >
> > 2) CGit has been discontinued
> >
> > The CGit instance previously available at cgit.kde.org has now been
> > shutdown and is no longer available. All repository browsing should
> > now take place via Gitlab at https://invent.kde.org/
> >
> > 3) The anongit network in general has been discontinued
> >
> > Following the migration to Gitlab, all developers as well as automated
> > systems began to use the master server for their traffic exclusively.
> > Load monitoring since then has indicated that the system is fully
> > capable of handling this load without the assistance of any additional
> > systems.
> >
> > To avoid issues that have come up in the past (with people trying to
> > push to anongit, or systems being out of sync) it has been decided
> > that the anongit service is no longer providing benefit to us and as
> > such it has also been discontinued.
> >
> > A legacy compatibility redirector will continue to operate under the
> > hostname 'anongit.kde.org' for https urls and will redirect older
> > style urls to their replacement Gitlab equivalents.
> >
> > If anyone has any questions on the above, please let us know.
> >
> > Thanks,
> > Ben Cooksley
> > KDE Sysadmin
> >
> --
> amyspark https://www.amyspark.me