From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: [PR PATCH] flashrom: update to 1.1
Date: Thu, 20 Jun 2019 02:29:15 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-12562@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 324 bytes --]
There is a new pull request by emacsomancer against master on the void-packages repository
https://github.com/emacsomancer/void-packages flashrom-v1.1
https://github.com/void-linux/void-packages/pull/12562
flashrom: update to 1.1
A patch file from https://github.com/void-linux/void-packages/pull/12562.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-flashrom-v1.1-12562.patch --]
[-- Type: application/text/x-diff, Size: 1345 bytes --]
From bba4440251dc5e422a5b2fc1498204c8a690cdb9 Mon Sep 17 00:00:00 2001
From: Benjamin Slade <slade@jnanam.net>
Date: Wed, 19 Jun 2019 18:27:58 -0600
Subject: [PATCH] flashrom: update to 1.1
---
srcpkgs/flashrom/template | 14 +++++++-------
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/srcpkgs/flashrom/template b/srcpkgs/flashrom/template
index 57bd4180b5f..b773671d5b4 100644
--- a/srcpkgs/flashrom/template
+++ b/srcpkgs/flashrom/template
@@ -1,16 +1,16 @@
# Template file for 'flashrom'
pkgname=flashrom
-version=1.0
+version=1.1
revision=1
+build_style=gnu-makefile
+hostmakedepends="pkg-config"
+makedepends="pciutils-devel libusb-compat-devel"
short_desc="Utility for reading, writing, erasing and verifying flash ROM chips"
maintainer="Juan RP <xtraeme@voidlinux.org>"
-makedepends="pciutils-devel libusb-compat-devel"
-hostmakedepends="pkg-config"
-homepage="http://www.flashrom.org"
-build_style=gnu-makefile
license="GPL-2"
-distfiles=https://download.flashrom.org/releases/$pkgname-$version.tar.bz2
-checksum=3702fa215ba5fb5af8e54c852d239899cfa1389194c1e51cb2a170c4dc9dee64
+homepage="http://www.flashrom.org"
+distfiles=https://github.com/flashrom/flashrom/archive/v$version.tar.gz
+checksum=b9bb67331bdde70d1f73c07fe770f32eb6dc8990ba87a10ee14ea8f722a3f810
pre_build() {
sed -i "s:sbin:bin:g" Makefile
next reply other threads:[~2019-06-20 0:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-20 0:29 voidlinux-github [this message]
2019-06-20 8:25 ` voidlinux-github
2019-06-20 20:10 ` [PR PATCH] [Closed]: " voidlinux-github
2019-06-20 20:10 ` voidlinux-github
2019-06-20 20:29 [PR PATCH] " voidlinux-github
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-12562@inbox.vuxu.org \
--to=voidlinux-github@inbox.vuxu.org \
--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).