Github messages for voidlinux
 help / color / mirror / Atom feed
From: clyhtsuriva <clyhtsuriva@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] eqonomize: update to 1.5.3
Date: Wed, 05 Jan 2022 17:28:05 +0100	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34868@inbox.vuxu.org> (raw)

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

There is a new pull request by clyhtsuriva against master on the void-packages repository

https://github.com/clyhtsuriva/void-packages eqonomize-update
https://github.com/void-linux/void-packages/pull/34868

eqonomize: update to 1.5.3
<!-- 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 [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements): **YES**|**NO**
-->

<!-- Note: If the build is likely to take more than 2 hours, please [skip CI](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, x86_64
- I built this PR locally for these architectures :
  - aarch64-musl
  - armv7l
  - armv6l-musl

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

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

From ca1cd656a5308e492ed7b412611d85839d473774 Mon Sep 17 00:00:00 2001
From: clyhtsuriva <aimeric@adjutor.xyz>
Date: Wed, 5 Jan 2022 17:26:33 +0100
Subject: [PATCH] eqonomize: update to 1.5.3

---
 srcpkgs/eqonomize/template | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/srcpkgs/eqonomize/template b/srcpkgs/eqonomize/template
index 9197b9c36b2c..f9c83fa5ddad 100644
--- a/srcpkgs/eqonomize/template
+++ b/srcpkgs/eqonomize/template
@@ -1,6 +1,6 @@
 # Template file for 'eqonomize'
 pkgname=eqonomize
-version=1.5.2
+version=1.5.3
 revision=1
 build_style=qmake
 hostmakedepends="qt5-qmake qt5-host-tools"
@@ -12,4 +12,4 @@ license="GPL-3.0-or-later"
 homepage="http://eqonomize.github.io"
 changelog="https://raw.githubusercontent.com/Eqonomize/Eqonomize/master/ChangeLog"
 distfiles="https://github.com/Eqonomize/Eqonomize/releases/download/v${version}/${pkgname}-${version}.tar.gz"
-checksum=6184b42d1bd5cb54dcd450e2db184ba8b6096ecd839eb432ade08190e32cc6ee
+checksum=ec4b28c9e43672634456a7d4cf8828ddd57b3343f601ba4526bfc94ee130f102

             reply	other threads:[~2022-01-05 16:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-05 16:28 clyhtsuriva [this message]
2022-01-05 19:21 ` [PR PATCH] [Merged]: " ericonr

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-34868@inbox.vuxu.org \
    --to=clyhtsuriva@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).