[PR PATCH] dunst: update to 1.9.1, adopt

[PR PATCH] dunst: update to 1.9.1, adopt

[mdkcore0]

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

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

https://github.com/mdkcore0/void-packages update-dunst
https://github.com/void-linux/void-packages/pull/43309

dunst: update to 1.9.1, adopt
#### Testing the changes
- I tested the changes in this PR: **YES**

#### Local build testing
- I built this PR locally for my native architecture, x86_64-libc
- I built this PR locally for these architectures (if supported. mark crossbuilds):
  - armv7l (crossbuild)
  - i686-libc

A patch file from https://github.com/void-linux/void-packages/pull/43309.patch is attached

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

From ac5cf41924300e4c0373b0b7e1174cf16bbd1355 Mon Sep 17 00:00:00 2001
From: Rodrigo Oliveira <mdkcore@qtrnn.io>
Date: Thu, 6 Apr 2023 17:54:36 -0300
Subject: [PATCH] dunst: update to 1.9.1, adopt

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

diff --git a/srcpkgs/dunst/template b/srcpkgs/dunst/template
index f1f57f153040..ff61b25caadb 100644
--- a/srcpkgs/dunst/template
+++ b/srcpkgs/dunst/template
@@ -1,6 +1,6 @@
 # Template file for 'dunst'
 pkgname=dunst
-version=1.9.0
+version=1.9.1
 revision=1
 build_style=gnu-makefile
 make_check_target=test
@@ -13,12 +13,12 @@ makedepends="gdk-pixbuf-devel libXScrnSaver-devel libXinerama-devel libXrandr-de
 checkdepends="dbus"
 conf_files="/etc/dunst/dunstrc"
 short_desc="Lightweight and customizable notification daemon"
-maintainer="Orphaned <orphan@voidlinux.org>"
+maintainer="Rodrigo Oliveira <mdkcore@qtrnn.io>"
 license="BSD-3-Clause"
 homepage="https://dunst-project.org"
 changelog="https://raw.githubusercontent.com/dunst-project/dunst/master/CHANGELOG.md"
 distfiles="https://github.com/dunst-project/dunst/archive/v${version}.tar.gz"
-checksum=b7b8d7d6560bb241b1e4d37eba770cdf19b9d5dbfc1d4d47572ad676f3f7c98a
+checksum=571d82d5feef995e69a35e708a400a0cfa12a0f81854c5a3357e17844bf6249a
 
 build_options="wayland"
 build_options_default="wayland"

Re: dunst: update to 1.9.1, adopt

[biopsin]

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

New comment by biopsin on void-packages repository

https://github.com/void-linux/void-packages/pull/43309#issuecomment-1500029054

Comment:
duplicate #42756

Re: dunst: update to 1.9.1, adopt

[mdkcore0]

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

New comment by mdkcore0 on void-packages repository

https://github.com/void-linux/void-packages/pull/43309#issuecomment-1500346498

Comment:
> duplicate #42756

oh, OK

Re: [PR PATCH] [Closed]: dunst: update to 1.9.1, adopt

[mdkcore0]

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

There's a closed pull request on the void-packages repository

dunst: update to 1.9.1, adopt
https://github.com/void-linux/void-packages/pull/43309

Description:
#### Testing the changes
- I tested the changes in this PR: **YES**

#### Local build testing
- I built this PR locally for my native architecture, x86_64-libc
- I built this PR locally for these architectures (if supported. mark crossbuilds):
  - armv7l (crossbuild)
  - i686-libc

Re: dunst: update to 1.9.1, adopt

[biopsin]

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

New comment by biopsin on void-packages repository

https://github.com/void-linux/void-packages/pull/43309#issuecomment-1517892195

Comment:
@mdkcore0 forgot to ask do you want to maintain it, I can put you in my pull?

Re: dunst: update to 1.9.1, adopt

[mdkcore0]

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

New comment by mdkcore0 on void-packages repository

https://github.com/void-linux/void-packages/pull/43309#issuecomment-1519141664

Comment:
hi @biopsin, it would be great, thanks!

On April 21, 2023 2:07:24 PM UTC, biopsin ***@***.***> wrote:
>@mdkcore0 forgot to ask do you want to maintain it, I can put you in my pull?
>