Github messages for voidlinux
 help / color / mirror / Atom feed
From: RAR27 <RAR27@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] mako: update to 1.8.0
Date: Thu, 01 Jun 2023 19:45:51 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-44216@inbox.vuxu.org> (raw)

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

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

https://github.com/RAR27/void-packages mako
https://github.com/void-linux/void-packages/pull/44216

mako: update to 1.8.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 [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/44216.patch is attached

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

From 1a743fce6471ed3de33ab0449c9db7d52035a1bf Mon Sep 17 00:00:00 2001
From: Rehan <rehanalirana@tuta.io>
Date: Thu, 1 Jun 2023 13:44:02 -0400
Subject: [PATCH] mako: update to 1.8.0

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

diff --git a/srcpkgs/mako/template b/srcpkgs/mako/template
index aad55bad6e21..2780bb58a057 100644
--- a/srcpkgs/mako/template
+++ b/srcpkgs/mako/template
@@ -1,6 +1,6 @@
 # Template file for 'mako'
 pkgname=mako
-version=1.7.1
+version=1.8.0
 revision=1
 build_style=meson
 configure_args="-Dicons=enabled -Dman-pages=enabled -Dzsh-completions=true
@@ -13,7 +13,7 @@ maintainer="Emerson Ferreira <me@skrps.me>"
 license="MIT"
 homepage="https://wayland.emersion.fr/mako/"
 distfiles="https://github.com/emersion/mako/archive/v${version}.tar.gz"
-checksum=4312ff6bc61708115b43b967a42813374de7a2022f10c84e20127606416c3c12
+checksum=f149f3dd2a083504a50307554c0a729ac56888c8ebb0704a78b7261be26166de
 
 post_install() {
 	vlicense LICENSE

             reply	other threads:[~2023-06-01 17:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-01 17:45 RAR27 [this message]
2023-06-01 20:24 ` mhmdanas
2023-06-09  1:21 ` [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-44216@inbox.vuxu.org \
    --to=rar27@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).