Github messages for voidlinux
 help / color / mirror / Atom feed
From: shtayerc <shtayerc@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] aerc: update to 0.15.2
Date: Sun, 14 May 2023 03:31:05 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-43866@inbox.vuxu.org> (raw)

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

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

https://github.com/shtayerc/void-packages aerc-0152
https://github.com/void-linux/void-packages/pull/43866

aerc: update to 0.15.2
<!-- 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/43866.patch is attached

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

From fbff58994119670848fb97f0a0c64268dd27c3e5 Mon Sep 17 00:00:00 2001
From: shtayerc <david.murko@mailbox.org>
Date: Sun, 14 May 2023 03:29:36 +0200
Subject: [PATCH] aerc: update to 0.15.2

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

diff --git a/srcpkgs/aerc/template b/srcpkgs/aerc/template
index 8f3768317397..4ce7cbc48a78 100644
--- a/srcpkgs/aerc/template
+++ b/srcpkgs/aerc/template
@@ -1,6 +1,6 @@
 # Template file for 'aerc'
 pkgname=aerc
-version=0.15.1
+version=0.15.2
 revision=1
 build_style=go
 go_import_path="git.sr.ht/~rjarry/aerc"
@@ -14,7 +14,7 @@ license="MIT"
 homepage="https://aerc-mail.org"
 changelog="https://git.sr.ht/~rjarry/aerc/blob/master/CHANGELOG.md"
 distfiles="https://git.sr.ht/~rjarry/aerc/archive/${version}.tar.gz"
-checksum=55cd54e45634d684590658ffc14c047cdf7366bbdf163d0445e2f093474ddef5
+checksum=722da196e8807c497f5472704b8a1737d7780ad0faa7166ae83348bc67b144f7
 ignore_elf_dirs="/usr/share/aerc/filters"
 
 post_install() {

             reply	other threads:[~2023-05-14  1:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-14  1:31 shtayerc [this message]
2023-05-17  4:56 ` [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-43866@inbox.vuxu.org \
    --to=shtayerc@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).