|
Bugzilla – Full Text Bug Listing |
| Summary: | selecting same update partition multiple time results random packages to update | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE Linux 10.1 | Reporter: | Johannes Meixner <jsmeix> |
| Component: | Update Problems | Assignee: | Ladislav Slezák <lslezak> |
| Status: | RESOLVED WONTFIX | QA Contact: | Klaus Kämpf <kkaempf> |
| Severity: | Critical | ||
| Priority: | P5 - None | CC: | suse-beta |
| Version: | Beta 8 | ||
| Target Milestone: | --- | ||
| Hardware: | x86-64 | ||
| OS: | SuSE Linux 10.1 | ||
| Whiteboard: | |||
| Found By: | Development | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
tgz of /var/log/YaST2/*
YaST "Installation Settings" screenshot YaST package manager screenshot YaST "Installation Settings" screenshot YaST package manager screenshot |
||
|
Description
Johannes Meixner
2006-03-10 10:52:38 UTC
Created attachment 72207 [details]
tgz of /var/log/YaST2/*
I will reboot from 10.1 CD and do the update again - i.e. I cannot provide further information.
After reboot I got again the YaST "Installation Settings" screen which shows that it will update about 900 Packages and that there is a package conflict which must be manually solved. After solving the conflict (it was only about one single package) the YaST "Installation Settings" screen shows 0 packages to update but 1088 new packages to be installed. Perhaps only a misleading message? Probably I should simply ignore what YaST tells me about packages ;-) (In reply to comment #2) > After solving the conflict (it was only about one single package) > the YaST "Installation Settings" screen shows 0 packages to update > but 1088 new packages to be installed. This one is already known - bug 155284 / bug 154720 About the remaining issue: When YaST shows only few packages to install/update, go to the package manager detail view - does it look "normal" (lots of packages marked for update)? I am afraid, at the moment I cannot re-do an update to answer your question - I need the updated system for other tests. Maby this one should be handled seperately. Reassigning. Reinstalled 10.0 system from scratch and updated it to 10.1 beta8. Created attachment 73968 [details]
YaST "Installation Settings" screenshot
Meanwhile probably correct size info but still wrong package numbers.
Created attachment 73969 [details]
YaST package manager screenshot
After leaving the package manager I got the same "Installation Settings" screen. Then I selected the "Selected for Update" and got the "Select for Update" screen where I only clicked [Accept] (still the same root partition to update which is o.k.) and got back to the "Installation Settings" screen which hangs for a few minutes with the "busy"-mouse cursor (the arrow with the running clock) and several y2log* files are filled up with tons of messages from the "Resolver*". Created attachment 73981 [details]
YaST "Installation Settings" screenshot
After "Selected for Update"
the packages to update are wrong.
Created attachment 73982 [details] YaST package manager screenshot Compare this with comment #8 I cannot answer further questions because I will redo the update because I need a correctly updated system for my own tests. In particular note that in screenshot comment #13 there is still "Packages to Remove: 0" which is dangerous misleading for the user according to the corresponding screenshot in comment #14 which shows that tons of packages would be actually removed. Sounds like a duplicate of #154720 As far as I see only comment #17 is a duplicate of bug #154720. But note the subject and the initial comment of this bug. Any progress on this? No big progress - I have tested it and it seems that zypp is probably not completely resetted when a new (or the same) target partition is set. I'll investigate more... It is not possible to change the root partition anymore. I do not understand comment #22 and why it is "WONTFIX". Do you mean that on the YaST "Installation Settings" screen the item "Selected for Update" was simply removed? If yes, I think it is perfectly o.k. and therefore FIXED because the user cannot expect to change anything later. Yes, "Selected for Update" item has been removed. |