Github messages for voidlinux
 help / color / mirror / Atom feed
From: maop <maop@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: spotify package currently broken due to an upstream download failure
Date: Mon, 15 Feb 2021 21:00:39 +0100	[thread overview]
Message-ID: <20210215200039.7xkPHldUZFpE4u4e8SuYhlsCKAyUDLlRsrPS-_BPi1I@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-28094@inbox.vuxu.org>

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

New comment by maop on void-packages repository

https://github.com/void-linux/void-packages/issues/28094#issuecomment-779424009

Comment:
Hello, i just had this problem too

```
=> 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 1%] 3766B/s ETA: 08h24m
spotify-client_1.1.42.622.gbd112320-37_amd64.deb: [120MB 1%] 88KB/s ETA: 27m14s
spotify-client_1.1.42.622.gbd112320-37_amd64.deb: [120MB 2%] 199KB/s ETA: 11m09s
spotify-client_1.1.42.622.gbd112320-37_amd64.deb: [120MB 2%] 308KB/s ETA: 07m00s
spotify-client_1.1.42.622.gbd112320-37_amd64.deb: [120MB 3%] 454KB/s ETA: 04m40s
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.
```

I tried to download the .deb file with wget and found out that the remote server disconnects and cancels de download

```
$ wget https://repository-origin.spotify.com/pool/non-free/s/spotify-client/spotify-client_1.1.42.622.gbd112320-37_amd64.deb
--2021-02-15 13:44:12--  https://repository-origin.spotify.com/pool/non-free/s/spotify-client/spotify-client_1.1.42.622.gbd112320-37_amd64.deb
Resolviendo repository-origin.spotify.com (repository-origin.spotify.com)... 35.186.224.25, 2600:1901:1:c36::
Conectando con repository-origin.spotify.com (repository-origin.spotify.com)[35.186.224.25]:443... conectado.
Petición HTTP enviada, esperando respuesta... 200 OK
Longitud: 126293582 (120M) [application/octet-stream]
Grabando a: «spotify-client_1.1.42.622.gbd112320-37_amd64.deb»

spotify-client_1.1.42.622.gbd   1%[                                                  ]   2.22M   545KB/s    en 4.8s    

2021-02-15 13:44:18 (478 KB/s) - Conexión cerrada en el byte 2326710. Reintentando.

--2021-02-15 13:44:19--  (intento: 2)  https://repository-origin.spotify.com/pool/non-free/s/spotify-client/spotify-client_1.1.42.622.gbd112320-37_amd64.deb
Conectando con repository-origin.spotify.com (repository-origin.spotify.com)[35.186.224.25]:443... conectado.
Petición HTTP enviada, esperando respuesta... 206 Partial Content
Longitud: 126293582 (120M), quedan 123966872 (118M) [application/octet-stream]
Grabando a: «spotify-client_1.1.42.622.gbd112320-37_amd64.deb»

spotify-client_1.1.42.622.gbd  30%[==============>                                   ]  37.02M  5.90MB/s    en 6.3s    

2021-02-15 13:44:25 (5.52 MB/s) - Conexión cerrada en el byte 38814691. Reintentando.
```

Even in a browser download disconnects! Anyway, my workaround was to download the deb with `wget -c` and put it in `hostdir/sources/spotify-1.1.42/` then the binary builds correctly.

Is there a way to tell xbps-src to retry the download (with resume) for X times?

  parent reply	other threads:[~2021-02-15 20:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-22  0:00 [ISSUE] " Noah-Huppert
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 [this message]
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=20210215200039.7xkPHldUZFpE4u4e8SuYhlsCKAyUDLlRsrPS-_BPi1I@z \
    --to=maop@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).