Github messages for voidlinux
 help / color / mirror / Atom feed
From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: [PR PATCH] rooster: update to 2.8.2
Date: Wed, 06 Nov 2019 06:09:35 +0100	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-16177@inbox.vuxu.org> (raw)

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

There is a new pull request by ndowens against master on the void-packages repository

https://github.com/ndowens/void-packages rooster
https://github.com/void-linux/void-packages/pull/16177

rooster: update to 2.8.2
Unmark broken for aarch64 and ppc64

@q66 Can you test this on ppc64? aarch64 pkg'd fine, but I can't test it; if it now works on ppc64 then chance previous issue has been fixed.

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

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-rooster-16177.patch --]
[-- Type: text/x-diff, Size: 1539 bytes --]

From ab441ef7439b4fc048213d48a45356f6cd0036ff Mon Sep 17 00:00:00 2001
From: Nathan Owens <ndowens04@gmail.com>
Date: Tue, 5 Nov 2019 22:49:10 -0600
Subject: [PATCH] rooster: update to 2.8.2

Unmark broken for aarch64 and ppc64
---
 srcpkgs/rooster/template | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/srcpkgs/rooster/template b/srcpkgs/rooster/template
index 9e5c5851faf..daf8fcc0adb 100644
--- a/srcpkgs/rooster/template
+++ b/srcpkgs/rooster/template
@@ -1,7 +1,7 @@
 # Template file for 'rooster'
 pkgname=rooster
-version=2.8.0
-revision=2
+version=2.8.2
+revision=1
 build_style=cargo
 hostmakedepends="pkg-config python3"
 makedepends="libX11-devel libXmu-devel libressl-devel libsodium-devel"
@@ -10,11 +10,11 @@ maintainer="Orphaned <orphan@voidlinux.org>"
 license="Apache-2.0"
 homepage="https://github.com/conradkdotcom/rooster"
 distfiles="https://github.com/conradkdotcom/rooster/archive/v${version}.tar.gz"
-checksum=49647992eb48ef7df4ffee897aeb8f651e403c86d08c5dac92bb96547951a68a
+checksum=73d62fde548cf13936db5918b67acc2d7590b44f99cc79811c144412f0a3102d
 
-case "$XBPS_TARGET_MACHINE" in
-	aarch64*|ppc64*) broken="undefined reference to rust_crypto_util_fixed_time_eq_asm https://github.com/DaGenix/rust-crypto/issues/383" ;;
-esac
+#case "$XBPS_TARGET_MACHINE" in
+#	aarch64*|ppc64*) broken="undefined reference to rust_crypto_util_fixed_time_eq_asm https://github.com/DaGenix/rust-crypto/issues/383" ;;
+#esac
 
 pre_build() {
 	cargo update --package openssl-sys --precise 0.9.46

             reply	other threads:[~2019-11-06  5:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-06  5:09 voidlinux-github [this message]
2019-11-06 18:25 ` [No merge] " voidlinux-github
2019-11-06 21:15 ` voidlinux-github
2019-11-06 21:18 ` voidlinux-github
2019-11-06 21:31 ` [PR PATCH] [Updated] " voidlinux-github
2019-11-07 14:51 ` [PR PATCH] [Merged]: " voidlinux-github

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-16177@inbox.vuxu.org \
    --to=voidlinux-github@inbox.vuxu.org \
    --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).