From: Christopher Baines <mail@cbaines.net>
To: zimoun <zimon.toutoune@gmail.com>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: Reproductibility, Data Services, guix weather
Date: Thu, 15 Oct 2020 09:45:44 +0100 [thread overview]
Message-ID: <87r1pzj2rr.fsf@cbaines.net> (raw)
In-Reply-To: <CAJ3okZ0b1=sC3fK8AXUDcBn3W8TpNi2bAiY7LsYvjy341mYbZQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1033 bytes --]
zimoun <zimon.toutoune@gmail.com> writes:
> Hi Chris,
>
> On Tue, 13 Oct 2020 at 21:41, Christopher Baines <mail@cbaines.net> wrote:
>
>> > First, Chris could you add the fields package name and version? Because
>> > it is hard to automatically reconstruct them by parsing the output-path.
>>
>> Done in [1], and I've updated data.guix-patches.cbaines.net.
>
> Neat! I have updated my script. Now, I need to add some build-system
> support to easy the triage. Keep you in touch.
>
> Thank you.
>
>> > (A working revision is 6cf35799dec60723f37d83a559429aa8b90482d5 which
>> > does not seems founding in Guix repo.)
>>
>> So, that particular commit is just some revision of Guix with some
>> patches applied. I picked it because it was the most recent
>> data. There's now recent commits for the master branch itself [2] like
>> [3].
>
> Can I expect that all the revisions are there? Or only some?
Well, definitely not all revisions, but for the patches instance of the
Guix Data Service I'm aiming to keep recent revisions.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 987 bytes --]
next prev parent reply other threads:[~2020-10-15 8:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-12 21:40 Reproductibility, Data Services, guix weather zimoun
2020-10-13 19:41 ` Christopher Baines
2020-10-14 20:17 ` zimoun
2020-10-15 8:45 ` Christopher Baines [this message]
2020-10-15 9:18 ` zimoun
2020-10-16 10:17 ` 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=87r1pzj2rr.fsf@cbaines.net \
--to=mail@cbaines.net \
--cc=guix-devel@gnu.org \
--cc=zimon.toutoune@gmail.com \
/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).