From: Tobias Geerinckx-Rice via Bug reports for GNU Guix <bug-guix@gnu.org>
To: Muhammad Hassan <muhammad.hassan@uwaterloo.ca>
Cc: 51492@debbugs.gnu.org, mail@cbaines.net
Subject: bug#51492: Request to use GNU guix reproducibility bugs data for research project | University of Waterloo
Date: Wed, 03 Nov 2021 07:12:09 +0100 [thread overview]
Message-ID: <877ddp911u.fsf@nckx> (raw)
In-Reply-To: <YQBPR0101MB581397F18F7C0B3DD13AEFCE86879@YQBPR0101MB5813.CANPRD01.PROD.OUTLOOK.COM>
[-- Attachment #1: Type: text/plain, Size: 1176 bytes --]
Muhammad,
[CCing Christopher Baines, who may skip straight to the last
paragraph because they're probably busy building cool stuff.]
Good luck in your research.
Muhammad Hassan 写道：
> Please tell me if there is an API that I can use to scrap the
> data.
>
> https://issues.guix.gnu.org/
Hm, are you sure that our bug tracker is at all useful here? I
doubt it! There are a relative handful of ‘foo isn't
reproducible’ bugs but they're the opposite of comprehensive or
standardised. There are no categories nor labels nor automated
closings when an issue is fixed.
I think what you really want is this[0] (source: [1]).
Mouth-watering indeed!
One problem: the Package Reproducibility page is gone :-( I'm
surprised: it was still there a few months ago. Christopher, is
this deliberate? If so, is there any way we could help bring it
back? Is the historical data safe and is new data still tracked?
Kind regards,
T G-R
[0]:
https://guix.gnu.org/static/blog/img/data-guix-patches-package-reproducibility.png
[1]:
https://guix.gnu.org/eo/blog/2020/introduction-to-the-guix-data-service-the-missing-blog-post
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]
prev parent reply other threads:[~2021-11-03 7:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-29 16:48 bug#51492: Request to use GNU guix reproducibility bugs data for research project | University of Waterloo Muhammad Hassan
2021-11-03 6:12 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix [this message]
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=877ddp911u.fsf@nckx \
--to=bug-guix@gnu.org \
--cc=51492@debbugs.gnu.org \
--cc=mail@cbaines.net \
--cc=me@tobias.gr \
--cc=muhammad.hassan@uwaterloo.ca \
/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).