unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: Preservation of Guix Report 2021-11-30
Date: Mon, 06 Dec 2021 15:00:25 +0100	[thread overview]
Message-ID: <86tuflomti.fsf@gmail.com> (raw)
In-Reply-To: <87fsr5najj.fsf@gnu.org>

Hi,

On Mon, 06 Dec 2021 at 14:10, Ludovic Courtès <ludo@gnu.org> wrote:
> zimoun <zimon.toutoune@gmail.com> skribis:
>
>> Where I am surprised is that PoG does not return 'python-scikit-learn' when:
>>
>> $ guix lint -c archival python-scikit-learn
>> gnu/packages/machine-learning.scm:946:5: python-scikit-learn@0.24.2:
>> scheduled Software Heritage archival
>
> This is most likely due to <https://issues.guix.gnu.org/51726>.

Yes, that’s the explanation why “guix lint” is always scheduling it. :-)

The very same mechanism is used to fallback.  Therefore, Guix cannot
uses SWH as fallback for ’python-scikit-learn’; for now. ;-)

PoG uses the same API point*, IIUC.  Somehow, «PoG code finds ’foo’» has
to match «Guix code can use SWH as fallback for ’foo’» and the question
using ’python-scikit-learn’ as example: is it the case?

Other said, does this coverage done by PoG code correctly represent what
Guix code can reach?  Looking for corner cases; the devil is in the
details. ;-)


*API: instead of one query by request, PoG sends 1000 queries by request.
Because SWH limits to 100 request per hour, PoG checks for all packages
when Guix requires… bah! :-)


Cheers,
simon


  reply	other threads:[~2021-12-06 14:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-01 18:48 Preservation of Guix Report 2021-11-30 Timothy Sample
2021-12-02 14:09 ` Timothy Sample
2021-12-02 17:15 ` zimoun
2021-12-03 10:02   ` Ricardo Wurmus
2021-12-03 13:22     ` zimoun
2021-12-06 13:10   ` Ludovic Courtès
2021-12-06 14:00     ` zimoun [this message]
2021-12-06 13:09 ` Ludovic Courtès

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=86tuflomti.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=ludo@gnu.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).