From: ramos <ramos@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] update version 1.8.10
Date: Wed, 21 Sep 2022 19:25:17 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39403@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1247 bytes --]
There is a new pull request by ramos against master on the void-packages repository
https://github.com/ramos/void-packages master
https://github.com/void-linux/void-packages/pull/39403
update version 1.8.10
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **YES**|**briefly**|**NO**
<!--
#### 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/39403.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-master-39403.patch --]
[-- Type: text/x-diff, Size: 1213 bytes --]
From 5da9d32166130a2fafda8898d5f43e031fff4787 Mon Sep 17 00:00:00 2001
From: Alberto Ramos <alberto.ramos@ific.uv.es>
Date: Wed, 21 Sep 2022 19:21:40 +0200
Subject: [PATCH] mu4e: bump version to 1.8.10
---
srcpkgs/mu4e/template | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/srcpkgs/mu4e/template b/srcpkgs/mu4e/template
index 3d804715d9db..67eb7ebb0751 100644
--- a/srcpkgs/mu4e/template
+++ b/srcpkgs/mu4e/template
@@ -1,6 +1,6 @@
# Template file for 'mu4e'
pkgname=mu4e
-version=1.6.10
+version=1.8.10
revision=1
wrksrc="mu-${version}"
build_style=gnu-configure
@@ -11,8 +11,8 @@ short_desc="Maildir-utils indexer/searcher and associated Emacs client"
maintainer="Benjamin Slade <slade@lambda-y.net>"
license="GPL-3.0-or-later"
homepage="https://www.djcbsoftware.nl/code/mu/"
-distfiles="https://github.com/djcb/mu/releases/download/${version}/mu-${version}.tar.xz"
-checksum=0bc224aab2bfe40b5209af14e0982e637789292b7979872658d4498b29e900b6
+distfiles="https://github.com/djcb/mu/releases/download/v${version}/mu-${version}.tar.xz"
+checksum=a60b330e8a360255134b1fa1d9f672363ebf318d5cbe4b4b0bee1e9f94ae15c9
replaces="mu<${version}"
provides="mu-${version}_${revision}"
next reply other threads:[~2022-09-21 17:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-21 17:25 ramos [this message]
2022-09-23 9:28 ` sgn
2022-12-23 1:57 ` github-actions
2023-01-06 2:00 ` [PR PATCH] [Closed]: " github-actions
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-39403@inbox.vuxu.org \
--to=ramos@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).