Github messages for voidlinux
 help / color / mirror / Atom feed
From: k4leg <k4leg@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] reuse: update to 1.0.0.
Date: Fri, 03 Jun 2022 20:57:24 +0200	[thread overview]
Message-ID: <20220603185724.Id4usuLTYXv5OiTaf8dkWsYaLBR6oVRsUuWjHs403cQ@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-37269@inbox.vuxu.org>

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

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

https://github.com/k4leg/void-packages reuse-update
https://github.com/void-linux/void-packages/pull/37269

reuse: update to 1.0.0.
<!-- 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 [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-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/37269.patch is attached

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

From 8754094107675e9e49d76bb841977a0b0f855f5e Mon Sep 17 00:00:00 2001
From: Bogdan Drozd <python.bogdan@gmail.com>
Date: Tue, 24 May 2022 17:13:53 +0300
Subject: [PATCH] reuse: update to 1.0.0.

---
 srcpkgs/reuse/template | 14 ++++++++------
 1 file changed, 8 insertions(+), 6 deletions(-)

diff --git a/srcpkgs/reuse/template b/srcpkgs/reuse/template
index 156b73ea9dbe..9da8deb6dcb8 100644
--- a/srcpkgs/reuse/template
+++ b/srcpkgs/reuse/template
@@ -1,18 +1,20 @@
 # Template file for 'reuse'
 pkgname=reuse
-version=0.13.0
-revision=2
+version=1.0.0
+revision=1
 build_style=python3-module
+# These tests pass on local machine but don't pass in CI.
 make_check_args="--deselect tests/test_lint.py::test_lint_read_errors
+ --deselect tests/test_main_addheader.py::test_addheader_to_read_only_file_does_not_traceback
  --deselect tests/test_report.py::test_generate_project_report_read_error"
 hostmakedepends="python3-setuptools python3-setuptools_scm gettext"
 depends="python3-binaryornot python3-boolean.py python3-debian python3-Jinja2
- python3-license-expression python3-requests"
-checkdepends="python3-pytest $depends"
+ python3-license-expression python3-requests python3-setuptools"
+checkdepends="python3-pytest $depends git mercurial"
 short_desc="Helper tool for compliance with REUSE Specification"
 maintainer="k4leg <python.bogdan@gmail.com>"
-license="GPL-3.0-or-later, CC0-1.0, Apache-2.0"
+license="GPL-3.0-or-later, CC0-1.0, Apache-2.0, CC-BY-SA-4.0"
 homepage="https://reuse.software"
 changelog="https://raw.githubusercontent.com/fsfe/reuse-tool/master/CHANGELOG.md"
 distfiles="${PYPI_SITE}/r/reuse/reuse-${version}.tar.gz"
-checksum=89c87bd49308c8059cc36f8116872d73dc6e5788a29af8869be6532202bff801
+checksum=db3022be2d87f69c8f508b928023de3026f454ce17d01e22f770f7147ac1e8d4

  parent reply	other threads:[~2022-06-03 18:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-24 14:19 [PR PATCH] " k4leg
2022-05-24 14:39 ` [PR PATCH] [Updated] " k4leg
2022-06-03 17:23 ` [PR REVIEW] " paper42
2022-06-03 18:54 ` [PR PATCH] [Updated] " k4leg
2022-06-03 18:57 ` k4leg [this message]
2022-06-25  0:41 ` [PR PATCH] [Merged]: " classabbyamp

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=20220603185724.Id4usuLTYXv5OiTaf8dkWsYaLBR6oVRsUuWjHs403cQ@z \
    --to=k4leg@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).