Github messages for voidlinux
 help / color / mirror / Atom feed
From: sprocklem <sprocklem@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] New package: gurk-0.2.4
Date: Thu, 04 Aug 2022 05:02:00 +0200	[thread overview]
Message-ID: <20220804030200.nh2hf3NYmue6qxp7J7W4EC5FEWE8aiUCc0RBNk09PbM@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38398@inbox.vuxu.org>

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

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

https://github.com/sprocklem/void-packages gurk
https://github.com/void-linux/void-packages/pull/38398

New package: gurk-0.2.4
#### Testing the changes
- I tested the changes in this PR: **YES**

#### New package
- This new package conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements): **YES**

#### Local build testing
- I built this PR locally for my native architecture, x86_64-glibc
- I built this PR locally for these architectures (if supported. mark crossbuilds):
  - armv7l

(Requested in issue #28974)

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

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

From 7249fd7b7144b41bc7f4731de75e23eb237696b1 Mon Sep 17 00:00:00 2001
From: Maeve Sproule <sprocklem@gmail.com>
Date: Sun, 31 Jul 2022 15:04:58 -0600
Subject: [PATCH] New package: gurk-0.2.4

---
 .../patches/fix-x86_64-musl-segfault.patch    | 16 ++++++++++++++++
 srcpkgs/gurk/template                         | 19 +++++++++++++++++++
 2 files changed, 35 insertions(+)
 create mode 100644 srcpkgs/gurk/patches/fix-x86_64-musl-segfault.patch
 create mode 100644 srcpkgs/gurk/template

diff --git a/srcpkgs/gurk/patches/fix-x86_64-musl-segfault.patch b/srcpkgs/gurk/patches/fix-x86_64-musl-segfault.patch
new file mode 100644
index 000000000000..8fc2de582b8b
--- /dev/null
+++ b/srcpkgs/gurk/patches/fix-x86_64-musl-segfault.patch
@@ -0,0 +1,16 @@
+diff -ruN a/.cargo/config.toml b/.cargo/config.toml
+--- a/.cargo/config.toml	2022-06-16 01:53:04.000000000 -0600
++++ b/.cargo/config.toml	2022-08-03 20:38:45.059841310 -0600
+@@ -13,4 +13,4 @@
+ linker = "rust-lld"
+ 
+# Without this, check stage fails with a SIGSEGV. Honestly, I can't test this
+# on my own computer (since it only occurs on this one target, which I don't
+# have on any of my systems), so this is currently a guess as to what the
+# problem is. But given that this doesn't occur on armv7l-musl, this makes the
+# most sense. If this doesn't work, I'm gonna have to create a x86_64-musl
+# partition to figure this out.
+# This workaround is from <https://github.com/rust-lang/rust/issues/82193>.
+ [target.x86_64-unknown-linux-musl]
+-rustflags = ["-Clink-self-contained=yes"]
++rustflags = ["-Clink-self-contained=yes", "-Ctarget-feature=-crt-static"]
diff --git a/srcpkgs/gurk/template b/srcpkgs/gurk/template
new file mode 100644
index 000000000000..1fa113085665
--- /dev/null
+++ b/srcpkgs/gurk/template
@@ -0,0 +1,19 @@
+# Template file for 'gurk'
+pkgname=gurk
+version=0.2.4
+revision=1
+archs="x86_64* i686* armv[67]* aarch64*" # depends (indirectly) on ring
+wrksrc="gurk-rs-${version}"
+build_style=cargo
+hostmakedepends="clang llvm protobuf"
+short_desc="Signal Messenger client for terminal"
+maintainer="Maeve Sproule <sprocklem@gmail.com>"
+license="AGPL-3.0-only"
+homepage="https://github.com/boxdot/gurk-rs"
+changelog="https://raw.githubusercontent.com/boxdot/gurk-rs/master/CHANGELOG.md"
+distfiles="https://github.com/boxdot/gurk-rs/archive/refs/tags/v${version}.tar.gz"
+checksum=fca42ea73a37514b17d7471cefe71233994dfa2d44da487358b3130dcd4780ca
+
+post_install() {
+	vlicense LICENSE-AGPL-3.0
+}

  parent reply	other threads:[~2022-08-04  3:02 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-31 21:20 [PR PATCH] " sprocklem
2022-07-31 21:28 ` [PR REVIEW] " classabbyamp
2022-07-31 21:46 ` [PR PATCH] [Updated] " sprocklem
2022-07-31 21:53 ` sprocklem
2022-07-31 22:05 ` [PR REVIEW] " classabbyamp
2022-07-31 22:47 ` [PR PATCH] [Updated] " sprocklem
2022-08-01 11:47 ` sprocklem
2022-08-04  3:02 ` sprocklem [this message]
2022-08-04 20:08 ` sprocklem
2022-11-03  2:13 ` github-actions
2022-11-18  2:12 ` [PR PATCH] [Closed]: " github-actions

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=20220804030200.nh2hf3NYmue6qxp7J7W4EC5FEWE8aiUCc0RBNk09PbM@z \
    --to=sprocklem@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).