Github messages for voidlinux
 help / color / mirror / Atom feed
From: classabbyamp <classabbyamp@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] budgie-control-center: update to 1.2.0.
Date: Wed, 29 Mar 2023 22:53:17 +0200	[thread overview]
Message-ID: <20230329205317.14FC2BlJTETMlqW1yTLH0dkxAN9PWvAgG6XgqgFFak4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41945@inbox.vuxu.org>

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

There is an updated pull request by classabbyamp against master on the void-packages repository

https://github.com/BlindRepublic/void-packages budgie-control-center-1.2.0
https://github.com/void-linux/void-packages/pull/41945

budgie-control-center: update to 1.2.0.
<!-- Uncomment relevant sections and delete options which are not applicable -->

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

#### Local build testing
- I built this PR locally for my native architecture, (ARCH-LIBC)



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

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-budgie-control-center-1.2.0-41945.patch --]
[-- Type: text/x-diff, Size: 1347 bytes --]

From 42fe00a9d825a6559ff86a04dd77155a1cc69473 Mon Sep 17 00:00:00 2001
From: Elliot <BlindRepublic@mailo.com>
Date: Wed, 15 Feb 2023 16:32:48 -0500
Subject: [PATCH] budgie-control-center: update to 1.2.0.

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

diff --git a/srcpkgs/budgie-control-center/template b/srcpkgs/budgie-control-center/template
index 37736255e165..e505ca9e6df1 100644
--- a/srcpkgs/budgie-control-center/template
+++ b/srcpkgs/budgie-control-center/template
@@ -1,7 +1,7 @@
 # Template file for 'budgie-control-center'
 pkgname=budgie-control-center
-version=1.1.1
-revision=3
+version=1.2.0
+revision=1
 build_style=meson
 hostmakedepends="glib-devel gsettings-desktop-schemas-devel gettext pkg-config
  polkit python3 libxml2"
@@ -20,7 +20,7 @@ maintainer="Orphaned <orphan@voidlinux.org>"
 license="GPL-2.0-or-later"
 homepage="https://github.com/BuddiesOfBudgie/budgie-control-center"
 distfiles="https://github.com/BuddiesOfBudgie/budgie-control-center/releases/download/v${version}/budgie-control-center-${version}.tar.xz"
-checksum=0a0f27cee3e5a33f17e6b34ad698b4a54fe8ef7c1d215a0aa9a07431722ac963
+checksum=b72ee32b914795107e3c65b21128cac984e8920aa2e1b2ecc4f6c8fd67be9cc2
 
 budgie-control-center-devel_package() {
 	depends="${sourcepkg}>=${version}_${revision}"

  parent reply	other threads:[~2023-03-29 20:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-29 19:57 [PR PATCH] " TrueTechie
2023-02-09  1:19 ` [PR PATCH] [Closed]: " TrueTechie
2023-02-09  1:19 ` [PR PATCH] [Updated] " TrueTechie
2023-02-15 21:41 ` BlindRepublic
2023-03-29 20:53 ` classabbyamp [this message]
2023-03-29 21:06 ` [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=20230329205317.14FC2BlJTETMlqW1yTLH0dkxAN9PWvAgG6XgqgFFak4@z \
    --to=classabbyamp@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).