Github messages for voidlinux
 help / color / mirror / Atom feed
From: 0x5c <0x5c@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] picom: update to 10.
Date: Tue, 15 Nov 2022 00:50:05 +0100	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40535@inbox.vuxu.org> (raw)

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

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

https://github.com/0x5c/void-packages update/picom
https://github.com/void-linux/void-packages/pull/40535

picom: update to 10.
<!-- 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/40535.patch is attached

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

From 3e189b0264822295a251697bd2d99490329f24af Mon Sep 17 00:00:00 2001
From: 0x5c <dev@0x5c.io>
Date: Mon, 14 Nov 2022 18:48:54 -0500
Subject: [PATCH] picom: update to 10.

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

diff --git a/srcpkgs/picom/template b/srcpkgs/picom/template
index 35f40f3b52e2..8662a779da30 100644
--- a/srcpkgs/picom/template
+++ b/srcpkgs/picom/template
@@ -1,7 +1,7 @@
 # Template file for 'picom'
 pkgname=picom
-version=9.1
-revision=2
+version=10
+revision=1
 build_style=meson
 configure_args="-Dwith_docs=true"
 hostmakedepends="pkg-config asciidoc"
@@ -14,7 +14,7 @@ maintainer="0x5c <dev@0x5c.io>"
 license="MIT, MPL-2.0"
 homepage="https://github.com/yshui/picom/"
 distfiles="https://github.com/yshui/picom/archive/v${version}.tar.gz"
-checksum=8700ac71bd496c91262c8576e29cb3aecf2b4ef48c04394a929509d3cb37b87d
+checksum=e840304c329f0797205963302894c55e11d77cf51a22c0a7208344ce6fd0a238
 
 post_install() {
 	vlicense LICENSES/MIT

             reply	other threads:[~2022-11-14 23:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-14 23:50 0x5c [this message]
2022-11-16 21:11 ` [PR PATCH] [Merged]: " leahneukirchen

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-40535@inbox.vuxu.org \
    --to=0x5c@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).