From: rehanzo <rehanzo@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] Waybar: update to 0.9.19
Date: Wed, 05 Jul 2023 21:11:42 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-44866@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1239 bytes --]
There is a new pull request by rehanzo against master on the void-packages repository
https://github.com/rehanzo/void-packages waybar
https://github.com/void-linux/void-packages/pull/44866
Waybar: update to 0.9.19
<!-- 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/44866.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-waybar-44866.patch --]
[-- Type: text/x-diff, Size: 1150 bytes --]
From eb9cd02eb61a4c2395c68fb1ba77bef5952afbe9 Mon Sep 17 00:00:00 2001
From: Rehan <rehanalirana@tuta.io>
Date: Wed, 5 Jul 2023 15:08:10 -0400
Subject: [PATCH] Waybar: update to 0.9.19
---
srcpkgs/Waybar/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/Waybar/template b/srcpkgs/Waybar/template
index 3da1c780f280..21205b72320a 100644
--- a/srcpkgs/Waybar/template
+++ b/srcpkgs/Waybar/template
@@ -1,6 +1,6 @@
# Template file for 'Waybar'
pkgname=Waybar
-version=0.9.18
+version=0.9.19
revision=1
build_style=meson
configure_args="-Dgtk-layer-shell=enabled -Dlibudev=enabled -Dman-pages=enabled
@@ -28,7 +28,7 @@ license="MIT"
homepage="https://github.com/Alexays/Waybar"
changelog="https://github.com/Alexays/Waybar/releases"
distfiles="https://github.com/Alexays/Waybar/archive/refs/tags/${version}.tar.gz"
-checksum=44927f71834196276cfcbf5607339f59b511edf0ecc496c09d4f5f115108df3e
+checksum=09695c9d6ae4cf33d8e8a2c3e4ba216e5d293e2d72d4115c64c5d2612976816d
build_options="libnl pulseaudio dbusmenugtk mpd sndio pipewire"
build_options_default="libnl pulseaudio dbusmenugtk mpd sndio pipewire"
next reply other threads:[~2023-07-05 19:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-05 19:11 rehanzo [this message]
2023-07-08 18:18 ` [PR PATCH] [Merged]: " Duncaen
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-44866@inbox.vuxu.org \
--to=rehanzo@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).