Script 'mail_helper' called by obssrc
Hello community,

here is the log from the commit of package go1.18 for openSUSE:Factory checked 
in at 2022-11-02 12:46:27
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/go1.18 (Old)
 and      /work/SRC/openSUSE:Factory/.go1.18.new.2275 (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "go1.18"

Wed Nov  2 12:46:27 2022 rev:17 rq:1032743 version:1.18.8

Changes:
--------
--- /work/SRC/openSUSE:Factory/go1.18/go1.18.changes    2022-10-10 
18:44:12.714823373 +0200
+++ /work/SRC/openSUSE:Factory/.go1.18.new.2275/go1.18.changes  2022-11-02 
12:46:42.549436344 +0100
@@ -1,0 +2,11 @@
+Tue Nov  1 17:18:30 UTC 2022 - Jeff Kowalczyk <jkowalc...@suse.com>
+
+- go1.18.8 (released 2022-11-01) includes security fixes to the
+  os/exec and syscall packages, as well as bug fixes to the
+  runtime.
+  Refs boo#1193742 go1.18 release tracking
+  CVE-2022-41716
+  * go#56327 boo#1204941 security: fix CVE-2022-41716 syscall, os/exec: 
unsanitized NUL in environment variables
+  * go#56308 runtime: "runtime??lock: lock count" fatal error when cgo is 
enabled
+
+-------------------------------------------------------------------

Old:
----
  go1.18.7.src.tar.gz

New:
----
  go1.18.8.src.tar.gz

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

Other differences:
------------------
++++++ go1.18.spec ++++++
--- /var/tmp/diff_new_pack.9n6ZA7/_old  2022-11-02 12:46:45.289450252 +0100
+++ /var/tmp/diff_new_pack.9n6ZA7/_new  2022-11-02 12:46:45.293450273 +0100
@@ -134,7 +134,7 @@
 %endif
 
 Name:           go1.18
-Version:        1.18.7
+Version:        1.18.8
 Release:        0
 Summary:        A compiled, garbage-collected, concurrent programming language
 License:        BSD-3-Clause

++++++ go1.18.7.src.tar.gz -> go1.18.8.src.tar.gz ++++++
/work/SRC/openSUSE:Factory/go1.18/go1.18.7.src.tar.gz 
/work/SRC/openSUSE:Factory/.go1.18.new.2275/go1.18.8.src.tar.gz differ: char 
153, line 1

Reply via email to