From: reback00 <reback00@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: textadept: update to 11.2
Date: Fri, 27 Aug 2021 09:07:04 +0200 [thread overview]
Message-ID: <20210827070704.A1Oow8kSODSK5hxHK9OiKIeAe6cyBAeF_9GkTglgxc4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-32697@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1080 bytes --]
New comment by reback00 on void-packages repository
https://github.com/void-linux/void-packages/pull/32697#issuecomment-906977967
Comment:
Just a small note. The `cdk` dependency from invisible-mirror.net fails sometimes with this message below:
```
=> textadept-11.2_1: fetching distfile 'cdk-5.0-20200923.tgz'...
https://invisible-mirror.net/archives/cdk/cdk-5.0-20200923.tgz: Operation timed out
=> ERROR: textadept-11.2_1: failed to fetch cdk-5.0-20200923.tgz.
Error: Process completed with exit code 1.
```
It used to go pretty well for the first few builds, but then [this used to happen](https://github.com/void-linux/void-packages/pull/29666#issuecomment-803646589). This is probably because the mirror site has some abuse detection in place and blocks later requests.
I've changed the dep url to be from `https://github.com/orbitalquark/textadept-build` so that this doesn't happen. The advice came from [the project itself](https://github.com/orbitalquark/textadept/discussions/78#discussioncomment-513052). The build doesn't fail now after this change.
next prev parent reply other threads:[~2021-08-27 7:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-27 6:19 [PR PATCH] " reback00
2021-08-27 6:55 ` [PR PATCH] [Updated] " reback00
2021-08-27 7:07 ` reback00 [this message]
2021-08-27 17:26 ` [PR REVIEW] " ericonr
2021-08-27 17:26 ` ericonr
2022-06-02 2:15 ` github-actions
2022-06-17 2:14 ` [PR PATCH] [Closed]: " github-actions
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=20210827070704.A1Oow8kSODSK5hxHK9OiKIeAe6cyBAeF_9GkTglgxc4@z \
--to=reback00@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).