Script 'mail_helper' called by obssrc
Hello community,

here is the log from the commit of package yast2-hardware-detection for 
openSUSE:Factory checked in at 2021-03-05 13:42:50
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/yast2-hardware-detection (Old)
 and      /work/SRC/openSUSE:Factory/.yast2-hardware-detection.new.2378 (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "yast2-hardware-detection"

Fri Mar  5 13:42:50 2021 rev:45 rq:876036 version:4.1.2

Changes:
--------
--- 
/work/SRC/openSUSE:Factory/yast2-hardware-detection/yast2-hardware-detection.changes
        2019-09-07 11:24:57.710498822 +0200
+++ 
/work/SRC/openSUSE:Factory/.yast2-hardware-detection.new.2378/yast2-hardware-detection.changes
      2021-03-05 13:42:52.399491133 +0100
@@ -1,0 +2,6 @@
+Mon Mar  1 16:47:31 UTC 2021 - Stefan Hundhammer <shundham...@suse.com>
+
+- Fixed pointer check to compile with GCC 11 (bsc#1181916)
+- 4.1.2
+
+-------------------------------------------------------------------

Old:
----
  yast2-hardware-detection-4.1.1.tar.bz2

New:
----
  yast2-hardware-detection-4.1.2.tar.bz2

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

Other differences:
------------------
++++++ yast2-hardware-detection.spec ++++++
--- /var/tmp/diff_new_pack.6KQS0b/_old  2021-03-05 13:42:52.947491631 +0100
+++ /var/tmp/diff_new_pack.6KQS0b/_new  2021-03-05 13:42:52.951491635 +0100
@@ -1,7 +1,7 @@
 #
 # spec file for package yast2-hardware-detection
 #
-# Copyright (c) 2019 SUSE LINUX GmbH, Nuernberg, Germany.
+# Copyright (c) 2021 SUSE LLC
 #
 # All modifications and additions to the file contributed by third parties
 # remain the property of their copyright owners, unless otherwise agreed
@@ -12,12 +12,12 @@
 # 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/
+# Please submit bugfixes or comments via https://bugs.opensuse.org/
 #
 
 
 Name:           yast2-hardware-detection
-Version:        4.1.1
+Version:        4.1.2
 Release:        0
 
 BuildRoot:      %{_tmppath}/%{name}-%{version}-build

++++++ yast2-hardware-detection-4.1.1.tar.bz2 -> 
yast2-hardware-detection-4.1.2.tar.bz2 ++++++
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' 
'--exclude=.svnignore' 
old/yast2-hardware-detection-4.1.1/.github/workflows/ci.yml 
new/yast2-hardware-detection-4.1.2/.github/workflows/ci.yml
--- old/yast2-hardware-detection-4.1.1/.github/workflows/ci.yml 1970-01-01 
01:00:00.000000000 +0100
+++ new/yast2-hardware-detection-4.1.2/.github/workflows/ci.yml 2021-03-01 
18:09:22.000000000 +0100
@@ -0,0 +1,23 @@
+
+# See 
https://docs.github.com/en/actions/reference/workflow-syntax-for-github-actions
+
+name: CI
+
+on: [push, pull_request]
+
+jobs:
+  Package:
+    runs-on: ubuntu-latest
+    container: registry.opensuse.org/yast/head/containers/yast-cpp:latest
+
+    steps:
+
+    - name: Git Checkout
+      uses: actions/checkout@v1
+
+    # just for easier debugging...
+    - name: Inspect Installed Packages
+      run: rpm -qa | sort
+
+    - name: Package Build
+      run:  yast-ci-cpp
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' 
'--exclude=.svnignore' old/yast2-hardware-detection-4.1.1/.travis.yml 
new/yast2-hardware-detection-4.1.2/.travis.yml
--- old/yast2-hardware-detection-4.1.1/.travis.yml      2019-08-27 
13:21:41.000000000 +0200
+++ new/yast2-hardware-detection-4.1.2/.travis.yml      1970-01-01 
01:00:00.000000000 +0100
@@ -1,11 +0,0 @@
-sudo: required
-language: bash
-services:
-  - docker
-
-before_install:
-  - docker build -t yast-hardware-detection-image .
-script:
-  # the "yast-travis-cpp" script is included in the base yastdevel/cpp image
-  # see https://github.com/yast/docker-yast-cpp/blob/master/yast-travis-cpp
-  - docker run -it yast-hardware-detection-image yast-travis-cpp
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' 
'--exclude=.svnignore' old/yast2-hardware-detection-4.1.1/CONTRIBUTING.md 
new/yast2-hardware-detection-4.1.2/CONTRIBUTING.md
--- old/yast2-hardware-detection-4.1.1/CONTRIBUTING.md  2019-08-27 
13:21:41.000000000 +0200
+++ new/yast2-hardware-detection-4.1.2/CONTRIBUTING.md  1970-01-01 
01:00:00.000000000 +0100
@@ -1,89 +0,0 @@
-YaST Contribution Guidelines
-============================
-
-YaST is an open source project and as such it welcomes all kinds of
-contributions. If you decide to contribute, please follow these guidelines to
-ensure the process is effective and pleasant both for you and the YaST 
maintainers.
-
-There are two main forms of contribution: reporting bugs and performing code
-changes.
-
-Bug Reports
------------
-
-If you find a problem, please report it either using
-[Bugzilla](https://bugzilla.suse.com/enter_bug.cgi?format=guided&product=openSUSE+Factory&component=YaST2)
-or [GitHub issues](../../issues). (For Bugzilla, use the [simplified
-registration](https://secure-www.novell.com/selfreg/jsp/createSimpleAccount.jsp)
-if you don't have an account yet.)
-
-When creating a bug report, please follow our [bug reporting
-guidelines](http://en.opensuse.org/openSUSE:Report_a_YaST_bug).
-
-We can't guarantee that every bug will be fixed, but we'll try.
-
-Code Changes
-------------
-
-We welcome all kinds of code contributions, from simple bug fixes to 
significant
-refactorings and implementation of new features. However, before making any
-non-trivial contribution, get in touch with us first ??? this can prevent 
wasted
-effort on both sides. Also, have a look at our [development
-documentation](http://en.opensuse.org/openSUSE:YaST_development).
-
-To send us your code change, use GitHub pull requests. The workflow is as
-follows:
-
-  1. Fork the project.
-
-  2. Create a topic branch based on `master`.
-
-  3. Implement your change, including tests (if possible). Make sure you adhere
-     to the [Ruby style
-     guide](https://github.com/SUSE/style-guides/blob/master/Ruby.md).
-
-  4. Update the package version (in `packages/*.spec`, usually by
-     `rake version:bump`) and add a new entry to the `package/*.changes` file
-     (by `osc vc package`).  
-     For bigger changes or changes which need longer discussion it is advised 
to
-     add this as a separate last commit so it can be easily updated when 
another
-     change is merged in the meantime.
-
-  5. Make sure your change didn't break anything by building the RPM package
-     (`rake osc:build`). The build process includes running the full testsuite.
-
-  6. Publish the branch and create a pull request.
-
-  7. YaST developers will review your change and possibly point out issues.
-     Adapt the code under their guidance until they are all resolved.
-
-  8. Finally, the pull request will get merged or rejected.
-
-See also [GitHub's guide on
-contributing](https://help.github.com/articles/fork-a-repo).
-
-If you want to do multiple unrelated changes, use separate branches and pull
-requests.
-
-### Commits
-
-Each commit in the pull request should do only one thing, which is clearly
-described by its commit message. Especially avoid mixing formatting changes and
-functional changes into one commit. When writing commit messages, adhere to
-[widely used
-conventions](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html).
-
-If your commit is related to a bug in Bugzilla or an issue on GitHub, make sure
-you mention it in the commit message for cross-reference. Use format like
-bnc#775814 or gh#yast/yast-foo#42. See also [GitHub
-autolinking](https://help.github.com/articles/github-flavored-markdown#references)
-and [openSUSE abbreviation
-reference](http://en.opensuse.org/openSUSE:Packaging_Patches_guidelines#Current_set_of_abbreviations).
-
-Additional Information
-----------------------
-
-If you have any question, feel free to ask at the [development mailing
-list](http://lists.opensuse.org/yast-devel/) or at the
-[#yast](http://webchat.freenode.net/?channels=%23yast) IRC channel on freenode.
-We'll do our best to provide a timely and accurate answer.
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' 
'--exclude=.svnignore' old/yast2-hardware-detection-4.1.1/Dockerfile 
new/yast2-hardware-detection-4.1.2/Dockerfile
--- old/yast2-hardware-detection-4.1.1/Dockerfile       2019-08-27 
13:21:41.000000000 +0200
+++ new/yast2-hardware-detection-4.1.2/Dockerfile       1970-01-01 
01:00:00.000000000 +0100
@@ -1,3 +0,0 @@
-FROM registry.opensuse.org/yast/head/containers/yast-cpp:latest
-COPY . /usr/src/app
-
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' 
'--exclude=.svnignore' old/yast2-hardware-detection-4.1.1/README.md 
new/yast2-hardware-detection-4.1.2/README.md
--- old/yast2-hardware-detection-4.1.1/README.md        2019-08-27 
13:21:41.000000000 +0200
+++ new/yast2-hardware-detection-4.1.2/README.md        2021-03-01 
18:09:22.000000000 +0100
@@ -1,7 +1,9 @@
 ## Yast Hardware Detection Agent
 
-Travis:  [![Build 
Status](https://travis-ci.org/yast/yast-hardware-detection.svg?branch=master)](https://travis-ci.org/yast/yast-hardware-detection)
-Jenkins: [![Jenkins 
Build](http://img.shields.io/jenkins/s/https/ci.opensuse.org/yast-hardware-detection-master.svg)](https://ci.opensuse.org/view/Yast/job/yast-hardware-detection-master/)
+[![Workflow 
Status](https://github.com/yast/yast-hardware-detection/workflows/CI/badge.svg?branch=master)](
+https://github.com/yast/yast-hardware-detection/actions?query=branch%3Amaster)
+[![Jenkins 
Status](https://ci.opensuse.org/buildStatus/icon?job=yast-yast-hardware-detection-master)](
+https://ci.opensuse.org/view/Yast/job/yast-yast-hardware-detection-master/)
 
 
 ## Summary
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' 
'--exclude=.svnignore' old/yast2-hardware-detection-4.1.1/agent/HwParse.cc 
new/yast2-hardware-detection-4.1.2/agent/HwParse.cc
--- old/yast2-hardware-detection-4.1.1/agent/HwParse.cc 2019-08-27 
13:21:41.000000000 +0200
+++ new/yast2-hardware-detection-4.1.2/agent/HwParse.cc 2021-03-01 
18:09:22.000000000 +0100
@@ -1543,7 +1543,7 @@
 
     // map of resources
 
-    if (hd->res > 0)
+    if (hd->res)
     {
        YCPMap map;
        hd_res_t *resource;
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' 
'--exclude=.svnignore' 
old/yast2-hardware-detection-4.1.1/package/yast2-hardware-detection.changes 
new/yast2-hardware-detection-4.1.2/package/yast2-hardware-detection.changes
--- old/yast2-hardware-detection-4.1.1/package/yast2-hardware-detection.changes 
2019-08-27 13:21:41.000000000 +0200
+++ new/yast2-hardware-detection-4.1.2/package/yast2-hardware-detection.changes 
2021-03-01 18:09:22.000000000 +0100
@@ -1,4 +1,10 @@
 -------------------------------------------------------------------
+Mon Mar  1 16:47:31 UTC 2021 - Stefan Hundhammer <shundham...@suse.com>
+
+- Fixed pointer check to compile with GCC 11 (bsc#1181916)
+- 4.1.2
+
+-------------------------------------------------------------------
 Tue Aug 27 11:10:25 UTC 2019 - Steffen Winterfeldt <snw...@suse.com>
 
 - add bug number (bsc#1148310)
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' 
'--exclude=.svnignore' 
old/yast2-hardware-detection-4.1.1/package/yast2-hardware-detection.spec 
new/yast2-hardware-detection-4.1.2/package/yast2-hardware-detection.spec
--- old/yast2-hardware-detection-4.1.1/package/yast2-hardware-detection.spec    
2019-08-27 13:21:41.000000000 +0200
+++ new/yast2-hardware-detection-4.1.2/package/yast2-hardware-detection.spec    
2021-03-01 18:09:22.000000000 +0100
@@ -17,7 +17,7 @@
 
 
 Name:           yast2-hardware-detection
-Version:        4.1.1
+Version:        4.1.2
 Release:        0
 
 BuildRoot:      %{_tmppath}/%{name}-%{version}-build

Reply via email to