Github messages for voidlinux
 help / color / mirror / Atom feed
From: Emru1 <Emru1@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] python3-cssutils: update to 2.6.0.
Date: Sat, 12 Nov 2022 17:09:44 +0100	[thread overview]
Message-ID: <20221112160944.i0kVWaDyvfOtobOxqThEhTKwB7MpDSPcb13qhHiI9i4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40408@inbox.vuxu.org>

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

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

https://github.com/Emru1/void-packages python3-cssutils
https://github.com/void-linux/void-packages/pull/40408

python3-cssutils: update to 2.6.0.
#### Testing the changes
- I tested the changes in this PR: **briefly**
- I built this PR locally for my native architecture, amd64

This package was strange, when I was updating to python3.11, byte-compile thrown errors about syntax, code looked like python2

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

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

From d80833d94efdc1df4cc83a8a2132fc6909ef6aae Mon Sep 17 00:00:00 2001
From: Emil Tomczyk <emil.tomczyk@skni.umcs.pl>
Date: Wed, 9 Nov 2022 11:29:30 +0100
Subject: [PATCH] python3-cssutils: update to 2.6.0.

---
 srcpkgs/python3-cssutils/template | 13 +++++++------
 1 file changed, 7 insertions(+), 6 deletions(-)

diff --git a/srcpkgs/python3-cssutils/template b/srcpkgs/python3-cssutils/template
index d5e43c8e2993..b246e8563721 100644
--- a/srcpkgs/python3-cssutils/template
+++ b/srcpkgs/python3-cssutils/template
@@ -1,16 +1,17 @@
 # Template file for 'python3-cssutils'
 pkgname=python3-cssutils
-version=1.0.2
-revision=7
-build_style=python3-module
-hostmakedepends="python3-setuptools"
-depends="python3-setuptools"
+version=2.6.0
+revision=1
+build_style=python3-pep517
+hostmakedepends="python3-setuptools python3-setuptools_scm python3-wheel"
+depends="python3"
 short_desc="CSS Cascading Style Sheets library for Python3"
 maintainer="Farhad Shahbazi <grauwolf@geekosphere.org>"
 # source files write 3.0-or-later, PKG-INFO writes 2.1
 license="LGPL-3.0-or-later"
 homepage="https://pypi.org/project/cssutils/"
+changelog="https://raw.githubusercontent.com/jaraco/cssutils/main/CHANGES.rst"
 distfiles="${PYPI_SITE}/c/cssutils/cssutils-${version}.tar.gz"
-checksum=a2fcf06467553038e98fea9cfe36af2bf14063eb147a70958cfcaa8f5786acaf
+checksum=f7dcd23c1cec909fdf3630de346e1413b7b2555936dec14ba2ebb9913bf0818e
 
 conflicts="python-cssutils>=0"

  parent reply	other threads:[~2022-11-12 16:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-09 10:34 [PR PATCH] " Emru1
2022-11-11  9:57 ` [PR REVIEW] " icp1994
2022-11-11  9:57 ` icp1994
2022-11-12 16:09 ` Emru1 [this message]
2022-11-12 16:11 ` Emru1
2022-11-12 16:35 ` icp1994
2023-02-11  1:58 ` github-actions
2023-02-25  2:01 ` [PR PATCH] [Closed]: " github-actions
2023-02-25 12:54 ` MarcinWieczorek

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=20221112160944.i0kVWaDyvfOtobOxqThEhTKwB7MpDSPcb13qhHiI9i4@z \
    --to=emru1@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).