[Bug 1040356] New: unmotivated downgrade of libopenssl1 when trying to install openQA
http://bugzilla.opensuse.org/show_bug.cgi?id=1040356 Bug ID: 1040356 Summary: unmotivated downgrade of libopenssl1 when trying to install openQA Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/407183#step/openqa_w ebui/9 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Patterns Assignee: dimstar@opensuse.org Reporter: okurz@suse.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- ## Observation openQA test trying to install openQA on last released snapshot before last released (20170516) fails in [openqa_webui](https://openqa.opensuse.org/tests/407183#step/openqa_webui/9) with ``` Problem: openQA-4.4.1495306603.5c05c24-3.4.noarch requires git-core, but this requirement cannot be provided uninstallable providers: git-core-2.13.0-1.1.i586[openSUSE-20170516-0] git-core-2.13.0-1.1.i86_64[openSUSE-20170516-0] Solution 1: dowmgrade of libopenssl1_0_0-1.0.2k-3.1.i86_64 to libopenssl1_0_0-1.0.2k-1.2.i86_64 Solution 2: install git-core-2.13.0-1.1.i586 despite the inferior architecture Solution 3: do not install openQA-4.4.1495306603.5c05c24-3.4.noarch Solution 4: break openQA-4.4.1495306603.5c05c24-3.4.noarch by ignoring some of its dependencies ``` ## Reproducible Fails as it seems when trying to install a new package in 20170516 after 20170521 just got released. ## Expected result Trying to install a new package should not need to pull in a new version. Also libopenssl1 should have a release counter higher than the previous one on a new package release. ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?flavor=dev&test=openqa_install%2Bpublish&machine=64bit&arch=x86_64&distri=openqa) -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1040356 http://bugzilla.opensuse.org/show_bug.cgi?id=1040356#c1 Dominique Leuenberger <dimstar@opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |WONTFIX --- Comment #1 from Dominique Leuenberger <dimstar@opensuse.org> --- Nothing is unmotivated openssl changed the source package name from openssl to openssl-1_0_0 - which caused a rebuild counter reset for OBS Your system is inconsistent - run zypper dup -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1040356 http://bugzilla.opensuse.org/show_bug.cgi?id=1040356#c2 --- Comment #2 from Oliver Kurz <okurz@suse.com> --- Do you know why `zypper install` wants to pull in a different version of libopenssl1? Do I need to call `zypper dup --no-allow-vendor-change` every time I want to install a package to ensure I don't get conflicts? I am thinking about confused users here. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1040356 http://bugzilla.opensuse.org/show_bug.cgi?id=1040356#c3 --- Comment #3 from Dominique Leuenberger <dimstar@opensuse.org> --- (In reply to Oliver Kurz from comment #2)
Do you know why `zypper install` wants to pull in a different version of libopenssl1?
Do I need to call `zypper dup --no-allow-vendor-change` every time I want to install a package to ensure I don't get conflicts? I am thinking about confused users here.
Your system is not up-to-date and between the snapshot you run and the one published, openssl has seen quite some changes with versioned symbols. your openQA package (and/or deps) are linked against the new version of libopenssl1 which provides those symbols - hence doing zypper in wants to solve this by getting this newer version. It's a rare corner case where such massive changes happen together with a package count reset - but they can happen. The good thing is with the new packaging style, openssl 1.1 can start existing and they should not destroy each other... so the small pain here is worth a lot of gain -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com