From: UsernameRandomlyGenerated <UsernameRandomlyGenerated@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] dino: update to 0.2.2.
Date: Mon, 03 Jan 2022 10:22:56 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34827@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1233 bytes --]
There is a new pull request by UsernameRandomlyGenerated against master on the void-packages repository
https://github.com/UsernameRandomlyGenerated/void-packages dino022
https://github.com/void-linux/void-packages/pull/34827
dino: update to 0.2.2.
<!-- Uncomment relevant sections and delete options which are not applicable -->
Testing the changes
- I tested the changes in this PR: NO
<!--
#### 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, (ARCH-LIBC)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
- aarch64-musl
- armv7l
- armv6l-musl
-->
A patch file from https://github.com/void-linux/void-packages/pull/34827.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-dino022-34827.patch --]
[-- Type: text/x-diff, Size: 1091 bytes --]
From 20c9d35eb902651becd1266f2d2fe074b97faada Mon Sep 17 00:00:00 2001
From: UsernameRandomlyGenerated <overtwist_wt@aleeas.com>
Date: Mon, 3 Jan 2022 10:22:31 +0100
Subject: [PATCH] dino: update to 0.2.2.
---
srcpkgs/dino/template | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/srcpkgs/dino/template b/srcpkgs/dino/template
index fda6cc8c94eb..3de80d3e799d 100644
--- a/srcpkgs/dino/template
+++ b/srcpkgs/dino/template
@@ -1,7 +1,7 @@
# Template file for 'dino'
pkgname=dino
-version=0.2.1
-revision=2
+version=0.2.2
+revision=1
build_style=cmake
configure_args="-GNinja -DDINO_PLUGIN_ENABLED_notification-sound=ON"
make_cmd=ninja
@@ -14,7 +14,7 @@ maintainer="Anjandev Momi <anjan@momi.ca>"
license="GPL-3.0-or-later"
homepage="https://github.com/dino/dino"
distfiles="https://github.com/dino/dino/archive/v${version}.tar.gz"
-checksum=56ead6fc54f8c10e1116d639431fe509ac8a390b68c60ed897562a215a075f32
+checksum=adb08b54971bf5b32875e058f1b1a4a3de96dd3431feb0399c1f21f834254bde
if [ "${XBPS_CHECK_PKGS}" ]; then
configure_args+=" -DBUILD_TESTS=ON"
next reply other threads:[~2022-01-03 9:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-03 9:22 UsernameRandomlyGenerated [this message]
2022-01-05 7:32 ` [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-34827@inbox.vuxu.org \
--to=usernamerandomlygenerated@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).