|
Bugzilla – Full Text Bug Listing |
| Summary: | Yast System Update crashes if update installation of new software is selected and no installation sources are available | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 10.2 | Reporter: | Seth Chaiklin <seth> |
| Component: | YaST2 | Assignee: | Jiri Srain <jsrain> |
| Status: | RESOLVED FIXED | QA Contact: | Klaus Kämpf <kkaempf> |
| Severity: | Enhancement | ||
| Priority: | P5 - None | CC: | suse-beta |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | 32bit | ||
| OS: | SuSE Linux 10.1 | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Seth Chaiklin
2006-03-14 12:23:18 UTC
Seth, which system did you want to update? SL 10.0 to 10.1 by adding a new installation source and runnning `yast2 update`? Or some older 10.1 Beta to SL 10.1 Beta6? I was trying to update an older 10.1 Beta to Beta6. I started with SL 10.0, and was been updating the betas as they come out (10.0.42). Around beta4, various Yast problems appeared, so that Software Management and System Update were no longer functional, so I have been using Kpackager to update (from the same /factory directory. Around beta4, System Update would report "unknown" system. Jsrain: Update.ycp fill_version_map() might be problematic with versions finishing "Beta[0-9]" The function has no comment, so I could only guess :) This might be the same issue (but another case) as in the bug 157924. Works well now, but might be problematic in the next Beta phase. Fixed in SVN (hopefully, could not find any beta) |