Github messages for voidlinux
 help / color / mirror / Atom feed
From: strec007 <strec007@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] New package: nostr-rs-relay
Date: Wed, 10 May 2023 22:35:06 +0200	[thread overview]
Message-ID: <20230510203506.q-3H_Zk_JsHe_WoLlmFOhdxAeu-O4E37er5AlyPkpbs@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41558@inbox.vuxu.org>

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

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

https://github.com/strec007/void-packages _pc_nostr-rs-relay
https://github.com/void-linux/void-packages/pull/41558

New package: nostr-rs-relay
<!-- Uncomment relevant sections and delete options which are not applicable -->

#### Testing the changes
- I tested the changes in this PR: **YES**


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


<!-- 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, (x86_64-glibc)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
  - aarch64-musl
  - armv7l
  - x86_64-musl


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

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-_pc_nostr-rs-relay-41558.patch --]
[-- Type: text/x-diff, Size: 2199 bytes --]

From 852f21a69093e0f0c069380a78832ee920960bb6 Mon Sep 17 00:00:00 2001
From: Petr Cizmar <xxb0322@xpc.ovh>
Date: Tue, 10 Jan 2023 14:30:16 +0100
Subject: [PATCH] New package: nostr-rs-relay

---
 srcpkgs/nostr-rs-relay/INSTALL                |  7 ++++++
 .../nostr-rs-relay/files/nostr-rs-relay/run   |  5 +++++
 srcpkgs/nostr-rs-relay/template               | 22 +++++++++++++++++++
 3 files changed, 34 insertions(+)
 create mode 100644 srcpkgs/nostr-rs-relay/INSTALL
 create mode 100644 srcpkgs/nostr-rs-relay/files/nostr-rs-relay/run
 create mode 100644 srcpkgs/nostr-rs-relay/template

diff --git a/srcpkgs/nostr-rs-relay/INSTALL b/srcpkgs/nostr-rs-relay/INSTALL
new file mode 100644
index 000000000000..58317b3914b4
--- /dev/null
+++ b/srcpkgs/nostr-rs-relay/INSTALL
@@ -0,0 +1,7 @@
+# INSTALL
+case "$ACTION" in
+post)
+   DBDIR=/var/db/nostr-rs-relay
+   mkdir $DBDIR
+   chown _nostr:_nostr $DBDIR
+esac
diff --git a/srcpkgs/nostr-rs-relay/files/nostr-rs-relay/run b/srcpkgs/nostr-rs-relay/files/nostr-rs-relay/run
new file mode 100644
index 000000000000..6b7dab484e98
--- /dev/null
+++ b/srcpkgs/nostr-rs-relay/files/nostr-rs-relay/run
@@ -0,0 +1,5 @@
+#!/bin/sh
+exec 2>&1
+exec \
+	chpst -u _nostr:_nostr \
+	nostr-rs-relay -c /etc/nostr-rs-relay.toml -d /var/db/nostr-rs-relay/ 2>&1
diff --git a/srcpkgs/nostr-rs-relay/template b/srcpkgs/nostr-rs-relay/template
new file mode 100644
index 000000000000..8ed75add3ab5
--- /dev/null
+++ b/srcpkgs/nostr-rs-relay/template
@@ -0,0 +1,22 @@
+# Template file for 'nostr-rs-relay'
+pkgname=nostr-rs-relay
+version=0.8.9
+revision=1
+build_style=cargo
+hostmakedepends="pkg-config protobuf"
+makedepends="openssl-devel"
+short_desc="Nostr relay"
+maintainer="Petr Cizmar <xxb0322@xpc.ovh>"
+license="MIT"
+homepage="https://git.sr.ht/~gheartsfield/nostr-rs-relay"
+changelog="https://git.sr.ht/~gheartsfield/nostr-rs-relay/refs"
+distfiles="https://git.sr.ht/~gheartsfield/nostr-rs-relay/archive/${version}.tar.gz"
+checksum=a497340760fc99745fdb42c7ea04013d25bc57e50ca4749887129361866a98fa
+system_accounts="_nostr"
+system_groups="_nostr"
+
+post_install() {
+	vlicense "LICENSE"
+	vconf config.toml nostr-rs-relay.toml
+	vsv nostr-rs-relay
+}

  parent reply	other threads:[~2023-05-10 20:35 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-10 13:37 [PR PATCH] " strec007
2023-02-07 15:53 ` [PR PATCH] [Updated] " strec007
2023-02-22  9:49 ` strec007
2023-02-22 16:55 ` strec007
2023-02-22 20:15 ` icp1994
2023-02-22 20:33 ` strec007
2023-02-22 20:40 ` [PR PATCH] [Updated] " strec007
2023-02-22 21:26 ` strec007
2023-05-07 12:30 ` strec007
2023-05-10 16:20 ` [PR REVIEW] " classabbyamp
2023-05-10 16:20 ` classabbyamp
2023-05-10 16:20 ` classabbyamp
2023-05-10 18:06 ` [PR PATCH] [Updated] " strec007
2023-05-10 18:09 ` strec007
2023-05-10 18:12 ` strec007
2023-05-10 18:19 ` [PR REVIEW] " strec007
2023-05-10 18:23 ` [PR PATCH] [Updated] " strec007
2023-05-10 18:29 ` classabbyamp
2023-05-10 18:36 ` strec007
2023-05-10 20:35 ` strec007 [this message]
2023-05-10 21:02 ` [PR REVIEW] " classabbyamp
2023-05-10 21:35 ` Duncaen
2023-05-11  9:31 ` strec007
2023-05-11 10:00 ` [PR PATCH] [Updated] " strec007
2023-05-11 10:02 ` [PR REVIEW] " strec007
2023-05-23 14:56 ` strec007
2023-06-20  9:46 ` strec007
2023-08-18 16:00 ` TinfoilSubmarine
2023-08-24 14:09 ` [PR PATCH] [Updated] " strec007
2023-08-24 14:09 ` sgn
2023-11-23  1:46 ` github-actions
2023-12-07  1:46 ` [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=20230510203506.q-3H_Zk_JsHe_WoLlmFOhdxAeu-O4E37er5AlyPkpbs@z \
    --to=strec007@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).