Hello community,

here is the log from the commit of package python-twine for openSUSE:Factory 
checked in at 2017-08-04 11:58:41
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/python-twine (Old)
 and      /work/SRC/openSUSE:Factory/.python-twine.new (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "python-twine"

Fri Aug  4 11:58:41 2017 rev:2 rq:508798 version:1.9.1

Changes:
--------
--- /work/SRC/openSUSE:Factory/python-twine/python-twine.changes        
2017-02-06 15:03:33.392221271 +0100
+++ /work/SRC/openSUSE:Factory/.python-twine.new/python-twine.changes   
2017-08-04 11:58:48.236506707 +0200
@@ -1,0 +2,17 @@
+Thu Jul  6 13:02:30 UTC 2017 - [email protected]
+
+- fix source url
+
+-------------------------------------------------------------------
+Wed Jul  5 18:50:28 UTC 2017 - [email protected]
+
+- update to version 1.9.1
+- update specfile to singlespec
+
+-------------------------------------------------------------------
+Wed Jan 18 11:48:32 UTC 2017 - [email protected]
+
+- Update to version 1.8.1
+- requires python-requests-toolbelt>=0.4.0
+
+-------------------------------------------------------------------

Old:
----
  twine-1.6.1.tar.gz

New:
----
  twine-1.9.1.tar.gz

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

Other differences:
------------------
++++++ python-twine.spec ++++++
--- /var/tmp/diff_new_pack.sjmHda/_old  2017-08-04 11:58:50.396201872 +0200
+++ /var/tmp/diff_new_pack.sjmHda/_new  2017-08-04 11:58:50.416199050 +0200
@@ -1,7 +1,7 @@
 #
 # spec file for package python-twine
 #
-# Copyright (c) 2015 SUSE LINUX Products GmbH, Nuernberg, Germany.
+# Copyright (c) 2017 SUSE LINUX GmbH, Nuernberg, Germany.
 #
 # All modifications and additions to the file contributed by third parties
 # remain the property of their copyright owners, unless otherwise agreed
@@ -16,92 +16,61 @@
 #
 
 
+%{?!python_module:%define python_module() python-%{**} python3-%{**}}
 Name:           python-twine
-Version:        1.6.1
+Version:        1.9.1
 Release:        0
 Summary:        Collection of utilities for interacting with PyPI
 License:        Apache-2.0
 Group:          Development/Languages/Python
-Url:            https://github.com/dstufft/twine
-Source:         
https://pypi.python.org/packages/source/t/twine/twine-%{version}.tar.gz
-BuildRequires:  python-devel
-BuildRequires:  python-setuptools
+Url:            https://github.com/pypa/twine
+Source:         
https://files.pythonhosted.org/packages/source/t/twine/twine-%{version}.tar.gz
+BuildRequires:  %{python_module setuptools >= 0.7.0}
+BuildRequires:  python-rpm-macros
 Requires(post): update-alternatives
 Requires(postun): update-alternatives
-Requires:       python-pkginfo
-Requires:       python-requests
-BuildRoot:      %{_tmppath}/%{name}-%{version}-build
-%if 0%{?suse_version} && 0%{?suse_version} <= 1110
-Requires:       python-argparse
-%{!?python_sitelib: %global python_sitelib %(python -c "from 
distutils.sysconfig import get_python_lib; print get_python_lib()")}
-%else
-BuildArch:      noarch
+Requires:       python-pkginfo >= 1.0
+Requires:       python-requests-toolbelt >= 0.8.0
+Requires:       python-tqdm >= 4.11
+Recommends:     python-keyring
+%if 0%{suse_version} <= 1320
+Recommends:     python-pyblake2
 %endif
+BuildRoot:      %{_tmppath}/%{name}-%{version}-build
+
+%python_subpackages
 
 %description
 Twine is a utility for interacting with PyPI.
 
-Currently it only supports uploading distributions.
-
-
-Why Should I Use This?
-----------------------
-
-The biggest reason to use twine is that python setup.py upload uploads
-files over plaintext. This means anytime you use it you expose your username
-and password to a MITM attack. Twine uses only verified TLS to upload to PyPI
-protecting your credentials from theft.
-
-Secondly it allows you to precreate your distribution files.
-python setup.py upload only allows you to upload something that you've
-created in the same command invocation. This means that you cannot test the
-exact file you're going to upload to PyPI to ensure that it works before
-uploading it.
-
-Finally it allows you to pre-sign your files and pass the .asc files into
-the command line invocation
-(twine upload twine-1.0.1.tar.gz twine-1.0.1.tar.gz.asc). This enables you
-to be assured that you're typing your gpg passphrase into gpg itself and not
-anything else since *you* will be the one directly executing
-gpg --detach-sign -a <filename>.
-
-
-Features
---------
-
-* Verified HTTPS Connections
-* Uploading doesn't require executing setup.py
-* Uploading files that have already been created, allowing testing of
-  distributions before release
+Currently it only supports registering projects and uploading distributions.
 
 %prep
 %setup -q -n twine-%{version}
+sed -i '1s/^#!.*//' twine/__main__.py
 
 %build
-python setup.py build
+%python_build
 
 %install
-python setup.py install --prefix=%{_prefix} --root=%{buildroot}
-mv %{buildroot}%{_bindir}/twine %{buildroot}%{_bindir}/twine-%{py_ver}
-mkdir -p %{buildroot}%{_sysconfdir}/alternatives
-touch %{buildroot}%{_sysconfdir}/alternatives/twine
-ln -s -f %{_sysconfdir}/alternatives/twine %{buildroot}%{_bindir}/twine
+%python_install
+%python_clone -a %{buildroot}%{_bindir}/twine
 
 %post
-%_sbindir/update-alternatives \
-   --install %{_bindir}/twine twine %{_bindir}/twine-%{py_ver} 30
+%python_install_alternative twine
    
 %postun
-if [ $1 -eq 0 ] ; then
-    %_sbindir/update-alternatives --remove twine %{_bindir}/twine-%{py_ver}
-fi
+%python_uninstall_alternative twine
 
-%files
+%files %{python_files}
 %defattr(-,root,root,-)
-%doc AUTHORS LICENSE README.rst
-%{_bindir}/twine
-%{_bindir}/twine-%{py_ver}
+%doc AUTHORS README.rst
+%if 0%{?leap_version} >= 420200 || 0%{?suse_version} > 1320
+%license LICENSE
+%else
+%doc LICENSE
+%endif
 %{python_sitelib}/*
-%ghost %{_sysconfdir}/alternatives/twine
+%python_alternative %{_bindir}/twine
 
 %changelog

++++++ twine-1.6.1.tar.gz -> twine-1.9.1.tar.gz ++++++
++++ 2188 lines of diff (skipped)


Reply via email to