Hello community,

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

Package is "honggfuzz"

Changes:
--------
--- /work/SRC/openSUSE:Factory/honggfuzz/honggfuzz.changes      2017-02-06 
15:04:23.193064223 +0100
+++ /work/SRC/openSUSE:Factory/.honggfuzz.new/honggfuzz.changes 2017-02-07 
12:07:55.227821695 +0100
@@ -1,0 +2,5 @@
+Sun Feb  5 01:09:52 UTC 2017 - [email protected]
+
+- Update description
+
+-------------------------------------------------------------------

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

Other differences:
------------------
++++++ honggfuzz.spec ++++++
--- /var/tmp/diff_new_pack.p9zc5V/_old  2017-02-07 12:07:55.567773596 +0100
+++ /var/tmp/diff_new_pack.p9zc5V/_new  2017-02-07 12:07:55.567773596 +0100
@@ -1,5 +1,5 @@
 #
-# spec file for package hongfuzx
+# spec file for package honggfuzz
 #
 # Copyright (c) 2017 SUSE LINUX GmbH, Nuernberg, Germany.
 #
@@ -19,7 +19,7 @@
 Version:        0.8
 Release:        0
 License:        Apache-2.0
-Summary:        Security oriented fuzzer with powerful analysis options
+Summary:        Security-oriented fuzzer with various analysis options
 Url:            https://google.github.io/honggfuzz/
 Group:          Development/Tools/Other
 Source:         
https://github.com/google/honggfuzz/archive/%{version}.tar.gz#/%{name}-%{version}.tar.gz
@@ -28,8 +28,9 @@
 BuildRequires:  zlib-devel
 
 %description
-Security oriented fuzzer with powerful analysis options. Supports
-evolutionary, feedback-driven fuzzing based on code coverage (sw and hw).
+Security-oriented fuzzer with powerful analysis options. Supports
+evolutionary, feedback-driven fuzzing based on code coverage
+(software and hardware).
 
 %prep
 %setup -q


Reply via email to