Github messages for voidlinux
 help / color / mirror / Atom feed
From: icp1994 <icp1994@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] memtester: fails to fetch
Date: Wed, 29 Mar 2023 21:30:51 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-43104@inbox.vuxu.org> (raw)

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

New issue by icp1994 on void-packages repository

https://github.com/void-linux/void-packages/issues/43104

Description:
```
» ./xbps-src -I fetch memtester
=> xbps-src: updating software in / masterdir...
=> xbps-src: cleaning up / masterdir...
=> memtester-4.5.1_1: running do-fetch hook: 00-distfiles ...
=> memtester-4.5.1_1: fetching distfile 'memtester-4.5.1.tar.gz' from 'http://pyropus.ca/software/memtester/old-versions/memtester-4.5.1.tar.gz'...
SSL certificate subject doesn't match host pyropus.ca.
http://pyropus.ca/software/memtester/old-versions/memtester-4.5.1.tar.gz: Operation not permitted
=> ERROR: memtester-4.5.1_1: failed to fetch 'memtester-4.5.1.tar.gz'.
```

I have tried changing `distfiles` to `https://pyropus.ca./software/memtester/old-versions/memtester-${version}.tar.gz` but that doesn't work either. Although locally
`curl -v -fsSL "http://pyropus.ca/software/memtester/old-versions/memtester-4.5.1.tar.gz" -O` works.

             reply	other threads:[~2023-03-29 19:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-29 19:30 icp1994 [this message]
2023-03-29 19:32 ` icp1994
2023-03-29 19:32 ` icp1994
2023-03-29 19:36 ` classabbyamp
2023-03-29 19:39 ` icp1994
2023-03-29 20:13 ` classabbyamp
2023-03-29 20:14 ` classabbyamp
2023-03-29 20:14 ` classabbyamp
2023-04-23 22:37 ` [ISSUE] [CLOSED] " Duncaen

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-43104@inbox.vuxu.org \
    --to=icp1994@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).