Github messages for voidlinux
 help / color / mirror / Atom feed
From: paper42 <paper42@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] spotify-tui: fix build with recent rust
Date: Sat, 20 Aug 2022 18:54:26 +0200	[thread overview]
Message-ID: <20220820165426.e5J98abKLwszcSWm20dd4CgDezTDQUITea4FRr8MzP8@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38796@inbox.vuxu.org>

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

There is an updated pull request by paper42 against master on the void-packages repository

https://github.com/paper42/void-packages spotify-fix-rust
https://github.com/void-linux/void-packages/pull/38796

spotify-tui: fix build with recent rust
<!-- Uncomment relevant sections and delete options which are not applicable -->

#### Testing the changes
- I tested the changes in this PR: **NO** only compile tested

@abenson I don't use spotify, but this seems to fix compilation issues with recent rust versions

<!--
#### New package
- This new package conforms to the [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **YES**|**NO**
-->

<!-- Note: If the build is likely to take more than 2 hours, please add ci skip tag as described in
https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->
<!--
#### Local build testing
- I built this PR locally for my native architecture, (ARCH-LIBC)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
  - aarch64-musl
  - armv7l
  - armv6l-musl
-->


A patch file from https://github.com/void-linux/void-packages/pull/38796.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-spotify-fix-rust-38796.patch --]
[-- Type: text/x-diff, Size: 963 bytes --]

From c7245dc1d358757b6ada7de9f6a5a106487ba32b Mon Sep 17 00:00:00 2001
From: Michal Vasilek <michal@vasilek.cz>
Date: Sat, 20 Aug 2022 17:17:40 +0200
Subject: [PATCH] spotify-tui: fix build with recent rust

---
 srcpkgs/spotify-tui/template | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/srcpkgs/spotify-tui/template b/srcpkgs/spotify-tui/template
index 8f94ee843c6f..3db1d2af43bf 100644
--- a/srcpkgs/spotify-tui/template
+++ b/srcpkgs/spotify-tui/template
@@ -13,7 +13,10 @@ distfiles="https://github.com/Rigellute/spotify-tui/archive/v${version}.tar.gz"
 checksum=9d6fa998e625ceff958a5355b4379ab164ba76575143a7b6d5d8aeb6c36d70a7
 
 pre_build() {
-	cargo update --package openssl-sys --precise 0.9.58
+	# fix various compilation issues
+	cargo update --package num-traits:0.2.12 --precise 0.2.15
+	cargo update --package num-integer:0.1.43 --precise 0.1.45
+	cargo update --package autocfg:1.0.0 --precise 1.1.0
 }
 
 post_install() {

  parent reply	other threads:[~2022-08-20 16:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-20 15:38 [PR PATCH] " paper42
2022-08-20 16:16 ` paper42
2022-08-20 16:54 ` paper42 [this message]
2022-08-20 16:54 ` paper42
2022-08-23 21:12 ` [PR PATCH] [Closed]: " abenson

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=20220820165426.e5J98abKLwszcSWm20dd4CgDezTDQUITea4FRr8MzP8@z \
    --to=paper42@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).