|
Bugzilla – Full Text Bug Listing |
| Summary: | pattern devel_basis: dependency issues on current Tumbleweed | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE Tumbleweed | Reporter: | Forgotten User FP9qWSQboW <forgotten_FP9qWSQboW> |
| Component: | YaST2 | Assignee: | YaST Team <yast-internal> |
| Status: | RESOLVED WONTFIX | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Minor | ||
| Priority: | P5 - None | CC: | ancor, chcao, forgotten_FP9qWSQboW, igonzalezsosa |
| Version: | Current | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| URL: | https://trello.com/c/dXEZLOTc | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
Hi Dominique, would you please help to take a look at this issue? Thank you! Peter, You must have some conflicting repositories configured (likely the DVD enabled?) The issue for you is that libgcc_s1-gcc6 is no longer available since the switch to GCC6 as the default compiler (the -gcc<VER> packages are the secondary compilers) To properly fix your issues, I recommend you: * Check your repositories enabled (remove the DVD if enabled, it does not make sense for Tumbleweed, as it's outdated 'the day it's released' - which is due to the rolling nature of Tumbleweed * Once all repos are fine, run "sudo zypper dup" this is likely going to put some changes in place (one of them being libgcc_s1-gcc6 to be removed) * You should then be able to install pattern devel_basis without issues. (In reply to Dominique Leuenberger from comment #2) As I wasn't sure whether I had fiddled with the repositories on the system in question I installed two new systems using ISOs "Current" and "NET" respectively. On the former repo "openSUSE-<date>-0" was disabled and pointing to the ODD, on the latter it was enabled and pointing to the same URL as download.opensuse.org-oss. After enabling repos "openSUSE-<date>-0" and having them point to the respective installation medium devel_basis completed without errors on both systems. IMO this could have been because the installation media weren't old enough to trigger the problem or, less likely, the problem is caused by a reason other than the one you stated. For now I'd suggest I'll wait some time until the media have become a bit older and try once more to reproduce the problem then. The installation medium on Tumbleweed is not to be enabled any day longer than you install the system - this is a rolling distro and the DVD becomes obsolete basically the day after. (In reply to Dominique Leuenberger from comment #4) > The installation medium on Tumbleweed is not to be enabled any day longer > than you install the system - this is a rolling distro and the DVD becomes > obsolete basically the day after. You mentioned this in comment 2 already. Intentionally enabling the media nevertheless as stated in comment 3 was meant to help figure out whether or not this could have been the reason of the problem we're discussing in this issue. I think I have to pass that one on to the YaST Team - maybe there is a control flag I miss But the 'issue' can be seen also in openQA, e.g: https://openqa.opensuse.org/tests/306315#step/zypper_lr/5 After the installation, the DVD medium, as well as the FTP tree, are enabled. With TW's fast moving situation, the DVD becomes obsolete too quick to make sense to remain a valid repository for the running system (it makes sense for regular releases such as Leap) In the past, we implemented support to disable the installation source if the system was registered (SLE 12 SP2). To do that, YaST2 checks whether all products from the installation source are available through online repositories. In that case, installation source is disabled. See https://github.com/yast/yast-packager/pull/157/files for details. With Tumbleweed, the situation is slightly different. When you compare products (see [Product class](https://github.com/yast/yast-yast2/blob/master/library/packages/src/lib/packages/product.rb#L45), usually the versions are different (for example 20161120-0 vs 20161119-0). I'm adding this bug to our SCRUM incoming board so we can plan for it. I don't think this is failing anymore in a current Tumbleweed. This looks to me like an old forgotten bug report. So I'm closing it. Please feel free to reopen is this is still an issue. |
On current Tumbleweed systems installing pattern devel_basis fails due to dependency issues. > # zypper install -t pattern devel_basis > Loading repository data... > Reading installed packages... > Resolving package dependencies... > > Problem: pattern:devel_basis-20151112-17.1.x86_64 requires patterns-openSUSE-devel_basis, but this requirement cannot be provided > uninstallable providers: patterns-openSUSE-devel_basis-20151112-17.1.i586[download.opensuse.org-oss] > patterns-openSUSE-devel_basis-20151112-17.1.x86_64[download.opensuse.org-oss] > patterns-openSUSE-devel_basis-20151112-17.1.i586[openSUSE-20160531-0] > patterns-openSUSE-devel_basis-20151112-17.1.x86_64[openSUSE-20160531-0] > Solution 1: deinstallation of libgcc_s1-gcc6-6.1.1+r236988-1.1.x86_64 > Solution 2: do not install pattern:devel_basis-20151112-17.1.x86_64 > Solution 3: do not install pattern:devel_basis-20151112-17.1.x86_64 > Solution 4: break pattern:devel_basis-20151112-17.1.x86_64 by ignoring some of its dependencies > > Choose from above solutions by number or cancel [1/2/3/4/c] (c): c Not sure whether you'll potentially consider this as an issue that may just happen due to the nature of Tumbleweed. But IMO it would help a lot if this pattern could be installed the normal way, in particular as the proposed "Solutions" don't seem to work too well either. Btw., the problem can not be seen in Leap 42.1.