From: sgn <sgn@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] Bcc fix
Date: Mon, 02 Aug 2021 13:24:50 +0200 [thread overview]
Message-ID: <20210802112450.NEt2bw-W5kdPAKvO5zfy2Pw5NA7h3uUiy7OBS7Rpzd0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-32296@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1573 bytes --]
There is an updated pull request by sgn against master on the void-packages repository
https://github.com/chexum/void-packages bcc-fix
https://github.com/void-linux/void-packages/pull/32296
Bcc fix
<!-- 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-glibc)
- [x] I built this PR locally for these architectures (if supported. mark crossbuilds):
- [x] aarch64-glibc
- [ ] armv7l
- [ ] armv6l-musl
-->
A patch file from https://github.com/void-linux/void-packages/pull/32296.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-bcc-fix-32296.patch --]
[-- Type: text/x-diff, Size: 1422 bytes --]
From 99a7b555e7bc849885a5d817322e7ded3b6c8ba8 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=C4=90o=C3=A0n=20Tr=E1=BA=A7n=20C=C3=B4ng=20Danh?=
<congdanhqx@gmail.com>
Date: Sat, 31 Jul 2021 12:12:41 +0700
Subject: [PATCH] bcc: (really) update to 0.21.0.
Versioning downloaded files to avoid forgetting update checksum.
See: 13d27981fc, (bcc: update to 0.21.0., 2021-07-29)
---
srcpkgs/bcc/template | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/srcpkgs/bcc/template b/srcpkgs/bcc/template
index 5fdf8be098b3..5a3e66c86c5d 100644
--- a/srcpkgs/bcc/template
+++ b/srcpkgs/bcc/template
@@ -1,7 +1,7 @@
# Template file for 'bcc'
pkgname=bcc
version=0.21.0
-revision=1
+revision=2
wrksrc="bcc"
build_style=cmake
configure_args="-DREVISION=${version}"
@@ -12,8 +12,8 @@ short_desc="BPF-based Linux IO analysis, networking, monitoring, and more"
maintainer="Leah Neukirchen <leah@vuxu.org>"
license="Apache-2.0"
homepage="https://github.com/iovisor/bcc"
-distfiles="https://github.com/iovisor/bcc/releases/download/v${version}/bcc-src-with-submodule.tar.gz"
-checksum=93edc925675262aa509f5eaf146f2fc7dfa3e01d1b0336a5de01ee6d72fa493b
+distfiles="https://github.com/iovisor/bcc/releases/download/v${version}/bcc-src-with-submodule.tar.gz>bcc-${version}.tar.gz"
+checksum=5323e2a505f6868976d973a234202332ec25dc36f0bf7c118c23fc24f6147215
python_version="3"
if [ "$XBPS_TARGET_NO_ATOMIC8" ]; then
next prev parent reply other threads:[~2021-08-02 11:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-02 11:08 [PR PATCH] " chexum
2021-08-02 11:09 ` [PR PATCH] [Updated] " chexum
2021-08-02 11:24 ` sgn [this message]
2021-08-02 20:25 ` ericonr
2021-08-02 20:25 ` [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=20210802112450.NEt2bw-W5kdPAKvO5zfy2Pw5NA7h3uUiy7OBS7Rpzd0@z \
--to=sgn@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).