python3-docutils: upgrade 0.18.1 -> 0.19
PATCH 1/1 python3-docutils: upgrade 0.18.1 -> 0.19
License-Update:
year updated to 2022
url of some reposity and license changed
exceptions of BSD 2-Clause License changed
Changelog:
===========
- Drop support for Python 2.7, 3.5, and 3.6.
- Output changes:
HTML5:
Wrap groups of footnotes in an <aside> for easier styling.
The CSS rule .footnote-list { display: contents; } can be used to restore the behaviour of custom CSS styles.
- After package installation, the CLI commands python -m docutils and docutils start the generic command line front end tool.
- Support parsing "Markdown" input with 3rd party parsers myst, pycmark, or recommonmark.
- The default values for the "pep-references", "rfc-base-url", and "python-home" configuration settings now use the "https:" scheme. The PEP-writer template's header is updated to fix links and resemble the header of official PEPs.
- Various bugfixes and improvements (see HISTORY).
---
.../{python3-docutils_0.18.1.bb => python3-docutils_0.19.bb} | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
rename meta/recipes-devtools/python/{python3-docutils_0.18.1.bb => python3-docutils_0.19.bb} (62%)meta/recipes-devtools/python/python3-docutils_0.19.bb renamed from meta/recipes-devtools/python/python3-docutils_0.18.1.bb +2 -2
@@ -2,9 +2,9 @@ SUMMARY = "Docutils is a modular system for processing documentation into useful HOMEPAGE = "http://docutils.sourceforge.net" SECTION = "devel/python" LICENSE = "PSF-2.0 & BSD-2-Clause & GPL-3.0-only" -LIC_FILES_CHKSUM = "file://COPYING.txt;md5=fecee07ad8df9116e1f739e2ed2ea513" +LIC_FILES_CHKSUM = "file://COPYING.txt;md5=41001b296a89bb2780bbe306e947ecee" -SRC_URI[sha256sum] = "679987caf361a7539d76e584cbeddc311e3aee937877c87346f31debc63e9d06" +SRC_URI[sha256sum] = "33995a6753c30b7f577febfc2c50411fec6aac7f7ffeb7c4cfe5991072dcf9e6" inherit pypi setuptools3
Signature · 1 line
2.25.1
PATCH 1/1 python3-hatchling: upgrade 1.3.1 -> 1.5.0
---
.../{python3-hatchling_1.3.1.bb => python3-hatchling_1.5.0.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-devtools/python/{python3-hatchling_1.3.1.bb => python3-hatchling_1.5.0.bb} (88%)meta/recipes-devtools/python/python3-hatchling_1.5.0.bb renamed from meta/recipes-devtools/python/python3-hatchling_1.3.1.bb +1 -1
@@ -8,7 +8,7 @@ inherit pypi python_hatchling DEPENDS += "python3-pluggy-native python3-tomli-native python3-pathspec-native python3-packaging-native python3-editables-native" DEPENDS:remove:class-native = "python3-hatchling-native" -SRC_URI[sha256sum] = "aaa63019c9d666053d9ff318097335e766123844547c52940155c0401c3c142f" +SRC_URI[sha256sum] = "9ca409a41140cc662164680b78adcd3ba77b23a945984bd9970d11fe38e86a38" # Until we have a proper tool to invoke PEP517 builds, hatchling can't # bootstrap itself automatically.
Signature · 1 line
2.25.1
PATCH 1/1 python3-imagesize: upgrade 1.3.0 -> 1.4.1
In reply to Wang Mingyu---
.../{python3-imagesize_1.3.0.bb => python3-imagesize_1.4.1.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-devtools/python/{python3-imagesize_1.3.0.bb => python3-imagesize_1.4.1.bb} (79%)meta/recipes-devtools/python/python3-imagesize_1.4.1.bb renamed from meta/recipes-devtools/python/python3-imagesize_1.3.0.bb +1 -1
@@ -4,7 +4,7 @@ SECTION = "devel/python" LICENSE = "MIT" LIC_FILES_CHKSUM = "file://LICENSE.rst;md5=0c128f0f7e8a02e1b83884c0b5a41cda" -SRC_URI[sha256sum] = "cd1750d452385ca327479d45b64d9c7729ecf0b3969a58148298c77092261f9d" +SRC_URI[sha256sum] = "69150444affb9cb0d5cc5a92b3676f0b2fb7cd9ae39e947a5e11a36b4497cd4a" inherit setuptools3 pypi
Signature · 1 line
2.25.1
PATCH 1/1 python3-jsonschema: upgrade 4.6.1 -> 4.7.1
In reply to Wang MingyuMinor tweak of the PyPI hyperlink names
---
...{python3-jsonschema_4.6.1.bb => python3-jsonschema_4.7.1.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-devtools/python/{python3-jsonschema_4.6.1.bb => python3-jsonschema_4.7.1.bb} (93%)meta/recipes-devtools/python/python3-jsonschema_4.7.1.bb renamed from meta/recipes-devtools/python/python3-jsonschema_4.6.1.bb +1 -1
@@ -4,7 +4,7 @@ LICENSE = "MIT" LIC_FILES_CHKSUM = "file://COPYING;md5=7a60a81c146ec25599a3e1dabb8610a8 \ file://json/LICENSE;md5=9d4de43111d33570c8fe49b4cb0e01af" -SRC_URI[sha256sum] = "ec2802e6a37517f09d47d9ba107947589ae1d25ff557b925d83a321fc2aa5d3b" +SRC_URI[sha256sum] = "25203dbebd62a1179f810f14339f7a638baaf279b5cc3b738a58c3744af56d65" inherit pypi python_hatchling
Signature · 1 line
2.25.1
Quoted 4 lines · wangmy
License-Update:
year updated to 2022
url of some reposity and license changed
exceptions of BSD 2-Clause License changed
This last bit sounds a little worrying. Is the code still under BSD-2- Clause? How did the exceptions change? Were new ones added or removed? Does it change the license?
Cheers,
Richard
Quoted 8 lines · Richard Purdie
Quoted 4 lines
License-Update:
year updated to 2022
url of some reposity and license changed
exceptions of BSD 2-Clause License changedThis last bit sounds a little worrying. Is the code still under BSD-2- Clause? How did the exceptions change? Were new ones added or removed? Does it change the license?
In cases like this it usually helps to include a link to the commit on the web (e.g. github) where the changes are. If there are several commits between the two releases, then include all of them, there's usually a way to browse history per-file.
Alex
The relevant updates of COPYING.txt are the following:
Command line“entry point”to the docutils package. Part 2/2.
Support ``python -m docutils`` with new module docutils.__ main__. Support ``docutils`` CLI command via“entry point”in setup. py.
Keep tools/docutils-cli. py for backwards compatibility and manual installation. Calls docutils.__ main__. main().
But the above content can be regarded as the change of COPYING.txt?
--
Best Regards
---------------------------------------------------
Wang Mingyu
Development Dept.I
Nanjing Fujitsu Nanda Software Tech. Co., Ltd.(FNST) No. 6 Wenzhu Road, Nanjing, 210012, China
TEL: +86+25-86630566-8568
COINS: 79988548
FAX: +86+25-83317685
MAIL: [email protected]
http://www.fujitsu.com/cn/fnst/
Quoted 25 lines
-----Original Message-----
From: Alexander Kanavin <[email protected]>
Sent: Saturday, July 16, 2022 12:45 AM
To: Wang, Mingyu/王 鸣瑜 <[email protected]>
Cc: OE-core <[email protected]>; Richard Purdie <[email protected]>
Subject: Re: [OE-core] [PATCH] python3-docutils: upgrade 0.18.1 -> 0.19Quoted 8 lines · Richard Purdie
Quoted 4 lines
License-Update:
year updated to 2022
url of some reposity and license changed exceptions of BSD
2-Clause License changedThis last bit sounds a little worrying. Is the code still under BSD-2- Clause? How did the exceptions change? Were new ones added or removed? Does it change the license?
In cases like this it usually helps to include a link to the commit on the web (e.g. github) where the changes are. If there are several commits between the two releases, then include all of them, there's usually a way to browse history per-file.
Alex
If you upgrade the package with 'devtool upgrade python3-docutils', then devtool will write a diff of the license into the new recipe:
# --- COPYING.txt
# +++ COPYING.txt
# @@ -4,8 +4,8 @@
#
# :Author: David Goodger
# :Contact: [email protected]
# -:Date: $Date: 2021-11-19 13:46:38 +0100 (Fr, 19. Nov 2021) $ # -:Web site: http://docutils.sourceforge.net/
# +:Date: $Date: 2022-05-30 18:54:46 +0200 (Mo, 30. Mai 2022) $ # +:Web site: https://docutils.sourceforge.io/
# :Copyright: This document has been placed in the public domain. #
# Most of the files included in this project have been placed in the # @@ -26,11 +26,11 @@
# below (the "Work") to the public domain.
#
# The primary repository for the Work is the Internet World Wide Web # -site <http://docutils.sourceforge.net/>. The Work consists of the # +site <https://docutils.sourceforge.io/>. The Work consists of the # files within the "docutils" module of the Docutils project Subversion # -repository (Internet host docutils.svn.sourceforge.net, filesystem path # -/svnroot/docutils), whose Internet web interface is located at # -<http://docutils.svn.sourceforge.net/viewvc/docutils/>. Files dedicated to the
# +repository (http://svn.code.sf.net/p/docutils/code/),
# +whose Internet web interface is located at
# +<https://sourceforge.net/p/docutils/code>. Files dedicated to the # public domain may be identified by the inclusion, near the beginning # of each file, of a declaration of the form::
#
# @@ -99,13 +99,18 @@
#
# .. _eLyXer: https://github.com/alexfernandez/elyxer
#
# -* docutils/parsers/recommonmark_wrapper.py,
# +* docutils/__main__.py,
# + docutils/parsers/commonmark_wrapper.py, # + docutils/parsers/recommonmark_wrapper.py, # docutils/utils/error_reporting.py, # docutils/utils/math/__init__.py, # docutils/utils/math/latex2mathml.py, # docutils/utils/math/tex2mathml_extern.py, # docutils/utils/punctuation_chars.py, # + docutils/utils/smartquotes.py, # docutils/writers/html5_polyglot/__init__.py, # + docutils/writers/html5_polyglot/*.css, # + docutils/writers/latex2e/docutils.sty, # docutils/writers/xetex/__init__.py, # test/test_parsers/test_recommonmark/\*.py, # test/test_parsers/test_rst/test_directives/test__init__.py,
# @@ -141,12 +146,12 @@
# Plaintext versions of all the linked-to licenses are provided in the # licenses_ directory.
#
# -.. _sandbox: http://docutils.sourceforge.net/sandbox/README.html
# +.. _sandbox: https://docutils.sourceforge.io/sandbox/README.html
# .. _licenses: licenses/
# -.. _Python 2.1.1 license: http://www.python.org/2.1.1/license.html
# -.. _GNU General Public License: http://www.gnu.org/copyleft/gpl.html
# +.. _Python 2.1.1 license: https://docs.python.org/3/license.html
# +.. _GNU General Public License: https://www.gnu.org/copyleft/gpl.html
# .. _BSD 2-Clause License: http://opensource.org/licenses/BSD-2-Clause # .. _BSD 3-Clause License: https://opensource.org/licenses/BSD-3-Clause # .. _OSI-approved: http://opensource.org/licenses/ # .. _license-list:
# -.. _GPL-compatible: http://www.gnu.org/licenses/license-list.html
# +.. _GPL-compatible: https://www.gnu.org/licenses/license-list.html
#
#
Then it's easy to see that the changes are dates, URLs and file lists only. You can also
go through the version history, but it's subversion on sourceforge, so not that simple:
https://sourceforge.net/p/docutils/code/9110/log/?path=/trunk/docutils/COPYING.txt
(e.g. you need to check the top three commits only)
Alex
Quoted 47 lines · On Mon, 18 Jul 2022 at 02:25, [email protected] <[email protected]> wrote:
The relevant updates of COPYING.txt are the following:
Command line“entry point”to the docutils package. Part 2/2.
Support ``python -m docutils`` with new moduledocutils.__ main__. Support ``docutils`` CLI command via“entry point”in setup. py.
Keeptools/docutils-cli. py for backwards compatibility and manual installation. Callsdocutils.__ main__. main().But the above content can be regarded as the change of COPYING.txt?
--
Best Regards
---------------------------------------------------
Wang Mingyu
Development Dept.I
Nanjing Fujitsu Nanda Software Tech. Co., Ltd.(FNST) No. 6 Wenzhu Road, Nanjing, 210012, China
TEL: +86+25-86630566-8568
COINS: 79988548
FAX: +86+25-83317685
MAIL: [email protected]
http://www.fujitsu.com/cn/fnst/Quoted 25 lines
-----Original Message-----
From: Alexander Kanavin <[email protected]>
Sent: Saturday, July 16, 2022 12:45 AM
To: Wang, Mingyu/王 鸣瑜 <[email protected]>
Cc: OE-core <[email protected]>; Richard Purdie <[email protected]>
Subject: Re: [OE-core] [PATCH] python3-docutils: upgrade 0.18.1 -> 0.19Quoted 8 lines · Richard Purdie
Quoted 4 lines
License-Update:
year updated to 2022
url of some reposity and license changed exceptions of BSD
2-Clause License changedThis last bit sounds a little worrying. Is the code still under BSD-2- Clause? How did the exceptions change? Were new ones added or removed? Does it change the license?
In cases like this it usually helps to include a link to the commit on the web (e.g. github) where the changes are. If there are several commits between the two releases, then include all of them, there's usually a way to browse history per-file.
Alex
I have seen the results of devtool, and also diff two versions of COPYING.txt. Sometimes, when the file differs greatly, I may not summarize them well
--
Best Regards
---------------------------------------------------
Wang Mingyu
Development Dept.I
Nanjing Fujitsu Nanda Software Tech. Co., Ltd.(FNST) No. 6 Wenzhu Road, Nanjing, 210012, China
TEL: +86+25-86630566-8568
COINS: 79988548
FAX: +86+25-83317685
MAIL: [email protected]
http://www.fujitsu.com/cn/fnst/
Quoted 140 lines
-----Original Message-----
From: Alexander Kanavin <[email protected]>
Sent: Tuesday, July 19, 2022 2:00 AM
To: Wang, Mingyu/王 鸣瑜 <[email protected]>
Cc: OE-core <[email protected]>; Richard Purdie <[email protected]>
Subject: Re: [OE-core] [PATCH] python3-docutils: upgrade 0.18.1 -> 0.19If you upgrade the package with 'devtool upgrade python3-docutils', then devtool will write a diff of the license into the new recipe:
# --- COPYING.txt
# +++ COPYING.txt
# @@ -4,8 +4,8 @@
#
# :Author: David Goodger
# :Contact: [email protected]
# -:Date: $Date: 2021-11-19 13:46:38 +0100 (Fr, 19. Nov 2021) $ # -:Web site:
http://docutils.sourceforge.net/ # +:Date: $Date: 2022-05-30 18:54:46 +0200 (Mo, 30. Mai 2022) $ # +:Web site: https://docutils.sourceforge.io/
# :Copyright: This document has been placed in the public domain.
#
# Most of the files included in this project have been placed in the # @@ -26,11 +26,11 @@ # below (the "Work") to the public domain.
#
# The primary repository for the Work is the Internet World Wide Web # -site
<http://docutils.sourceforge.net/>. The Work consists of the # +site
<https://docutils.sourceforge.io/>. The Work consists of the # files within the "docutils" module of the Docutils project Subversion # -repository (Internet host docutils.svn.sourceforge.net, filesystem path # -/svnroot/docutils), whose Internet web interface is located at # -<http://docutils.svn.sourceforge.net/viewvc/docutils/>. Files dedicated to the # +repository (http://svn.code.sf.net/p/docutils/code/),
# +whose Internet web interface is located at # +<https://sourceforge.net/p/docutils/code>. Files dedicated to the # public domain may be identified by the inclusion, near the beginning # of each file, of a declaration of the form::
#
# @@ -99,13 +99,18 @@
#
# .._eLyXer: https://github.com/alexfernandez/elyxer
#
# -*docutils/parsers/recommonmark_wrapper.py,
# +*docutils/__main__.py,# + docutils/parsers/commonmark_wrapper.py, # + docutils/parsers/recommonmark_wrapper.py, # docutils/utils/error_reporting.py, # docutils/utils/math/__init__.py, # docutils/utils/math/latex2mathml.py, # docutils/utils/math/tex2mathml_extern.py, # docutils/utils/punctuation_chars.py, # + docutils/utils/smartquotes.py, # docutils/writers/html5_polyglot/__init__.py, # + docutils/writers/html5_polyglot/*.css, # + docutils/writers/latex2e/docutils.sty, # docutils/writers/xetex/__init__.py, # test/test_parsers/test_recommonmark/\*.py, # test/test_parsers/test_rst/test_directives/test__init__.py,# @@ -141,12 +146,12 @@
# Plaintext versions of all the linked-to licenses are provided in the #licenses_directory.
#
# -.._sandbox: http://docutils.sourceforge.net/sandbox/README.html
# +.._sandbox: https://docutils.sourceforge.io/sandbox/README.html
# .._licenses: licenses/
# -.._Python2.1.1 license: http://www.python.org/2.1.1/license.html
# -.._GNUGeneral Public License: http://www.gnu.org/copyleft/gpl.html
# +.._Python2.1.1 license: https://docs.python.org/3/license.html
# +.._GNUGeneral Public License: https://www.gnu.org/copyleft/gpl.html# .. _BSD 2-Clause License: http://opensource.org/licenses/BSD-2-Clause # .. _BSD 3-Clause License: https://opensource.org/licenses/BSD-3-Clause # .. _OSI-approved: http://opensource.org/licenses/ # .. _license-list:# -.. _GPL-compatible: http://www.gnu.org/licenses/license-list.html
# +.. _GPL-compatible: https://www.gnu.org/licenses/license-list.html
#
#Then it's easy to see that the changes are dates, URLs and file lists only. You can also go through the version history, but it's subversion on sourceforge, so not that simple:
https://sourceforge.net/p/docutils/code/9110/log/?path=/trunk/docutils/COPYI
NG.txt
(e.g. you need to check the top three commits only)Alex
Quoted 9 lines · On Mon, 18 Jul 2022 at 02:25, [email protected] <[email protected]> wrote:
The relevant updates of COPYING.txt are the following:
Command line“entry point”to the docutils package. Part 2/2.
Support ``python -m docutils`` with new moduledocutils.__ main__. Support ``docutils`` CLI command via“entry point”in setup. py.
Keeptools/docutils-cli. py for backwards compatibility and manual installation. Callsdocutils.__ main__. main().Quoted 32 lines
But the above content can be regarded as the change of COPYING.txt?
--
Best Regards
---------------------------------------------------
Wang Mingyu
Development Dept.I
Nanjing Fujitsu Nanda Software Tech. Co., Ltd.(FNST) No. 6 Wenzhu Road, Nanjing, 210012, China
TEL: +86+25-86630566-8568
COINS: 79988548
FAX: +86+25-83317685
MAIL: [email protected]
http://www.fujitsu.com/cn/fnst/Quoted 18 lines
-----Original Message-----
From: Alexander Kanavin <[email protected]>
Sent: Saturday, July 16, 2022 12:45 AM
To: Wang, Mingyu/王 鸣瑜 <[email protected]>
Cc: OE-core <[email protected]>; Richard Purdie <[email protected]>
Subject: Re: [OE-core] [PATCH] python3-docutils: upgrade 0.18.1 -> 0.19Quoted 7 lines · Richard Purdie
Quoted 4 lines
License-Update:
year updated to 2022
url of some reposity and license changed exceptions of BSD
2-Clause License changedThis last bit sounds a little worrying. Is the code still under BSD-2- Clause? How did the exceptions change? Were new ones added or
removed?
Quoted 3 lines
Quoted 3 lines
Quoted 1 line
Does it change the license?
In cases like this it usually helps to include a link to the commit on the web
(e.g.
Quoted 5 lines
Quoted 5 lines
github) where the changes are. If there are several commits between the two releases, then include all of them, there's usually a way to browse history per-file.
Alex