From: Noah-Huppert <Noah-Huppert@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] spotify package currently broken due to an upstream download failure
Date: Fri, 22 Jan 2021 01:00:56 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-28094@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 3126 bytes --]
New issue by Noah-Huppert on void-packages repository
https://github.com/void-linux/void-packages/issues/28094
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.9.16_1 x86_64 GenuineIntel notuptodate rrrmFFFFFFFFFF*
* package:
*spotify-1.1.42_1*
### Expected behavior
Building spotify via `xbps-src pkg spotify` should succeed.
### Actual behavior
```
=> xbps-src: updating repositories for host (x86_64)...
[*] Updating repository `https://alpha.de.repo.voidlinux.org/current/x86_64-repodata' ...
[*] Updating repository `https://alpha.de.repo.voidlinux.org/current/nonfree/x86_64-repodata' ...
[*] Updating repository `https://alpha.de.repo.voidlinux.org/current/debug/x86_64-repodata' ...
[*] Updating repository `https://alpha.de.repo.voidlinux.org/current/multilib/x86_64-repodata' ...
[*] Updating repository `https://alpha.de.repo.voidlinux.org/current/multilib/nonfree/x86_64-repodata' ...
=> xbps-src: updating software in / masterdir...
=> xbps-src: cleaning up / masterdir...
=> spotify-1.1.42_3: removing autodeps, please wait...
=> spotify-1.1.42_3: building [fetch] for x86_64...
[host] curl-7.74.0_1: found (https://alpha.de.repo.voidlinux.org/current)
[host] w3m-0.5.3+git20210102_1: found (https://alpha.de.repo.voidlinux.org/current)
[host] libcurl-7.74.0_1: found (https://alpha.de.repo.voidlinux.org/current)
[runtime] GConf-3.2.6_9: found (https://alpha.de.repo.voidlinux.org/current)
[runtime] libcurl-7.74.0_1: found (https://alpha.de.repo.voidlinux.org/current)
=> spotify-1.1.42_3: installing host dependencies: curl-7.74.0_1 w3m-0.5.3+git20210102_1 libcurl-7.74.0_1 ...
=> spotify-1.1.42_3: running do-fetch hook: 00-distfiles ...
=> spotify-1.1.42_3: fetching distfile 'spotify-client_1.1.42.622.gbd112320-37_amd64.deb'...
spotify-client_1.1.42.622.gbd112320-37_amd64.deb: [120MB 3%] 2438B/s ETA: 08h15m
spotify-client_1.1.42.622.gbd112320-37_amd64.deb: [120MB 3%] 39KB/s ETA: 52m06s
spotify-client_1.1.42.622.gbd112320-37_amd64.deb: [120MB 3%] 168KB/s ETA: 11m56s
spotify-client_1.1.42.622.gbd112320-37_amd64.deb: [120MB 4%] 305KB/s ETA: 06m31s
http://repository.spotify.com/pool/non-free/s/spotify-client/spotify-client_1.1.42.622.gbd112320-37_amd64.deb: (null)
=> ERROR: spotify-1.1.42_3: failed to fetch spotify-client_1.1.42.622.gbd112320-37_amd64.deb.
```
Verbose curl-ling this file seems to indicate that the server closes the connection. Same thing happens if I try and use Firefox to download.
I'm creating this issue to keep track of this. In a day or so I'll try the download again, maybe their server's are feeling a little silly today. If this issue persists I'll dig further and hopefully I can find a fix and make a PR :)
### Steps to reproduce the behavior
0. Be in North America east coast
1. Clone down void-packages
2. In `etc/conf` place `XBPS_ALLOW_RESTRICTED=yes`
3. Run `./xbps-src binary-bootstrap && ./xbps-src pkg spotify`
next reply other threads:[~2021-01-22 0:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-22 0:00 Noah-Huppert [this message]
2021-01-22 0:52 ` ericonr
2021-01-23 1:32 ` [ISSUE] [CLOSED] " Noah-Huppert
2021-01-23 1:32 ` Noah-Huppert
2021-02-15 20:00 ` maop
2021-02-16 6:37 ` Noah-Huppert
2021-02-16 16:45 ` Noah-Huppert
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-28094@inbox.vuxu.org \
--to=noah-huppert@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).