Re: [gentoo-dev] Adding heptapod as new <remote-id> in metadata.dtd

[Torokhov Sergey]

15.10.2020, 21:15, "Michał Górny" <mgorny@g.o>:
> On Wed, 2020-10-14 at 02:19 +0300, Torokhov Sergey wrote:
>>  Excuse me for text/html in initial letter. I duplicate start message with text/plain below
>>  without attachments as they are available on MARC:
>>
>>  Hello!
>>
>>  Due to recent sunset on mercurial support by Bitbucket [1]
>>  the project early hosted there that uses mercurial vcs
>>  have to migrate to other mercurial hosting.
>>
>>  One of them is new hosting heptapod [2] based on the Gitlab.
>>  For free and open source project the service provides free of charge hosting [3].
>>
>>  E.g. the following projects migrate to heptapod:
>>
>>  Tortoisehg : https://foss.heptapod.net/mercurial/tortoisehg/thg
>>  PyPy : https://foss.heptapod.net/pypy/pypy
>>
>>  The attached patches offer to add 'heptapod' (i.e. 'foss.heptapod.net' [3])
>>  as new <remote-id> item to 'dtd/metadata.dtd' and to 'xml-schema/metadata.xsd'.
>>
>>  Then it could be used to set in 'matadata.xml' an additional info about :
>>
>>  for dev-python/pypy{,3}: <remote-id type="heptapod">pypy/pypy</remote-id>
>>
>>  for dev-vcs/tortoisehg: <remote-id type="heptapod">mercurial/tortoisehg/thg</remote-id>
>>
>>  [1] https://bitbucket.org/blog/sunsetting-mercurial-support-in-bitbucket
>>  [2] https://heptapod.net
>>  [3] https://foss.heptapod.net
>>
>>  --
>>  Sergey Torokhov
>>
>>  <<<
>
> Both pushed.
>
> --
> Best regards,
> Michał Górny

Hello again.

It seems that after merge of this patches there are still some issues remain:

1) Github gentoo/gentoo CI don't know about new remote-id "heptapod" and result in error on QA check.

2) packages.gentoo.org source code is also required to be updated to use this new remote-id.
Is it https://gitweb.gentoo.org/sites/soko.git/tree/pkg/app/handler/packages/utils.go file is required to be patched
in "func RemoteIdLink(remoteId models.RemoteId) string" ?

--
Sergey Torokhov