From: adriangoransson <adriangoransson@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] autotiling: update to 1.6
Date: Fri, 26 Nov 2021 16:52:28 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34260@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1229 bytes --]
There is a new pull request by adriangoransson against master on the void-packages repository
https://github.com/adriangoransson/void-packages master
https://github.com/void-linux/void-packages/pull/34260
autotiling: update to 1.6
<!-- 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 [skip CI](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/34260.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-master-34260.patch --]
[-- Type: text/x-diff, Size: 1147 bytes --]
From f058dd5cf1949d034954667ea4ec46e7536cd642 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Adrian=20G=C3=B6ransson?= <adriangoransson@gmail.com>
Date: Fri, 26 Nov 2021 16:48:25 +0100
Subject: [PATCH] autotiling: update to 1.6
---
srcpkgs/autotiling/template | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/srcpkgs/autotiling/template b/srcpkgs/autotiling/template
index 437d2a955294..8488a77f5315 100644
--- a/srcpkgs/autotiling/template
+++ b/srcpkgs/autotiling/template
@@ -1,7 +1,7 @@
# Template file for 'autotiling'
pkgname=autotiling
-version=1.5
-revision=2
+version=1.6
+revision=1
build_style=python3-module
hostmakedepends="python3-wheel"
depends="python3-i3ipc"
@@ -10,6 +10,6 @@ maintainer="Adrian Göransson <adriangoransson@gmail.com>"
license="GPL-3.0-or-later"
homepage="https://github.com/nwg-piotr/autotiling"
distfiles="https://github.com/nwg-piotr/${pkgname}/archive/v${version}.tar.gz"
-checksum=aa7ec1e3efbd409c06002c9229f2c198686bef1f907bc9d811b97a02de6ed0de
+checksum=a92b67e081df4923ef83d1b22cd9c046f878dfd5f17ff987c08da3db4ec50349
# There is no test suite for this package
make_check=no
next reply other threads:[~2021-11-26 15:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-26 15:52 adriangoransson [this message]
2021-11-27 4:04 ` [PR PATCH] [Merged]: " ericonr
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-34260@inbox.vuxu.org \
--to=adriangoransson@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).