From: mhmdanas <mhmdanas@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] tdb: update to 1.4.8.
Date: Fri, 26 May 2023 22:27:00 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-44106@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1218 bytes --]
There is a new pull request by mhmdanas against master on the void-packages repository
https://github.com/mhmdanas/void-packages tdb-1.4.8
https://github.com/void-linux/void-packages/pull/44106
tdb: update to 1.4.8.
<!-- 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/44106.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-tdb-1.4.8-44106.patch --]
[-- Type: text/x-diff, Size: 1168 bytes --]
From d243a1d7f963da9112b56cbb53a4ecb9e0de9521 Mon Sep 17 00:00:00 2001
From: triallax <triallax@tutanota.com>
Date: Fri, 26 May 2023 21:25:06 +0100
Subject: [PATCH] tdb: update to 1.4.8.
---
srcpkgs/tdb/template | 8 ++++++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/tdb/template b/srcpkgs/tdb/template
index 23bea72ec8e0..5df924f26a67 100644
--- a/srcpkgs/tdb/template
+++ b/srcpkgs/tdb/template
@@ -1,6 +1,6 @@
# Template file for 'tdb'
pkgname=tdb
-version=1.4.7
+version=1.4.8
revision=1
build_style=waf3
build_helper="qemu"
@@ -15,11 +15,15 @@ maintainer="Orphaned <orphan@voidlinux.org>"
license="GPL-3.0-or-later"
homepage="https://tdb.samba.org/"
distfiles="https://download.samba.org/pub/tdb/tdb-${version}.tar.gz"
-checksum=a4fb168def533f31ff2c07f7d9844bb3131e6799f094ebe77d0380adc987c20e
+checksum=8434c9c857d13ce3fa8466f75601f25c3693676b36919f159e0ad6121baf5ce8
export PYTHON_CONFIG="${XBPS_CROSS_BASE}/usr/bin/python3-config"
export PYTHONHASHSEED=1
+do_check() {
+ ${configure_script} test ${makejobs}
+}
+
tdb-devel_package() {
depends="libtdb-${version}_${revision}"
short_desc+=" - development files"
next reply other threads:[~2023-05-26 20:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-26 20:27 mhmdanas [this message]
2023-06-09 2:10 ` [PR PATCH] [Merged]: " classabbyamp
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-44106@inbox.vuxu.org \
--to=mhmdanas@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).