From: classabbyamp <classabbyamp@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: spotify: update to 1.2.31.
Date: Wed, 27 Mar 2024 06:35:43 +0100 [thread overview]
Message-ID: <20240327053543.7576B210A7@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-48955@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 2701 bytes --]
There's a closed pull request on the void-packages repository
spotify: update to 1.2.31.
https://github.com/void-linux/void-packages/pull/48955
Description:
#### Testing the changes
- I tested the changes in this PR: **YES**
#### Local build testing
- I built this PR locally for my native architecture, (x86_64)
Current upstream does not work. Log:
```
=> xbps-src: updating repositories for host (x86_64)...
[*] Updating repository `https://repo-default.voidlinux.org/current/bootstrap/x86_64-repodata' ...
[*] Updating repository `https://repo-default.voidlinux.org/current/x86_64-repodata' ...
[*] Updating repository `https://repo-default.voidlinux.org/current/nonfree/x86_64-repodata' ...
[*] Updating repository `https://repo-default.voidlinux.org/current/debug/x86_64-repodata' ...
[*] Updating repository `https://repo-default.voidlinux.org/current/multilib/bootstrap/x86_64-repodata' ...
[*] Updating repository `https://repo-default.voidlinux.org/current/multilib/x86_64-repodata' ...
[*] Updating repository `https://repo-default.voidlinux.org/current/multilib/nonfree/x86_64-repodata' ...
=> xbps-src: updating software in / masterdir...
=> xbps-src: cleaning up / masterdir...
=> spotify-1.2.26_1: removing autodeps, please wait...
=> spotify-1.2.26_1: building for x86_64...
[host] libcurl-8.6.0_1: found (https://repo-default.voidlinux.org/current)
[runtime] libcurl-8.6.0_1: found (https://repo-default.voidlinux.org/current)
=> spotify-1.2.26_1: installing host dependencies: libcurl-8.6.0_1 ...
=> spotify-1.2.26_1: running do-fetch hook: 00-distfiles ...
=> spotify-1.2.26_1: fetching distfile 'spotify-client_1.2.26.1187.g36b715a1_amd64.deb' from 'http://repository.spotify.com/pool/non-free/s/spotify-client/spotify-client_1.2.26.1187.g36b715a1_amd64.deb'...
http://repository.spotify.com/pool/non-free/s/spotify-client/spotify-client_1.2.26.1187.g36b715a1_amd64.deb: Not Found
=> ERROR: spotify-1.2.26_1: failed to fetch 'spotify-client_1.2.26.1187.g36b715a1_amd64.deb'.
```
Version 1.2.31 exists on the upstream but Spotify launches with a gray screen on my testing machine. Current upstream does not exist thus, ~it might be a good idea to downgrade the version unless installation of 1.2.31 is confirmed to work correctly.~
Edit:
I am unsure as if this problem only exists for me but even tough Spotify launches correctly it gives an error during login saying:
`A firewall may be blocking Spotify. Please update your firewall to allow Spotify. Additionally you could try changing the currently used proxy settings`
I need further confirmation and testing as both 1.2.31 and 1.1.26 seem to be working incorrectly on my machine.
next prev parent reply other threads:[~2024-03-27 5:35 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-26 19:41 [PR PATCH] spotify: downgrade version to 1.1.26 hsnovel
2024-02-26 20:13 ` dataCobra
2024-02-26 20:30 ` hsnovel
2024-02-27 6:17 ` dataCobra
2024-02-27 6:18 ` dataCobra
2024-02-27 20:13 ` hsnovel
2024-02-27 20:18 ` hsnovel
2024-02-27 20:24 ` hsnovel
2024-02-28 6:45 ` dataCobra
2024-02-28 10:22 ` [PR PATCH] [Updated] " hsnovel
2024-02-28 10:26 ` hsnovel
2024-02-28 11:57 ` Clos3y
2024-02-28 12:45 ` [PR PATCH] [Updated] spotify: update to 1.2.31 hsnovel
2024-02-28 12:46 ` hsnovel
2024-03-02 15:54 ` classabbyamp
2024-03-02 16:29 ` [PR PATCH] [Updated] " hsnovel
2024-03-27 5:35 ` classabbyamp
2024-03-27 5:35 ` classabbyamp [this message]
2024-03-26 12:25 [PR PATCH] Updated Spotify " jasoncsleung
2024-03-27 2:34 ` [PR PATCH] [Closed]: spotify: update " jasoncsleung
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=20240327053543.7576B210A7@inbox.vuxu.org \
--to=classabbyamp@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).