Github messages for voidlinux
 help / color / mirror / Atom feed
From: CabrioletDiskette <CabrioletDiskette@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] qt6ct: update to 0.8
Date: Fri, 31 Mar 2023 08:39:12 +0200	[thread overview]
Message-ID: <20230331063912.6v6Vi-CPgpWRJL8MntrvvFrnOd3BMaOPZseGZVyT9RU@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-43133@inbox.vuxu.org>

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

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

https://github.com/CabrioletDiskette/void-packages qt6ct
https://github.com/void-linux/void-packages/pull/43133

qt6ct: update to 0.8
#### 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)

I noticed that there is some discussion about the need of qt6ct.sh. I am merely updating qt6ct in this commit but if a conclusion is arrived at in #40619 I can modify this PR. 

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

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

From a21d79241b3ab11e98b601176fe201837fed77b8 Mon Sep 17 00:00:00 2001
From: CabrioletDiskette <adampschorr13@aol.com>
Date: Fri, 31 Mar 2023 00:28:00 -0600
Subject: [PATCH] qt6ct: update to 0.8.

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

diff --git a/srcpkgs/qt6ct/template b/srcpkgs/qt6ct/template
index 64f166fb4767..21edb46beadb 100644
--- a/srcpkgs/qt6ct/template
+++ b/srcpkgs/qt6ct/template
@@ -1,7 +1,7 @@
 # Template file for 'qt6ct'
 pkgname=qt6ct
-version=0.7
-revision=2
+version=0.8
+revision=1
 build_style=cmake
 hostmakedepends="qt6-tools qt6-base"
 makedepends="qt6-base-devel"
@@ -11,7 +11,7 @@ maintainer="Adam Pschorr <adampschorr13@aol.com>"
 license="BSD-2-Clause"
 homepage="https://github.com/trialuser02/qt6ct"
 distfiles="https://github.com/trialuser02/qt6ct/archive/refs/tags/${version}.tar.gz"
-checksum=6bc4c35e7c567908d8e123b8ccc11a55d27b5353ad035905cfa44b98c29ca862
+checksum=ca3706770cbdbce769ee4393de9f7469be043810fe40283690612f5f6552018a
 
 post_install() {
 	vlicense COPYING

  reply	other threads:[~2023-03-31  6:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-31  6:36 [PR PATCH] " CabrioletDiskette
2023-03-31  6:39 ` CabrioletDiskette [this message]
2023-06-24  6:01 ` [PR PATCH] [Closed]: " CabrioletDiskette
2023-06-24  6:01 ` [PR PATCH] [Updated] " CabrioletDiskette
2023-06-24  6:12 ` CabrioletDiskette
2023-06-24  6:22 ` [PR PATCH] [Updated] " CabrioletDiskette
2023-06-24  6:25 ` CabrioletDiskette
2023-06-24 11:42 ` [PR PATCH] [Closed]: " 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=20230331063912.6v6Vi-CPgpWRJL8MntrvvFrnOd3BMaOPZseGZVyT9RU@z \
    --to=cabrioletdiskette@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).