|
Bugzilla – Full Text Bug Listing |
| Summary: | can't resolv conflict | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 11.0 | Reporter: | Harald Koenig <koenig> |
| Component: | YaST2 | Assignee: | Stefan Schubert <schubi> |
| Status: | RESOLVED FIXED | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Blocker | ||
| Priority: | P5 - None | CC: | coolo, dmacvicar, ma |
| Version: | Factory | Flags: | coolo:
SHIP_STOPPER-
|
| Target Milestone: | --- | ||
| Hardware: | x86-64 | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
y2log
testcase |
||
Hello, could you send please all yast2 logs (/var/log/YaST2) ? Thanks Created attachment 217844 [details]
y2log
"it's not groundhog day today, isn;t it?" I like your homour :-) Harald, could you please provide a testcase ? It could be the same error as Bug 391785. (In reply to comment #4 from Stefan Schubert) > "it's not groundhog day today, isn;t it?" > I like your homour :-) > Harald, could you please provide a testcase ? what exactly do you expect as "testcase" here ? I could try to reconstruct a rpm list for that situation (y2log should show most of this information too ?!). as mentioned above I did a "search beagle" and marked everything for deletion including that libeagle1. whatelse can I privide ? See comment#3. Try to reproduce the error popup, generate a testcase and attach it to bugzilla. Thats all :-) Created attachment 218551 [details]
testcase
ah, _that_ test case!!! that URL to the mega-long web page doesn't exactly tell me what you're looking for (as I already provided y2log)
Thank you. Yes, I can reproduce it. I think it is a blocker. Coolo ? I guess you can cancel the dialog and select keep libbeagle1 there - so it's technically not a blocker. But it would still be good to have it fixed. SOLVER_ERASE_SOLVABLE_NAME: As we do not know, if this request has come from resolvePool or resolveQueue we will have to take care for both cases. --> fixed and testcase added to the testsuite. Harald, thank you for your fast answers. (In reply to comment #10 from Stefan Schubert) > Harald, thank you for your fast answers. thanks have to go too to the LinuxTag team in Berlin for the good & fast network connectivity this years! greating from LinuxTag in (still quite cool and windy) Berlin;-) |
I tried to get rid of beagle so in yast2 I did a search for "beagle" and set all pkgs to delete. then I got the dependency conflict below and whenever I select "keep libbeagle1" and "try again" I get the same message box over and over again (it's not groundhog day today, isn;t it?;-) #### YaST2 conflicts list - generated 2008-05-23 16:21:24 #### yelp-2.22.1-21.x86_64 requires libbeagle >= 0.2.0, but this requirement cannot be provided [ ] Following actions will be done: deinstallation of yelp-2.22.1-21.x86_64 deinstallation of brasero-0.7.1-66.x86_64 deinstallation of nautilus-2.22.2-24.x86_64 deinstallation of gnome-control-center-2.22.1-24.x86_64 [...] architecture change of canna-libs-3.7p3-164.x86_64 to canna-libs-3.7p3-164.i586 architecture change of xemacs-21.5.28.20080401-13.x86_64 to xemacs-21.5.28.20080401-13.i586 architecture change of libkcompactdisc4-4.0.4-10.x86_64 to libkcompactdisc4-4.0.4-10.i586 architecture change of scsi-1.7_2.38_1.25_0.19_1.02_0.93-24.x86_64 to scsi-1.7_2.38_1.25_0.19_1.02_0.93-24.i586 [ ] keep libbeagle1 [ ] Ignore some dependencies of yelp #### YaST2 conflicts list END ###