Hello community,

here is the log from the commit of package python-dbf for openSUSE:Factory 
checked in at 2018-06-02 12:04:47
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/python-dbf (Old)
 and      /work/SRC/openSUSE:Factory/.python-dbf.new (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "python-dbf"

Sat Jun  2 12:04:47 2018 rev:1 rq:612073 version:0.97.5

Changes:
--------
New Changes file:

--- /dev/null   2018-05-30 11:41:29.140556178 +0200
+++ /work/SRC/openSUSE:Factory/.python-dbf.new/python-dbf.changes       
2018-06-02 12:04:54.191933306 +0200
@@ -0,0 +1,49 @@
+-------------------------------------------------------------------
+Thu May 24 17:31:07 UTC 2018 - toddrme2...@gmail.com
+
+- Update to 0.97.5
+  * Fix bug in VFP doubles
+  * Fix field creation flag handling
+  * Allow (redundant) "binary" flag on binary type fields
+  * Fix fp/FoxBase table header creation
+  * Can now open dbf files as read-only when lacking write permissions.
+  * Moved to a single 2/3 code base.
+  * Opening a database now defaults to dbf.READ_ONLY; can also use 
dbf.READ_WRITE;
+    the corresponding strings are no longer supported.
+- Spec file cleanups
+- License is now included in source archive
+
+-------------------------------------------------------------------
+Wed Jul 26 08:53:07 UTC 2017 - br...@ioda-net.ch
+
+-specfile add line to fix build for Leap 
+
+-------------------------------------------------------------------
+Wed Jun  7 12:07:29 UTC 2017 - br...@ioda-net.ch
+
+- specfile move to unified single-spec-python
+
+-------------------------------------------------------------------
+Sat Jul 23 18:07:35 UTC 2016 - a...@gmx.de
+
+- specfile:
+  * update copyright year
+  * no more README or WHATSNEW in tar-ball
+
+- update to version 0.96.8:
+  (no changelog available)
+
+-------------------------------------------------------------------
+Sun May  8 07:14:51 UTC 2016 - a...@gmx.de
+
+- specfile:
+  * changed to https for source url
+  * updated source url to files.pythonhosted.org
+
+-------------------------------------------------------------------
+Thu Nov 19 16:36:34 UTC 2015 - br...@ioda-net.ch
+
+- Initial packaging on obs
+  * Including from upstream missing LICENSE file
+  * Fix eol by sed 
+

New:
----
  LICENSE
  dbf-0.97.5.tar.gz
  python-dbf.changes
  python-dbf.spec

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

Other differences:
------------------
++++++ python-dbf.spec ++++++
#
# spec file for package python-dbf
#
# Copyright (c) 2018 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
# upon. The license for this file, and modifications and additions to the
# file, is the same license as for the pristine package itself (unless the
# license for the pristine package is not an Open Source License, in which
# case the license is the MIT License). An "Open Source License" is a
# license that conforms to the Open Source Definition (Version 1.9)
# published by the Open Source Initiative.

# Please submit bugfixes or comments via http://bugs.opensuse.org/
#


%{?!python_module:%define python_module() python-%{**} python3-%{**}}
Name:           python-dbf
Version:        0.97.5
Release:        0
Summary:        Pure python package for reading/writing dBase, FoxPro, and 
Visual FoxPro .dbf
License:        BSD-3-Clause
Group:          Development/Languages/Python
Url:            https://bitbucket.org/stoneleaf/dbf/src/default/
Source:         
https://files.pythonhosted.org/packages/source/d/dbf/dbf-%{version}.tar.gz
Source10:       https://bitbucket.org/stoneleaf/dbf/raw/%{version}/dbf/LICENSE
BuildRequires:  %{python_module devel}
BuildRequires:  %{python_module setuptools}
BuildRequires:  fdupes
BuildRequires:  python-rpm-macros
BuildArch:      noarch

%python_subpackages

%description
Pure python package for reading/writing dBase, FoxPro, and Visual FoxPro .dbf
files (including memos)

Currently supports dBase III, Clipper, FoxPro, and Visual FoxPro tables. Text is
returned as unicode, and codepage settings in tables are honored. Memos and Null
fields are supported.

%prep
%setup -q -n dbf-%{version}
cp %{SOURCE10} .

%build
%python_build

%install
%python_install
%fdupes %{buildroot}%{_prefix}

%files %{python_files}
%defattr(-,root,root,-)
%license LICENSE
%{python_sitelib}/dbf-%{version}-py*.egg-info
%{python_sitelib}/dbf

%changelog
++++++ LICENSE ++++++
Copyright (c) 2008-2018 Ethan Furman
All rights reserved.

Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions
are met:

    Redistributions of source code must retain the above
    copyright notice, this list of conditions and the
    following disclaimer.

    Redistributions in binary form must reproduce the above
    copyright notice, this list of conditions and the following
    disclaimer in the documentation and/or other materials
    provided with the distribution.

    Neither the name Ethan Furman nor the names of any
    contributors may be used to endorse or promote products
    derived from this software without specific prior written
    permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE
LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
POSSIBILITY OF SUCH DAMAGE.

Reply via email to