Incorrect/outdated metadata links on gem page about rubygems.org HOT 3 CLOSED

You are right - that's interesting.

The .gemspec file has this entry:

spec.homepage      = "https://github.com/net-ssh/net-sftp"

Perhaps there needs to be some additional routine to check specifically whether the
URL shown on rubygems.org needs to be updated; I assume it has had to be stored
at one point in the past, as you indicate e. g. in 2021 or so. Perhaps some other older
gems also have that problem.

Aside from this, I think it would be pretty neat if we could have autogenerated documentation
at rubygems.org for gems too. I don't know if we have enough resources for that,
but I have had issues with external documentation before - often the gems I publish,
where the documentation is on, https://www.rubydoc.info/gems/, is often lagging behind,
or sometimes claiming that it does not exist, even though I pushed the gem just recently.
So there is some delay. Would be neat if there would be no delay and all could be contained
on rubygems.org directly, without having to depend on anything external (github, rubydoc
and so forth).

from rubygems.org.

Uff, this was though one to resolve, but I think I got it.

Before 2019, it was only possible to maintain those links (like docs) manually using WEB UI form, but that was removed at #1815.

net-sftp gem has this value still filled in.

irb(main):001:0> Rubygem.find_by(name: 'net-sftp').linkset
=> 
#<Linkset:                               
 id: 0,
 rubygem_id: 0,
 home: "https://github.com/net-ssh/net-sftp",
 wiki: "",
 docs: "http://net-ssh.github.com/net-sftp",
 mail: "",
 code: "https://github.com/net-ssh/net-sftp",
 bugs: "https://github.com/net-ssh/net-sftp/issues",

To override those values, net-sftp gem should utilize gemspec metadata. Logic picking on one of the values (from old linkset or modern metadata) lives in links model.

If I understand it well, there is nothing to do on rubygems.org side to fix this. 🤔

from rubygems.org.

Ah, .homepage is for the homepage, not the documentation of course. All my own gems get the default documentation link e. g. via https://www.rubydoc.info/gems/NAME_OF_THE_GEM_GOES_IN_HERE. I guess a new routine should check whether this entry is still specified or not; and if not, delete it (unless it was specified e. g. in the .gemspec file).

from rubygems.org.