Hello community,

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

Package is "python-TermRecord"

Sat Jun  2 12:07:06 2018 rev:1 rq:612082 version:1.2.5

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

--- /dev/null   2018-05-30 11:41:29.140556178 +0200
+++ /work/SRC/openSUSE:Factory/.python-TermRecord.new/python-TermRecord.changes 
2018-06-02 12:07:16.766704327 +0200
@@ -0,0 +1,14 @@
+-------------------------------------------------------------------
+Thu May 24 17:50:13 UTC 2018 - toddrme2...@gmail.com
+
+- Update to 1.2.5
+  * make sure we include LICENSE files when packaging
+  * Adding optional named tempfiles
+- spec file cleanups
+
+-------------------------------------------------------------------
+Wed May  3 01:55:24 UTC 2017 - ralf.dann...@suse.com
+
+- initial package submission
+- new Version 1.2.4
+

New:
----
  TermRecord-1.2.5.tar.gz
  python-TermRecord.changes
  python-TermRecord.spec

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

Other differences:
------------------
++++++ python-TermRecord.spec ++++++
#
# spec file for package python-TermRecord
#
# 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-TermRecord
Version:        1.2.5
Release:        0
License:        MIT
Summary:        A simple terminal session recorder with easy-to-share HTML 
output!
Url:            http://github.com/theonewolf/TermRecord
Group:          Development/Languages/Python
Source:         
https://pypi.python.org/packages/source/T/TermRecord/TermRecord-%{version}.tar.gz
BuildRequires:  %{python_module devel}
BuildRequires:  %{python_module setuptools}
BuildRequires:  fdupes
BuildRequires:  python-rpm-macros
# SECTION test requirements
BuildRequires:  %{python_module Jinja2 >= 2.6}
# /SECTION
Requires:       python-Jinja2 >= 2.6
BuildArch:      noarch
Requires(post):   update-alternatives
Requires(postun):  update-alternatives

%python_subpackages

%description
TermRecord is a program that wraps the ``script`` command.  It automagically
detects your terminal size, records your session, and stores the output as
either JSON, embeddable JavaScript, or a static HTML file.  The HTML is
completely self-contained, embedding all necessary dependencies in one file
and can be shipped to anyone that has a modern browser.  It even embeds a
font!

You can store these files as your own notes, email them to collaborators,
use them as instructional examples, or whatever you want!  Because they are
self-contained there are no third-party middlemen involved, you are free to
share and keep them forever---they will never go away!
Development <https://github.com/theonewolf/TermRecord>

%prep
%setup -q -n TermRecord-%{version}

%build
%python_build

%install
%python_install
%python_expand %fdupes %{buildroot}%{$python_sitelib}
%python_clone -a %{buildroot}%{_bindir}/TermRecord

%post
%python_install_alternative TermRecord

%postun
%python_uninstall_alternative TermRecord

%files %{python_files}
%license LICENSE
%python_alternative %{_bindir}/TermRecord
%{python_sitelib}/*

%changelog


Reply via email to