Github messages for voidlinux
 help / color / mirror / Atom feed
From: travankor <travankor@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] gdown: update to 3.13.0.
Date: Wed, 25 Aug 2021 00:45:22 +0200	[thread overview]
Message-ID: <20210824224522.8q8VYQephSmQHYn9ccIuGpwqHBXliQk5Fbs2djXdjj4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-32622@inbox.vuxu.org>

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

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

https://github.com/travankor/void-packages gdown
https://github.com/void-linux/void-packages/pull/32622

gdown: update to 3.13.0.
<!-- 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?
- [X] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
- [ ] 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/32622.patch is attached

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

From e1646010a67511b91051059926a3a58854e41ac3 Mon Sep 17 00:00:00 2001
From: travankor <travankor@tuta.io>
Date: Sat, 21 Aug 2021 20:14:48 -0700
Subject: [PATCH] gdown: update to 3.13.0.

---
 srcpkgs/gdown/template | 8 +++++---
 1 file changed, 5 insertions(+), 3 deletions(-)

diff --git a/srcpkgs/gdown/template b/srcpkgs/gdown/template
index e855fef80caa..e2b19518da59 100644
--- a/srcpkgs/gdown/template
+++ b/srcpkgs/gdown/template
@@ -1,17 +1,19 @@
 # Template file for 'gdown'
 pkgname=gdown
-version=3.12.2
-revision=2
+version=3.13.0
+revision=1
 build_style=python3-module
 hostmakedepends="python3 python3-setuptools"
 depends="python3-filelock python3-requests python3-six python3-tqdm
  python3-pysocks"
+checkdepends="${depends} python3-pytest"
 short_desc="Download a large file from Google Drive"
 maintainer="travankor <travankor@tuta.io>"
 license="MIT"
 homepage="https://github.com/wkentaro/gdown"
 distfiles="https://github.com/wkentaro/gdown/archive/v${version}.tar.gz"
-checksum=c2c58283236b87371ede8692626c44a839e1a962d48eceb269841535bef21a73
+checksum=830d88d3ab4640ff2f0a34d51bda4badda64ed6df4eefd5b1a4823c96e574a19
+make_check=no # doesn't create egg-info during build
 
 post_install() {
 	vlicense LICENSE

  parent reply	other threads:[~2021-08-24 22:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-22  3:15 [PR PATCH] " travankor
2021-08-22  4:09 ` [PR PATCH] [Updated] " travankor
2021-08-22  4:18 ` travankor
2021-08-22  4:25 ` travankor
2021-08-22  4:34 ` travankor
2021-08-23 19:07 ` [PR REVIEW] " Chocimier
2021-08-24 22:45 ` travankor [this message]
2021-08-27 18:39 ` [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=20210824224522.8q8VYQephSmQHYn9ccIuGpwqHBXliQk5Fbs2djXdjj4@z \
    --to=travankor@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).