From: Simon Tournier <zimon.toutoune@gmail.com>
To: "Ricardo Wurmus" <rekado@elephly.net>,
"Ludovic Courtès" <ludovic.courtes@inria.fr>
Cc: Timothy Sample <samplet@ngyro.com>, 39885@debbugs.gnu.org, me@tobias.gr
Subject: bug#39885: Bioconductor URI, fallback and time-machine
Date: Thu, 11 Jan 2024 17:11:21 +0100 [thread overview]
Message-ID: <87h6jj26l2.fsf@gmail.com> (raw)
In-Reply-To: <87frz7j0tl.fsf@elephly.net>
Hi,
On Mon, 08 Jan 2024 at 16:34, Ricardo Wurmus <rekado@elephly.net> wrote:
> The WIP commit is here:
>
> https://git.savannah.gnu.org/cgit/guix.git/commit/?h=wip-r&id=e81a75a7b28c633a658ceeb0a728255674f56c58
IIRC, the main feedback [1] of this approach is:
- the repositories at https://git.bioconductor.org/package/NAME do not
tag package versions. The only method of organization is branches
that are named after *Bioconductor releases* (not package releases),
e.g. RELEASE_3_15. We can only determine the package version by
reading its DESCRIPTION file or by looking up the version index for
all Bioconductor packages (we do that already). This means that there
could be different commits for the same package version in the same
release branch — so we have to include the commit hash and a revision
counter in the version string.
Have you tried the wip commit at scale?
Cheers,
simon
1:bug#39885: Bioconductor URI, fallback and time-machine
Ricardo Wurmus <rekado@elephly.net>
Wed, 10 Aug 2022 20:25:00 +0200
id:878rnwuemq.fsf@elephly.net
https://issues.guix.gnu.org/39885
https://issues.guix.gnu.org/msgid/878rnwuemq.fsf@elephly.net
https://yhetil.org/guix/878rnwuemq.fsf@elephly.net
next prev parent reply other threads:[~2024-01-12 12:52 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 [this message]
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
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=87h6jj26l2.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=39885@debbugs.gnu.org \
--cc=ludovic.courtes@inria.fr \
--cc=me@tobias.gr \
--cc=rekado@elephly.net \
--cc=samplet@ngyro.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).