Hello community,

here is the log from the commit of package modsecurity for openSUSE:Factory 
checked in at 2018-07-17 09:42:58
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/modsecurity (Old)
 and      /work/SRC/openSUSE:Factory/.modsecurity.new (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "modsecurity"

Tue Jul 17 09:42:58 2018 rev:2 rq:623120 version:3.0.0

Changes:
--------
--- /work/SRC/openSUSE:Factory/modsecurity/modsecurity.changes  2018-07-10 
16:15:44.953506625 +0200
+++ /work/SRC/openSUSE:Factory/.modsecurity.new/modsecurity.changes     
2018-07-17 09:43:54.980956049 +0200
@@ -1,0 +2,5 @@
+Sat Jul 14 09:58:58 UTC 2018 - [email protected]
+
+- Remove rhetoric part from descriptions.
+
+-------------------------------------------------------------------

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

Other differences:
------------------
++++++ modsecurity.spec ++++++
--- /var/tmp/diff_new_pack.Uittkm/_old  2018-07-17 09:43:55.476954232 +0200
+++ /var/tmp/diff_new_pack.Uittkm/_new  2018-07-17 09:43:55.476954232 +0200
@@ -15,12 +15,13 @@
 # Please submit bugfixes or comments via http://bugs.opensuse.org/
 #
 
+
 Name:           modsecurity
 Version:        3.0.0
 Release:        0
-Summary:        Open source, cross platform web application firewall (WAF) 
engine
-Group:          Productivity/Networking/Security
+Summary:        Web application firewall engine
 License:        BSD-2-Clause
+Group:          Productivity/Networking/Security
 Url:            https://www.modsecurity.org/
 Source:         
https://github.com/SpiderLabs/ModSecurity/releases/download/v%{version}/modsecurity-v%{version}.tar.gz
 BuildRequires:  automake
@@ -35,46 +36,25 @@
 BuildRequires:  pkgconfig
 
 %description
-
 ModSecurity is a toolkit for real-time web application monitoring, logging, and
-access control. I like to think about it as an enabler: there are no hard rules
-telling you what to do; instead, it is up to you to choose your own path 
through
-the available features.
-
-The freedom to choose what to do is an essential part of ModSecurity\'s 
identity
-and goes very well with its open source nature. With full access to the source
-code, your freedom to choose extends to the ability to customize and extend the
-tool itself to make it fit your needs. It\'s not a matter of ideology, but of
-practicality. I simply don\'t want my tools to restrict what I can do.
+access control.
 
 %package -n libmodsecurity3
-Summary:        Open source, cross platform web application firewall (WAF) 
engine
+Summary:        Web application firewall engine
 Group:          System/Libraries
 
 %description -n libmodsecurity3
-
 ModSecurity is a toolkit for real-time web application monitoring, logging, and
-access control. I like to think about it as an enabler: there are no hard rules
-telling you what to do; instead, it is up to you to choose your own path 
through
-the available features.
-
-The freedom to choose what to do is an essential part of ModSecurity\'s 
identity
-and goes very well with its open source nature. With full access to the source
-code, your freedom to choose extends to the ability to customize and extend the
-tool itself to make it fit your needs. It\'s not a matter of ideology, but of
-practicality. I simply don\'t want my tools to restrict what I can do.
+access control.
 
 %package devel
-Summary:        Development diles for modsecurity, web application firewall 
(WAF) engine
+Summary:        Development files for modsecurity, a web application firewall 
engine
 Group:          Development/Languages/C and C++
 Requires:       libmodsecurity3 = %{version}
 
 %description devel
-
 ModSecurity is a toolkit for real-time web application monitoring, logging, and
-access control. I like to think about it as an enabler: there are no hard rules
-telling you what to do; instead, it is up to you to choose your own path 
through
-the available features.
+access control.
 
 This subpackage holds the development headers for the library.
 


Reply via email to