Github messages for voidlinux
 help / color / mirror / Atom feed
From: heliocat <heliocat@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] binfmt-support: fix license, fix build
Date: Wed, 07 Apr 2021 21:20:35 +0200	[thread overview]
Message-ID: <20210407192035.FYcMIkW5XUG45js2kFiKWQTl13GkUJQjEQE9S0QtaGg@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-29802@inbox.vuxu.org>

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

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

https://github.com/heliocat/void-packages binfmt-support
https://github.com/void-linux/void-packages/pull/29802

binfmt-support: fix license, fix build
<!-- Mark items with [x] where applicable -->

#### General
- [ ] 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?
- [ ] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
- [x] 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, (x86-64)
- [ ] 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/29802.patch is attached

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

From 250a2fcdfaa95a610256989e19e2cf43eb0f902a Mon Sep 17 00:00:00 2001
From: Colin Booth <colin@heliocat.net>
Date: Sun, 28 Mar 2021 01:23:07 -0700
Subject: [PATCH] binfmt-support: fix license, fix build

---
 srcpkgs/binfmt-support/template | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/srcpkgs/binfmt-support/template b/srcpkgs/binfmt-support/template
index 4208b1969b05..252d05051cd3 100644
--- a/srcpkgs/binfmt-support/template
+++ b/srcpkgs/binfmt-support/template
@@ -1,13 +1,13 @@
 # Template file for 'binfmt-support'
 pkgname=binfmt-support
 version=2.2.1
-revision=1
+revision=2
 build_style=gnu-configure
 hostmakedepends="pkg-config"
 makedepends="libpipeline-devel"
 short_desc="Register interpreters for various binary formats"
 maintainer="Andrea Brancaleoni <abc@pompel.me>"
-license="GPL-3"
+license="GPL-2.0-or-later"
 homepage="http://packages.debian.org/en/sid/binfmt-support"
 distfiles="${DEBIAN_SITE}/main/b/binfmt-support/binfmt-support_$version.orig.tar.gz"
 checksum=9c9da3306501a834663ccd14023fc8d29bd08a34df74585e11f97735ea1fb31d

  parent reply	other threads:[~2021-04-07 19:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-28  8:26 [PR PATCH] " heliocat
2021-03-28  8:29 ` [PR PATCH] [Updated] " heliocat
2021-03-28 16:00 ` ericonr
2021-03-28 16:29 ` heliocat
2021-04-04 23:17 ` ericonr
2021-04-07 19:20 ` heliocat [this message]
2021-04-07 19:20 ` heliocat
2021-04-07 19:24 ` [PR PATCH] [Closed]: " ericonr

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=20210407192035.FYcMIkW5XUG45js2kFiKWQTl13GkUJQjEQE9S0QtaGg@z \
    --to=heliocat@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).