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/ > -----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.19 > > 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/COPYI > NG.txt > (e.g. you need to check the top three commits only) > > Alex > > 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 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/ > > > > > -----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.19 > > > > > > On Fri, 15 Jul 2022 at 18:41, Richard Purdie > > > <[email protected]> wrote: > > > > > 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? > > > > > > 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
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#168263): https://lists.openembedded.org/g/openembedded-core/message/168263 Mute This Topic: https://lists.openembedded.org/mt/92328558/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
