From mboxrd@z Thu Jan 1 00:00:00 1970 From: zimoun Subject: Guix Data Services: whishlist about SWH Date: Sat, 15 Feb 2020 17:05:08 +0100 Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:46557) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1j2zwY-0003By-KQ for guix-devel@gnu.org; Sat, 15 Feb 2020 11:05:23 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1j2zwX-0007Sp-It for guix-devel@gnu.org; Sat, 15 Feb 2020 11:05:22 -0500 Received: from mail-qk1-x72d.google.com ([2607:f8b0:4864:20::72d]:46042) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1j2zwX-0007SO-D8 for guix-devel@gnu.org; Sat, 15 Feb 2020 11:05:21 -0500 Received: by mail-qk1-x72d.google.com with SMTP id a2so12185172qko.12 for ; Sat, 15 Feb 2020 08:05:21 -0800 (PST) List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane-mx.org@gnu.org Sender: "Guix-devel" To: Guix Devel , Christopher Baines Hi, Recently, the source of package was missing and so "guix time-machine" was broken [1]. It is not the first time that it appears [2]; patches are coming... :-) Using the Software Heritage (SWH) API [3], does it seems a good idea to add SWH coverage somewhere in the Guix Data Services? I do not remember where the Reproducibility chart is located, but a chart there could be added, telling how many packages are already archived in SWH and how many not yet. And for example, on the webpage about the history of the package [4], some information about SWH could be added. What do you think? [1] https://debbugs.gnu.org/cgi/bugreport.cgi?bug=39575 [2] https://debbugs.gnu.org/cgi/bugreport.cgi?bug=28659 [3] https://archive.softwareheritage.org/api/ [4] http://data.guix.gnu.org/repository/1/branch/master/package/harfbuzz (Note that on [4] the version 2.4.0 which is the culprit is not shown, is it expected?) All the best, simon