Script 'mail_helper' called by obssrc
Hello community,

here is the log from the commit of package python-pip-tools for 
openSUSE:Factory checked in at 2022-06-16 18:21:05
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/python-pip-tools (Old)
 and      /work/SRC/openSUSE:Factory/.python-pip-tools.new.1548 (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "python-pip-tools"

Thu Jun 16 18:21:05 2022 rev:4 rq:982919 version:6.6.2

Changes:
--------
--- /work/SRC/openSUSE:Factory/python-pip-tools/python-pip-tools.changes        
2022-04-08 00:29:03.149422360 +0200
+++ 
/work/SRC/openSUSE:Factory/.python-pip-tools.new.1548/python-pip-tools.changes  
    2022-06-16 18:22:24.244266990 +0200
@@ -1,0 +2,8 @@
+Thu Jun 16 05:46:18 UTC 2022 - Steve Kowalik <steven.kowa...@suse.com>
+
+- Update to 6.6.2:
+  * Fix support for pip>=22.1 (#1618).
+  * Update PyPIRepository::resolve_reqs() for pip>=22.1.1 (#1624).
+- Add ca-certificates to BuildRequires.
+
+-------------------------------------------------------------------

Old:
----
  pip-tools-6.6.0.tar.gz

New:
----
  pip-tools-6.6.2.tar.gz

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Other differences:
------------------
++++++ python-pip-tools.spec ++++++
--- /var/tmp/diff_new_pack.rLclvh/_old  2022-06-16 18:22:24.656267576 +0200
+++ /var/tmp/diff_new_pack.rLclvh/_new  2022-06-16 18:22:24.660267581 +0200
@@ -19,11 +19,10 @@
 %{?!python_module:%define python_module() python-%{**} python3-%{**}}
 %define skip_python2 1
 Name:           python-pip-tools
-Version:        6.6.0
+Version:        6.6.2
 Release:        0
 Summary:        Tool to keep pinned dependencies up to date
 License:        BSD-3-Clause
-Group:          Development/Languages/Python
 URL:            https://github.com/jazzband/pip-tools/
 Source:         
https://files.pythonhosted.org/packages/source/p/pip-tools/pip-tools-%{version}.tar.gz
 BuildRequires:  %{python_module setuptools_scm}
@@ -46,6 +45,7 @@
 BuildRequires:  %{python_module pytest}
 BuildRequires:  %{python_module six}
 BuildRequires:  %{python_module wheel}
+BuildRequires:  ca-certificates
 BuildRequires:  git-core
 # /SECTION
 %python_subpackages
@@ -73,7 +73,7 @@
 
 %check
 export LANG=en_US.UTF-8
-# https://github.com/jazzband/pip-tools/issues/1590
+# test_direct_reference_with_extras also requires network access
 %pytest -k 'not (network or test_direct_reference_with_extras)'
 
 %files %{python_files}

++++++ pip-tools-6.6.0.tar.gz -> pip-tools-6.6.2.tar.gz ++++++
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' 
'--exclude=.svnignore' old/pip-tools-6.6.0/CHANGELOG.md 
new/pip-tools-6.6.2/CHANGELOG.md
--- old/pip-tools-6.6.0/CHANGELOG.md    2022-04-06 09:33:46.000000000 +0200
+++ new/pip-tools-6.6.2/CHANGELOG.md    2022-05-23 22:06:51.000000000 +0200
@@ -1,3 +1,17 @@
+## 6.6.2 (2022-05-23)
+
+Bug Fixes:
+
+- Update `PyPIRepository::resolve_reqs()` for pip>=22.1.1
+  ([#1624](https://github.com/jazzband/pip-tools/pull/1624)). Thanks @m000
+
+## 6.6.1 (2022-05-13)
+
+Bug Fixes:
+
+- Fix support for pip>=22.1 
([#1618](https://github.com/jazzband/pip-tools/pull/1618)).
+  Thanks @wizpig64
+
 ## 6.6.0 (2022-04-06)
 
 Features:
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' 
'--exclude=.svnignore' old/pip-tools-6.6.0/PKG-INFO new/pip-tools-6.6.2/PKG-INFO
--- old/pip-tools-6.6.0/PKG-INFO        2022-04-06 09:34:00.712910700 +0200
+++ new/pip-tools-6.6.2/PKG-INFO        2022-05-23 22:07:08.524079000 +0200
@@ -1,12 +1,11 @@
 Metadata-Version: 2.1
 Name: pip-tools
-Version: 6.6.0
+Version: 6.6.2
 Summary: pip-tools keeps your pinned dependencies fresh.
 Home-page: https://github.com/jazzband/pip-tools/
 Author: Vincent Driessen
 Author-email: m...@nvie.com
 License: BSD 3 Clause
-Platform: UNKNOWN
 Classifier: Development Status :: 5 - Production/Stable
 Classifier: Intended Audience :: Developers
 Classifier: Intended Audience :: System Administrators
@@ -256,7 +255,7 @@
 
 .. code-block:: bash
 
-    $ pip-compile requirements.in --pip-args '--retries 10 --timeout 30'
+    $ pip-compile requirements.in --pip-args "--retries 10 --timeout 30"
 
 Configuration
 -------------
@@ -468,7 +467,7 @@
 
 .. code-block:: bash
 
-    $ pip-sync requirements.txt --pip-args '--no-cache-dir --no-deps'
+    $ pip-sync requirements.txt --pip-args "--no-cache-dir --no-deps"
 
 **Note**: ``pip-sync`` will not upgrade or uninstall packaging tools like
 ``setuptools``, ``pip``, or ``pip-tools`` itself. Use ``python -m pip install 
--upgrade``
@@ -481,7 +480,7 @@
 then yes, you should commit both ``requirements.in`` and ``requirements.txt`` 
to source control.
 
 Note that if you are deploying on multiple Python environments (read the 
section below),
-then you must commit a seperate output file for each Python environment.
+then you must commit a separate output file for each Python environment.
 We suggest to use the ``{env}-requirements.txt`` format
 (ex: ``win32-py3.7-requirements.txt``, ``macos-py3.10-requirements.txt``, 
etc.).
 
@@ -560,5 +559,3 @@
 +---------------+----------------+----------------+
 | 6.5.0+        | 21.2+          | 3.7 - 3.10     |
 +---------------+----------------+----------------+
-
-
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' 
'--exclude=.svnignore' old/pip-tools-6.6.0/README.rst 
new/pip-tools-6.6.2/README.rst
--- old/pip-tools-6.6.0/README.rst      2022-04-06 09:33:46.000000000 +0200
+++ new/pip-tools-6.6.2/README.rst      2022-05-23 22:06:51.000000000 +0200
@@ -227,7 +227,7 @@
 
 .. code-block:: bash
 
-    $ pip-compile requirements.in --pip-args '--retries 10 --timeout 30'
+    $ pip-compile requirements.in --pip-args "--retries 10 --timeout 30"
 
 Configuration
 -------------
@@ -439,7 +439,7 @@
 
 .. code-block:: bash
 
-    $ pip-sync requirements.txt --pip-args '--no-cache-dir --no-deps'
+    $ pip-sync requirements.txt --pip-args "--no-cache-dir --no-deps"
 
 **Note**: ``pip-sync`` will not upgrade or uninstall packaging tools like
 ``setuptools``, ``pip``, or ``pip-tools`` itself. Use ``python -m pip install 
--upgrade``
@@ -452,7 +452,7 @@
 then yes, you should commit both ``requirements.in`` and ``requirements.txt`` 
to source control.
 
 Note that if you are deploying on multiple Python environments (read the 
section below),
-then you must commit a seperate output file for each Python environment.
+then you must commit a separate output file for each Python environment.
 We suggest to use the ``{env}-requirements.txt`` format
 (ex: ``win32-py3.7-requirements.txt``, ``macos-py3.10-requirements.txt``, 
etc.).
 
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' 
'--exclude=.svnignore' old/pip-tools-6.6.0/pip_tools.egg-info/PKG-INFO 
new/pip-tools-6.6.2/pip_tools.egg-info/PKG-INFO
--- old/pip-tools-6.6.0/pip_tools.egg-info/PKG-INFO     2022-04-06 
09:33:59.000000000 +0200
+++ new/pip-tools-6.6.2/pip_tools.egg-info/PKG-INFO     2022-05-23 
22:07:07.000000000 +0200
@@ -1,12 +1,11 @@
 Metadata-Version: 2.1
 Name: pip-tools
-Version: 6.6.0
+Version: 6.6.2
 Summary: pip-tools keeps your pinned dependencies fresh.
 Home-page: https://github.com/jazzband/pip-tools/
 Author: Vincent Driessen
 Author-email: m...@nvie.com
 License: BSD 3 Clause
-Platform: UNKNOWN
 Classifier: Development Status :: 5 - Production/Stable
 Classifier: Intended Audience :: Developers
 Classifier: Intended Audience :: System Administrators
@@ -256,7 +255,7 @@
 
 .. code-block:: bash
 
-    $ pip-compile requirements.in --pip-args '--retries 10 --timeout 30'
+    $ pip-compile requirements.in --pip-args "--retries 10 --timeout 30"
 
 Configuration
 -------------
@@ -468,7 +467,7 @@
 
 .. code-block:: bash
 
-    $ pip-sync requirements.txt --pip-args '--no-cache-dir --no-deps'
+    $ pip-sync requirements.txt --pip-args "--no-cache-dir --no-deps"
 
 **Note**: ``pip-sync`` will not upgrade or uninstall packaging tools like
 ``setuptools``, ``pip``, or ``pip-tools`` itself. Use ``python -m pip install 
--upgrade``
@@ -481,7 +480,7 @@
 then yes, you should commit both ``requirements.in`` and ``requirements.txt`` 
to source control.
 
 Note that if you are deploying on multiple Python environments (read the 
section below),
-then you must commit a seperate output file for each Python environment.
+then you must commit a separate output file for each Python environment.
 We suggest to use the ``{env}-requirements.txt`` format
 (ex: ``win32-py3.7-requirements.txt``, ``macos-py3.10-requirements.txt``, 
etc.).
 
@@ -560,5 +559,3 @@
 +---------------+----------------+----------------+
 | 6.5.0+        | 21.2+          | 3.7 - 3.10     |
 +---------------+----------------+----------------+
-
-
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' 
'--exclude=.svnignore' old/pip-tools-6.6.0/piptools/repositories/pypi.py 
new/pip-tools-6.6.2/piptools/repositories/pypi.py
--- old/pip-tools-6.6.0/piptools/repositories/pypi.py   2022-04-06 
09:33:46.000000000 +0200
+++ new/pip-tools-6.6.2/piptools/repositories/pypi.py   2022-05-23 
22:06:51.000000000 +0200
@@ -20,7 +20,6 @@
 
 from click import progressbar
 from pip._internal.cache import WheelCache
-from pip._internal.cli.progress_bars import BAR_TYPES
 from pip._internal.commands import create_command
 from pip._internal.commands.install import InstallCommand
 from pip._internal.index.package_finder import PackageFinder
@@ -190,7 +189,12 @@
 
             reqset = RequirementSet()
             ireq.user_supplied = True
-            reqset.add_requirement(ireq)
+            if PIP_VERSION[:3] < (22, 1, 1):
+                reqset.add_requirement(ireq)
+            elif getattr(ireq, "name", None):
+                reqset.add_named_requirement(ireq)
+            else:
+                reqset.add_unnamed_requirement(ireq)
 
             resolver = self.command.make_resolver(
                 preparer=preparer,
@@ -473,6 +477,9 @@
             # refactored-out logging config.
             log.warning("Couldn't find a 'console' logging handler")
 
+        # This import will fail with pip 22.1, but here we're pip<22.0
+        from pip._internal.cli.progress_bars import BAR_TYPES
+
         # Sync pip's progress bars stream with LogContext.stream
         for bar_cls in itertools.chain(*BAR_TYPES.values()):
             bar_cls.file = log.stream

Reply via email to