The following 10 noarch packages:

>  blender-lang-2.78c-3.2.noarch
>  blender-lang-2.78c-3.2.noarch
>  pitivi-lang-0.98-2.2.noarch
>  pitivi-lang-0.98-2.2.noarch
>  python3-holoviews-1.6.2-1.2.noarch
>  python3-holoviews-1.6.2-1.2.noarch
>  python3-jupyter_ipython-iptest-5.3.0-1.1.noarch
>  python3-jupyter_ipython-iptest-5.3.0-1.1.noarch
>  python3-opengl-3.1.0-5.2.noarch
>  python3-opengl-3.1.0-5.2.noarch
>  python3-patsy-0.4.1-1.2.noarch
>  python3-patsy-0.4.1-1.2.noarch
>  python3-pygame-doc-1.9.2+hg3425-2.1.noarch
>  python3-pygame-doc-1.9.2+hg3425-2.1.noarch
>  python3-seaborn-0.7.1-2.1.noarch
>  python3-seaborn-0.7.1-2.1.noarch
>  ski-6.11-1.3.noarch
>  ski-6.11-1.3.noarch
>  spyder3-hdf5-3.0.0-1.2.noarch
>  spyder3-hdf5-3.0.0-1.2.noarch


they have a dependency on 'libopenblas_pthreads0-0.2.19-1.15.x86_64' package.
Upon the installation of this package, the following error happens:

>  Transaction ID 59012ce4 started
>  Installing: libopenblas_pthreads0-0.2.19-1.15.x86_64 [............done]
>  Additional rpm output:
>  update-alternatives: error: no alternatives for libblas.so.3
>  update-alternatives: error: no alternatives for liblapack.so.3
>  update-alternatives: using /usr/lib64/libopenblas_pthreads.so.0 to provide /usr/lib64/libblas.so.3 (libblas.so.3) in auto mode
>  update-alternatives: using /usr/lib64/libopenblas_pthreads.so.0 to provide /usr/lib64/libcblas.so.3 (libcblas.so.3) in auto mode
>  update-alternatives: using /usr/lib64/libopenblas_pthreads.so.0 to provide /usr/lib64/liblapack.so.3 (liblapack.so.3) in auto mode
>  update-alternatives: using /usr/lib64/libopenblas_pthreads.so.0 to provide /usr/lib64/libopenblas.so.0 (libopenblas.so.0) in auto mode
>  /var/tmp/rpm-tmp.0TgvVF: line 17: [: =: unary operator expected
>  /var/tmp/rpm-tmp.0TgvVF: line 20: [: =: unary operator expected

As you can see, `update-alternatives` throws the following *error*:

>  update-alternatives: error: no alternatives for libblas.so.3
>  update-alternatives: error: no alternatives for liblapack.so.3

Note: If you think that is not an error, please change the message to not use
the word 'error' but something else (e.g. warning).

Furthermore:

>  /var/tmp/rpm-tmp.0TgvVF: line 17: [: =: unary operator expected
>  /var/tmp/rpm-tmp.0TgvVF: line 20: [: =: unary operator expected

As a result the transaction is not finished normally. This means that when
`zypper` is initiating an installation
process you see the message `Transaction ID 59012ce8 started`. When `zypper`
has been finished, you see the message
`Transaction ID 59012ce8 finished: 0` -- which is not the case for this
package.