Github messages for voidlinux
 help / color / mirror / Atom feed
From: ar-jan <ar-jan@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] python3-outcome: update to 1.2.0.
Date: Mon, 17 Apr 2023 01:02:56 +0200	[thread overview]
Message-ID: <20230416230256.Icz2JilWX9qq-XQHwKOYADQ3rj-J2RNGy_snL70gCt8@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-43488@inbox.vuxu.org>

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

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

https://github.com/ar-jan/void-packages python3-outcome
https://github.com/void-linux/void-packages/pull/43488

python3-outcome: update to 1.2.0.
<!-- Uncomment relevant sections and delete options which are not applicable -->

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

<!--
#### New package
- This new package conforms to the [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-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/43488.patch is attached

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

From d0a9d48087465e43686f8a83c836e526364fdb74 Mon Sep 17 00:00:00 2001
From: Arjan Mossel <arjanmossel@gmail.com>
Date: Mon, 17 Apr 2023 00:56:54 +0200
Subject: [PATCH] python3-outcome: update to 1.2.0.

---
 srcpkgs/python3-outcome/template | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/srcpkgs/python3-outcome/template b/srcpkgs/python3-outcome/template
index daabfffe61de..6f6d448dd6b3 100644
--- a/srcpkgs/python3-outcome/template
+++ b/srcpkgs/python3-outcome/template
@@ -1,7 +1,7 @@
 # Template file for 'python3-outcome'
 pkgname=python3-outcome
-version=1.1.0
-revision=3
+version=1.2.0
+revision=1
 build_style=python3-module
 hostmakedepends="python3-setuptools"
 depends="python3"
@@ -11,7 +11,7 @@ maintainer="Arjan Mossel <arjanmossel@gmail.com>"
 license="Apache-2.0, MIT"
 homepage="https://github.com/python-trio/outcome"
 distfiles="${PYPI_SITE}/o/outcome/outcome-${version}.tar.gz"
-checksum=e862f01d4e626e63e8f92c38d1f8d5546d3f9cce989263c521b2e7990d186967
+checksum=6f82bd3de45da303cf1f771ecafa1633750a358436a8bb60e06a1ceb745d2672
 
 post_install() {
 	vlicense LICENSE

  reply	other threads:[~2023-04-16 23:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-16 22:58 [PR PATCH] " ar-jan
2023-04-16 23:02 ` ar-jan [this message]
2023-04-30  7:18 ` [PR PATCH] [Merged]: " classabbyamp

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=20230416230256.Icz2JilWX9qq-XQHwKOYADQ3rj-J2RNGy_snL70gCt8@z \
    --to=ar-jan@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).