Github messages for voidlinux
 help / color / mirror / Atom feed
From: natrys <natrys@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] xapian-core: update to 1.4.21.
Date: Wed, 19 Oct 2022 15:25:34 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40039@inbox.vuxu.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1251 bytes --]

There is a new pull request by natrys against master on the void-packages repository

https://github.com/natrys/void-packages xapian-core-1.4.21
https://github.com/void-linux/void-packages/pull/40039

xapian-core: update to 1.4.21.
<!-- Uncomment relevant sections and delete options which are not applicable -->

#### Testing the changes
- I tested the changes in this PR: **YES**

<!--
#### 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/40039.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-xapian-core-1.4.21-40039.patch --]
[-- Type: text/x-diff, Size: 1126 bytes --]

From 158dd0abb84186532374b5ee73b22628ac4c8840 Mon Sep 17 00:00:00 2001
From: Imran Khan <imrankhan@teknik.io>
Date: Wed, 19 Oct 2022 19:23:03 +0600
Subject: [PATCH] xapian-core: update to 1.4.21.

---
 srcpkgs/xapian-core/template | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/srcpkgs/xapian-core/template b/srcpkgs/xapian-core/template
index 369cccb082f0..8f8ece9bfc59 100644
--- a/srcpkgs/xapian-core/template
+++ b/srcpkgs/xapian-core/template
@@ -1,7 +1,7 @@
 # Template file for 'xapian-core'
 pkgname=xapian-core
-version=1.4.18
-revision=2
+version=1.4.21
+revision=1
 build_style=gnu-configure
 configure_args="--disable-static"
 makedepends="zlib-devel libuuid-devel"
@@ -10,7 +10,7 @@ maintainer="Orphaned <orphan@voidlinux.org>"
 license="GPL-2.0-or-later"
 homepage="https://www.xapian.org/"
 distfiles="https://oligarchy.co.uk/xapian/${version}/${pkgname}-${version}.tar.xz"
-checksum=196ddbb4ad10450100f0991a599e4ed944cbad92e4a6fe813be6dce160244b77
+checksum=80f86034d2fb55900795481dfae681bfaa10efbe818abad3622cdc0c55e06f88
 
 # xapian-config needs the .la
 keep_libtool_archives=yes

             reply	other threads:[~2022-10-19 13:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-19 13:25 natrys [this message]
2022-10-20  5:24 ` [PR REVIEW] " classabbyamp
2022-10-20  7:53 ` [PR PATCH] [Updated] " natrys
2022-10-23 18:23 ` [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-40039@inbox.vuxu.org \
    --to=natrys@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).