From: chax <chax@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] budgie-desktop: update to 10.7.2
Date: Sat, 10 Jun 2023 23:47:52 +0200 [thread overview]
Message-ID: <20230610214752.b04bFAXINyQ_TrGT-8R9rBSIztl9MsCySa9qmpNFH7Y@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-43663@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 577 bytes --]
There is an updated pull request by chax against master on the void-packages repository
https://github.com/chax/void-packages budgie-bump
https://github.com/void-linux/void-packages/pull/43663
budgie-desktop: update to 10.7.2
This version bump fixes issue #43400 since the bug was obviously fixed upstream.
#### Testing the changes
- I tested the changes in this PR: **briefly**
#### Local build testing
- I built this PR locally for my native architecture, (x86_64-LIBC)
A patch file from https://github.com/void-linux/void-packages/pull/43663.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-budgie-bump-43663.patch --]
[-- Type: text/x-diff, Size: 1614 bytes --]
From d47c698213135c5c0250c19cd62f897d5c7876b8 Mon Sep 17 00:00:00 2001
From: chax <mcakaric@gmail.com>
Date: Sat, 29 Apr 2023 00:00:14 +0200
Subject: [PATCH] budgie-desktop: update to 10.7.2
---
srcpkgs/budgie-desktop/template | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/srcpkgs/budgie-desktop/template b/srcpkgs/budgie-desktop/template
index bfde56e60dc7..b35b53ffd8ca 100644
--- a/srcpkgs/budgie-desktop/template
+++ b/srcpkgs/budgie-desktop/template
@@ -1,6 +1,6 @@
# Template file for 'budgie-desktop'
pkgname=budgie-desktop
-version=10.7.1
+version=10.7.2
revision=1
build_style=meson
build_helper=gir
@@ -13,13 +13,13 @@ makedepends="alsa-lib-devel libcanberra-devel libgee-devel libnotify-devel
gnome-bluetooth1-devel gnome-menus-devel gnome-settings-daemon-devel vala
libupower-glib3 libuuid-devel"
depends="gnome-session gnome-settings-daemon budgie-control-center elogind
- gnome-themes-extra budgie-screensaver budgie-desktop-view"
+ gnome-themes-extra budgie-screensaver budgie-desktop-view zenity"
short_desc="Modern desktop environment from the Solus Project"
maintainer="Orphaned <orphan@voidlinux.org>"
license="GPL-2.0-only, LGPL-2.1-only"
homepage="https://github.com/BuddiesOfBudgie/budgie-desktop"
distfiles="https://github.com/BuddiesOfBudgie/budgie-desktop/releases/download/v${version}/budgie-desktop-v${version}.tar.xz"
-checksum=f8b277fb674f4c9e9d1dac9e45a7f93a1364d2f25cb1b3b513ec8154cfd7d6bd
+checksum=cce9ebe21b4bba4886bb2a227d739b7340c35085f08c132d3d8ae6b6621ba7b4
budgie-desktop-devel_package() {
short_desc+=" - development files"
next prev parent reply other threads:[~2023-06-10 21:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-28 22:07 [PR PATCH] " chax
2023-05-06 9:16 ` JoshStrobl
2023-06-10 19:53 ` chax
2023-06-10 21:46 ` [PR PATCH] [Updated] " chax
2023-06-10 21:47 ` chax [this message]
2023-06-11 0:43 ` JoshStrobl
2023-06-11 9:29 ` [PR PATCH] [Updated] " chax
2023-06-11 9:31 ` chax
2023-06-11 10:19 ` paper42
2023-06-11 13:25 ` [PR PATCH] [Updated] " chax
2023-06-11 17:12 ` [PR PATCH] [Merged]: " paper42
2023-10-17 20:16 ` aandmsantos0910
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=20230610214752.b04bFAXINyQ_TrGT-8R9rBSIztl9MsCySa9qmpNFH7Y@z \
--to=chax@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).