On Fri, 01 Dec 2017 08:36:15 +0100, Dominique Leuenberger / DimStar wrote:

Hi all,

On Thu, 2017-11-30 at 22:33 +0200, Stratos Zolotas wrote:

...

Hello,

I'm getting the following result with the latest snapshot and I can't find an obvious solution. Any possible solution results on deinstallation of multiple packages and multiple dependency problems..

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: libopenssl-1_0_0-devel-1.0.2m-1.1.x86_64 conflicts with libopenssl-devel > 1.0.2m provided by libopenssl-devel-1.1.0g-1.1.noarch Problem: openssl-1.1.0g-1.1.noarch requires openssl-1_1_0 = 1.1.0g, but this requirement cannot be provided

...

Problem: libopenssl-1_0_0-devel-1.0.2m-1.1.x86_64 conflicts with libopenssl-devel > 1.0.2m provided by libopenssl-devel-1.1.0g-1.1.noarch Solution 1: deinstallation of libopenssl-1_0_0-devel-1.0.2m- 1.1.x86_64 Solution 2: deinstallation of libopenssl-devel-1.0.2m-1.1.noarch Solution 3: keep obsolete libopenssl-devel-1.0.2m-1.1.noarch

Choose from above solutions by number or skip, retry or cancel [1/2/3/s/r/c] (c):

Seems we missed an obsoletes for the -devel package. The best answer depends on why you even have libopenssl-devel installed on your system. The 'Tumbleweed default' should be to 'deinstall libopenssl-1_0_0- devel', which would then pull in libopenssl-1_1_0-devel instead.

Packages that depend on 1.0.2m: # zypper rm libopenssl-devel-1.0.2m-1.1.noarch Loading repository data... Reading installed packages... Resolving package dependencies... The following 9 packages are going to be REMOVED: libetpan-devel libksane-devel libmysqlclient-devel libopenssl-devel libserf-devel libssh2-devel net-snmp-devel sane-backends-devel wvstreams-devel 9 packages to remove. After the operation, 13.0 MiB will be freed. Continue? [y/n/...? shows all options] (y): Packages that block moving forward: # zypper up libopenssl-devel Loading repository data... Reading installed packages... Resolving package dependencies... Problem: libopenssl-1_0_0-devel-1.0.2m-1.1.x86_64 conflicts with libopenssl-devel > 1.0.2m provided by libopenssl-devel-1.1.0g-1.1.noarch Solution 1: Following actions will be done: deinstallation of libopenssl-1_0_0-devel-1.0.2m-1.1.x86_64 deinstallation of libqt4-devel-4.8.7-9.1.x86_64 deinstallation of phonon-devel-4.9.0-1.7.x86_64 deinstallation of gstreamer-plugins-qt-devel-1.2.0-7.2.x86_64 deinstallation of libQtWebKit-devel-4.8.7+2.3.4-3.5.x86_64 deinstallation of libakonadiprotocolinternals-devel-1.13.0-10.2.x86_64 deinstallation of libattica-devel-0.4.2-5.9.x86_64 deinstallation of libavahi-qt4-devel-0.6.32-4.1.x86_64 deinstallation of libpolkit-qt-1-devel-0.112.0-1.7.x86_64 deinstallation of libpoppler-qt4-devel-0.59.0-2.1.x86_64 deinstallation of libqimageblitz-devel-0.0.6-13.9.x86_64 deinstallation of libqjson-devel-0.8.1-9.10.x86_64 Solution 2: do not install libopenssl-devel-1.1.0g-1.1.noarch Choose from above solutions by number or cancel [1/2/c] (c): Being me test/development box, I'd rather not de-install other packages

Depending of what kind of software you're building locally, you might want to switch between the provided openssl-1_x_0-devel packages.

Cheers, Dominique

-- H.Merijn Brand http://tux.nl Perl Monger http://amsterdam.pm.org/ using perl5.00307 .. 5.27 porting perl5 on HP-UX, AIX, and openSUSE http://mirrors.develooper.com/hpux/ http://www.test-smoke.org/ http://qa.perl.org http://www.goldmark.org/jeff/stupid-disclaimers/

On Fri, 01 Dec 2017 10:20:56 +0100, Dominique Leuenberger / DimStar wrote:

On Fri, 2017-12-01 at 10:12 +0100, H.Merijn Brand wrote:

...

2 Problems: [...]

...

Seems we missed an obsoletes for the -devel package. The best answer depends on why you even have libopenssl-devel installed on your system. The 'Tumbleweed default' should be to 'deinstall libopenssl-1_0_0- devel', which would then pull in libopenssl-1_1_0-devel instead.

Packages that depend on 1.0.2m:

# zypper rm libopenssl-devel-1.0.2m-1.1.noarch Loading repository data... Reading installed packages... Resolving package dependencies...

Not sure why you decided to remove libopenssl-devel and not libopenssl- 1_0_0-devel as recommended by me earlier.

I didn't want to remove it at all. I just used it to demonstrate the feedback. removing libopenssl-1_0_0-devel suggests to uninstall even more # rpm -qa | grep openssl | sort libopenssl1_0_0-1.0.2m-1.1.x86_64 libopenssl1_0_0-32bit-1.0.2m-1.1.x86_64 libopenssl-1_0_0-devel-1.0.2m-1.1.x86_64 libopenssl1_0_0-steam-32bit-1.0.2m-1.1.x86_64 libopenssl1_1_0-1.1.0g-2.1.x86_64 libopenssl1_1_0-32bit-1.1.0g-2.1.x86_64 libopenssl-devel-1.0.2m-1.1.noarch openssl-1_0_0-1.0.2m-1.1.x86_64 openssl-1.0.2m-1.1.noarch php7-openssl-7.1.11-2.2.x86_64 # zypper rm libopenssl-1_0_0-devel-1.0.2m-1.1.x86_64 Loading repository data... Reading installed packages... Resolving package dependencies... The following 21 packages are going to be REMOVED: gstreamer-plugins-qt-devel libakonadiprotocolinternals-devel libattica-devel libavahi-qt4-devel libetpan-devel libksane-devel libmysqlclient-devel libopenssl-1_0_0-devel libopenssl-devel libpolkit-qt-1-devel libpoppler-qt4-devel libqimageblitz-devel libqjson-devel libqt4-devel libQtWebKit-devel libserf-devel libssh2-devel net-snmp-devel phonon-devel sane-backends-devel wvstreams-devel 21 packages to remove. After the operation, 49.3 MiB will be freed. Continue? [y/n/...? shows all options] (y):

There are some more changes piled up for openssl 1.0/1.1 to be a bit less aggressive on each other. But I can't yet estimate when those will reach Tumbleweed.

I'll wait :)

Cheers Dominique

-- H.Merijn Brand http://tux.nl Perl Monger http://amsterdam.pm.org/ using perl5.00307 .. 5.27 porting perl5 on HP-UX, AIX, and openSUSE http://mirrors.develooper.com/hpux/ http://www.test-smoke.org/ http://qa.perl.org http://www.goldmark.org/jeff/stupid-disclaimers/

On Fri, 01 Dec 2017 10:43:11 +0100, Dominique Leuenberger / DimStar wrote:

On Fri, 2017-12-01 at 10:32 +0100, H.Merijn Brand wrote:

...

I didn't want to remove it at all. I just used it to demonstrate the feedback. removing libopenssl-1_0_0-devel suggests to uninstall even more

# rpm -qa | grep openssl | sort libopenssl1_0_0-1.0.2m-1.1.x86_64 libopenssl1_0_0-32bit-1.0.2m-1.1.x86_64 libopenssl-1_0_0-devel-1.0.2m-1.1.x86_64 libopenssl1_0_0-steam-32bit-1.0.2m-1.1.x86_64 libopenssl1_1_0-1.1.0g-2.1.x86_64 libopenssl1_1_0-32bit-1.1.0g-2.1.x86_64 libopenssl-devel-1.0.2m-1.1.noarch openssl-1_0_0-1.0.2m-1.1.x86_64 openssl-1.0.2m-1.1.noarch php7-openssl-7.1.11-2.2.x86_64

call zypper dup - and at the question on how to handle openssl upgrade, pick the option to uninstall libopenssl-1_0_0-devel

Oh, I did, and I chose Cancel :) # zypper dup 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: libopenssl-1_0_0-devel-1.0.2m-1.1.x86_64 conflicts with libopenssl-devel > 1.0.2m provided by libopenssl-devel-1.1.0g-1.1.noarch Problem: libopenssl-1_0_0-devel-1.0.2m-1.1.x86_64 requires openssl-1_0_0 = 1.0.2m, but this requirement cannot be provided Problem: libopenssl-1_0_0-devel-1.0.2m-1.1.x86_64 conflicts with libopenssl-devel > 1.0.2m provided by libopenssl-devel-1.1.0g-1.1.noarch Solution 1: deinstallation of libopenssl-1_0_0-devel-1.0.2m-1.1.x86_64 Solution 2: deinstallation of libopenssl-devel-1.0.2m-1.1.noarch Solution 3: keep obsolete libopenssl-devel-1.0.2m-1.1.noarch Choose from above solutions by number or skip, retry or cancel [1/2/3/s/r/c] (c): 1 Problem: libopenssl-1_0_0-devel-1.0.2m-1.1.x86_64 requires openssl-1_0_0 = 1.0.2m, but this requirement cannot be provided Solution 1: Following actions will be done: deinstallation of openssl-1.0.2m-1.1.noarch deinstallation of sendmail-starttls-8.15.2-10.2.noarch deinstallation of ca-certificates-2+git20170807.10b2785-1.2.noarch deinstallation of kernel-syms-4.14.2-1.6.x86_64 deinstallation of kernel-syms-4.14.1-1.4.x86_64 deinstallation of ca-certificates-mozilla-2.11-2.1.noarch deinstallation of python2-certifi-2017.11.5-1.1.noarch deinstallation of python2-httplib2-0.10.3-1.1.noarch deinstallation of python2-requests-2.18.4-1.1.noarch deinstallation of python3-certifi-2017.11.5-1.1.noarch deinstallation of python3-pip-9.0.1-3.1.noarch deinstallation of python3-requests-2.18.4-1.1.noarch deinstallation of python3-Sphinx-1.6.5-1.2.noarch deinstallation of dbus-sharp-0.7.0-17.7.noarch deinstallation of dbus-sharp-glib-0.5.0-14.5.noarch deinstallation of dbus-sharp-glib2-0.6.0-1.5.noarch deinstallation of dbus-sharp2-0.8.1-2.3.noarch deinstallation of log4net-1.2.10-75.8.noarch deinstallation of mono-addins-1.3-2.3.noarch deinstallation of mono-basic-4.6-1.2.noarch deinstallation of xsp-3.0.11-9.1.noarch deinstallation of taglib-sharp-2.1.0.0-7.12.noarch deinstallation of nunit-2.6.4-2.3.noarch deinstallation of ndesk-dbus-glib-0.4.1-59.5.noarch deinstallation of ndesk-dbus-0.6.0-85.8.noarch deinstallation of libpurple-branding-openSUSE-42.2-1.4.noarch deinstallation of zypper-migration-plugin-0.10.1488806253.1c712c3-1.2.noarch deinstallation of rollback-helper-0.1-2.1.noarch deinstallation of tomboy-lang-1.15.9-1.2.noarch deinstallation of system-config-printer-applet-1.5.7-12.1.noarch deinstallation of python3-Sphinx-doc-man-1.6.5-1.2.noarch deinstallation of python3-docrepr-0.1.0-1.2.noarch Solution 2: deinstallation of libqt4-devel-4.8.7-9.1.x86_64 Solution 3: keep obsolete openssl-1.0.2m-1.1.noarch Solution 4: break libopenssl-1_0_0-devel-1.0.2m-1.1.x86_64 by ignoring some of its dependencies Choose from above solutions by number or skip, retry or cancel [1/2/3/4/s/r/c] (c): e.g. I check if packages are removed. For most, (often) a zupper dup will show the removal of packages where a newer version is installed, but e.g. kernel-syms removes all with no newer available. Why? Why are ca-certificates removed instead of upgraded/updated?

There is no reason trying to do the whole migration manually. Let computers do what they can best: find solutions to tricky problems.

I agree, but I like to keep my stuff working till I am confident. My "normal" procedure 1. save the list of currently installed packages # rpm -qa --queryformat='%{NAME}\n' | sort -u > TW-`date '+%Y%m%d'`.lst 2. Refresh repos # zypper ref 3. Check what's new # zypper lu 4. Update # zypper up -l 5. Dist update # zypper dup -l If in 4. or 5. packages are to be removed, I will investigate a. Will it be replaced by something newer/better b. Do I need it for something If I want to keep it (for whatever reason), I either lock it or make a backup and re-install it after I'm done updating e.g. I am *very* *very* *very* fond on keeping Opera-12.16 running, even though I have all alternatives available: # rpm -qa | grep -i -e opera -e vivaldi -e chromium -e google-chr -e moon -e epiph -e konqer -e lynx -e links -e w3m -e firef -e midori -e otter -e pzilla | sort chromium-62.0.3202.94-2.1.x86_64 chromium-plugin-widevinecdm-1.4.8.1029-1.1.x86_64 elinks-0.11.996-2.7.x86_64 epiphany-3.26.2-1.1.x86_64 epiphany-branding-openSUSE-42.1-7.8.noarch epiphany-lang-3.26.2-1.1.noarch gnome-shell-search-provider-epiphany-3.26.2-1.1.x86_64 google-chrome-beta-63.0.3239.18-1.x86_64 google-chrome-stable-61.0.3163.100-1.x86_64 google-chrome-unstable-64.0.3251.0-1.x86_64 libmidori-core1-0.5.11-4.1.x86_64 libplotter2-2.6-27.4.x86_64 links-2.14-2.2.x86_64 lynx-2.8.9~dev.16-1.2.x86_64 midori-0.5.11-4.1.x86_64 midori-branding-openSUSE-4.12.0-4.3.noarch midori-lang-0.5.11-4.1.noarch MozillaFirefox-57.0-1.1.x86_64 MozillaFirefox-branding-openSUSE-45-3.2.x86_64 MozillaFirefox-translations-common-57.0-1.1.x86_64 newmoon-27.6.2-1.2.x86_64 opera-12.16-1860.x86_64 opera-beta-50.0.2762.18-0.x86_64 opera-developer-51.0.2791.0-0.x86_64 otter-browser-0.9.92-1.1.x86_64 qupzilla-2.2.1-1.2.x86_64 qupzilla-gnome-keyring-2.2.1-1.2.x86_64 qupzilla-kwallet-2.2.1-1.2.x86_64 vivaldi-snapshot-1.14.1030.3-1.x86_64 w3m-0.5.3.git20161120-1.5.x86_64 w3m-inline-image-0.5.3.git20161120-1.5.x86_64

Cheers Dominique

-- H.Merijn Brand http://tux.nl Perl Monger http://amsterdam.pm.org/ using perl5.00307 .. 5.27 porting perl5 on HP-UX, AIX, and openSUSE http://mirrors.develooper.com/hpux/ http://www.test-smoke.org/ http://qa.perl.org http://www.goldmark.org/jeff/stupid-disclaimers/

On Fri, 01 Dec 2017 11:21:40 +0100, Dominique Leuenberger / DimStar wrote:

On Fri, 2017-12-01 at 11:17 +0100, H.Merijn Brand wrote:

...

Solution 2: deinstallation of libqt4-devel-4.8.7-9.1.x86_64 Solution 3: keep obsolete openssl-1.0.2m-1.1.noarch Solution 4: break libopenssl-1_0_0-devel-1.0.2m-1.1.x86_64 by ignoring some of its dependencies

Choose from above solutions by number or skip, retry or cancel [1/2/3/4/s/r/c] (c):

e.g. I check if packages are removed. For most, (often) a zupper dup will show the removal of packages where a newer version is installed, but e.g. kernel-syms removes all with no newer available. Why?

ohh.. libqt4 - yes, that beast cannot cope with openSSL 1.1; do you really still develop stuff for Qt4? you should stop this asap.

I don't but some packages I use(d) probably require(d) it (in the past)

if you must keep libqt4-devel, then you are confined to the openSSL 1.0 devel setup on your machine (which in turn will disallow many other modern things to co-exist on your machine though)

# zypper rm libqt4-devel Loading repository data... Reading installed packages... Resolving package dependencies... The following 11 packages are going to be REMOVED: gstreamer-plugins-qt-devel libakonadiprotocolinternals-devel libattica-devel libavahi-qt4-devel libpolkit-qt-1-devel libpoppler-qt4-devel libqimageblitz-devel libqjson-devel libqt4-devel libQtWebKit-devel phonon-devel I recognize poppler as something I once worked on for PDF. Anyway, that probably could go now Gone *now* zypper dup makes me confident again The following 5 packages are going to be REMOVED: libgps22 libopenssl-1_0_0-devel libSPIRV-Tools-suse3 openssl-1_0_0 pam-modules-32bit The following 2 packages are going to be upgraded: libopenssl-devel openssl DONE! (Thanks for all the feedback!)

Cheers Dominique

-- H.Merijn Brand http://tux.nl Perl Monger http://amsterdam.pm.org/ using perl5.00307 .. 5.27 porting perl5 on HP-UX, AIX, and openSUSE http://mirrors.develooper.com/hpux/ http://www.test-smoke.org/ http://qa.perl.org http://www.goldmark.org/jeff/stupid-disclaimers/

On Fri, Dec 1, 2017 at 12:14 PM, Stratos Zolotas wrote:

...

*now* zypper dup makes me confident again

The following 5 packages are going to be REMOVED: libgps22 libopenssl-1_0_0-devel libSPIRV-Tools-suse3 openssl-1_0_0 pam-modules-32bit

gpsd.spec in OBS has this: BuildRequires: pkgconfig(QtCore) >= 4.5.3 BuildRequires: pkgconfig(QtNetwork) >= 4.5.3 The OBS build used QT4 and not QT5. I suspect that is generally the case in OBS? -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On Fri, Dec 1, 2017 at 1:50 PM, Dominique Leuenberger / DimStar wrote:

The sumbols are Qt4 symbols.. the Qt5 ones are called Qt5Core and Qt5Network.

So there is no way OBS could potentially chose Qt5 with those deps specified - this is a packagers choice.

gpsd seems to want Qt4. I get this when Requiring Qt5Core and Qt5Network: Turning off Qt support, library not found. -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

new request for GPSD sent with correctly moved from QT4 to QT5 bindings :) On 1 December 2017 at 15:03, Jan Engelhardt wrote:

On Friday 2017-12-01 13:58, Roger Oberholtzer wrote:

...

On Fri, Dec 1, 2017 at 1:50 PM, Dominique Leuenberger / DimStar wrote:

...

The sumbols are Qt4 symbols.. the Qt5 ones are called Qt5Core and Qt5Network.

So there is no way OBS could potentially chose Qt5 with those deps specified - this is a packagers choice.

gpsd seems to want Qt4. I get this when Requiring Qt5Core and Qt5Network:

Turning off Qt support, library not found.

It is conceivable that the gpsd source itself also checks for "QtNetwork" rather than "Qt5Network" and thus runs into the same "issue" that the OBS resolver does/did. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Bernhard M. Wiedemann wrote:

On 2017-12-01 11:17, H.Merijn Brand wrote:

...

Solution 2: deinstallation of libqt4-devel-4.8.7-9.1.x86_64

seems to be the best choice there and maybe also a good hint on why no automatic solution could be found.

That would effectively mean QT4 is no longer supported in TW, yes? Bad choice, IMHO... -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On Dez 02 2017, Dominique Leuenberger / DimStar wrote:

Qt4 apps can still be used and can still be built for Tumbleweed.

Not in general. <buildinfo project="openSUSE:Factory" repository="standard" package="kmymoney" downloadurl="http://download.opensuse.org/repositories"> <arch>x86_64</arch> <error>unresolvable: libopenssl-1_0_0-devel conflicts with libopenssl-devel</error> <srcmd5>2d37f0343beac7cd16c7dbc36b6c24cb</srcmd5> <verifymd5>2d37f0343beac7cd16c7dbc36b6c24cb</verifymd5> <rev>54</rev> <specfile>kmymoney.spec</specfile> <file>kmymoney.spec</file> <versrel>4.8.0-8</versrel> <bcnt>3</bcnt> <release>8.3</release> <debuginfo>1</debuginfo> <subpack>kmymoney</subpack> <subpack>kmymoney-debuginfo</subpack> <subpack>kmymoney-debugsource</subpack> <subpack>kmymoney-devel</subpack> <subpack>kmymoney-doc</subpack> <subpack>kmymoney-lang</subpack> </buildinfo> Andreas. -- Andreas Schwab, SUSE Labs, schwab@suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different." -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Am Montag, 11. Dezember 2017, 11:57:17 schrieb Dominique Leuenberger / DimStar:

it might well be possible to simply put a Buildignore: openssl-devel in place and be done with it.

Yes. https://build.opensuse.org/request/show/555992 Kind Regards, Wolfgang -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org