From: Max Magorsch <max@magorsch.de>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Improving warnings on packages.g.o
Date: Thu, 27 Aug 2020 12:37:17 +0200 [thread overview]
Message-ID: <CA+vObejL2KKMVxRrSeyy7ywZSmxEN+LHTVvupD8NXjDakUKL9A@mail.gmail.com> (raw)
In-Reply-To: <36abd21874b734a6478dee2bb2874f4c4a98cbfb.camel@gentoo.org>
On Thu, Aug 27, 2020 at 12:10 PM Alexis Ballier <aballier@gentoo.org> wrote:
> Any plans on using the remoteid from metadata.xml ?
> It's likely to be much more accurate since people have been filling
> those manually for some time now ;)
>
I think we could use the remoteid in future to improve the repology
warnings. However, I am not fully convinced that we can completely
replace the repology check using the remoteid, as a simple grep shows,
that currently 9873 packages contain at least one remote id. That's
just half of our packages in the tree. So I could imagine that we do
use the remoteid whenever it is available and otherwise fall back on
the repology data. However, for this to work we would need to things
imo:
1) Get the latest version available given the remoteid
2) Compare the latest version available with our latest version
It's especially the second part that I think is not done that quickly.
However, if anyone is interested in coming up with some logic / code
for this, any contributions are highly welcome.
next prev parent reply other threads:[~2020-08-27 10:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-26 18:57 [gentoo-dev] Improving warnings on packages.g.o Max Magorsch
2020-08-27 10:00 ` Nils Freydank
2020-08-27 10:24 ` Max Magorsch
2020-08-27 10:08 ` Alexis Ballier
2020-08-27 10:37 ` Max Magorsch [this message]
2020-08-27 16:25 ` Louis Sautier
2020-08-27 11:26 ` Marek Szuba
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CA+vObejL2KKMVxRrSeyy7ywZSmxEN+LHTVvupD8NXjDakUKL9A@mail.gmail.com \
--to=max@magorsch.de \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox