Github messages for voidlinux
 help / color / mirror / Atom feed
From: balejk <balejk@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] aerc: update to 0.11.0.
Date: Fri, 15 Jul 2022 12:55:42 +0200	[thread overview]
Message-ID: <20220715105542.VJgnSFFIMz72Rlz9m0LWMwe0BCk2HPRZLSHF9BBC2jo@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38084@inbox.vuxu.org>

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

There is an updated pull request by balejk against master on the void-packages repository

https://github.com/balejk/void-packages aerc
https://github.com/void-linux/void-packages/pull/38084

aerc: update to 0.11.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 [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-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, (x86_64-musl)


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

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-aerc-38084.patch --]
[-- Type: text/x-diff, Size: 1060 bytes --]

From 4527f54d63fcb46c99ed6b806320116551ab3986 Mon Sep 17 00:00:00 2001
From: Karel Balej <balejk@matfyz.cz>
Date: Fri, 15 Jul 2022 12:43:53 +0200
Subject: [PATCH] aerc: update to 0.11.0.

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

diff --git a/srcpkgs/aerc/template b/srcpkgs/aerc/template
index 9741c99ba38a..b3b55adc4c92 100644
--- a/srcpkgs/aerc/template
+++ b/srcpkgs/aerc/template
@@ -1,6 +1,6 @@
 # Template file for 'aerc'
 pkgname=aerc
-version=0.10.0
+version=0.11.0
 revision=1
 build_style=go
 go_import_path="git.sr.ht/~rjarry/aerc"
@@ -13,9 +13,9 @@ maintainer="shtayerc <david.murko@mailbox.org>"
 license="MIT"
 homepage="https://aerc-mail.org"
 distfiles="https://git.sr.ht/~rjarry/aerc/archive/${version}.tar.gz"
-checksum=14d6c622a012069deb1a31b51ecdd187fd11041c8e46f396ac22830b00e4c114
+checksum=3d8f3a2800946fce070e3eb02122e77c427a61c670a06337539b3e7f09e57861
 
 post_install() {
- 	make PREFIX=/usr DESTDIR=${DESTDIR} install
+	make PREFIX=/usr DESTDIR=${DESTDIR} install
 	vlicense LICENSE
 }

  reply	other threads:[~2022-07-15 10:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-15 10:44 [PR PATCH] " balejk
2022-07-15 10:55 ` balejk [this message]
2022-07-15 15:46 ` [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=20220715105542.VJgnSFFIMz72Rlz9m0LWMwe0BCk2HPRZLSHF9BBC2jo@z \
    --to=balejk@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).