From: "Ludovic Courtès" <ludovic.courtes@inria.fr>
To: Simon Tournier <zimon.toutoune@gmail.com>
Cc: rekado@elephly.net, Timothy Sample <samplet@ngyro.com>,
39885@debbugs.gnu.org, me@tobias.gr
Subject: bug#39885: Bioconductor tarballs are not archived
Date: Mon, 08 Jan 2024 16:02:53 +0100 [thread overview]
Message-ID: <878r4z7tr6.fsf@inria.fr> (raw)
In-Reply-To: <87le9019aj.fsf@gmail.com> (Simon Tournier's message of "Mon, 08 Jan 2024 10:09:08 +0100")
Hi!
Simon Tournier <zimon.toutoune@gmail.com> skribis:
>> I was wondering whether we’re now doing better for Bioconductor
>> tarballs. The answer, based on small sample, seems to be “not quite”:
[...]
> but, now the past reads,
>
> $ for url in https://bioconductor.org/packages/release/bioc/src/contrib/BiocNeighbors_1.20.0.tar.gz \
> https://bioconductor.org/packages/3.18/bioc/src/contrib/BiocNeighbors_1.20.0.tar.gz ; \
> do guix download $url ;done
Thanks for investigating & explaining!
I my previous message, I wrote:
> As for past tarballs, #swh-devel comrades say we could send them a list
> of URLs and they’d create “Save Code Now” requests on our behalf (we
> cannot do it ourselves since the site doesn’t accept plain tarballs.)
Were you able to retrieve some of these? What are the chances of
success?
> Hence the discussion we had: switch from url-fetch to git-fetch.
> However, after some investigations, it does not seem straightforward:
> The main issue being the almost automatic current updater. See for
> details [2].
[...]
> https://issues.guix.gnu.org/msgid/878rnwuemq.fsf@elephly.net
Indeed, thanks for the link. I agree that long-term moving to
‘git-fetch’ sounds preferable, but there are quite a few obstacles to
overcome.
Ludo’.
next prev parent reply other threads:[~2024-01-08 15:04 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-03 15:59 bug#39885: Bioconductor URI, fallback and time-machine zimoun
2020-03-23 21:20 ` Ricardo Wurmus
2020-05-21 23:29 ` zimoun
2020-06-24 11:07 ` zimoun
2020-06-28 20:14 ` Ludovic Courtès
2020-06-29 17:36 ` zimoun
2020-06-29 20:42 ` Ludovic Courtès
2020-11-19 14:22 ` zimoun
2021-11-22 19:48 ` zimoun
2022-07-18 16:03 ` zimoun
2022-07-18 16:21 ` Ricardo Wurmus
2022-08-10 18:25 ` Ricardo Wurmus
2022-08-10 19:44 ` Maxime Devos
2022-08-10 19:48 ` Maxime Devos
2022-09-09 17:23 ` zimoun
2024-01-08 15:07 ` Ludovic Courtès
2024-01-08 15:34 ` Ricardo Wurmus
2024-01-11 16:11 ` Simon Tournier
2023-12-22 13:40 ` bug#39885: Bioconductor tarballs are not archived Ludovic Courtès
2024-01-08 9:09 ` Simon Tournier
2024-01-08 15:02 ` Ludovic Courtès [this message]
2024-01-10 12:41 ` Ricardo Wurmus
2024-01-10 15:23 ` Simon Tournier
2024-01-19 15:46 ` Timothy Sample
2024-01-23 9:10 ` Ludovic Courtès
2024-02-14 15:23 ` Simon Tournier
2024-02-16 16:14 ` Timothy Sample
2024-02-19 16:50 ` Simon Tournier
2024-02-21 18:16 ` Timothy Sample
2023-12-22 20:57 ` bug#39885: Bioconductor URI, fallback and time-machine Ludovic Courtès
2024-01-02 9:20 ` Simon Tournier
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=878r4z7tr6.fsf@inria.fr \
--to=ludovic.courtes@inria.fr \
--cc=39885@debbugs.gnu.org \
--cc=me@tobias.gr \
--cc=rekado@elephly.net \
--cc=samplet@ngyro.com \
--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).