app-backup/b2: bump to 2.5.0

Signed-off-by: Wolfgang E. Sanyer <ezzieyguywuf@gmail.com>

app-backup/b2/files/b2-2.1.0-nameclash.patch

@@ -1,12 +0,0 @@
-diff --git a/setup.py b/setup.py
-index fee3261..f90056b 100644
---- a/setup.py
-+++ b/setup.py
-@@ -140,6 +140,6 @@ setup(
-     # "scripts" keyword. Entry points provide cross-platform support and allow
-     # pip to create the appropriate form of executable for the target platform.
-     entry_points={
--        'console_scripts': ['b2=b2.console_tool:main',],
-+        'console_scripts': ['backblaze2=b2.console_tool:main',],
-     },
- )

app-backup/b2/files/b2-2.5.0-disable-pip-requirement-installs.patch

@@ -0,0 +1,23 @@
+# These configurations attempt to install missing dependencies using pip, which
+# violates the network sandbox. Instead, we'll manage the dependencies in
+# portage.
+--- a/setup.py
++++ b/setup.py
+@@ -103,7 +103,7 @@ setup(
+     # requirements files see:
+     # https://packaging.python.org/en/latest/requirements.html
+     dependency_links=[],
+-    install_requires=requirements,
++    # install_requires=requirements,
+ 
+     # List additional groups of dependencies here (e.g. development
+     # dependencies). You can install these using the following syntax,
+@@ -116,7 +116,7 @@ setup(
+                 'sphinxcontrib-plantuml', 'sadisplay'
+             ],
+     },
+-    setup_requires=['setuptools_scm<6.0'],  # setuptools_scm>=6.0 doesn't support Python 3.5
++    # setup_requires=['setuptools_scm<6.0'],  # setuptools_scm>=6.0 doesn't support Python 3.5
+     use_scm_version=True,
+ 
+     # If there are data files included in your packages that need to be

app-backup/b2/files/b2-2.5.0-nameclash.patch

@@ -0,0 +1,14 @@
+# boost installs an executable named b2, which clashes with the default name for
+# this package. This package changes the executable name to avoid this clash.
+diff --git a/setup.py b/setup.py
+index f9c1bbe..76ca28f 100644
+--- a/setup.py
++++ b/setup.py
+@@ -135,6 +135,6 @@ setup(
+     # "scripts" keyword. Entry points provide cross-platform support and allow
+     # pip to create the appropriate form of executable for the target platform.
+     entry_points={
+-        'console_scripts': ['b2=b2.console_tool:main'],
++        'console_scripts': ['backblaze2=b2.console_tool:main'],
+     },
+ )