|
Bugzilla – Full Text Bug Listing |
| Summary: | update has destroyed system | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE Linux 10.1 | Reporter: | Elmar Stellnberger <estellnb> |
| Component: | Zenworks | Assignee: | Stefan Schubert <schubi> |
| Status: | RESOLVED INVALID | QA Contact: | Forgotten User YrvzK78Vmi <forgotten_YrvzK78Vmi> |
| Severity: | Critical | ||
| Priority: | P5 - None | CC: | wstephenson |
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | i686 | ||
| OS: | SuSE Linux 10.1 | ||
| Whiteboard: | |||
| Found By: | Customer | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | zmd message log | ||
|
Description
Elmar Stellnberger
2007-01-23 11:43:29 UTC
Created attachment 114373 [details]
zmd message log
The updater should probably view packages to be deleted red, fat and with 12pt! 8pt black messages are often overlooked! please have a look at bug #238770, too. Whoops, I just wanted to watch this bug, not assign it to myself Probably a wontfix though, buildservice packages are unsupported. What concerns me is that it was so easy for zen-updater to take all newer packages known to the system as updates. IMO it should only take patches from the update source on 'update', as opensuse-updater does. Blindly updating with everything available in there is roughly equivalent to dd if=/dev/random of=/dev/hda, just slower. It has probably been my mistake not to have a look at the uninstall list, but the examples seem to reveal certain errors in the dependency resolution: * If it decided to uninstall kdebase3 it would have to remove Kde completely. * It can not be true that the dependency resolution fails one minute later on exactly the same package selection which had already been accepted. Aber nein, werden wir doch nicht gleich wegen ein paar Fehlern aufgeben! und außerdem: Wenn das neue System nicht mehr leistet als das alte aber langsamer ist wieso verwenden wir dann nicht gleich das alte *? nur ein paar kleine Hacks und alles geht wieder ... -> gute Software fördert eben die Kreativität ihrer Anwender! * it should only take patches from the update source on 'update' Note: The updates from "http://software.opensuse.org/download/DBUS/" are very valueable since they have fixed bug 206352 (kpowersave-dbus) under Suse10.1. Moreover this update has been necessary to make the HAL-automounter work. Please, attach /var/log/zmd-backend log as well The zmd-backend log is already online at bug 243494. OK. Schubi, is there anything broken in the dependency handling? Why user is not provided with a way to fix them? I had a look to the lofiles of bug 243494 but I cannot see any delete request of e.G. ibzypp or libzypp-backend. Elmar can you reproduce it ? If yes, please start the ZMD deamon with: export ZYPP_FULLLOG=1; rczmd restart So the logfiles would be more verbose. They have both definitely been removed (No; this is not a joke). I know it because I had to reinstall them on my own. > rug hi -a removal|grep zypp 18.01.2007 | removal | libzypp | 1.3.2-0.9 18.01.2007 | removal | libzypp-zmd-backend | 7.1.1.0-42.53 Persuade yourself by: > sed -n "s#.*Removing .*package\]\(.*\)..#\1#p" <zmd-messages.log.2007-01-18 or particularly by > sed -n "s#.*Removing .*package\]\(.*\)..#\1#p" | grep zypp : libzypp-zmd-backend-7.1.1.0-42.53.i586 : libzypp-1.3.2-0.9.i586 Perhaps Zenworks should stop where it has to remove itself - very reasonable. Reproduce that? You lucky having a good mood! At least not now (From Tomorrow on I will be away). To reproduce that I would at first have to downgrade dbus-1 (upgrade desc: bug 206352) and then perform the upgrade again just to get an unusable system. Perhaps I can do that before I wrack down my old Suse10.1-Installation to replace it by OpenSuse 10.2. I did not want to do so up to now because 10.1 is still working and because I would loose the proprietary addons (OpenOffice:NovellEdition, YaST-Cfg) uo. It would be cat's pajamas if you could provide them for me if I should reproduce this with ZYPP_FULLLOG=1. Feel free to reopen the bug, if you can provide the required information. |