From: "Peter Müller" <peter.mueller@link38.eu>
To: development@lists.ipfire.org
Subject: [PATCH v2] pciutils: update to 3.5.6
Date: Wed, 15 Aug 2018 16:55:44 +0200 [thread overview]
Message-ID: <00bc9593-1316-88ff-0b6c-c0d4423c3f9a@link38.eu> (raw)
[-- Attachment #1: Type: text/plain, Size: 2271 bytes --]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
The second version of this patch supersedes the first one,
which contained crappy line wraps due to a bug in PGP/MIME
implementation in MUA.
Signed-off-by: Peter Müller <peter.mueller(a)link38.eu>
- ---
config/rootfiles/common/pciutils | 2 +-
lfs/pciutils | 6 +++---
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/config/rootfiles/common/pciutils b/config/rootfiles/common/pciutils
index 5bb11a259..da35ef6a1 100644
- --- a/config/rootfiles/common/pciutils
+++ b/config/rootfiles/common/pciutils
@@ -1,7 +1,7 @@
bin/lspci
bin/setpci
lib/libpci.so.3
- -lib/libpci.so.3.4.1
+lib/libpci.so.3.5.6
sbin/update-pciids
#usr/include/pci
#usr/include/pci/config.h
diff --git a/lfs/pciutils b/lfs/pciutils
index 7c313ba3e..1ebfef0c8 100644
- --- a/lfs/pciutils
+++ b/lfs/pciutils
@@ -24,10 +24,10 @@
include Config
- -VER = 3.4.1
+VER = 3.5.6
THISAPP = pciutils-$(VER)
- -DL_FILE = $(THISAPP).tar.xz
+DL_FILE = $(THISAPP).tar.gz
DL_FROM = $(URL_IPFIRE)
DIR_APP = $(DIR_SRC)/$(THISAPP)
TARGET = $(DIR_INFO)/$(THISAPP)
@@ -40,7 +40,7 @@ objects = $(DL_FILE)
$(DL_FILE) = $(DL_FROM)/$(DL_FILE)
- -$(DL_FILE)_MD5 = 35763bb1eab7bc9bf6eb6efb72cbc8a1
+$(DL_FILE)_MD5 = 63b347d2bb5719b7769c03a1bb72a5b7
install : $(TARGET)
- --
2.16.4
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEvP4SiGhEYDJyrRLk2UjyD317n2gFAlt0Pu8ACgkQ2UjyD317
n2jPAA/8DKTI7qWx+B/ImrukDn0jthFhgzOiCFCU5d8GChR5YgP5c6nhuVo2rPEH
Riwr7TxdZ4dXKt66Fojw59iNNkE9hGAmEgkve06DQPrUH5z3irsF81BysHzgtu/+
Z7nzxge6OIWlbygvmNh9Qu7Hi9OyW8O4D7LJkqVUXkV1DKzuLVOFhAnMF5OqUp6k
R0WoaERo6GMrzzJSggnjHB4XSl2sr1+DTbrdJL4f/3LxO9ZY8zoZ1gh+zDY49p9N
l406pXNMMlBRnbDaEuasiNbDSSsWIl97hKAO98KHlbtZew7DyFK/VR9JYTqJ1muv
Dt1a8fznX2fEAuGcYJzwuV1sCs1Nt4CCOHureLkVL+vOeL/yxqJZRp9Xa+02XI8K
vYBu3kk/3sAVUPR4kDm9oUJgTbm7O7nCvEBhP8jeCF8dWpV20zpZOmEiXveBA7KW
Qz9dnyZLZibAR4kk1F9G7deSAbxgQOStmv55cH69MEakEB1UbTvMqu8j79hK/S+F
LEj4RRXddVzC+V59u2tUQExnB0WxSSoCURUB+BXKYxRgfptvCmkXXQrJHRO1PhMq
y9RvLPXRWxZzxodgzkEXQoJZzQRSdPVea8HNpN0E60yeZ7ydzgb2v15c0TkpPXzR
ARUBiZieNFUkbjuGQXnzYJXAOrdGhdoL3zVuye7UfaoXOI3SeT4=
=MPld
-----END PGP SIGNATURE-----
reply other threads:[~2018-08-15 14:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=00bc9593-1316-88ff-0b6c-c0d4423c3f9a@link38.eu \
--to=peter.mueller@link38.eu \
--cc=development@lists.ipfire.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