Github messages for voidlinux
 help / color / mirror / Atom feed
From: g4s8 <g4s8@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] New package: hashcash-1.23
Date: Wed, 03 Feb 2021 17:12:14 +0100	[thread overview]
Message-ID: <20210203161214.4F-z0ZY22tkdeKTBTfPnTladcAlOsp29BmXAUxffvys@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-28379@inbox.vuxu.org>

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

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

https://github.com/g4s8/void-packages hashcash-1.23
https://github.com/void-linux/void-packages/pull/28379

New package: hashcash-1.23
<!-- Mark items with [x] where applicable -->
Added new `hashcash` package for www.hashcash.org/ 
It's currently available in default Debian and Ubuntu repositories, but not in Void repo.

#### General
- [x] This is a new package and it conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements)

#### Have the results of the proposed changes been tested?
- [x] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
- [ ] I generally don't use the affected packages but briefly tested this PR

<!--
If GitHub CI cannot be used to validate the build result (for example, if the
build is likely to take several hours), make sure to
[skip CI](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration).
When skipping CI, uncomment and fill out the following section.
Note: for builds that are likely to complete in less than 2 hours, it is not
acceptable to skip CI.
-->

#### Does it build and run successfully? 
(Please choose at least one native build and, if supported, at least one cross build. More are better.)
- [x] 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/28379.patch is attached

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

From ac817e081e743bfb027c1ac118c0a9281385fbef Mon Sep 17 00:00:00 2001
From: Kirill <g4s8.public@gmail.com>
Date: Mon, 1 Feb 2021 13:50:29 +0300
Subject: [PATCH] New package: hashcash-1.23

---
 srcpkgs/hashcash/patches/musl.patch | 11 +++++++++++
 srcpkgs/hashcash/template           | 14 ++++++++++++++
 2 files changed, 25 insertions(+)
 create mode 100644 srcpkgs/hashcash/patches/musl.patch
 create mode 100644 srcpkgs/hashcash/template

diff --git a/srcpkgs/hashcash/patches/musl.patch b/srcpkgs/hashcash/patches/musl.patch
new file mode 100644
index 00000000000..5c8cf15b38e
--- /dev/null
+++ b/srcpkgs/hashcash/patches/musl.patch
@@ -0,0 +1,11 @@
+--- array.h	2011-03-31 15:35:12.000000000 +0400
++++ array.h	2021-02-02 15:45:43.232048145 +0300
+@@ -3,6 +3,8 @@
+ #if !defined( _array_h )
+ #define _array_h
+ 
++#include <time.h>
++
+ #if defined( __cplusplus )
+ extern "C" {
+ #endif
diff --git a/srcpkgs/hashcash/template b/srcpkgs/hashcash/template
new file mode 100644
index 00000000000..5e325ef2feb
--- /dev/null
+++ b/srcpkgs/hashcash/template
@@ -0,0 +1,14 @@
+# Template file for 'hashcash'
+pkgname=hashcash
+version=1.23
+revision=1
+build_style=gnu-makefile
+make_build_args="LIBCRYPTO=-lcrypto generic-openssl docs"
+makedepends="libressl-devel"
+short_desc="Hashcash proof-of-work algorithm"
+maintainer="Kirill Che. <g4s8.public@gmail.com>"
+license="GPL-3.0-or-later"
+homepage="http://www.hashcash.org"
+distfiles="http://www.hashcash.org/source/hashcash-${version}-pr.tgz"
+checksum=03a85b6a8a84be93f76a7297fccd5f61dcb8255de25f3fbd77c26be3ef9be999
+conflicts="outils"

  parent reply	other threads:[~2021-02-03 16:12 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-01 10:54 [PR PATCH] " g4s8
2021-02-01 11:40 ` [PR PATCH] [Updated] " g4s8
2021-02-01 15:00 ` [PR REVIEW] " ericonr
2021-02-01 15:00 ` ericonr
2021-02-01 15:00 ` ericonr
2021-02-01 15:02 ` ericonr
2021-02-01 15:06 ` [PR REVIEW] " g4s8
2021-02-01 15:07 ` [PR PATCH] [Updated] " g4s8
2021-02-01 15:12 ` g4s8
2021-02-01 15:16 ` [PR REVIEW] " ericonr
2021-02-01 15:21 ` ericonr
2021-02-01 15:26 ` g4s8
2021-02-01 15:28 ` g4s8
2021-02-01 15:36 ` ericonr
2021-02-01 15:48 ` [PR PATCH] [Updated] " g4s8
2021-02-01 15:48 ` [PR REVIEW] " g4s8
2021-02-01 19:25 ` [PR PATCH] [Updated] " g4s8
2021-02-01 20:00 ` g4s8
2021-02-01 20:18 ` g4s8
2021-02-01 20:59 ` ericonr
2021-02-02  5:36 ` [PR PATCH] [Updated] " g4s8
2021-02-02  5:41 ` g4s8
2021-02-02 12:40 ` [PR REVIEW] " sgn
2021-02-02 12:40 ` sgn
2021-02-02 12:40 ` sgn
2021-02-02 12:49 ` [PR PATCH] [Updated] " g4s8
2021-02-02 12:51 ` [PR REVIEW] " g4s8
2021-02-02 12:52 ` [PR PATCH] [Updated] " g4s8
2021-02-02 12:53 ` [PR REVIEW] " sgn
2021-02-02 12:56 ` g4s8
2021-02-02 13:07 ` [PR PATCH] [Updated] " g4s8
2021-02-02 13:08 ` [PR REVIEW] " ericonr
2021-02-02 13:09 ` ericonr
2021-02-02 13:13 ` [PR PATCH] [Updated] " g4s8
2021-02-02 13:13 ` [PR REVIEW] " g4s8
2021-02-02 13:14 ` ericonr
2021-02-02 13:14 ` [PR REVIEW] " sgn
2021-02-02 13:15 ` ericonr
2021-02-02 13:19 ` [PR PATCH] [Updated] " g4s8
2021-02-02 13:24 ` g4s8
2021-02-02 13:33 ` [PR REVIEW] " g4s8
2021-02-02 13:46 ` ericonr
2021-02-02 14:03 ` g4s8
2021-02-03 15:55 ` abenson
2021-02-03 16:01 ` ericonr
2021-02-03 16:11 ` [PR PATCH] [Updated] " abenson
2021-02-03 16:12 ` g4s8 [this message]
2021-02-03 16:12 ` g4s8
2021-02-03 16:14 ` [PR REVIEW] " g4s8
2021-05-01  5:08 ` [PR PATCH] [Closed]: " g4s8

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=20210203161214.4F-z0ZY22tkdeKTBTfPnTladcAlOsp29BmXAUxffvys@z \
    --to=g4s8@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).