From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] Distfiles for x265 can't be accessed
Date: Wed, 03 Feb 2021 15:27:35 +0100 [thread overview]
Message-ID: <20210203142735.H9OhP-Dbyw92pYUzNXXt3SWtUUsM4lxImtS8tzKYK5I@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-28424@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 924 bytes --]
Closed issue by RossComputerGuy on void-packages repository
https://github.com/void-linux/void-packages/issues/28424
Description:
<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
### System
* xuname: `Void 5.10.12_1 x86_64 AuthenticAMD notuptodate rrrrmmnFFFFF`
* package: `x265-3.4_1`
### Expected behavior
The do-fetch step should finish
### Actual behavior
```
=> x265-3.4_1: installing host dependencies: nasm-2.15.05_1 nasm-2.15.05_1 cmake-3.19.3_1 ...
=> x265-3.4_1: running do-fetch hook: 00-distfiles ...
=> x265-3.4_1: fetching distfile 'x265_3.4.tar.gz'...
https://bitbucket.org/multicoreware/x265/downloads/x265_3.4.tar.gz: Not Found
=> ERROR: x265-3.4_1: failed to fetch x265_3.4.tar.gz.
```
### Steps to reproduce the behavior
`./xbps-src -N pkg x265`
prev parent reply other threads:[~2021-02-03 14:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-03 5:22 [ISSUE] x265 fails to compile RossComputerGuy
2021-02-03 5:34 ` ericonr
2021-02-03 5:36 ` RossComputerGuy
2021-02-03 5:38 ` ericonr
2021-02-03 5:38 ` ericonr
2021-02-03 5:39 ` Distfiles for x265 can't be accessed RossComputerGuy
2021-02-03 5:47 ` RossComputerGuy
2021-02-03 5:48 ` RossComputerGuy
2021-02-03 5:58 ` RossComputerGuy
2021-02-03 6:01 ` ericonr
2021-02-03 6:04 ` RossComputerGuy
2021-02-03 6:18 ` RossComputerGuy
2021-02-03 14:27 ` ericonr [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=20210203142735.H9OhP-Dbyw92pYUzNXXt3SWtUUsM4lxImtS8tzKYK5I@z \
--to=ericonr@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).