From: tranzystorek-io <tranzystorek-io@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] bkt: update to 0.6.0
Date: Sun, 02 Apr 2023 12:02:16 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-43184@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1248 bytes --]
There is a new pull request by tranzystorek-io against master on the void-packages repository
https://github.com/tranzystorek-io/void-packages bkt
https://github.com/void-linux/void-packages/pull/43184
bkt: update to 0.6.0
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **briefly**
<!--
#### New package
- This new package conforms to the [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-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/43184.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-bkt-43184.patch --]
[-- Type: text/x-diff, Size: 1224 bytes --]
From 5be5eec37b621ae369329686d8a011b43ecc4fa5 Mon Sep 17 00:00:00 2001
From: Marcin Puc <tranzystorek.io@protonmail.com>
Date: Sun, 2 Apr 2023 12:01:41 +0200
Subject: [PATCH] bkt: update to 0.6.0
---
srcpkgs/bkt/template | 8 +++-----
1 file changed, 3 insertions(+), 5 deletions(-)
diff --git a/srcpkgs/bkt/template b/srcpkgs/bkt/template
index 66ec4d376b09..13d8230f586c 100644
--- a/srcpkgs/bkt/template
+++ b/srcpkgs/bkt/template
@@ -1,17 +1,15 @@
# Template file for 'bkt'
pkgname=bkt
-version=0.5.4
+version=0.6.0
revision=1
build_style=cargo
-# disable flaky test: https://github.com/dimo414/bkt/issues/14
-make_check_args=" -- --skip cli::discard_failures_in_background"
short_desc="Subprocess caching utility"
maintainer="Marcin Puc <tranzystorek.io@protonmail.com>"
license="MIT"
homepage="https://www.bkt.rs/"
changelog="https://github.com/dimo414/bkt/releases"
-distfiles="https://github.com/dimo414/bkt/archive/${version}.tar.gz"
-checksum=172c413709dc81ced9dfa2750aaa398864e904d1ed213bd19e51d45d1ff0a8ff
+distfiles="https://github.com/dimo414/bkt/archive/refs/tags/${version}.tar.gz"
+checksum=59c8fe8b29101a47d928896468dce2f8fb3cee7598201d46011804a7bee7f6e2
post_install() {
vlicense LICENSE
next reply other threads:[~2023-04-02 10:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-02 10:02 tranzystorek-io [this message]
2023-04-02 19:40 ` [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-43184@inbox.vuxu.org \
--to=tranzystorek-io@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).