[opensuse-factory] up vs dup with commerical intel compilers installed
Hello, I'm a TW user and hope that I'm right here with my question, if the forum is more appropriate, please tell me. I have TW and the following commercial intel packages installed: C/C++, Fortran, MKL (part of the compiler) and vTune Amplifier. The software is installed by a script and it always takes some time to install. I used to do zypper up because with zypper dup I have to reinstall my intel stuff and it always takes more than an hour. Recently I did a zypper up but no after some hours away I cannot log in graphically. I just see the mouse. After init 3 followed by init 5 on the text console I get an ugly X window displaying "could not syn environment to dbus.". I assume that a zypper dup might help?! BTW I use nuveau (as far as I know). I use KDE. However zypper dup --no-allow-vendor-change will remove my intel stuff. sudo zypper dup --no-allow-vendor-change Warning: You are about to do a distribution upgrade with all enabled repositories. Make sure these repositories are compatible before you continue. See 'man zypper' for more information about this command. Retrieving repository 'Packman Repository' metadata ...........................................................................................................................[done] Building repository 'Packman Repository' cache ................................................................................................................................[done] Loading repository data... Reading installed packages... Computing distribution upgrade... Problem: problem with installed package libuchardet0-0.0.6-2.1.x86_64 Solution 1: install libuchardet0-0.0.6-1.1.x86_64 (with vendor change) http://packman.links2linux.de --> openSUSE Choose the above solution using '1' or cancel using 'c' [1/c] (c): 1 Resolving dependencies... Computing distribution upgrade... The following 3 items are locked and will not be changed by any action: Installed: intel-icsxe-pset intel-mpi-rt-core-109 intel-mpi-rt-mic-109 The following application is going to be installed: digiKam The following 16 NEW packages are going to be installed: digikam digikam-lang gnome-nettool-lang k3b-lang kernel-default-4.10.1-1.3 kernel-default-devel-4.10.1-1.3 libixion-0_12-0 liborcus-0_12-0 libstaroffice-0_0-0 libzmf-0_0-0 perl-File-Find-Rule perl-Number-Compare perl-Text-Glob pulseaudio-esound-compat python3-appdirs python3-packaging The following 2 applications are going to be REMOVED: Desktop "System Tray" The following 102 packages are going to be REMOVED: baloo-core baloo-kioslaves esound-daemon intel-ccomp-doc intel-ccompxe intel-ccompxe-doc intel-comp-all-doc intel-comp-l-all-common-109 intel-comp-l-all-devel-109 intel-comp-l-all-vars-109 intel-comp-l-ps-common-109 intel-comp-l-ps-devel-109 intel-comp-l-ps-ss-devel-109 intel-comp-ps-ss-doc intel-daal-psxe-047 intel-fcomp-doc intel-fcompxe intel-fcompxe-doc intel-gdb intel-gdb-common intel-gdb-doc intel-gdb-ps-cdt intel-gdb-ps-cdt-source intel-gdb-ps-common intel-gdb-ps-doc intel-gdb-ps-mic intel-gdb-ps-mpm intel-icc-doc intel-icc-l-all-109 intel-icc-l-all-common-109 intel-icc-l-all-devel-109 intel-icc-l-all-vars-109 intel-icc-l-ps-common-109 intel-icc-l-ps-devel-109 intel-icc-l-ps-ss-109 intel-icc-l-ps-ss-devel-109 intel-icc-ps-doc intel-icc-ps-ss-doc intel-ifort-l-ps-109 intel-ifort-l-ps-common-109 intel-ifort-l-ps-devel-109 intel-ifort-l-ps-vars-109 intel-ifort-ps-doc intel-ipp-psxe-047 intel-mkl-109 intel-mkl-common-109 intel-mkl-devel-109 intel-mkl-doc intel-mkl-gnu-109 intel-mkl-gnu-devel-109 intel-mkl-ps-109 intel-mkl-ps-cluster-109 intel-mkl-ps-cluster-common-109 intel-mkl-ps-cluster-devel-109 intel-mkl-ps-common-109 intel-mkl-ps-doc intel-mkl-ps-f95-common-109 intel-mkl-ps-f95-devel-109 intel-mkl-ps-gnu-109 intel-mkl-ps-gnu-devel-109 intel-mkl-psxe-047 intel-openmp-l-all-109 intel-openmp-l-all-devel-109 intel-openmp-l-ps-109 intel-openmp-l-ps-devel-109 intel-openmp-l-ps-mic-109 intel-openmp-l-ps-mic-devel-109 intel-openmp-l-ps-ss-109 intel-openmp-l-ps-ss-devel-109 intel-psxe-common intel-psxe-doc intel-tbb-psxe-047 kernel-default-4.10.1-1.2 kernel-default-devel-4.10.1-1.2 kfilemetadata libass5 libbaloofiles4 libbaloopim4 libbalooqueryparser4 libbaloowidgets4 libevent-2_0-5 libgrantlee_core0 libgrantlee_gui0 libixion-0_11-0 liborcus-0_11-0 libpackagekitqt4-0 libsoprano4 libwx_baseu-suse1 libwx_baseu_net-suse1 libwx_baseu_xml-suse1 libwx_gtk2u_adv-suse1 libwx_gtk2u_aui-suse1 libwx_gtk2u_core-suse1 libwx_gtk2u_gl-suse1 libwx_gtk2u_html-suse1 libwx_gtk2u_media-suse1 libwx_gtk2u_propgrid-suse1 libwx_gtk2u_qa-suse1 libwx_gtk2u_richtext-suse1 libwx_gtk2u_stc-suse1 libwx_gtk2u_webview-suse1 libwx_gtk2u_xrc-suse1 The following 88 packages are going to be upgraded: apparmor-utils dbus-1-python3 gnome-music libapparmor-devel libapparmor1 libreoffice libreoffice-base libreoffice-base-drivers-mysql libreoffice-calc libreoffice-calc-extensions libreoffice-draw libreoffice-filters-optional libreoffice-gnome libreoffice-gtk3 libreoffice-icon-theme-tango libreoffice-impress libreoffice-kde4 libreoffice-l10n-en libreoffice-mailmerge libreoffice-math libreoffice-pyuno libreoffice-writer libreoffice-writer-extensions libreofficekit libstdc++6-32bit orca perl-apparmor python3 python3-Cycler python3-Cython python3-apparmor python3-atspi python3-base python3-bottle python3-brlapi python3-cairo python3-cairocffi python3-cffi python3-chardet python3-coverage python3-cryptography python3-cssselect python3-cups python3-cupshelpers python3-curses python3-dbm python3-devel python3-gedit python3-gmpy python3-gobject python3-gobject-Gdk python3-gobject-cairo python3-gobject2 python3-h5py python3-idle python3-idna python3-louis python3-lxml python3-matplotlib python3-matplotlib-cairo python3-matplotlib-gtk2 python3-matplotlib-tk python3-mpmath python3-nose python3-numpy python3-numpy-devel python3-pip python3-pyOpenSSL python3-pyasn1 python3-pycparser python3-pycurl python3-pyparsing python3-python-dateutil python3-pytz python3-qt5 python3-requests python3-scipy python3-setuptools python3-simplejson python3-sip python3-smbc python3-speechd python3-sympy python3-tk python3-urllib3 python3-vtk python3-vtk-qt python3-wheel The following 3 packages are going to be downgraded: desktop-translations libuchardet0 python3-six The following package is going to be reinstalled: python3-py The following package is going to change vendor: libuchardet0 http://packman.links2linux.de -> openSUSE 88 packages to upgrade, 3 to downgrade, 16 new, 1 to reinstall, 102 to remove, 1 to change vendor. Shall I lock more? Currently I have sudo zypper locks # | Name | Type | Repository --+-----------------------+---------+----------- 1 | intel-mpi-rt-core-109 | package | (any) 2 | intel-mpi-rt-mic-109 | package | (any) 3 | intel-icsxe-pset | package | (any) And this are my repos: sudo zypper repos Repository priorities are without effect. All enabled repositories share the same priority. # | Alias | Name | Enabled | GPG Check | Refresh ---+-------------------------------------+-----------------------------+---------+-----------+-------- 1 | adobe | adobe | Yes | ( p) Yes | Yes 2 | google-chrome | google-chrome | Yes | (r ) Yes | Yes 3 | home_AndnoVember_test | Test (openSUSE_Factory) | Yes | (r ) Yes | No 4 | http-download.opensuse.org-22f95660 | windows:mingw | No | ---- | ---- 5 | http-download.opensuse.org-512bc994 | home:tiwai:kernel:4.4 | Yes | (r ) Yes | Yes 6 | http-download.opensuse.org-f5a8b2d7 | science | No | ---- | ---- 7 | http-download.opensuse.org-ff1a1965 | Office | Yes | (r ) Yes | Yes 8 | http-download.opensuse.org-ffb3672f | windows:mingw:win64 | Yes | (r ) Yes | Yes 9 | http-ftp.gwdg.de-5c2dab74 | Packman Repository | Yes | (r ) Yes | Yes 10 | http-opensuse-guide.org-a3f71627 | libdvdcss repository | Yes | (r ) Yes | Yes 11 | openSUSE-20151002-0 | openSUSE-20151002-0 | No | ---- | ---- 12 | repo-debug | openSUSE-Tumbleweed-Debug | No | ---- | ---- 13 | repo-non-oss | openSUSE-Tumbleweed-Non-Oss | Yes | (r ) Yes | Yes 14 | repo-oss | openSUSE-Tumbleweed-Oss | Yes | (r ) Yes | Yes 15 | repo-source | openSUSE-Tumbleweed-Source | No | ---- | ---- 16 | repo-update | openSUSE-Tumbleweed-Update | Yes | (r ) Yes | Yes I Settings/Configure Desktop Screen locking is deactivated. Any ideas? Or shall I ask at another place? Thanks, Fabian -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2017-03-09 15:15, Fabian Wein wrote:
Hello,
I'm a TW user and hope that I'm right here with my question, if the forum is more appropriate, please tell me.
I have TW and the following commercial intel packages installed: C/C++, Fortran, MKL (part of the compiler) and vTune Amplifier. The software is installed by a script and it always takes some time to install.
rpms from some repo?
I used to do zypper up because with zypper dup I have to reinstall my intel stuff and it always takes more than an hour.
Recently I did a zypper up but no after some hours away I cannot log in graphically. I just see the mouse. After init 3 followed by init 5 on the text console I get an ugly X window displaying "could not syn environment to dbus.". I assume that a zypper dup might help?! BTW I use nuveau (as far as I know). I use KDE.
However zypper dup --no-allow-vendor-change will remove my intel stuff.
I suppose you have to lock those packages, as many as necessary till zypper dup leaves them alone. - -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iF4EAREIAAYFAljBZeYACgkQja8UbcUWM1zQVQD/dmm9TObRCzDKWya6HWlOz06X mKnZPHN8WYsFSAVW6bAA/2c9t7hOxc2nHWzuD8gJL2prKAy2Kj2Wq0x9AIs+9A3E =4Awa -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
I have TW and the following commercial intel packages installed: C/C++, Fortran, MKL (part of the compiler) and vTune Amplifier. The software is installed by a script and it always takes some time to install.
rpms from some repo?
No, a tar file contains an install.sh and a directory with many repos. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 03/09/2017 10:03 AM, Fabian Wein wrote:
I have TW and the following commercial intel packages installed: C/C++, Fortran, MKL (part of the compiler) and vTune Amplifier. The software is installed by a script and it always takes some time to install.
rpms from some repo?
No, a tar file contains an install.sh and a directory with many repos.
A directory with many 'repos' or many rpm's'? -- Ken Schneider -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 03/09/17 17:02, Ken Schneider - Factory wrote:
On 03/09/2017 10:03 AM, Fabian Wein wrote:
I have TW and the following commercial intel packages installed: C/C++, Fortran, MKL (part of the compiler) and vTune Amplifier. The software is installed by a script and it always takes some time to install.
rpms from some repo?
No, a tar file contains an install.sh and a directory with many repos.
A directory with many 'repos' or many rpm's'?
Sorry, 127 rpm's. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
* Fabian Wein
On 03/09/17 17:02, Ken Schneider - Factory wrote:
On 03/09/2017 10:03 AM, Fabian Wein wrote:
I have TW and the following commercial intel packages installed: C/C++, Fortran, MKL (part of the compiler) and vTune Amplifier. The software is installed by a script and it always takes some time to install.
rpms from some repo?
No, a tar file contains an install.sh and a directory with many repos.
A directory with many 'repos' or many rpm's'?
Sorry, 127 rpm's.
perhaps for your system you create your own "repo" containing the 127 rpms and lock those rpms to only your repo. I do this for a few perferred packages on my home-work computer. look at "createrepo" package, for tw I have createrepo-0.10.4-1.2.x86_64, and it is in OSS. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 Photos: http://wahoo.no-ip.org/piwigo @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Fabian Wein wrote:
On 03/09/17 17:02, Ken Schneider - Factory wrote:
On 03/09/2017 10:03 AM, Fabian Wein wrote:
I have TW and the following commercial intel packages installed: C/C++, Fortran, MKL (part of the compiler) and vTune Amplifier. The software is installed by a script and it always takes some time to install.
rpms from some repo?
No, a tar file contains an install.sh and a directory with many repos.
A directory with many 'repos' or many rpm's'?
Sorry, 127 rpm's.
In that case you can also install 'createrepo', and create a repodata directory for those, then add this to your repositories. This is what I did for my self-compiled RPMs in /usr/src/packages Pit -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Fabian Wein wrote:
On 03/09/17 17:02, Ken Schneider - Factory wrote:
On 03/09/2017 10:03 AM, Fabian Wein wrote:
I have TW and the following commercial intel packages installed: C/C++, Fortran, MKL (part of the compiler) and vTune Amplifier. The software is installed by a script and it always takes some time to install.
rpms from some repo?
No, a tar file contains an install.sh and a directory with many repos.
A directory with many 'repos' or many rpm's'?
Sorry, 127 rpm's.
In that case you can also install 'createrepo', and create a repodata directory for those, then add this to your repositories. This is what I did for my self-compiled RPMs in /usr/src/packages
What would be the reason? Such that I would not have to clean my locks when I upgrade the intel stuff and add the locks manually again afterwards? I did not had the impression that addLock supports wildcards?! So I added all packages which zypper wanted to remove manually. Then using createrepo sounds like a good and clear way. But for now it wouldn't make a difference, right?! BTW, why wanted zypper to remove the intel stuff? Thanks, Fabian -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hi Fabian, you shall install intel tools as user that will prevent it from creating rpm entries. crete /opt/intel as root and chown to your user and then use a custom install path. look in install.sh --help and there is some other option about rpms that I never tried but it may help. Regards, Alin On Thursday, 9 March 2017 16:42:45 GMT Fabian Wein wrote:
Fabian Wein wrote:
On 03/09/17 17:02, Ken Schneider - Factory wrote:
On 03/09/2017 10:03 AM, Fabian Wein wrote:
> I have TW and the following commercial intel packages installed: > C/C++, Fortran, MKL (part of the compiler) and vTune Amplifier. The > software is installed by a script and it always takes some time to > install.
rpms from some repo?
No, a tar file contains an install.sh and a directory with many repos.
A directory with many 'repos' or many rpm's'?
Sorry, 127 rpm's.
In that case you can also install 'createrepo', and create a repodata directory for those, then add this to your repositories. This is what I did for my self-compiled RPMs in /usr/src/packages
What would be the reason? Such that I would not have to clean my locks when I upgrade the intel stuff and add the locks manually again afterwards? I did not had the impression that addLock supports wildcards?! So I added all packages which zypper wanted to remove manually. Then using createrepo sounds like a good and clear way.
But for now it wouldn't make a difference, right?!
BTW, why wanted zypper to remove the intel stuff?
Thanks,
Fabian
-- Without Questions there are no Answers! _______________________________________ Dr. Alin Marin ELENA http://alin.elena.space/ _______________________________________
Am Thu, 9 Mar 2017 17:42:45 +0100
schrieb Fabian Wein
I did not had the impression that addLock supports wildcards?!
zypper al 'libpyl*' is a must-have, and it works.
Then using createrepo sounds like a good and clear way.
I think putting all rpms into a directory and create a plain-dir repo would work as well. Then these pkgs are always available and visible to zypper. Olaf
On 2017-03-09 17:42, Fabian Wein wrote:
Fabian Wein wrote:
On 03/09/17 17:02, Ken Schneider - Factory wrote:
A directory with many 'repos' or many rpm's'?
Sorry, 127 rpm's.
In that case you can also install 'createrepo', and create a repodata directory for those, then add this to your repositories. This is what I did for my self-compiled RPMs in /usr/src/packages
What would be the reason?
The new repo is also another vendor. Zypper can not switch automatically.
BTW, why wanted zypper to remove the intel stuff?
Well, apparently those packages contain obsolete components that conflict with what TW wants. I think you should use an older distribution. Also doing a local user install instead of a global install would keep zypper happy, as Alin suggests. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" (Minas Tirith))
On 03/09/2017 11:07 AM, Fabian Wein wrote:
On 03/09/17 17:02, Ken Schneider - Factory wrote:
On 03/09/2017 10:03 AM, Fabian Wein wrote:
I have TW and the following commercial intel packages installed: C/C++, Fortran, MKL (part of the compiler) and vTune Amplifier. The software is installed by a script and it always takes some time to install.
rpms from some repo?
No, a tar file contains an install.sh and a directory with many repos.
A directory with many 'repos' or many rpm's'?
Sorry, 127 rpm's.
Alright, start YaST and use the repo management to add that directory as a local repo. Once you do that the rpm's will always be available for easy install and allow you to lock the packages so that they will not be deleted. HTH -- Ken Schneider -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
However zypper dup --no-allow-vendor-change will remove my intel stuff.
I suppose you have to lock those packages, as many as necessary till zypper dup leaves them alone.
I did it and now remember what the problem was: Shall I "Solution 2: keep obsolete libstdc++6-32bit-6.3.1+r245043-1.1.x86_64"? sudo zypper dup --no-allow-vendor-change Warning: You are about to do a distribution upgrade with all enabled repositories. Make sure these repositories are compatible before you continue. See 'man zypper' for more information about this command. Loading repository data... Reading installed packages... Computing distribution upgrade... 2 Problems: Problem: problem with installed package libuchardet0-0.0.6-2.1.x86_64 Problem: intel-ccomp-doc-2016.0-047.noarch requires /usr/lib/libstdc++.so.6, but this requirement cannot be provided Problem: problem with installed package libuchardet0-0.0.6-2.1.x86_64 Solution 1: install libuchardet0-0.0.6-1.1.x86_64 (with vendor change) http://packman.links2linux.de --> openSUSE Choose the above solution using '1' or skip, retry or cancel [1/s/r/c] (c): 1 Problem: intel-ccomp-doc-2016.0-047.noarch requires /usr/lib/libstdc++.so.6, but this requirement cannot be provided deleted providers: libstdc++6-32bit-6.3.1+r245043-1.1.x86_64 Solution 1: Following actions will be done: remove lock to allow removal of intel-ccomp-doc-2016.0-047.noarch remove lock to allow removal of intel-ccompxe-2016.0-047.noarch remove lock to allow removal of intel-ccompxe-doc-2016.0-047.noarch remove lock to allow removal of intel-comp-all-doc-16.0.0-109.noarch remove lock to allow removal of intel-comp-l-all-common-109-16.0.0-109.noarch remove lock to allow removal of intel-comp-l-all-devel-109-16.0.0-109.x86_64 remove lock to allow removal of intel-comp-l-all-vars-109-16.0.0-109.noarch remove lock to allow removal of intel-comp-l-ps-common-109-16.0.0-109.noarch remove lock to allow removal of intel-comp-l-ps-devel-109-16.0.0-109.x86_64 remove lock to allow removal of intel-comp-l-ps-ss-devel-109-16.0.0-109.x86_64 remove lock to allow removal of intel-comp-ps-ss-doc-16.0.0-109.noarch remove lock to allow removal of intel-daal-psxe-047-2016.0-047.noarch remove lock to allow removal of intel-fcomp-doc-2016.0-047.noarch remove lock to allow removal of intel-fcompxe-2016.0-047.noarch remove lock to allow removal of intel-fcompxe-doc-2016.0-047.noarch remove lock to allow removal of intel-gdb-7.8.0-109.x86_64 remove lock to allow removal of intel-gdb-common-7.8.0-109.noarch remove lock to allow removal of intel-gdb-doc-7.8.0-109.noarch remove lock to allow removal of intel-gdb-ps-cdt-7.8.0-047.x86_64 remove lock to allow removal of intel-gdb-ps-cdt-source-7.8.0-047.x86_64 remove lock to allow removal of intel-gdb-ps-common-7.8.0-047.noarch remove lock to allow removal of intel-gdb-ps-doc-7.8.0-047.noarch remove lock to allow removal of intel-gdb-ps-mic-7.8.0-047.x86_64 remove lock to allow removal of intel-gdb-ps-mpm-7.8.0-047.x86_64 remove lock to allow removal of intel-icc-doc-16.0.0-109.noarch remove lock to allow removal of intel-icc-l-all-109-16.0.0-109.x86_64 remove lock to allow removal of intel-icc-l-all-common-109-16.0.0-109.noarch remove lock to allow removal of intel-icc-l-all-devel-109-16.0.0-109.x86_64 remove lock to allow removal of intel-icc-l-all-vars-109-16.0.0-109.noarch remove lock to allow removal of intel-icc-l-ps-common-109-16.0.0-109.noarch remove lock to allow removal of intel-icc-l-ps-devel-109-16.0.0-109.x86_64 remove lock to allow removal of intel-icc-l-ps-ss-109-16.0.0-109.x86_64 remove lock to allow removal of intel-icc-l-ps-ss-devel-109-16.0.0-109.x86_64 remove lock to allow removal of intel-icc-ps-doc-16.0.0-109.noarch remove lock to allow removal of intel-icc-ps-ss-doc-16.0.0-109.noarch remove lock to allow removal of intel-ifort-l-ps-109-16.0.0-109.x86_64 remove lock to allow removal of intel-ifort-l-ps-common-109-16.0.0-109.noarch remove lock to allow removal of intel-ifort-l-ps-devel-109-16.0.0-109.x86_64 remove lock to allow removal of intel-ifort-l-ps-vars-109-16.0.0-109.noarch remove lock to allow removal of intel-ifort-ps-doc-16.0.0-109.noarch remove lock to allow removal of intel-ipp-psxe-047-9.0.0-047.noarch remove lock to allow removal of intel-mkl-109-11.3.0-109.x86_64 remove lock to allow removal of intel-mkl-common-109-11.3.0-109.noarch remove lock to allow removal of intel-mkl-devel-109-11.3.0-109.x86_64 remove lock to allow removal of intel-mkl-doc-11.3.0-109.noarch remove lock to allow removal of intel-mkl-gnu-109-11.3.0-109.x86_64 remove lock to allow removal of intel-mkl-gnu-devel-109-11.3.0-109.x86_64 remove lock to allow removal of intel-mkl-ps-109-11.3.0-109.x86_64 remove lock to allow removal of intel-mkl-ps-cluster-109-11.3.0-109.x86_64 remove lock to allow removal of intel-mkl-ps-cluster-common-109-11.3.0-109.noarch remove lock to allow removal of intel-mkl-ps-cluster-devel-109-11.3.0-109.x86_64 remove lock to allow removal of intel-mkl-ps-common-109-11.3.0-109.noarch remove lock to allow removal of intel-mkl-ps-doc-11.3.0-109.noarch remove lock to allow removal of intel-mkl-ps-f95-common-109-11.3.0-109.noarch remove lock to allow removal of intel-mkl-ps-f95-devel-109-11.3.0-109.x86_64 remove lock to allow removal of intel-mkl-ps-gnu-109-11.3.0-109.x86_64 remove lock to allow removal of intel-mkl-ps-gnu-devel-109-11.3.0-109.x86_64 remove lock to allow removal of intel-mkl-psxe-047-11.3.0-047.noarch remove lock to allow removal of intel-openmp-l-all-109-16.0.0-109.x86_64 remove lock to allow removal of intel-openmp-l-all-devel-109-16.0.0-109.x86_64 remove lock to allow removal of intel-openmp-l-ps-109-16.0.0-109.x86_64 remove lock to allow removal of intel-openmp-l-ps-devel-109-16.0.0-109.x86_64 remove lock to allow removal of intel-openmp-l-ps-mic-109-16.0.0-109.x86_64 remove lock to allow removal of intel-openmp-l-ps-mic-devel-109-16.0.0-109.x86_64 remove lock to allow removal of intel-openmp-l-ps-ss-109-16.0.0-109.x86_64 remove lock to allow removal of intel-openmp-l-ps-ss-devel-109-16.0.0-109.x86_64 remove lock to allow removal of intel-psxe-common-2016.0-047.noarch remove lock to allow removal of intel-psxe-doc-2016.0-047.noarch remove lock to allow removal of intel-tbb-psxe-047-4.4.0-047.noarch Solution 2: keep obsolete libstdc++6-32bit-6.3.1+r245043-1.1.x86_64 Solution 3: break intel-ccomp-doc-2016.0-047.noarch by ignoring some of its dependencies Choose from above solutions by number or skip, retry or cancel [1/2/3/s/r/c] -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
* Fabian Wein
However zypper dup --no-allow-vendor-change will remove my intel stuff.
I suppose you have to lock those packages, as many as necessary till zypper dup leaves them alone.
I did it and now remember what the problem was:
Shall I "Solution 2: keep obsolete libstdc++6-32bit-6.3.1+r245043-1.1.x86_64"?
sudo zypper dup --no-allow-vendor-change Warning: You are about to do a distribution upgrade with all enabled repositories. Make sure these repositories are compatible before you continue. See 'man zypper' for more information about this command. Loading repository data... Reading installed packages... Computing distribution upgrade... 2 Problems: Problem: problem with installed package libuchardet0-0.0.6-2.1.x86_64 Problem: intel-ccomp-doc-2016.0-047.noarch requires /usr/lib/libstdc++.so.6, but this requirement cannot be provided
Problem: problem with installed package libuchardet0-0.0.6-2.1.x86_64 Solution 1: install libuchardet0-0.0.6-1.1.x86_64 (with vendor change) http://packman.links2linux.de --> openSUSE
Choose the above solution using '1' or skip, retry or cancel [1/s/r/c] (c): 1
Problem: intel-ccomp-doc-2016.0-047.noarch requires /usr/lib/libstdc++.so.6, but this requirement cannot be provided deleted providers: libstdc++6-32bit-6.3.1+r245043-1.1.x86_64 Solution 1: Following actions will be done: remove lock to allow removal of intel-ccomp-doc-2016.0-047.noarch remove lock to allow removal of intel-ccompxe-2016.0-047.noarch remove lock to allow removal of intel-ccompxe-doc-2016.0-047.noarch remove lock to allow removal of intel-comp-all-doc-16.0.0-109.noarch remove lock to allow removal of intel-comp-l-all-common-109-16.0.0-109.noarch remove lock to allow removal of intel-comp-l-all-devel-109-16.0.0-109.x86_64 remove lock to allow removal of intel-comp-l-all-vars-109-16.0.0-109.noarch remove lock to allow removal of intel-comp-l-ps-common-109-16.0.0-109.noarch remove lock to allow removal of intel-comp-l-ps-devel-109-16.0.0-109.x86_64 remove lock to allow removal of intel-comp-l-ps-ss-devel-109-16.0.0-109.x86_64 remove lock to allow removal of intel-comp-ps-ss-doc-16.0.0-109.noarch remove lock to allow removal of intel-daal-psxe-047-2016.0-047.noarch remove lock to allow removal of intel-fcomp-doc-2016.0-047.noarch remove lock to allow removal of intel-fcompxe-2016.0-047.noarch remove lock to allow removal of intel-fcompxe-doc-2016.0-047.noarch remove lock to allow removal of intel-gdb-7.8.0-109.x86_64 remove lock to allow removal of intel-gdb-common-7.8.0-109.noarch remove lock to allow removal of intel-gdb-doc-7.8.0-109.noarch remove lock to allow removal of intel-gdb-ps-cdt-7.8.0-047.x86_64 remove lock to allow removal of intel-gdb-ps-cdt-source-7.8.0-047.x86_64 remove lock to allow removal of intel-gdb-ps-common-7.8.0-047.noarch remove lock to allow removal of intel-gdb-ps-doc-7.8.0-047.noarch remove lock to allow removal of intel-gdb-ps-mic-7.8.0-047.x86_64 remove lock to allow removal of intel-gdb-ps-mpm-7.8.0-047.x86_64 remove lock to allow removal of intel-icc-doc-16.0.0-109.noarch remove lock to allow removal of intel-icc-l-all-109-16.0.0-109.x86_64 remove lock to allow removal of intel-icc-l-all-common-109-16.0.0-109.noarch remove lock to allow removal of intel-icc-l-all-devel-109-16.0.0-109.x86_64 remove lock to allow removal of intel-icc-l-all-vars-109-16.0.0-109.noarch remove lock to allow removal of intel-icc-l-ps-common-109-16.0.0-109.noarch remove lock to allow removal of intel-icc-l-ps-devel-109-16.0.0-109.x86_64 remove lock to allow removal of intel-icc-l-ps-ss-109-16.0.0-109.x86_64 remove lock to allow removal of intel-icc-l-ps-ss-devel-109-16.0.0-109.x86_64 remove lock to allow removal of intel-icc-ps-doc-16.0.0-109.noarch remove lock to allow removal of intel-icc-ps-ss-doc-16.0.0-109.noarch remove lock to allow removal of intel-ifort-l-ps-109-16.0.0-109.x86_64 remove lock to allow removal of intel-ifort-l-ps-common-109-16.0.0-109.noarch remove lock to allow removal of intel-ifort-l-ps-devel-109-16.0.0-109.x86_64 remove lock to allow removal of intel-ifort-l-ps-vars-109-16.0.0-109.noarch remove lock to allow removal of intel-ifort-ps-doc-16.0.0-109.noarch remove lock to allow removal of intel-ipp-psxe-047-9.0.0-047.noarch remove lock to allow removal of intel-mkl-109-11.3.0-109.x86_64 remove lock to allow removal of intel-mkl-common-109-11.3.0-109.noarch remove lock to allow removal of intel-mkl-devel-109-11.3.0-109.x86_64 remove lock to allow removal of intel-mkl-doc-11.3.0-109.noarch remove lock to allow removal of intel-mkl-gnu-109-11.3.0-109.x86_64 remove lock to allow removal of intel-mkl-gnu-devel-109-11.3.0-109.x86_64 remove lock to allow removal of intel-mkl-ps-109-11.3.0-109.x86_64 remove lock to allow removal of intel-mkl-ps-cluster-109-11.3.0-109.x86_64 remove lock to allow removal of intel-mkl-ps-cluster-common-109-11.3.0-109.noarch remove lock to allow removal of intel-mkl-ps-cluster-devel-109-11.3.0-109.x86_64 remove lock to allow removal of intel-mkl-ps-common-109-11.3.0-109.noarch remove lock to allow removal of intel-mkl-ps-doc-11.3.0-109.noarch remove lock to allow removal of intel-mkl-ps-f95-common-109-11.3.0-109.noarch remove lock to allow removal of intel-mkl-ps-f95-devel-109-11.3.0-109.x86_64 remove lock to allow removal of intel-mkl-ps-gnu-109-11.3.0-109.x86_64 remove lock to allow removal of intel-mkl-ps-gnu-devel-109-11.3.0-109.x86_64 remove lock to allow removal of intel-mkl-psxe-047-11.3.0-047.noarch remove lock to allow removal of intel-openmp-l-all-109-16.0.0-109.x86_64 remove lock to allow removal of intel-openmp-l-all-devel-109-16.0.0-109.x86_64 remove lock to allow removal of intel-openmp-l-ps-109-16.0.0-109.x86_64 remove lock to allow removal of intel-openmp-l-ps-devel-109-16.0.0-109.x86_64 remove lock to allow removal of intel-openmp-l-ps-mic-109-16.0.0-109.x86_64 remove lock to allow removal of intel-openmp-l-ps-mic-devel-109-16.0.0-109.x86_64 remove lock to allow removal of intel-openmp-l-ps-ss-109-16.0.0-109.x86_64 remove lock to allow removal of intel-openmp-l-ps-ss-devel-109-16.0.0-109.x86_64 remove lock to allow removal of intel-psxe-common-2016.0-047.noarch remove lock to allow removal of intel-psxe-doc-2016.0-047.noarch remove lock to allow removal of intel-tbb-psxe-047-4.4.0-047.noarch Solution 2: keep obsolete libstdc++6-32bit-6.3.1+r245043-1.1.x86_64 Solution 3: break intel-ccomp-doc-2016.0-047.noarch by ignoring some of its dependencies
Choose from above solutions by number or skip, retry or cancel [1/2/3/s/r/c]
allow the change from packman for libuchardet0. it doesn't need to be from packman and I don't believe they provide it any longer. choose "keep obsolete" for all packages relating to your perferred "intel packages". -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 Photos: http://wahoo.no-ip.org/piwigo @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
remove lock to allow removal of intel-psxe-doc-2016.0-047.noarch remove lock to allow removal of intel-tbb-psxe-047-4.4.0-047.noarch Solution 2: keep obsolete libstdc++6-32bit-6.3.1+r245043-1.1.x86_64 Solution 3: break intel-ccomp-doc-2016.0-047.noarch by ignoring some of its dependencies
Choose from above solutions by number or skip, retry or cancel [1/2/3/s/r/c]
allow the change from packman for libuchardet0. it doesn't need to be from packman and I don't believe they provide it any longer.
choose "keep obsolete" for all packages relating to your perferred "intel packages".
I did both and it installed without any further issues. Thanks so far to all of you. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2017-03-09 16:24, Fabian Wein wrote:
However zypper dup --no-allow-vendor-change will remove my intel stuff.
I suppose you have to lock those packages, as many as necessary till zypper dup leaves them alone.
I did it and now remember what the problem was:
Shall I "Solution 2: keep obsolete libstdc++6-32bit-6.3.1+r245043-1.1.x86_64"?
2 Problems: Problem: problem with installed package libuchardet0-0.0.6-2.1.x86_64 Problem: intel-ccomp-doc-2016.0-047.noarch requires /usr/lib/libstdc++.so.6, but this requirement cannot be provided
Maybe you should not be using TW. :-? Maybe that compiler brings its own libstdc library? :-?? - -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iF4EAREIAAYFAljBd/IACgkQja8UbcUWM1wlWgD+OGBVK26r97WjGnfKXPg3LSLK HU08F0+5L2czs4XvKCcA/1COTyx/zSePMbCJIEZJyPL2c3hCnp+/o9BOY4wnliUc =XGzJ -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Thu, 9 Mar 2017, Fabian Wein wrote:
However zypper dup --no-allow-vendor-change will remove my intel stuff.
I suppose you have to lock those packages, as many as necessary till zypper dup leaves them alone.
I did it and now remember what the problem was:
Shall I "Solution 2: keep obsolete libstdc++6-32bit-6.3.1+r245043-1.1.x86_64"?
Huh, what obsoletes libstdc++6-32bit-6.3.1+r245043-1.1.x86_64? Do we maybe auto-obsolete all -32bit packages at dup time?
sudo zypper dup --no-allow-vendor-change Warning: You are about to do a distribution upgrade with all enabled repositories. Make sure these repositories are compatible before you continue. See 'man zypper' for more information about this command. Loading repository data... Reading installed packages... Computing distribution upgrade... 2 Problems: Problem: problem with installed package libuchardet0-0.0.6-2.1.x86_64 Problem: intel-ccomp-doc-2016.0-047.noarch requires /usr/lib/libstdc++.so.6, but this requirement cannot be provided
Problem: problem with installed package libuchardet0-0.0.6-2.1.x86_64 Solution 1: install libuchardet0-0.0.6-1.1.x86_64 (with vendor change) http://packman.links2linux.de --> openSUSE
Choose the above solution using '1' or skip, retry or cancel [1/s/r/c] (c): 1
Problem: intel-ccomp-doc-2016.0-047.noarch requires /usr/lib/libstdc++.so.6, but this requirement cannot be provided deleted providers: libstdc++6-32bit-6.3.1+r245043-1.1.x86_64 Solution 1: Following actions will be done: remove lock to allow removal of intel-ccomp-doc-2016.0-047.noarch remove lock to allow removal of intel-ccompxe-2016.0-047.noarch remove lock to allow removal of intel-ccompxe-doc-2016.0-047.noarch remove lock to allow removal of intel-comp-all-doc-16.0.0-109.noarch remove lock to allow removal of intel-comp-l-all-common-109-16.0.0-109.noarch remove lock to allow removal of intel-comp-l-all-devel-109-16.0.0-109.x86_64 remove lock to allow removal of intel-comp-l-all-vars-109-16.0.0-109.noarch remove lock to allow removal of intel-comp-l-ps-common-109-16.0.0-109.noarch remove lock to allow removal of intel-comp-l-ps-devel-109-16.0.0-109.x86_64 remove lock to allow removal of intel-comp-l-ps-ss-devel-109-16.0.0-109.x86_64 remove lock to allow removal of intel-comp-ps-ss-doc-16.0.0-109.noarch remove lock to allow removal of intel-daal-psxe-047-2016.0-047.noarch remove lock to allow removal of intel-fcomp-doc-2016.0-047.noarch remove lock to allow removal of intel-fcompxe-2016.0-047.noarch remove lock to allow removal of intel-fcompxe-doc-2016.0-047.noarch remove lock to allow removal of intel-gdb-7.8.0-109.x86_64 remove lock to allow removal of intel-gdb-common-7.8.0-109.noarch remove lock to allow removal of intel-gdb-doc-7.8.0-109.noarch remove lock to allow removal of intel-gdb-ps-cdt-7.8.0-047.x86_64 remove lock to allow removal of intel-gdb-ps-cdt-source-7.8.0-047.x86_64 remove lock to allow removal of intel-gdb-ps-common-7.8.0-047.noarch remove lock to allow removal of intel-gdb-ps-doc-7.8.0-047.noarch remove lock to allow removal of intel-gdb-ps-mic-7.8.0-047.x86_64 remove lock to allow removal of intel-gdb-ps-mpm-7.8.0-047.x86_64 remove lock to allow removal of intel-icc-doc-16.0.0-109.noarch remove lock to allow removal of intel-icc-l-all-109-16.0.0-109.x86_64 remove lock to allow removal of intel-icc-l-all-common-109-16.0.0-109.noarch remove lock to allow removal of intel-icc-l-all-devel-109-16.0.0-109.x86_64 remove lock to allow removal of intel-icc-l-all-vars-109-16.0.0-109.noarch remove lock to allow removal of intel-icc-l-ps-common-109-16.0.0-109.noarch remove lock to allow removal of intel-icc-l-ps-devel-109-16.0.0-109.x86_64 remove lock to allow removal of intel-icc-l-ps-ss-109-16.0.0-109.x86_64 remove lock to allow removal of intel-icc-l-ps-ss-devel-109-16.0.0-109.x86_64 remove lock to allow removal of intel-icc-ps-doc-16.0.0-109.noarch remove lock to allow removal of intel-icc-ps-ss-doc-16.0.0-109.noarch remove lock to allow removal of intel-ifort-l-ps-109-16.0.0-109.x86_64 remove lock to allow removal of intel-ifort-l-ps-common-109-16.0.0-109.noarch remove lock to allow removal of intel-ifort-l-ps-devel-109-16.0.0-109.x86_64 remove lock to allow removal of intel-ifort-l-ps-vars-109-16.0.0-109.noarch remove lock to allow removal of intel-ifort-ps-doc-16.0.0-109.noarch remove lock to allow removal of intel-ipp-psxe-047-9.0.0-047.noarch remove lock to allow removal of intel-mkl-109-11.3.0-109.x86_64 remove lock to allow removal of intel-mkl-common-109-11.3.0-109.noarch remove lock to allow removal of intel-mkl-devel-109-11.3.0-109.x86_64 remove lock to allow removal of intel-mkl-doc-11.3.0-109.noarch remove lock to allow removal of intel-mkl-gnu-109-11.3.0-109.x86_64 remove lock to allow removal of intel-mkl-gnu-devel-109-11.3.0-109.x86_64 remove lock to allow removal of intel-mkl-ps-109-11.3.0-109.x86_64 remove lock to allow removal of intel-mkl-ps-cluster-109-11.3.0-109.x86_64 remove lock to allow removal of intel-mkl-ps-cluster-common-109-11.3.0-109.noarch remove lock to allow removal of intel-mkl-ps-cluster-devel-109-11.3.0-109.x86_64 remove lock to allow removal of intel-mkl-ps-common-109-11.3.0-109.noarch remove lock to allow removal of intel-mkl-ps-doc-11.3.0-109.noarch remove lock to allow removal of intel-mkl-ps-f95-common-109-11.3.0-109.noarch remove lock to allow removal of intel-mkl-ps-f95-devel-109-11.3.0-109.x86_64 remove lock to allow removal of intel-mkl-ps-gnu-109-11.3.0-109.x86_64 remove lock to allow removal of intel-mkl-ps-gnu-devel-109-11.3.0-109.x86_64 remove lock to allow removal of intel-mkl-psxe-047-11.3.0-047.noarch remove lock to allow removal of intel-openmp-l-all-109-16.0.0-109.x86_64 remove lock to allow removal of intel-openmp-l-all-devel-109-16.0.0-109.x86_64 remove lock to allow removal of intel-openmp-l-ps-109-16.0.0-109.x86_64 remove lock to allow removal of intel-openmp-l-ps-devel-109-16.0.0-109.x86_64 remove lock to allow removal of intel-openmp-l-ps-mic-109-16.0.0-109.x86_64 remove lock to allow removal of intel-openmp-l-ps-mic-devel-109-16.0.0-109.x86_64 remove lock to allow removal of intel-openmp-l-ps-ss-109-16.0.0-109.x86_64 remove lock to allow removal of intel-openmp-l-ps-ss-devel-109-16.0.0-109.x86_64 remove lock to allow removal of intel-psxe-common-2016.0-047.noarch remove lock to allow removal of intel-psxe-doc-2016.0-047.noarch remove lock to allow removal of intel-tbb-psxe-047-4.4.0-047.noarch Solution 2: keep obsolete libstdc++6-32bit-6.3.1+r245043-1.1.x86_64 Solution 3: break intel-ccomp-doc-2016.0-047.noarch by ignoring some of its dependencies
Choose from above solutions by number or skip, retry or cancel [1/2/3/s/r/c]
--
Richard Biener
Am Thu, 9 Mar 2017 15:15:19 +0100
schrieb Fabian Wein
The following 102 packages are going to be REMOVED: baloo-core baloo-kioslaves esound-daemon intel-ccomp-doc ...
Maybe these intel-* packages provide something that is globally obsoleted by? Please paste the output of this command: rpm -qa | grep ^intel | xargs rpm -q --provides | sort -u Olaf
What do you mean with "globally obsoleted"?
Maybe these intel-* packages provide something that is globally obsoleted by? Please paste the output of this command:
rpm -qa | grep ^intel | xargs rpm -q --provides | sort -u
rpm -qa | grep ^intel | xargs rpm -q --provides | sort -u intel-ccomp-doc = 2016.0-047 intel-ccompxe = 2016.0-047 intel-ccompxe-doc = 2016.0-047 intel-comp-all-doc = 16.0.0-109 intel-comp-l-all-common-109 = 16.0.0-109 intel-comp-l-all-devel-109 = 16.0.0-109 intel-comp-l-all-vars-109 = 16.0.0-109 intel-comp-l-ps-common-109 = 16.0.0-109 intel-comp-l-ps-devel-109 = 16.0.0-109 intel-comp-l-ps-ss-devel-109 = 16.0.0-109 intel-comp-ps-ss-doc = 16.0.0-109 intel-daal-psxe-047 = 2016.0-047 intel-fcomp-doc = 2016.0-047 intel-fcompxe = 2016.0-047 intel-fcompxe-doc = 2016.0-047 intel-gdb = 7.8.0-109 intel-gdb-common = 7.8.0-109 intel-gdb-doc = 7.8.0-109 intel-gdb-ps-cdt = 7.8.0-047 intel-gdb-ps-cdt-source = 7.8.0-047 intel-gdb-ps-common = 7.8.0-047 intel-gdb-ps-doc = 7.8.0-047 intel-gdb-ps-mic = 7.8.0-047 intel-gdb-ps-mpm = 7.8.0-047 intel-icc-doc = 16.0.0-109 intel-icc-l-all-109 = 16.0.0-109 intel-icc-l-all-common-109 = 16.0.0-109 intel-icc-l-all-devel-109 = 16.0.0-109 intel-icc-l-all-vars-109 = 16.0.0-109 intel-icc-l-ps-common-109 = 16.0.0-109 intel-icc-l-ps-devel-109 = 16.0.0-109 intel-icc-l-ps-ss-109 = 16.0.0-109 intel-icc-l-ps-ss-devel-109 = 16.0.0-109 intel-icc-ps-doc = 16.0.0-109 intel-icc-ps-ss-doc = 16.0.0-109 intel-icsxe-pset = 2016.0-047 intel-ifort-l-ps-109 = 16.0.0-109 intel-ifort-l-ps-common-109 = 16.0.0-109 intel-ifort-l-ps-devel-109 = 16.0.0-109 intel-ifort-l-ps-vars-109 = 16.0.0-109 intel-ifort-ps-doc = 16.0.0-109 intel-ipp-psxe-047 = 9.0.0-047 intel-mkl-109 = 11.3.0-109 intel-mkl-common-109 = 11.3.0-109 intel-mkl-devel-109 = 11.3.0-109 intel-mkl-doc = 11.3.0-109 intel-mkl-gnu-109 = 11.3.0-109 intel-mkl-gnu-devel-109 = 11.3.0-109 intel-mkl-ps-109 = 11.3.0-109 intel-mkl-ps-cluster-109 = 11.3.0-109 intel-mkl-ps-cluster-common-109 = 11.3.0-109 intel-mkl-ps-cluster-devel-109 = 11.3.0-109 intel-mkl-ps-common-109 = 11.3.0-109 intel-mkl-ps-doc = 11.3.0-109 intel-mkl-ps-f95-common-109 = 11.3.0-109 intel-mkl-ps-f95-devel-109 = 11.3.0-109 intel-mkl-ps-gnu-109 = 11.3.0-109 intel-mkl-ps-gnu-devel-109 = 11.3.0-109 intel-mkl-psxe-047 = 11.3.0-047 intel-mpi-rt-core-109 = 5.1.1-109 intel-mpi-rt-mic-109 = 5.1.1-109 intel-openmp-l-all-109 = 16.0.0-109 intel-openmp-l-all-devel-109 = 16.0.0-109 intel-openmp-l-ps-109 = 16.0.0-109 intel-openmp-l-ps-devel-109 = 16.0.0-109 intel-openmp-l-ps-mic-109 = 16.0.0-109 intel-openmp-l-ps-mic-devel-109 = 16.0.0-109 intel-openmp-l-ps-ss-109 = 16.0.0-109 intel-openmp-l-ps-ss-devel-109 = 16.0.0-109 intel-psxe-common = 2016.0-047 intel-psxe-doc = 2016.0-047 intel-tbb-psxe-047 = 4.4.0-047 intel-vtune-amplifier-xe-2017-cli = 17.0-478468 intel-vtune-amplifier-xe-2017-cli-common = 17.0-478468 intel-vtune-amplifier-xe-2017-collector-32linux = 17.0-478468 intel-vtune-amplifier-xe-2017-collector-64linux = 17.0-478468 intel-vtune-amplifier-xe-2017-common = 17.0-478468 intel-vtune-amplifier-xe-2017-common-pset = 17.0-478468 intel-vtune-amplifier-xe-2017-doc = 17.0-478468 intel-vtune-amplifier-xe-2017-gui = 17.0-478468 intel-vtune-amplifier-xe-2017-gui-common = 17.0-478468 intel-vtune-amplifier-xe-2017-sep = 17.0-478468 fwein@eamc061:~/tmp> -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Op donderdag 9 maart 2017 15:15:19 CET schreef Fabian Wein:
Hello,
I'm a TW user and hope that I'm right here with my question, if the forum is more appropriate, please tell me.
I have TW and the following commercial intel packages installed: C/C++, Fortran, MKL (part of the compiler) and vTune Amplifier. The software is installed by a script and it always takes some time to install.
I used to do zypper up because with zypper dup I have to reinstall my intel stuff and it always takes more than an hour.
Recently I did a zypper up but no after some hours away I cannot log in graphically. I just see the mouse. After init 3 followed by init 5 on the text console I get an ugly X window displaying "could not syn environment to dbus.". I assume that a zypper dup might help?! BTW I use nuveau (as far as I know). I use KDE.
However zypper dup --no-allow-vendor-change will remove my intel stuff.
sudo zypper dup --no-allow-vendor-change Warning: You are about to do a distribution upgrade with all enabled repositories. Make sure these repositories are compatible before you continue. See 'man zypper' for more information about this command. Retrieving repository 'Packman Repository' metadata ............................................................................ ...............................................[done] Building repository 'Packman Repository' cache ............................................................................ ....................................................[done] Loading repository data... Reading installed packages... Computing distribution upgrade...
Problem: problem with installed package libuchardet0-0.0.6-2.1.x86_64 Solution 1: install libuchardet0-0.0.6-1.1.x86_64 (with vendor change) http://packman.links2linux.de --> openSUSE
Choose the above solution using '1' or cancel using 'c' [1/c] (c): 1 Resolving dependencies... Computing distribution upgrade...
The following 3 items are locked and will not be changed by any action: Installed: intel-icsxe-pset intel-mpi-rt-core-109 intel-mpi-rt-mic-109
The following application is going to be installed: digiKam
The following 16 NEW packages are going to be installed: digikam digikam-lang gnome-nettool-lang k3b-lang kernel-default-4.10.1-1.3 kernel-default-devel-4.10.1-1.3 libixion-0_12-0 liborcus-0_12-0 libstaroffice-0_0-0 libzmf-0_0-0 perl-File-Find-Rule perl-Number-Compare perl-Text-Glob pulseaudio-esound-compat python3-appdirs python3-packaging
The following 2 applications are going to be REMOVED: Desktop "System Tray"
The following 102 packages are going to be REMOVED: baloo-core baloo-kioslaves esound-daemon intel-ccomp-doc intel-ccompxe intel-ccompxe-doc intel-comp-all-doc intel-comp-l-all-common-109 intel-comp-l-all-devel-109 intel-comp-l-all-vars-109 intel-comp-l-ps-common-109 intel-comp-l-ps-devel-109 intel-comp-l-ps-ss-devel-109 intel-comp-ps-ss-doc intel-daal-psxe-047 intel-fcomp-doc intel-fcompxe intel-fcompxe-doc intel-gdb intel-gdb-common intel-gdb-doc intel-gdb-ps-cdt intel-gdb-ps-cdt-source intel-gdb-ps-common intel-gdb-ps-doc intel-gdb-ps-mic intel-gdb-ps-mpm intel-icc-doc intel-icc-l-all-109 intel-icc-l-all-common-109 intel-icc-l-all-devel-109 intel-icc-l-all-vars-109 intel-icc-l-ps-common-109 intel-icc-l-ps-devel-109 intel-icc-l-ps-ss-109 intel-icc-l-ps-ss-devel-109 intel-icc-ps-doc intel-icc-ps-ss-doc intel-ifort-l-ps-109 intel-ifort-l-ps-common-109 intel-ifort-l-ps-devel-109 intel-ifort-l-ps-vars-109 intel-ifort-ps-doc intel-ipp-psxe-047 intel-mkl-109 intel-mkl-common-109 intel-mkl-devel-109 intel-mkl-doc intel-mkl-gnu-109 intel-mkl-gnu-devel-109 intel-mkl-ps-109 intel-mkl-ps-cluster-109 intel-mkl-ps-cluster-common-109 intel-mkl-ps-cluster-devel-109 intel-mkl-ps-common-109 intel-mkl-ps-doc intel-mkl-ps-f95-common-109 intel-mkl-ps-f95-devel-109 intel-mkl-ps-gnu-109 intel-mkl-ps-gnu-devel-109 intel-mkl-psxe-047 intel-openmp-l-all-109 intel-openmp-l-all-devel-109 intel-openmp-l-ps-109 intel-openmp-l-ps-devel-109 intel-openmp-l-ps-mic-109 intel-openmp-l-ps-mic-devel-109 intel-openmp-l-ps-ss-109 intel-openmp-l-ps-ss-devel-109 intel-psxe-common intel-psxe-doc intel-tbb-psxe-047 kernel-default-4.10.1-1.2 kernel-default-devel-4.10.1-1.2 kfilemetadata libass5 libbaloofiles4 libbaloopim4 libbalooqueryparser4 libbaloowidgets4 libevent-2_0-5 libgrantlee_core0 libgrantlee_gui0 libixion-0_11-0 liborcus-0_11-0 libpackagekitqt4-0 libsoprano4 libwx_baseu-suse1 libwx_baseu_net-suse1 libwx_baseu_xml-suse1 libwx_gtk2u_adv-suse1 libwx_gtk2u_aui-suse1 libwx_gtk2u_core-suse1 libwx_gtk2u_gl-suse1 libwx_gtk2u_html-suse1 libwx_gtk2u_media-suse1 libwx_gtk2u_propgrid-suse1 libwx_gtk2u_qa-suse1 libwx_gtk2u_richtext-suse1 libwx_gtk2u_stc-suse1 libwx_gtk2u_webview-suse1 libwx_gtk2u_xrc-suse1
The following 88 packages are going to be upgraded: apparmor-utils dbus-1-python3 gnome-music libapparmor-devel libapparmor1 libreoffice libreoffice-base libreoffice-base-drivers-mysql libreoffice-calc libreoffice-calc-extensions libreoffice-draw libreoffice-filters-optional libreoffice-gnome libreoffice-gtk3 libreoffice-icon-theme-tango libreoffice-impress libreoffice-kde4 libreoffice-l10n-en libreoffice-mailmerge libreoffice-math libreoffice-pyuno libreoffice-writer libreoffice-writer-extensions libreofficekit libstdc++6-32bit orca perl-apparmor python3 python3-Cycler python3-Cython python3-apparmor python3-atspi python3-base python3-bottle python3-brlapi python3-cairo python3-cairocffi python3-cffi python3-chardet python3-coverage python3-cryptography python3-cssselect python3-cups python3-cupshelpers python3-curses python3-dbm python3-devel python3-gedit python3-gmpy python3-gobject python3-gobject-Gdk python3-gobject-cairo python3-gobject2 python3-h5py python3-idle python3-idna python3-louis python3-lxml python3-matplotlib python3-matplotlib-cairo python3-matplotlib-gtk2 python3-matplotlib-tk python3-mpmath python3-nose python3-numpy python3-numpy-devel python3-pip python3-pyOpenSSL python3-pyasn1 python3-pycparser python3-pycurl python3-pyparsing python3-python-dateutil python3-pytz python3-qt5 python3-requests python3-scipy python3-setuptools python3-simplejson python3-sip python3-smbc python3-speechd python3-sympy python3-tk python3-urllib3 python3-vtk python3-vtk-qt python3-wheel
The following 3 packages are going to be downgraded: desktop-translations libuchardet0 python3-six
The following package is going to be reinstalled: python3-py
The following package is going to change vendor: libuchardet0 http://packman.links2linux.de -> openSUSE
88 packages to upgrade, 3 to downgrade, 16 new, 1 to reinstall, 102 to remove, 1 to change vendor.
Shall I lock more? Currently I have sudo zypper locks
# | Name | Type | Repository --+-----------------------+---------+----------- 1 | intel-mpi-rt-core-109 | package | (any) 2 | intel-mpi-rt-mic-109 | package | (any) 3 | intel-icsxe-pset | package | (any)
And this are my repos: sudo zypper repos Repository priorities are without effect. All enabled repositories share the same priority.
# | Alias | Name
| Enabled | GPG Check | Refresh
---+-------------------------------------+-----------------------------+---- -----+-----------+-------- 1 | adobe | adobe
| Yes | ( p) Yes | Yes
2 | google-chrome | google-chrome
| Yes | (r ) Yes | Yes
3 | home_AndnoVember_test | Test (openSUSE_Factory)
| Yes | (r ) Yes | No
4 | http-download.opensuse.org-22f95660 | windows:mingw
| No | ---- | ----
5 | http-download.opensuse.org-512bc994 | home:tiwai:kernel:4.4
| Yes | (r ) Yes | Yes
6 | http-download.opensuse.org-f5a8b2d7 | science
| No | ---- | ----
7 | http-download.opensuse.org-ff1a1965 | Office
| Yes | (r ) Yes | Yes
8 | http-download.opensuse.org-ffb3672f | windows:mingw:win64
| Yes | (r ) Yes | Yes
9 | http-ftp.gwdg.de-5c2dab74 | Packman Repository
| Yes | (r ) Yes | Yes
10 | http-opensuse-guide.org-a3f71627 | libdvdcss repository
| Yes | (r ) Yes | Yes
11 | openSUSE-20151002-0 | openSUSE-20151002-0
| No | ---- | ----
12 | repo-debug | openSUSE-Tumbleweed-Debug
| No | ---- | ----
13 | repo-non-oss | openSUSE-Tumbleweed-Non-Oss
| Yes | (r ) Yes | Yes
14 | repo-oss | openSUSE-Tumbleweed-Oss
| Yes | (r ) Yes | Yes
15 | repo-source | openSUSE-Tumbleweed-Source
| No | ---- | ----
16 | repo-update | openSUSE-Tumbleweed-Update
| Yes | (r ) Yes | Yes
I Settings/Configure Desktop Screen locking is deactivated.
Any ideas? Or shall I ask at another place?
Thanks,
Fabian
Put your intel stuff in a repo "Intel stuff" zypper dup --from Intel\ stuff zypper dup --no-allow-vendor-change AFAICT that should help you on the way -- Gertjan Lettink, a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Put your intel stuff in a repo "Intel stuff" You mean plaindir repo as I just learned from Olaf?
zypper dup --from Intel\ stuff zypper dup --no-allow-vendor-change
AFAICT that should help you on the way
I do not really understand. The two dups are independent of each other, right?! Do you mean that with zypper dup --from Intel\ stuff that I shall skip intel upgrade by install.sh but add the newer rpms to the plaindir repo? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2017-03-09 18:20, Fabian Wein wrote:
Put your intel stuff in a repo "Intel stuff" You mean plaindir repo as I just learned from Olaf?
zypper dup --from Intel\ stuff zypper dup --no-allow-vendor-change
AFAICT that should help you on the way
I do not really understand. The two dups are independent of each other, right?!
Do you mean that with zypper dup --from Intel\ stuff that I shall skip intel upgrade by install.sh but add the newer rpms to the plaindir repo?
What exactly does that script do? Can the packages be installed without that script? - -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iF4EAREIAAYFAljCyz8ACgkQja8UbcUWM1xf0QEAjEOSsIObj5axeVW/CX+aplWT zGeglAjTco6gXS+DAZgA/1zaS+ypO3L6zxJ8oi1s36CPR76IkpnZMJKfSPkMqLFK =pqYa -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am Donnerstag, 9. März 2017, 15:15:19 CET schrieb Fabian Wein:
Hello,
I'm a TW user and hope that I'm right here with my question, if the forum is more appropriate, please tell me.
I have TW and the following commercial intel packages installed: C/C++, Fortran, MKL (part of the compiler) and vTune Amplifier. The software is installed by a script and it always takes some time to install.
I used to do zypper up because with zypper dup I have to reinstall my intel stuff and it always takes more than an hour.
Recently I did a zypper up but no after some hours away I cannot log in graphically. I just see the mouse. After init 3 followed by init 5 on the text console I get an ugly X window displaying "could not syn environment to dbus.". I assume that a zypper dup might help?! BTW I use nuveau (as far as I know). I use KDE.
However zypper dup --no-allow-vendor-change will remove my intel stuff.
maybe bug 966000? https://bugzilla.suse.com/show_bug.cgi?id=966000 Marc
participants (11)
-
Alin M Elena -
Carlos E. R. -
Fabian Wein -
Ken Schneider - Factory -
Knurpht - Gertjan Lettink -
Marc Dietrich -
Olaf Hering -
Patrick B. Shanahan -
Patrick Shanahan
-
Peter Suetterlin -
Richard Biener