Re: [gentoo-dev] Upstream remote-id types in package metadata
> On Sun, 22 May 2022, Ulrich Mueller wrote: > On Sun, 22 May 2022, Hanno Böck wrote: >> I'm not sure about Google code. >> While it's no longer an active site, it is still online in an >> archived state. We maintain plenty of packages that have no active >> upstream, and having a reference to an unmaintained previous upstream >> which still allows downloading the code and the repo archive seems >> like a good thing. > The same is true for gitorious, but we have dropped those remote-ids > from the tree nevertheless: > https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=f8fd6bd07efee4d36a1babf55d6e69c7cb4a93d4 > However, I think that your point is valid. So the basic question is > whether we should keep dead upstreams in that list, for archival > purposes? If the answer is yes, then consequently we should also keep > gitorious (and maybe revert above commit?). For gitorious, I went through all packages where that remote-id was dropped in the above mentioned commit. These packages were either last-rited, or moved to different hosting. So restoring gitorious in package metadata makes no sense for either of them. Also, https://gitorious.org/ has a security certificate that expired in early 2019. Unless I see any objections here, I'll drop gitorious from the XML schema and the DTD tomorrow. Ulrich signature.asc Description: PGP signature
Re: [gentoo-dev] Upstream remote-id types in package metadata
> On Sun, 22 May 2022, Ulrich Mueller wrote: > Some of them seem to be obsolete. Presumably freshmeat, gitorious, and > google-code should be removed? Any other removal candidates? > Looks like SourceForge-JP was renamed to OSDN, should the file reflect > that? > Also, the "gentoo" remote-id was added the the DTD [2] but is missing > from the XML schema. Presumably it should be added there, too? Thanks for all your comments. Taking them into account, the plan is: 1. Remove all freecode and freshmeat remote-ids from the Gentoo repo: https://github.com/gentoo/gentoo/pull/25599 2. Remove freecode, freshmeat, and rubyforge from the XML schema. We'll keep gitorious and google-code for now, because archived versions of them exist. 3. Add gentoo and osdn to the XML schema. 4. Update pkgcore (it bundles a local copy of metadata.xsd) and wait for a new release. 5. Rename all sourceforge-jp remote-ids to osdn in the Gentoo repo: https://github.com/ulm/gentoo/tree/remote-id-osdn (no PR yet because CI/pkgcheck would complain) 6. Remove sourceforce-jp from the XML schema. Sync pkgcore again. 7. Create a wiki page documenting remote-id types and their syntax. Ulrich signature.asc Description: PGP signature
Re: [gentoo-dev] Upstream remote-id types in package metadata
> On Sun, 22 May 2022, Hanno Böck wrote: >> Some of them seem to be obsolete. Presumably freshmeat, gitorious, and >> google-code should be removed? Any other removal candidates? > I'm not sure about Google code. > While it's no longer an active site, it is still online in an archived > state. We maintain plenty of packages that have no active upstream, > and having a reference to an unmaintained previous upstream which > still allows downloading the code and the repo archive seems like a > good thing. The same is true for gitorious, but we have dropped those remote-ids from the tree nevertheless: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=f8fd6bd07efee4d36a1babf55d6e69c7cb4a93d4 However, I think that your point is valid. So the basic question is whether we should keep dead upstreams in that list, for archival purposes? If the answer is yes, then consequently we should also keep gitorious (and maybe revert above commit?). Ulrich signature.asc Description: PGP signature
Re: [gentoo-dev] Upstream remote-id types in package metadata
> On Sun, 22 May 2022, Alessandro Barbieri wrote: > How to propose new values? I'd say, file a bug with some rationale and the proposed syntax. Ulrich signature.asc Description: PGP signature
Re: [gentoo-dev] Upstream remote-id types in package metadata
Il Dom 22 Mag 2022, 09:09 Ulrich Mueller ha scritto: > According to the XML schema [1], the following remote-id types are > currently allowed: > >bitbucket >cpan >cpan-module >cpe >cran >ctan >freecode >freshmeat >github >gitlab >gitorious >google-code >heptapod >launchpad >pear >pecl >pypi >rubyforge >rubygems >sourceforge >sourceforge-jp >vim > > Some of them seem to be obsolete. Presumably freshmeat, gitorious, and > google-code should be removed? Any other removal candidates? > > Looks like SourceForge-JP was renamed to OSDN, should the file reflect > that? > > Also, the "gentoo" remote-id was added the the DTD [2] but is missing > from the XML schema. Presumably it should be added there, too? > > Comments please. > How to propose new values? >
Re: [gentoo-dev] Upstream remote-id types in package metadata
Hi, On Sun, 22 May 2022 09:09:23 +0200 Ulrich Mueller wrote: > Some of them seem to be obsolete. Presumably freshmeat, gitorious, and > google-code should be removed? Any other removal candidates? I'm not sure about Google code. While it's no longer an active site, it is still online in an archived state. We maintain plenty of packages that have no active upstream, and having a reference to an unmaintained previous upstream which still allows downloading the code and the repo archive seems like a good thing. -- Hanno Böck https://hboeck.de/ pgp7tX5P3KIP1.pgp Description: OpenPGP digital signature
Re: [gentoo-dev] Upstream remote-id types in package metadata
> On Sun, 22 May 2022, Michał Górny wrote: > I think we should start documenting these values somewhere. Perhaps > in the GLEP, or maybe on some wiki page — particularly linking > the provider in question Wiki page sounds good. Presumably, we don't want to update the GLEP for every change of the list. > and documenting the value syntax. Let's start with gentoo. :) We have one (currently commented out) precedent in sys-kernel/genkernel which has: git://git.gentoo.org/proj/genkernel This is a little verbose. I propose using github or gitlab as a blueprint, so above would simply be "proj/genkernel". Ulrich signature.asc Description: PGP signature
Re: [gentoo-dev] Upstream remote-id types in package metadata
On Sun, 2022-05-22 at 09:09 +0200, Ulrich Mueller wrote: > > rubyforge > > Some of them seem to be obsolete. Presumably freshmeat, gitorious, > and > google-code should be removed? Any other removal candidates? rubyforge has been shut down since 2015 so it can be removed as well. Hans signature.asc Description: This is a digitally signed message part
Re: [gentoo-dev] Upstream remote-id types in package metadata
On Sun, 2022-05-22 at 09:09 +0200, Ulrich Mueller wrote: > Some of them seem to be obsolete. Presumably freshmeat, gitorious, and > google-code should be removed? Any other removal candidates? LGTM. > Looks like SourceForge-JP was renamed to OSDN, should the file reflect > that? > > Also, the "gentoo" remote-id was added the the DTD [2] but is missing > from the XML schema. Presumably it should be added there, too? > > Comments please. I think we should start documenting these values somewhere. Perhaps in the GLEP, or maybe on some wiki page — particularly linking the provider in question and documenting the value syntax. -- Best regards, Michał Górny
[gentoo-dev] Upstream remote-id types in package metadata
According to the XML schema [1], the following remote-id types are currently allowed: bitbucket cpan cpan-module cpe cran ctan freecode freshmeat github gitlab gitorious google-code heptapod launchpad pear pecl pypi rubyforge rubygems sourceforge sourceforge-jp vim Some of them seem to be obsolete. Presumably freshmeat, gitorious, and google-code should be removed? Any other removal candidates? Looks like SourceForge-JP was renamed to OSDN, should the file reflect that? Also, the "gentoo" remote-id was added the the DTD [2] but is missing from the XML schema. Presumably it should be added there, too? Comments please. Ulrich [1] https://gitweb.gentoo.org/data/xml-schema.git/tree/metadata.xsd?id=e8495470d00cd9912f3d216eb576b72a0f1fc77f#n273 [2] https://gitweb.gentoo.org/data/dtd.git/commit/?id=f265dac730ca5299280186f1d2ec90c84aa2a848 signature.asc Description: PGP signature
