Github messages for voidlinux
 help / color / mirror / Atom feed
From: misuchiru03 <misuchiru03@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] python3-MechanicalSoup
Date: Fri, 01 Oct 2021 19:44:32 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-33215@inbox.vuxu.org> (raw)

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

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

https://github.com/misuchiru03/void-packages up_python3-MechanicalSoup_1.1.0
https://github.com/void-linux/void-packages/pull/33215

python3-MechanicalSoup
<!-- Mark items with [x] where applicable -->

#### General
- [X] 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?
- [ ] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
- [X] 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.)
- [X] I built this PR locally for my native architecture, (x86_64,GLIBC)
- [X] I built this PR locally for these architectures (if supported. mark crossbuilds):
  - [X] aarch64-musl
  - [X] armv7l
  - [X] armv6l-musl
-->


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

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-up_python3-MechanicalSoup_1.1.0-33215.patch --]
[-- Type: text/x-diff, Size: 1216 bytes --]

From 482fb882e9910ca9328a91e631d94e027c9b1e9c Mon Sep 17 00:00:00 2001
From: Alex Childs <misuchiru03+void@gmail.com>
Date: Thu, 30 Sep 2021 21:57:33 -0500
Subject: [PATCH] python3-MechanicalSoup: update to 1.1.0

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

diff --git a/srcpkgs/python3-MechanicalSoup/template b/srcpkgs/python3-MechanicalSoup/template
index f763efcf4e72..44d992fca3e8 100644
--- a/srcpkgs/python3-MechanicalSoup/template
+++ b/srcpkgs/python3-MechanicalSoup/template
@@ -1,7 +1,7 @@
 # Template file for 'python3-MechanicalSoup'
 pkgname=python3-MechanicalSoup
-version=0.12.0
-revision=3
+version=1.1.0
+revision=1
 wrksrc=MechanicalSoup-${version}
 build_style=python3-module
 pycompile_module="mechanicalsoup"
@@ -13,7 +13,7 @@ maintainer="Alex Childs <misuchiru03+void@gmail.com>"
 license="MIT"
 homepage="https://mechanicalsoup.readthedocs.io/en/stable/index.html"
 distfiles="${PYPI_SITE}/M/MechanicalSoup/MechanicalSoup-${version}.tar.gz"
-checksum=39a60627a97981869251837b8bd082485f2f681df8a3315836ffaa74663627bd
+checksum=2be8ad9b7571990fce16d0f99a741779921510eb133d3a4dfdeccb2ff2cd00e5
 
 post_install() {
 	vlicense LICENSE

             reply	other threads:[~2021-10-01 17:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-01 17:44 misuchiru03 [this message]
2021-10-01 17:45 ` [PR PATCH] [Updated] python3-MechanicalSoup: update to 1.1.0 misuchiru03
2021-10-01 20:23 ` paper42
2021-10-01 20:24 ` paper42
2022-06-06  2:15 ` [WIP] " github-actions
2022-06-21  2:12 ` [PR PATCH] [Closed]: " github-actions

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-33215@inbox.vuxu.org \
    --to=misuchiru03@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).