Github messages for voidlinux
 help / color / mirror / Atom feed
From: pascal-huber <pascal-huber@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] mu4e: update to 1.8.14
Date: Fri, 10 Feb 2023 13:52:06 +0100	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42184@inbox.vuxu.org> (raw)

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

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

https://github.com/pascal-huber/void-packages mu4e_1.8.14_1
https://github.com/void-linux/void-packages/pull/42184

mu4e: update to 1.8.14
#### Testing the changes
- I tested the changes in this PR: **briefly**

#### Local build testing
- I built this PR locally for my native architecture, x86_64-glibc
- I built this PR locally for these architectures:
  - x86_64-musl (crossbuild)
  - armv7l (crossbuild)



A patch file from https://github.com/void-linux/void-packages/pull/42184.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-mu4e_1.8.14_1-42184.patch --]
[-- Type: text/x-diff, Size: 1081 bytes --]

From 0d964a10ed16929a7e8a505a605bb992fc4eb386 Mon Sep 17 00:00:00 2001
From: Pascal Huber <pascal.huber@resolved.ch>
Date: Fri, 10 Feb 2023 13:35:44 +0100
Subject: [PATCH] mu4e: update to 1.8.14

---
 srcpkgs/mu4e/template | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/srcpkgs/mu4e/template b/srcpkgs/mu4e/template
index 8739f346ac18..1a6f8a7037c9 100644
--- a/srcpkgs/mu4e/template
+++ b/srcpkgs/mu4e/template
@@ -1,6 +1,6 @@
 # Template file for 'mu4e'
 pkgname=mu4e
-version=1.8.13
+version=1.8.14
 revision=1
 build_style=gnu-configure
 configure_args="--enable-mu4e $(vopt_if guile --enable-guile)"
@@ -11,7 +11,7 @@ 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/v${version}/mu-${version}.tar.xz"
-checksum=20d69c1a918c1e48e6dbf5375d87ef3ed358bb6b3b7d0a120e93a88b16d5a026
+checksum=1a9c5e15b5e8b67622f7e58dfadd453abf232c0b715bd5f89b955e704455219c
 replaces="mu<${version}"
 provides="mu-${version}_${revision}"
 

             reply	other threads:[~2023-02-10 12:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-10 12:52 pascal-huber [this message]
2023-02-11  5:17 ` [PR REVIEW] " classabbyamp
2023-02-11  8:39 ` pascal-huber
2023-02-11  8:40 ` pascal-huber
2023-02-11  8:52 ` classabbyamp
2023-02-11  9:11 ` [PR PATCH] [Updated] " pascal-huber
2023-02-11  9:15 ` pascal-huber
2023-02-11  9:21 ` [PR REVIEW] " pascal-huber
2023-02-11 15:42 ` [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-42184@inbox.vuxu.org \
    --to=pascal-huber@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).