Bug 366919

Summary: Check dependency resolution for software management
Product: [openSUSE] openSUSE 10.3 Reporter: Markus Elfring <Markus.Elfring>
Component: YaST2Assignee: Harald Mueller-Ney <hmuelle>
Status: RESOLVED INVALID QA Contact: Jiri Srain <jsrain>
Severity: Normal    
Priority: P5 - None CC: ast, coolo, hmuelle
Version: Final   
Target Milestone: ---   
Hardware: x86-64   
OS: openSUSE 10.3   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: screenshot
YaST notices
repository list

Description Markus Elfring 2008-03-04 12:45:53 UTC
Created attachment 198493 [details]
screenshot

I noticed that there are software packages like for the recent NVIDIA G01 driver where the update selection of a component automatically results in an update of the corresponding parts.

I have found an other package where it does not work in this convenient way.
If I want to update to the current Thunderbird 2.0.0.12, a warning is displayed. I can accept the suggested conflict resolution to delete the previous translations. The dustbin symbol is displayed for this list entry. The refresh symbol is displayed after I have pressed the key "+" there. But I do not get a conflict message. I wonder why the dependencies can only be manually resolved in this small use case.

A similar issue happened with OpenOffice some weeks ago.

By the way: I would appreciate the support for copying of message text from the warning dialogue to the clipboard.
Comment 1 Stefan Hundhammer 2008-03-28 10:26:59 UTC
That's a resolver problem, not a problem of the UI.

> By the way: I would appreciate the support for copying of message text from 
> the warning dialogue to the clipboard.

    "Expert" -> "Save to Text File"

doesnt' work for you?
Comment 2 Markus Elfring 2008-03-29 10:02:33 UTC
>     "Expert" -> "Save to Text File"
> doesnt' work for you?

Single lines can be marked in the tree view. It would be convenient if a copy action will be supported.
Comment 3 Markus Elfring 2008-03-29 10:10:07 UTC
Created attachment 204801 [details]
YaST notices

Has the resolver software component got problems with dependency resolution for translation packages?
Comment 4 Stefan Schubert 2008-04-22 16:04:22 UTC
I would say the the translation packages are not available for the new mozilla.
Harald, Anja is this intent ?
Comment 5 Harald Mueller-Ney 2008-04-22 16:26:13 UTC
Current version for openSUSE 10.3 is MozillaFirefox 2.0.0.13

It is part of patch update: patch-MozillaFirefox-5135.xml

Looking at the patch metadata of mentioned patch update:
-----------------------------------------------------------------------------
     <name>MozillaFirefox-translations</name>
      <arch>x86_64</arch>
      <version epoch="0" ver="2.0.0.13" rel="0.1"/>
      <checksum type="sha" pkgid="YES">5b8ee4567f4cce0e697cfdebfd7154f5618bbeca</checksum>
      <time file="1206703556" build="1206629361"/>
      <size package="5203414" installed="29505361" archive="29518968"/>
      <location href="rpm/x86_64/MozillaFirefox-translations-2.0.0.13-0.1.x86_64.rpm"/>
-----------------------------------------------------------------------------

Please provide a list of update sources used - I assume the mirror used is outdated.

If you could reproduce this issue, would you be so kind to attach an solver test case:

http://en.opensuse.org/Bugs/YaST#I_want_to_report_a_bug_related_to_package_dependencies_and_libzypp_solver._Which_logs_to_attach.3F

I could not reproduce this error on any of my system here at work or at home. I use openSUSE redirector and at home hard coded ftp5.gwdg.de (or was it ftp1?)
Comment 6 Markus Elfring 2008-04-22 16:43:06 UTC
My Firefox is at the version 2.0.0.14-2.1 currently.
The are still a few update problems with translations and "lang" packages.

I can not append a solver test case to this issue tracker because the corresponding compressed file will be bigger than your upload limit (10 MB).
Comment 7 Markus Elfring 2008-04-22 16:57:15 UTC
I occasionally "overwrite" the indicated deletion with a "forced" update (key "+") for various software items in YOU.
Comment 8 Harald Mueller-Ney 2008-04-22 17:09:10 UTC
It is not an issue with our released update repository - the needed file is in place and referenced in the repository.

Providing a list of repositories (sources) might help. 
Provide the output of following commandline:

rpm -qa "MozillaFirefox*" --qf "%{NAME}-%{VERSION}-%{RELEASE}-%{ARCH}\n"

Comment 9 Harald Mueller-Ney 2008-04-22 17:14:09 UTC
(In reply to comment #8 from Harald Mueller-Ney)
> Providing a list of repositories (sources) might help. 
Reading it again after having it send, it might be clear.
A list of repositories(sources) you have enabled might help to solve this issue.

Currently it does not look like a bug to me and we have no other reports of this kind.
Comment 10 Markus Elfring 2008-04-22 17:51:53 UTC
Created attachment 209693 [details]
repository list
Comment 11 Harald Mueller-Ney 2008-04-23 09:05:56 UTC
You use the "download.opensuse.org" redirector for most of your repositories, it is not clear to me which repository is really used for openSUSE updates.

It doesn't really matter for the Mozilla issue, cause you have also Mozilla BuildService repository:
http://download.opensuse.org/repositories/mozilla/openSUSE_10.3/repodata/

This is maintained by community member Wolfgang Rosenauer, it often has newer Mozilla versions before our official update repository. Wolfgang is an active member of Mozilla community.

There is no bug in our repositories, you might ask on opensuse ML for help or if more people run in to this issue. Looking at the current repodata of Mozilla repository also points into direction no issue in repository.
You use many repositories, which make it hard to say anything without good logs/solver testcase.

My suggestion you be, completely remove all Mozilla packages and install these agian from scratch.
Comment 12 Markus Elfring 2008-04-23 10:14:13 UTC
Other software can also be affected. Which package specifications result in a requested deletion of language/translation parts while it is accepted to mark them for an update afterwards?

Are you going to increase the upload limit for solver test cases to 15 or 20 MB?
Comment 13 Harald Mueller-Ney 2008-04-23 11:58:52 UTC
Using many respositories from various sources - build service repositories are "maintained" by various community members. It is always possible to run in such situations.

We could and will not test our update repositories against all combinations of community repositories. Dependencies are cross repository so all repositories could influence behavior.