Github messages for voidlinux
 help / color / mirror / Atom feed
From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: [PR PATCH] docker-compose: update to 1.24.1, patch version check for pyYAML.
Date: Mon, 09 Sep 2019 09:37:03 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-14362@inbox.vuxu.org> (raw)

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

There is a new pull request by shizonic against master on the void-packages repository

https://github.com/shizonic/void-packages docker-compose
https://github.com/void-linux/void-packages/pull/14362

docker-compose: update to 1.24.1, patch version check for pyYAML.


A patch file from https://github.com/void-linux/void-packages/pull/14362.patch is attached

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

From fc021a9fd778ba543f60dac9b42d6a2b12a55e1e Mon Sep 17 00:00:00 2001
From: Toby Merz <realtiaz@gmail.com>
Date: Mon, 9 Sep 2019 09:25:37 +0200
Subject: [PATCH] docker-compose: update to 1.24.1, patch version check for
 pyYAML.

---
 srcpkgs/docker-compose/patches/pyyaml_version.patch | 13 +++++++++++++
 srcpkgs/docker-compose/template                     |  8 +++++---
 2 files changed, 18 insertions(+), 3 deletions(-)
 create mode 100644 srcpkgs/docker-compose/patches/pyyaml_version.patch

diff --git a/srcpkgs/docker-compose/patches/pyyaml_version.patch b/srcpkgs/docker-compose/patches/pyyaml_version.patch
new file mode 100644
index 00000000000..77c69fd89a5
--- /dev/null
+++ b/srcpkgs/docker-compose/patches/pyyaml_version.patch
@@ -0,0 +1,13 @@
+diff --git a/setup.py b/setup.py
+index 8371cc756ee0..5e27ab7c5d0e 100644
+--- a/setup.py
++++ b/setup.py
+@@ -32,7 +32,7 @@ def find_version(*file_paths):
+ install_requires = [
+     'cached-property >= 1.2.0, < 2',
+     'docopt >= 0.6.1, < 0.7',
+-    'PyYAML >= 3.10, < 4.3',
++    'PyYAML >= 3.10',
+     'requests >= 2.6.1, != 2.11.0, != 2.12.2, != 2.18.0, < 2.21',
+     'texttable >= 0.9.0, < 0.10',
+     'websocket-client >= 0.32.0, < 1.0',
diff --git a/srcpkgs/docker-compose/template b/srcpkgs/docker-compose/template
index eaa967790b6..c3383fdf1ad 100644
--- a/srcpkgs/docker-compose/template
+++ b/srcpkgs/docker-compose/template
@@ -1,7 +1,7 @@
 # Template file for 'docker-compose'
 pkgname=docker-compose
-version=1.24.0
-revision=1
+version=1.24.1
+revision=2
 archs=noarch
 wrksrc="compose-${version}"
 build_style=python3-module
@@ -16,7 +16,9 @@ maintainer="pancake <pancake@nopcode.org>"
 license="Apache-2.0"
 homepage="https://docs.docker.com/compose/"
 distfiles="https://github.com/docker/compose/archive/${version}.tar.gz"
-checksum=31933e401d295812617f23377f63fc2b8da13d8456b61a60cec0e02afcad5672
+checksum=63a0e0d3819ff77aebd3d5ea30f77b36475ed522c4dabed2eb10636e35aa9370
+patch_args="-Np1"
+
 
 pre_build() {
 	# relax texttable and requests upper bound

             reply	other threads:[~2019-09-09  7:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-09  7:37 voidlinux-github [this message]
2019-09-09  8:34 ` [PR PATCH] [Merged]: " voidlinux-github

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-14362@inbox.vuxu.org \
    --to=voidlinux-github@inbox.vuxu.org \
    --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).