Github messages for voidlinux
 help / color / mirror / Atom feed
From: tibequadorian <tibequadorian@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] bitwig-studio: update to 4.1.6.
Date: Thu, 17 Mar 2022 17:17:49 +0100	[thread overview]
Message-ID: <20220317161749.Uz7QprZD3Os1xiqWagT_R1ZPIpnurs5Wtg_PsmntGks@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35633@inbox.vuxu.org>

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

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

https://github.com/tibequadorian/void-packages bitwig-studio
https://github.com/void-linux/void-packages/pull/35633

bitwig-studio: update to 4.1.6.
@ale-saglia

<!-- Uncomment relevant sections and delete options which are not applicable -->

#### Testing the changes
- I tested the changes in this PR: **YES**

<!--
#### 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/35633.patch is attached

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

From 237df0ec14a4c99fe11db6e5a778bf2286b7ca75 Mon Sep 17 00:00:00 2001
From: tibequadorian <tibequadorian@posteo.de>
Date: Tue, 15 Feb 2022 13:45:25 +0100
Subject: [PATCH] bitwig-studio: update to 4.2.

---
 srcpkgs/bitwig-studio/template | 8 ++++----
 srcpkgs/bitwig-studio/update   | 2 ++
 2 files changed, 6 insertions(+), 4 deletions(-)
 create mode 100644 srcpkgs/bitwig-studio/update

diff --git a/srcpkgs/bitwig-studio/template b/srcpkgs/bitwig-studio/template
index 894ac6e30207..e5a30fdd07e9 100644
--- a/srcpkgs/bitwig-studio/template
+++ b/srcpkgs/bitwig-studio/template
@@ -1,16 +1,16 @@
 # Template file for 'bitwig-studio'
 pkgname=bitwig-studio
-version=4.0.1
+version=4.2
 revision=1
 archs="x86_64"
 depends="xdg-utils xcb-util-wm libbsd"
 short_desc="DAW for music production, remixing and live performance"
-maintainer="Alessandro Saglia <ale.saglia@gmail.com>"
+maintainer="Orphaned <orphan@voidlinux.org>"
 license="custom:bitwig"
 homepage="https://bitwig.com/"
 _file="bitwig-studio-${version}.deb"
 distfiles="https://downloads.bitwig.com/stable/${version}/${_file}"
-checksum=ca10802a56cb8f2072c244986356aa6d41859401c12d1f20f313c322aa142199
+checksum=848204563e6c33f35d8418b07ab16fc885ea8f447c12f731c0ce94674084e36f
 nostrip=yes
 restricted=yes
 repository=nonfree
@@ -25,5 +25,5 @@ do_install() {
 }
 
 post_install() {
-	vlicense ${DESTDIR}/opt/bitwig-studio/EULA.rtf
+	vlicense ${DESTDIR}/opt/bitwig-studio/EULA.txt
 }
diff --git a/srcpkgs/bitwig-studio/update b/srcpkgs/bitwig-studio/update
new file mode 100644
index 000000000000..e9b00911312f
--- /dev/null
+++ b/srcpkgs/bitwig-studio/update
@@ -0,0 +1,2 @@
+site="https://www.bitwig.com/de/download/"
+pattern="Bitwig Studio \K[\d.]+"

  reply	other threads:[~2022-03-17 16:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-15 12:53 [PR PATCH] " tibequadorian
2022-03-17 16:17 ` tibequadorian [this message]
2022-04-22 21:57 ` [PR PATCH] [Closed]: bitwig-studio: update to 4.2 tibequadorian

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=20220317161749.Uz7QprZD3Os1xiqWagT_R1ZPIpnurs5Wtg_PsmntGks@z \
    --to=tibequadorian@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).