Github messages for voidlinux
 help / color / mirror / Atom feed
From: RunningDroid <RunningDroid@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] megatools: update to 1.11.0.
Date: Sun, 29 May 2022 04:35:48 +0200	[thread overview]
Message-ID: <20220529023548.whZx0D3qVKGLdsRTZtxmHzcnFPe4Mit3bfKarzQoE7c@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-37204@inbox.vuxu.org>

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

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

https://github.com/RunningDroid/void-packages update_megatools
https://github.com/void-linux/void-packages/pull/37204

megatools: update to 1.11.0.
<!-- 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 add ci skip tag as described in
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/37204.patch is attached

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

From 641c70515fd5f56d2fe309b0ce0dd56ab5df7eb4 Mon Sep 17 00:00:00 2001
From: RunningDroid <runningdroid@zoho.com>
Date: Thu, 19 May 2022 23:28:00 -0400
Subject: [PATCH] megatools: update to 1.11.0.

---
 srcpkgs/megatools/template | 16 +++++++++-------
 1 file changed, 9 insertions(+), 7 deletions(-)

diff --git a/srcpkgs/megatools/template b/srcpkgs/megatools/template
index bb7e53221866..2296f9ac7748 100644
--- a/srcpkgs/megatools/template
+++ b/srcpkgs/megatools/template
@@ -1,21 +1,23 @@
 # Template file for 'megatools'
 pkgname=megatools
-version=1.10.3
-revision=3
-build_style=gnu-configure
-hostmakedepends="pkg-config asciidoc"
+version=1.11.0
+revision=1
+_release_date=20220519
+wrksrc="megatools-${version}.${_release_date}"
+build_style=meson
+hostmakedepends="pkg-config asciidoc docbook2x"
 makedepends="glib-networking gobject-introspection openssl-devel libcurl-devel fuse-devel libsodium-devel glib-devel"
 short_desc="Command line client for Mega.nz file sharing service"
 maintainer="RunningDroid <runningdroid@zoho.com>"
 license="GPL-2.0-or-later"
 homepage="https://megatools.megous.com/"
-distfiles="${homepage}/builds/megatools-${version}.tar.gz"
-checksum=8dc1ca348633fd49de7eb832b323e8dc295f1c55aefb484d30e6475218558bdb
+distfiles="${homepage}/builds/megatools-${version}.${_release_date}.tar.gz"
+checksum=b30b1d87d916570f7aa6d36777dd378e83215d75ea5a2c14106028b6bddc261b
 
 post_install() {
 	vinstall contrib/bash-completion/megatools 644 usr/share/bash-completion/completions
 
-	for i in megadl megadf megamkdir megaget megareg megarm megaput megals megacopy; do
+	for i in megadl megadf megamkdir megaget megareg megarm megaput megals megacopy megaexport megatest; do
 		ln -sf megatools "${DESTDIR}/usr/share/bash-completion/completions/${i}"
 	done
 }

  reply	other threads:[~2022-05-29  2:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-20  3:37 [PR PATCH] " RunningDroid
2022-05-29  2:35 ` RunningDroid [this message]
2022-05-29  8:34 ` [PR REVIEW] " paper42
2022-05-30  0:44 ` RunningDroid
2022-06-01 20:18 ` [PR PATCH] [Merged]: " paper42

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=20220529023548.whZx0D3qVKGLdsRTZtxmHzcnFPe4Mit3bfKarzQoE7c@z \
    --to=runningdroid@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).