|
Bugzilla – Full Text Bug Listing |
| Summary: | Yast System repair tool does complain about version conflict | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 10.3 | Reporter: | Casual J. Programmer <casualprogrammer> |
| Component: | YaST2 | Assignee: | Jiří Suchomel <jsuchome> |
| Status: | RESOLVED INVALID | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Normal | ||
| Priority: | P5 - None | ||
| Version: | Alpha 4plus | ||
| Target Milestone: | --- | ||
| Hardware: | x86 | ||
| OS: | openSUSE 10.3 | ||
| Whiteboard: | |||
| Found By: | Beta-Customer | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
Screenshot of Message "different product installed"
yast2 logs |
||
|
Description
Casual J. Programmer
2007-05-26 10:16:58 UTC
Created attachment 142420 [details]
Screenshot of Message "different product installed"
I cannot reproduce it (= works for me). Please run again with full debugging (Y2DEBUG=1 yast2 repair) and attach the log files just after you see the message (logs will be huge). Hello, were you able to test it? Good you reminded me, I almost forgot about this issue :-)
Actually it is still the same:
After performing a "clean" install from alpha6 DVD and several updates ( last big one last night /etc/SuSe-release is now at alpha7 )
"Y2DEBUG=1 yast2 repair" displays exactly the same message as in attachment 142420 [details].
Created attachment 154037 [details]
yast2 logs
Well, but that's correct behaviour. I thought the products were the same or that the screenshot is showing some strange name of theproduct, but nothing from this is true. -> invalid (You might say that alpha6 and alpha7 are of the same product, but I woudln't take that point. Only released products count here, and e.g. 10.3 is definitelly different product from 10.2) Now, if that is so, this "tool" should be removed completely, as it creates a false sense of safety. If I understand you correctly, this will only work directly upon installation from media. Since _every_ real life installation is living, after a few ( maybe even a single ) updates it will cease to work. No. With real life installations, you install updates regularly which doesn't mean you are changing the product version. If you upgrade to new version of product, you can use repair function of that new function. Using "factory" and updating from alphas to betas doesn't count as real life installation; that intended for testing only. |