From: Chocimier <Chocimier@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] spotify: SHA256 of EULA mismatching
Date: Mon, 18 Jan 2021 22:09:27 +0100 [thread overview]
Message-ID: <20210118210927.rzM75sl7eIbhwUxJnqc6SwXxMjXE_aYVUAkpH9wj_xI@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-27998@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1198 bytes --]
Closed issue by waynevanson on void-packages repository
https://github.com/void-linux/void-packages/issues/27998
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 uptodate rrFFFFFFF
* package:
spotify-1.1.42_2
### Expected behavior
Installing package works without any errors.
### Actual behavior
`post_extract()` calls `message_error()` because the checksum of Spotify's EULA does not match the current.
```bash
post_extract() {
curl -L https://www.spotify.com/us/legal/end-user-agreement/ |
w3m -dump -I utf-8 -T text/html |
sed -n '/Spotify Terms and Conditions of Use/,/^USA$/p' > EULA
filesum="$(xbps-digest EULA)"
if [ "$filesum" != "$_license_checksum" ]; then
msg_error "SHA256 mismatch for EULA:\n$filesum\n"
fi
}
```
### Steps to reproduce the behavior
- enable restricted packages
- `./xbps-src pkg spotify` in `void-packages/`
### Questions
@teh-jazzman What is the reason behind checking the EULA and throwing an error?
next prev parent reply other threads:[~2021-01-18 21:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-17 23:24 [ISSUE] " waynevanson
2021-01-18 18:34 ` teh-jazzman
2021-01-18 19:00 ` ericonr
2021-01-18 19:03 ` ericonr
2021-01-18 21:09 ` Chocimier
2021-01-18 21:09 ` Chocimier [this message]
2021-10-08 5:23 ` Animeshz
2021-10-09 7:06 ` teh-jazzman
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=20210118210927.rzM75sl7eIbhwUxJnqc6SwXxMjXE_aYVUAkpH9wj_xI@z \
--to=chocimier@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).