[Bug 255725] New: Updating with YaST2 Software Management results in "failed integrity check" for second and subsequent pacakages
https://bugzilla.novell.com/show_bug.cgi?id=255725 Summary: Updating with YaST2 Software Management results in "failed integrity check" for second and subsequent pacakages Product: openSUSE 10.3 Version: Alpha 2 Platform: i686 OS/Version: SuSE Other Status: NEW Severity: Major Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: casualprogrammer@yahoo.com QAContact: jsrain@novell.com Updating just now from openSuSE 10.3 alpha 2 with YaST2 "Software Management", selecting packages by Filter "Installation Summary/Keep", then right clicking on any package and selecting "All in this list/Update if newer version available", then pressing "Accept", results in 1 (one) package being installed, the second and subsequent packages experience "Package xyz is broken, integrity check has failed". Downloading one by one works. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=255725 chrubis@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |casualprogrammer@yahoo.com ------- Comment #1 from chrubis@novell.com 2007-03-20 09:38 MST ------- Please attach y2logs. If you are in doubt follow: http://en.opensuse.org/Bugs/YaST Thanks! -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=255725 ------- Comment #2 from casualprogrammer@yahoo.com 2007-03-20 09:53 MST ------- Created an attachment (id=125525) --> (https://bugzilla.novell.com/attachment.cgi?id=125525&action=view) YaST2 logs as requested It appears that this is a matter of precedence. On the other machine I repeated the process. When running into this problem I updated all *zypp* first, then all *yast2* then *kernel* manually. After that it seemed to work normally. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=255725 casualprogrammer@yahoo.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|casualprogrammer@yahoo.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=255725 chrubis@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team- |lslezak@novell.com |screening@forge.provo.novell| |.com | Status|ASSIGNED |NEW -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=255725 sh@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID ------- Comment #3 from sh@novell.com 2007-06-06 04:13 MST ------- That's why the normal update procedure (in particular online update) has safeguards to update the update stack (libzypp, YaST2 binaries) first and then all other packages (after restarting YaST2 etc. with the updated versions). If you simply set all the individual packages to "update", the update stack might get inconsistent during updating. Of course it would be desirable to have everything always compatible with all versions, but this does not always work out. Resolution: This is not the recommended and/or documented way to update. It might work (then you are lucky), or it might not -> INVALID. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
participants (1)
-
bugzilla_noreply＠novell.com