From: paper42 <paper42@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] openocd: loosen jimtcl dep version restriction
Date: Mon, 04 Jul 2022 15:06:20 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-37836@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1273 bytes --]
There is a new pull request by paper42 against master on the void-packages repository
https://github.com/paper42/void-packages openocd-jimtcl
https://github.com/void-linux/void-packages/pull/37836
openocd: loosen jimtcl dep version restriction
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **NO**
@classabbyamp
<!--
#### 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/37836.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-openocd-jimtcl-37836.patch --]
[-- Type: text/x-diff, Size: 1898 bytes --]
From 14a4907381f710bc4b3f5368e20bc3b7a2fed00e Mon Sep 17 00:00:00 2001
From: Michal Vasilek <michal@vasilek.cz>
Date: Mon, 4 Jul 2022 15:01:25 +0200
Subject: [PATCH 1/2] openocd: loosen jimtcl dep version restriction
---
srcpkgs/openocd/template | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/srcpkgs/openocd/template b/srcpkgs/openocd/template
index 856977b045ec..d6370930edc1 100644
--- a/srcpkgs/openocd/template
+++ b/srcpkgs/openocd/template
@@ -4,6 +4,7 @@ version=0.11.0+1
revision=1
# update to a commit that has a compatible jimtcl version
_commit=830d70bfc66ada2a68c73283b9e4fa4770d408ee
+_jimtcl_version=0.81
wrksrc="${pkgname}-${_commit}"
build_style=gnu-configure
configure_args="
@@ -41,7 +42,8 @@ configure_args="
--enable-cmsis-dap-v2
--disable-internal-libjaylink"
hostmakedepends="automake pkg-config libtool which"
-makedepends="hidapi-devel jimtcl-devel-0.81_1 libftdi1-devel
+makedepends="hidapi-devel libftdi1-devel
+ jimtcl-devel>=${_jimtcl_version}_1<=${_jimtcl_version}_9999
libusb-devel libjaylink-devel capstone-devel"
short_desc="Open On-Chip Debugger"
maintainer="Érico Nogueira <ericonr@disroot.org>"
From 2be87d0ac1333f9858f7f80ae300659f3328943a Mon Sep 17 00:00:00 2001
From: Michal Vasilek <michal@vasilek.cz>
Date: Mon, 4 Jul 2022 15:04:00 +0200
Subject: [PATCH 2/2] jimtcl: mention version restriction in openocd
openocd depends on a specific version of jimtcl, so when jimtcl is
updated, openocd needs to be updated as well
---
srcpkgs/jimtcl/template | 1 +
1 file changed, 1 insertion(+)
diff --git a/srcpkgs/jimtcl/template b/srcpkgs/jimtcl/template
index 25d32bb5c5ae..0cf62f5657b6 100644
--- a/srcpkgs/jimtcl/template
+++ b/srcpkgs/jimtcl/template
@@ -1,5 +1,6 @@
# Template file for 'jimtcl'
pkgname=jimtcl
+# keep in sync with _jimtcl_version in openocd
version=0.81
revision=1
build_style=gnu-configure
next reply other threads:[~2022-07-04 13:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-04 13:06 paper42 [this message]
2022-07-04 13:17 ` [PR PATCH] [Merged]: " paper42
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-37836@inbox.vuxu.org \
--to=paper42@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).