Github messages for voidlinux
 help / color / mirror / Atom feed
From: chrysos349 <chrysos349@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] python3-BeautifulSoup4: update to 4.12.2
Date: Sat, 10 Jun 2023 23:59:03 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-44356@inbox.vuxu.org> (raw)

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

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

https://github.com/chrysos349/void-packages python3-BeautifulSoup4
https://github.com/void-linux/void-packages/pull/44356

python3-BeautifulSoup4: update to 4.12.2
#### Testing the changes
- I tested the changes in this PR: **briefly**

#### Local build testing
- I built this PR locally for my native architecture, (x86_64-LIBC)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
  - aarch64

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

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

From 7734f0c66b69ff1e99067f4a444b516eb7175a9e Mon Sep 17 00:00:00 2001
From: chrysos349 <chrysostom349@gmail.com>
Date: Sun, 11 Jun 2023 00:56:34 +0300
Subject: [PATCH] python3-BeautifulSoup4: update to 4.12.2

---
 srcpkgs/python3-BeautifulSoup4/template | 15 +++++++--------
 1 file changed, 7 insertions(+), 8 deletions(-)

diff --git a/srcpkgs/python3-BeautifulSoup4/template b/srcpkgs/python3-BeautifulSoup4/template
index 882ea8a33214..e5e0ccbbecc7 100644
--- a/srcpkgs/python3-BeautifulSoup4/template
+++ b/srcpkgs/python3-BeautifulSoup4/template
@@ -1,20 +1,19 @@
 # Template file for 'python3-BeautifulSoup4'
 pkgname=python3-BeautifulSoup4
-version=4.11.1
-revision=2
-build_style=python3-module
-hostmakedepends="python3-setuptools"
-depends="python3 python3-soupsieve"
+version=4.12.2
+revision=1
+build_style=python3-pep517
+hostmakedepends="python3-wheel hatchling"
+depends="python3-soupsieve python3-html5lib python3-lxml"
 checkdepends="python3-pytest $depends"
 short_desc="Python3 HTML/XML parser"
 maintainer="Orphaned <orphan@voidlinux.org>"
 license="MIT"
 homepage="https://www.crummy.com/software/BeautifulSoup"
-changelog="https://bazaar.launchpad.net/~leonardr/beautifulsoup/bs4/view/head:/CHANGELOG"
+changelog="https://git.launchpad.net/beautifulsoup/plain/CHANGELOG"
 distfiles="${PYPI_SITE}/b/beautifulsoup4/beautifulsoup4-${version}.tar.gz"
-checksum=ad9aa55b65ef2808eb405f46cf74df7fcb7044d5cbc26487f96eb2ef2e436693
+checksum=492bbc69dca35d12daac71c4db1bfff0c876c00ef4a2ffacce226d4638eb72da
 
 post_install() {
 	vlicense LICENSE
-	rm -r ${DESTDIR}/${py3_sitelib}/bs4/tests
 }

             reply	other threads:[~2023-06-10 21:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-10 21:59 chrysos349 [this message]
2023-06-19 21:14 ` tornaria
2023-06-20 19:45 ` [PR PATCH] [Closed]: " chrysos349

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