Github messages for voidlinux
 help / color / mirror / Atom feed
From: hervyqa <hervyqa@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] signond: don't use -fno-rtti
Date: Mon, 18 Apr 2022 11:39:50 +0200	[thread overview]
Message-ID: <20220418093950.mL31VEeHRaVzymCkXQRtjnzRK6arHFg4azW8UMagT04@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36748@inbox.vuxu.org>

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

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

https://github.com/hervyqa/void-packages signond
https://github.com/void-linux/void-packages/pull/36748

signond: don't use -fno-rtti
Close: #34935
Successfully add a new account in Online Account (kde plasma).

Reference:
- https://build.opensuse.org/package/view_file/openSUSE:Factory/signon/0001-Don-t-use-fno-rtti.patch?expand=1

bug:
- https://bugs.kde.org/show_bug.cgi?id=427063
- https://bugzilla.opensuse.org/show_bug.cgi?id=1172904
 
#### 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)

Before:
![img1](https://user-images.githubusercontent.com/45872139/148634365-473e71b4-a971-412c-a783-6882ba44fc34.png)

After:
![Screenshot_20220418_145223](https://user-images.githubusercontent.com/45872139/163780197-aa4618cf-7111-4ec9-af7d-40d36c1b0b3e.png)



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

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

From a97cb3fffca4312cb6521bf20a6c9f757b20b5a7 Mon Sep 17 00:00:00 2001
From: Hervy Qurrotul Ainur Rozi <hervyqa@pm.me>
Date: Mon, 18 Apr 2022 15:22:04 +0700
Subject: [PATCH] signond: update to 8.61

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

diff --git a/srcpkgs/signond/template b/srcpkgs/signond/template
index 9a2f0cff8c26..6a3bb44122ab 100644
--- a/srcpkgs/signond/template
+++ b/srcpkgs/signond/template
@@ -1,7 +1,7 @@
 # Template file for 'signond'
 pkgname=signond
-version=8.60
-revision=3
+version=8.61
+revision=1
 wrksrc="signond-VERSION_${version}"
 build_style=qmake
 configure_args="LIBDIR=/usr/lib"
@@ -13,7 +13,7 @@ maintainer="John Rowley <enterthevoid@codesector.co>"
 license="LGPL-2.1-only"
 homepage="https://gitlab.com/accounts-sso/signond"
 distfiles="${homepage}/-/archive/VERSION_${version}/signond-VERSION_${version}.tar.gz"
-checksum=0da2a080e4b01f44855d1a519f828007a5c756ee93827db9098a1b4b880f28fe
+checksum=3dd57c25e1bf1583b2cb857f96831e38e73d40264ff66ca43e63bb7233f76828
 
 pre_configure() {
 	if [ "$CROSS_BUILD" ]; then

  parent reply	other threads:[~2022-04-18  9:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-18  8:29 [PR PATCH] " hervyqa
2022-04-18  9:22 ` hervyqa
2022-04-18  9:39 ` hervyqa [this message]
2022-04-18 18:16 ` signond: update to 8.61 hervyqa
2022-04-18 21:00 ` [PR PATCH] [Merged]: " Johnnynator

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=20220418093950.mL31VEeHRaVzymCkXQRtjnzRK6arHFg4azW8UMagT04@z \
    --to=hervyqa@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).