From: chexum <chexum@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] boost: new distfiles location
Date: Sun, 11 Jul 2021 00:18:35 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-31899@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1752 bytes --]
There is a new pull request by chexum against master on the void-packages repository
https://github.com/chexum/void-packages boost-1720
https://github.com/void-linux/void-packages/pull/31899
boost: new distfiles location
Download location documented to replace the old, non-working one:
https://www.boost.org/users/news/boost_has_moved_downloads_to_jfr.html
>> Instead of: https://dl.bintray.com/boostorg/release/ you should use https://boostorg.jfrog.io/artifactory/main/release/ to retrieve boost releases.
Tested availability of the present version:
$ curl -I https://boostorg.jfrog.io/artifactory/main/release/1.72.0/source/boost_1_72_0.tar.bz2 2>&1|egrep Date\|256
Date: Sat, 10 Jul 2021 21:30:24 GMT
X-Checksum-Sha256: 59c9b274bc451cf91a9ba1dd2c7fdcaf5d60b1b3aa83f2c9fa143417cc660722
#### General
- [ ] This is a new package and it conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements)
#### Have the results of the proposed changes been tested?
- [ ] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
- [x] I generally don't use the affected packages but briefly tested this PR
[skip ci] no package change expected, only the distribution location for future builds
<!--
#### Does it build and run successfully?
(Please choose at least one native build and, if supported, at least one cross build. More are better.)
- [x] I built this PR locally for my native architecture, (x86_64)
- [ ] I built this PR locally for these architectures (if supported. mark crossbuilds):
- [ ] aarch64
-->
A patch file from https://github.com/void-linux/void-packages/pull/31899.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-boost-1720-31899.patch --]
[-- Type: text/x-diff, Size: 1488 bytes --]
From af34c7fc61c3999bce63d9aa7162f1364dc68bd7 Mon Sep 17 00:00:00 2001
From: J Farkas <chexum+git@gmail.com>
Date: Sat, 10 Jul 2021 23:12:31 +0100
Subject: [PATCH] boost: new distfiles location
Download location documented to replace the old, non-working one:
https://www.boost.org/users/news/boost_has_moved_downloads_to_jfr.html
>> Instead of: https://dl.bintray.com/boostorg/release/ you should use https://boostorg.jfrog.io/artifactory/main/release/ to retrieve boost releases.
Tested availability of the present version:
$ curl -I https://boostorg.jfrog.io/artifactory/main/release/1.72.0/source/boost_1_72_0.tar.bz2 2>&1|egrep Date\|256
Date: Sat, 10 Jul 2021 21:30:24 GMT
X-Checksum-Sha256: 59c9b274bc451cf91a9ba1dd2c7fdcaf5d60b1b3aa83f2c9fa143417cc660722
---
srcpkgs/boost/template | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/srcpkgs/boost/template b/srcpkgs/boost/template
index 5b559e932d18..d1dd74577e7a 100644
--- a/srcpkgs/boost/template
+++ b/srcpkgs/boost/template
@@ -9,7 +9,7 @@ short_desc="Free peer-reviewed portable C++ source libraries"
maintainer="John <me@johnnynator.dev>"
license="BSL-1.0"
homepage="http://www.boost.org/"
-distfiles="https://dl.bintray.com/boostorg/release/${version}/source/boost_${version//./_}.tar.bz2"
+distfiles="https://boostorg.jfrog.io/artifactory/main/release/${version}/source/boost_${version//./_}.tar.bz2"
checksum=59c9b274bc451cf91a9ba1dd2c7fdcaf5d60b1b3aa83f2c9fa143417cc660722
python_version=3
next reply other threads:[~2021-07-10 22:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-10 22:18 chexum [this message]
2021-07-10 23:44 ` [PR PATCH] [Merged]: " Johnnynator
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-31899@inbox.vuxu.org \
--to=chexum@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).