From: vutunganh <vutunganh@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] zlib: Fetch error when building
Date: Sat, 16 Apr 2022 13:56:43 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36720@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1526 bytes --]
New issue by vutunganh on void-packages repository
https://github.com/void-linux/void-packages/issues/36720
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.15.34_1 x86_64-musl GenuineIntel uptodate rrnFFF`
*output of ``xuname`` (part of xtools)*
* package: `zlib-1.2.12_2`
### Expected behavior
zlib builds successfully.
### Actual behavior
```
$ ./xbps-src pkg zlib
=> xbps-src: updating repositories for host (x86_64-musl)...
[*] Updating repository `https://alpha.de.repo.voidlinux.org/current/musl/x86_64-musl-repodata' ...
[*] Updating repository `https://alpha.de.repo.voidlinux.org/current/musl/nonfree/x86_64-musl-repodata' ...
[*] Updating repository `https://alpha.de.repo.voidlinux.org/current/musl/debug/x86_64-musl-repodata' ...
=> xbps-src: updating software in / masterdir...
=> xbps-src: cleaning up / masterdir...
=> zlib-1.2.11_4: removing autodeps, please wait...
=> zlib-1.2.11_4: building [configure] for x86_64-musl...
[runtime] zlib-1.2.11_4: not found (self, ignored)
=> zlib-1.2.11_4: running do-fetch hook: 00-distfiles ...
=> zlib-1.2.11_4: fetching distfile 'zlib-1.2.11.tar.gz'...
http://www.zlib.net/zlib-1.2.11.tar.gz: Not Found
=> ERROR: zlib-1.2.11_4: failed to fetch zlib-1.2.11.tar.gz.
```
### Steps to reproduce the behavior
Try building zlib.
`./xbps-src pkg zlib`
next reply other threads:[~2022-04-16 11:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-16 11:56 vutunganh [this message]
2022-04-16 20:22 ` oreo639
2022-04-16 20:24 ` oreo639
2022-04-16 20:24 ` oreo639
2022-04-16 20:42 ` [ISSUE] [CLOSED] " vutunganh
2022-04-16 20:42 ` vutunganh
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-36720@inbox.vuxu.org \
--to=vutunganh@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).