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 11.1.
Date: Mon, 12 Feb 2024 07:08:27 +0100	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-48667@inbox.vuxu.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1233 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/48667

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

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

From e6095a8955b75a0437640d5984637c9fe39dc0e9 Mon Sep 17 00:00:00 2001
From: 0x5c <dev@0x5c.io>
Date: Mon, 12 Feb 2024 01:07:29 -0500
Subject: [PATCH] picom: update to 11.1.

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

diff --git a/srcpkgs/picom/template b/srcpkgs/picom/template
index 5e30a25af9f07..040845f6f7679 100644
--- a/srcpkgs/picom/template
+++ b/srcpkgs/picom/template
@@ -1,11 +1,11 @@
 # Template file for 'picom'
 pkgname=picom
-version=10.2
+version=11.1
 revision=1
 build_style=meson
 configure_args="-Dwith_docs=true"
 hostmakedepends="pkg-config asciidoc"
-makedepends="MesaLib-devel dbus-devel libconfig-devel libev-devel pcre-devel
+makedepends="MesaLib-devel dbus-devel libconfig-devel libev-devel pcre2-devel
  pixman-devel xcb-util-image-devel xcb-util-renderutil-devel
  libxdg-basedir-devel uthash"
 depends="desktop-file-utils"
@@ -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=9741577df0136d8a2be48005ca2b93edc15913528e19bceb798535ca4683341c
+checksum=96f2a33a93064a74b557942d0300a2ac77ac853f50efbbf6466849fcc7542ec8
 
 post_install() {
 	vlicense LICENSES/MIT

             reply	other threads:[~2024-02-12  6:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-12  6:08 0x5c [this message]
2024-02-12 17:13 ` [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-48667@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).