Github messages for voidlinux
 help / color / mirror / Atom feed
From: CameronNemo <CameronNemo@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: xbps-src: fetch from CRAN archive
Date: Tue, 20 Sep 2022 14:20:09 +0200	[thread overview]
Message-ID: <20220920122009.CjXV4ddD3Zw_iyKf1IaPTmlfgwZtL5HO9uhWwcCYE8w@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38438@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 972 bytes --]

There's a closed pull request on the void-packages repository

xbps-src: fetch from CRAN archive
https://github.com/void-linux/void-packages/pull/38438

Description:
CRAN has a lovely practice of moving the latest releases into an archive
after a new release is made. So when pillar 1.8.0 is released, for
example, version 1.7.0 gets moved into the archive.

Add the CRAN archive as a mirror to handle this case.

See below for an example:

```
=> R-cran-pillar-1.5.1_1: running do-fetch hook: 00-distfiles ...
=> R-cran-pillar-1.5.1_1: fetching distfile 'pillar_1.5.1.tar.gz' from 'https://cran.r-project.org/src/contrib/Archive/pillar'...
```

#### Testing the changes
- I tested the changes in this PR: **briefly**

<!--
#### Local build testing
- I built this PR locally for my native architecture, (ARCH-LIBC)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
  - aarch64-musl
  - armv7l
  - armv6l-musl
-->


      parent reply	other threads:[~2022-09-20 12:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-02 20:55 [PR PATCH] " CameronNemo
2022-08-02 21:43 ` Chocimier
2022-08-02 22:00 ` [PR PATCH] [Updated] " CameronNemo
2022-08-02 22:05 ` CameronNemo
2022-08-05 20:23 ` CameronNemo
2022-08-05 20:23 ` [PR PATCH] [Updated] " CameronNemo
2022-09-20 12:20 ` CameronNemo [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220920122009.CjXV4ddD3Zw_iyKf1IaPTmlfgwZtL5HO9uhWwcCYE8w@z \
    --to=cameronnemo@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /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.
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 NNTP newsgroup(s).