Github messages for voidlinux
 help / color / mirror / Atom feed
From: UsernameRandomlyGenerated <UsernameRandomlyGenerated@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] lingot: update to 1.1.1.
Date: Sun, 07 Feb 2021 14:56:55 +0100	[thread overview]
Message-ID: <20210207135655.mHfumPyBJfrwXoLe1G8W9tvW2NJpeJ4CFOtrRZG0aio@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-28566@inbox.vuxu.org>

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

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

https://github.com/UsernameRandomlyGenerated/void-packages lingot111
https://github.com/void-linux/void-packages/pull/28566

lingot: update to 1.1.1.
<!-- Mark items with [x] where applicable -->

#### General
- [ ] This is a new package and it conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements)

#### Have the results of the proposed changes been tested?
- [ ] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
- [x] I generally don't use the affected packages but briefly tested this PR

<!--
If GitHub CI cannot be used to validate the build result (for example, if the
build is likely to take several hours), make sure to
[skip CI](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration).
When skipping CI, uncomment and fill out the following section.
Note: for builds that are likely to complete in less than 2 hours, it is not
acceptable to skip CI.
-->
<!-- 
#### Does it build and run successfully? 
(Please choose at least one native build and, if supported, at least one cross build. More are better.)
- [ ] 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/28566.patch is attached

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

From 83d6f30e39d396cc53b6ee5b7de0ce69cd113341 Mon Sep 17 00:00:00 2001
From: UsernameRandomlyGenerated <coredavid@tutanota.com>
Date: Sun, 7 Feb 2021 14:53:25 +0100
Subject: [PATCH] lingot: update to 1.1.1.

---
 srcpkgs/lingot/template | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/srcpkgs/lingot/template b/srcpkgs/lingot/template
index c7d3f58f757..8afcf99ca0c 100644
--- a/srcpkgs/lingot/template
+++ b/srcpkgs/lingot/template
@@ -1,14 +1,14 @@
 # Template file for 'lingot'
 pkgname=lingot
-version=1.0.1
+version=1.1.1
 revision=1
 build_style=gnu-configure
-hostmakedepends="intltool pkg-config glib-devel"
+hostmakedepends="intltool pkg-config glib-devel json-c-devel"
 makedepends="alsa-lib-devel gtk+3-devel jack-devel fftw-devel libglade-devel
  pulseaudio-devel"
-short_desc="A musical instrument tuner"
+short_desc="Musical instrument tuner"
 maintainer="David <kalichakra@zoho.com>"
 license="GPL-2.0-or-later"
 homepage="http://www.nongnu.org/lingot/"
 distfiles="http://download.savannah.gnu.org/releases/lingot/${pkgname}-${version}.tar.gz"
-checksum=71b8c77bb988e8384a0ecbf4c861d838f7b985284a8e18f75532ab9816c6a00f
+checksum=c4f97e496a3666c70786d136e6f2ccc5e8a3813eb08cda35cacd7eb0d16f4d56

  reply	other threads:[~2021-02-07 13:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-07 13:56 [PR PATCH] " UsernameRandomlyGenerated
2021-02-07 13:56 ` UsernameRandomlyGenerated [this message]
2021-02-07 16:11 ` [PR PATCH] [Updated] " UsernameRandomlyGenerated
2021-02-10  0:57 ` [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=20210207135655.mHfumPyBJfrwXoLe1G8W9tvW2NJpeJ4CFOtrRZG0aio@z \
    --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).