Bug 439134

Summary: conflict resolution: replacement of X with X
Product: [openSUSE] openSUSE 11.1 Reporter: Olaf Hering <ohering>
Component: libzyppAssignee: Michael Schröder <mls>
Status: RESOLVED FIXED QA Contact: E-mail List <qa-bugs>
Severity: Normal    
Priority: P2 - High CC: captain.magnus, dmacvicar, kkaempf, rguenther, schubi
Version: Beta 3   
Target Milestone: ---   
Hardware: PowerPC   
OS: Linux   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: bug439134.tar.bz2
Added new testcase

Description Olaf Hering 2008-10-27 09:54:19 UTC
An update from 11.0 minimal+x11 without updates to 11.1beta3 leads to bogus conflict messages.
What means 'replacement of X with X'?
Shouldnt there be a 'X with Y'?


 /conflicts.txt 
#### YaST2 conflicts list - generated 2008-10-27 07:53:40 ####

nothing provides gnome-vfs2-lang = 2.23.0 needed by gnome-vfs2-2.23.0-1.23.ppc

    [ ] replacement of gnome-vfs2-2.22.0-33.1.ppc with gnome-vfs2-2.22.0-33.1.ppc



nothing provides gnome-vfs2-lang = 2.23.0 needed by gnome-vfs2-2.23.0-1.23.ppc

    [ ] Following actions will be done:
deinstallation of libgnome-2.22.0-30.1.ppc
deinstallation of mozilla-xulrunner190-gnomevfs-1.8.99.5-28.1.ppc
replacement of mozilla-xulrunner190-1.8.99.5-28.1.ppc with mozilla-xulrunner190-1.9.0.3-1.11.ppc
replacement of MozillaFirefox-2.9.95-25.1.ppc with MozillaFirefox-3.0.3-2.7.ppc
    [ ] replacement of bundle-lang-common-en-11.0-118.1.noarch with bundle-lang-common-en-11.0-118.1.noarch




#### YaST2 conflicts list END ###
Comment 1 Olaf Hering 2008-10-27 09:58:10 UTC
Created attachment 248065 [details]
bug439134.tar.bz2

logs from coconut.suse.de
Comment 2 Michael Schröder 2008-10-27 16:52:33 UTC
libzypp glitch, the satsolver deptestomatic prints:

nothing provides gnome-vfs2-lang = 2.23.0 needed by gnome-vfs2-2.23.0-1.23.ppc

- keep obsolete gnome-vfs2-2.22.0-33.1.ppc

Reassigned to schubi.
Comment 3 Stefan Schubert 2008-10-28 08:30:03 UTC
Yes, I can reproduce that error
Comment 4 Stefan Schubert 2008-10-28 08:32:59 UTC
And will take care about the special case of a distupgrade:
if (s == sd && solv->distupgrade)
    {
      POOL_DEBUG(SAT_DEBUG_RESULT, "- keep obsolete %s\n", solvable2str(pool, s));
    }
Comment 5 Stefan Schubert 2008-10-28 09:02:11 UTC
I have added a keep request for this solution:

2008-10-28 09:51:40 <1> waerden(15533) [satsolver] PoolImpl.cc(logSat):80 job: weak install gnome-vfs2-2.22.0-33.1.ppc
2008-10-28 09:51:40 <1> waerden(15533) [satsolver] PoolImpl.cc(logSat):80  - job Rule #9465:
2008-10-28 09:51:40 <1> waerden(15533) [satsolver] PoolImpl.cc(logSat):80     gnome-vfs2-2.22.0-33.1.ppc [123] (w1)
2008-10-28 09:51:40 <1> waerden(15533) [satsolver] PoolImpl.cc(logSat):80     next rules: 0 0

But this will be ignored and the next run returns the same error again.
Michael could you please check this again ?
Comment 6 Stefan Schubert 2008-10-28 15:34:10 UTC
Created attachment 248355 [details]
Added new testcase
Comment 7 Michael Schröder 2008-10-29 17:20:32 UTC
Schubi, please map the solution to ILH.
Comment 8 Stefan Schubert 2008-10-30 09:30:56 UTC
I have done, but the solver still disable this rule:

2008-10-30 10:26:33 <1> waerden(8173) [satsolver] PoolImpl.cc(logSat):80 UPDATE Rule #8674: (disabled)
2008-10-30 10:26:33 <1> waerden(8173) [satsolver] PoolImpl.cc(logSat):80     bundle-lang-common-en-11.1-2.2.noarch [626] (w1) Conflict.level1
2008-10-30 10:26:33 <1> waerden(8173) [satsolver] PoolImpl.cc(logSat):80     next rules: 0 0
2008-10-30 10:26:33 <1> waerden(8173) [satsolver] PoolImpl.cc(logSat):80 => JOB 14
2008-10-30 10:26:33 <1> waerden(8173) [satsolver] PoolImpl.cc(logSat):80 - Rule #9218: (disabled)
2008-10-30 10:26:33 <1> waerden(8173) [satsolver] PoolImpl.cc(logSat):80     gnome-vfs2-2.22.0-33.1.ppc [123] (w1) Install.level1
2008-10-30 10:26:33 <1> waerden(8173) [satsolver] PoolImpl.cc(logSat):80     next rules: 0 0
Comment 9 Michael Schröder 2008-10-30 09:51:19 UTC
Yes, but that's to be expected. Is the output correct?
Comment 10 Stefan Schubert 2008-10-30 10:01:04 UTC
Unfortunately not. The same error is reported again.
Otherwise I would have not blamed :-)
Comment 11 Stefan Schubert 2008-10-30 13:26:56 UTC
I have checked. It works now. Thank you !
Comment 12 Stefan Schubert 2008-11-03 14:31:54 UTC
*** Bug 441066 has been marked as a duplicate of this bug. ***
Comment 13 Stefan Schubert 2008-11-05 16:56:32 UTC
*** Bug 441772 has been marked as a duplicate of this bug. ***
Comment 14 Stefan Schubert 2008-11-06 09:25:13 UTC
*** Bug 441066 has been marked as a duplicate of this bug. ***
Comment 15 Stefan Schubert 2008-11-06 10:46:24 UTC
*** Bug 440953 has been marked as a duplicate of this bug. ***
Comment 16 Stefan Schubert 2008-11-18 10:50:28 UTC
*** Bug 445360 has been marked as a duplicate of this bug. ***