Bug 461374

Summary: update woes
Product: [openSUSE] openSUSE 11.1 Reporter: Harald Koenig <koenig>
Component: Update ProblemsAssignee: Stephan Kulow <coolo>
Status: RESOLVED WONTFIX QA Contact: Jiri Srain <jsrain>
Severity: Normal    
Priority: P2 - High CC: dmacvicar, mls
Version: Final   
Target Milestone: ---   
Hardware: x86-64   
OS: Other   
Whiteboard: .
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: y2log of update nightmare
updateTestcase

Description Harald Koenig 2008-12-22 00:02:31 UTC
the update from 11.0 to 11.1 was IMHO a medium desaster :-(

- again conflicts nightmare
- unsupported/old packages got deleted ( I do *NOT* want this to happen!)
- error in kvm-kmp-default postinstall
- no boot loader -- and no display of grub/install error
- many (623) RPMs changed arch from x86_86 to i586 including Xserver, emacs etc.

details:

T61p x86_64 (2.4 GHz T7700), update from 11.0 to 11.1 with DVD9 image:

1) again conflicts nightmare

I tried to add some more/new patterns before starting the update.  after successfully adding some patterns, I got into the dependency conflict resolution nightmare again!  after ~20 CPU minutes (!!!) and _many_ conflict resolution selections I resigned and aborted any pattern -- just start the update without any new patterns for now.   the final y2log is 290 MEGAbytes, likely because of this conflict "problems" ?!  I'll attach y2log....


2) unsupported/old packages got deleted ( I do *NOT* want this to happen!)

I was surpriesed that in update options it's no longer possible to specify if unsupported RPMs shall be kept or deleted (because I want them to be kept!). hmmmm....

so I started a plain update with no special settings.  and first I got told that 200+ packages will be deleted :-((((  I see package names like "tpb" and "enigma" which I _really_ want to be kept.  deep sigh...


3) error in kvm-kmp-default postinstall

there was an error trying to update kvm-kmp-default -- retry did not work, I had to ignore that error and continue. now there are two RPMs installed, I had to remove the old package manually:

      harald harald > rpm -q kvm-kmp-default
      kvm-kmp-default-63_2.6.25.5_1.1-31.1
      kvm-kmp-default-78_2.6.27.7_9.1-6.4


4) no boot loader -- and no display of grub/install error

at the end of the update, the installation of thr boot lodaer failed -- but it's not possible to display the error logs or similar (tried several cycles through the yast boot loader menues without success:-(  the grub menu.lst did not get updated at all, still showed the kernel versions from 11.0 :-(
so I had to ignore that boot loder stuff and fix that from rescue system:(


5) many (623) RPMs changed arch from x86_86 to i586 including Xserver, emacs etc.
after reboot the *BIG* shock was to realize that 623 RPMs are arch i586 instead of x86_64 -- what's going on here ?????????????????  full rpm arch list on request (I guess you'll extract this from y2log ?!)

I used "zypper install emacs.x86_64" etc. for all those i586 packages to manually switch back to 64 bit arch -- now only wine etc. are left as i586  (not counted in those 623 RPMs).



this update really was disapointing -- I which I'd have had time and disk space to beta-test this before.  is no one testing updates anymore these days ?????
Comment 1 Harald Koenig 2008-12-22 00:06:00 UTC
Created attachment 261716 [details]
y2log of update nightmare

beware, this will be 290 Mbytes uncompressed!
Comment 2 Duncan Mac-Vicar 2008-12-22 13:44:29 UTC
Do you happen to have a solver testcase in the logs directory?
Comment 3 Duncan Mac-Vicar 2008-12-22 14:01:15 UTC
Note, from all the unmaintained candidates, only the following packages were removed (and I guess those are due to obsoletes).

pattern:laptop-11.1-71.1.x86_64(openSUSE 11.1-0)
RealPlayer-10.0.9-51.1.i586(@System)
gnome-cups-manager-0.33-26.1.x86_64(@System)
gnome-printer-add-1.0.1-242.1.x86_64(@System)
libGraphicsMagick1-1.1.11-29.2.x86_64(@System)
libdjvulibre15-3.5.20-51.1.x86_64(@System)
libdvdread3-0.9.7-4.1.x86_64(@System)
libiniparser-2.17-66.1.x86_64(@System)
libiniparser-32bit-2.17-66.1.x86_64(@System)
libltdl-3-32bit-1.5.26-23.1.x86_64(@System)
libpisync0-0.12.2-112.1.x86_64(@System)
librasqal0-0.9.15-41.1.x86_64(@System)
libusb-0.1.12-110.1.x86_64(@System)
multisync-0.82+cvs-244.1.x86_64(@System)
powersave-libs-0.15.20-38.1.x86_64(@System)
resmgr-32bit-1.1.0_SVNr155-26.1.x86_64(@System)
siga-10.101-110.1.noarch(@System)
supertux-0.1.3-164.1.x86_64(@System)
tpb-0.6.4-107.x86_64(@System)
xgl-git_071026-79.3.x86_64(@System)
xgl-hardware-list-060526-115.1.noarch(@System)
Comment 4 Harald Koenig 2008-12-22 14:07:05 UTC
(In reply to comment #2 from Duncan Mac-Vicar)
> Do you happen to have a solver testcase in the logs directory?

no I don't, sorry.  all I have is the huge y2log file.

though I can offer the rpm database, either /var/adm/backup/rpmdb/Packages* or /var/lib/rpm/ from my backup if this can help you to test/reproduce?!
Comment 5 Harald Koenig 2008-12-22 14:23:51 UTC
(In reply to comment #3 from Duncan Mac-Vicar)
> Note, from all the unmaintained candidates, only the following packages were
> removed (and I guess those are due to obsoletes).

I did not check all the 149 removed rpms in detail so far (grepping for "doRemovePackage"), but tools like octave or obexfs or the nice game enigma got removed too.

for enigma the reason might be that libXerces-c-28 got renamed to libXerces-c28,
the reason for octave might be that it's missing on the DVD9 or this was triggered  by the change from libhdf5.so.0 to libhdf5.so.5 ?!

anyway, this is not the behaviour I expected for an update -- and up to 11.0 I was very happy in general with updating, but this time....

is it only me that I didn't find the check box in the update options to disable "remove unsupported packages" and update might have gone smoother with different options, or is this missing option a new "feature" in 11.1 ?
Comment 6 Duncan Mac-Vicar 2008-12-22 14:32:52 UTC
Harald, YaST makes a testcase automatically under /var/log/updateTestcase/

can you attach it?
Comment 7 Michael Schröder 2008-12-22 14:35:36 UTC
No, the update automatically tries to keep as many unsupported packages installed as possible (as long as they don't interfere with the rest of the installation).

The i586 packages are due to a bug in the wine package. Sorry about that. Bad testing from our side.
(It's also possible that those arch changes caused the removal of some of the packages you complained about.)

Removing wine and calling 'zypper dup' should switch the packages back to x86_64.
Comment 8 Harald Koenig 2008-12-22 15:23:36 UTC
Created attachment 261947 [details]
updateTestcase
Comment 9 Michael Schröder 2008-12-22 15:41:20 UTC
Thanks. Regarding enigma, it requires "libxerces-c.so.28()(64bit)", but there is no libxerces on the medium.
Afaik there's a "update problems" list somewhere hidden in the UI, setting enigma to "lock" would have produced some solver error with the possibilities to ignore some deps from enigma (leading to a still installed but broken application) or not updating some packages. 
Comment 10 Harald Koenig 2008-12-22 15:46:56 UTC
(In reply to comment #7 from Michael Schroeder)
> No, the update automatically tries to keep as many unsupported packages
> installed as possible (as long as they don't interfere with the rest of the
> installation).

hmm, enigma and octave did not "interfere" but there have been some unresolved issues due to missing packatges on the DVD9.  nothing which couldn't have been fixed later with updates from the net -- but so those packages are "gone" from the list of installed apps...


> The i586 packages are due to a bug in the wine package. Sorry about that. Bad
> testing from our side.
> (It's also possible that those arch changes caused the removal of some of the
> packages you complained about.)
> 
> Removing wine and calling 'zypper dup' should switch the packages back to
> x86_64.

interesting!  just did that and it "solved" all the update problems with strange version numbers which I just reported in bug #461625.  is it possible to explain/understand that behaviour ?

your new wine package seems to drive yast/zypper _very_ crazy ;-)
dump question: is an wine update already scheduled ?


one more question about zypper magic:

(how) is it possible to tell zypper/yast _not_ to update any packages with the name pattern "*xfce*" (or specify an explicit exception/black list) ?

I need this as a workaround for bug #444858 -- I have to keep xfce 4.4.2 from 110.0 for now....
Comment 11 Michael Schröder 2008-12-22 16:19:26 UTC
Wine problem: wine needs libodbc.so.1, but we forgot to put unixODBC-32bit on the DVD. Thus, the solver installs unixODBC.i586 and switches some packages to i586. So we don't need an update but just a repository that contains the 32bit
package.

xfce: run "zypper al '*xfce*'", this will create an entry in /etc/zypp/locks.
Comment 12 Duncan Mac-Vicar 2008-12-29 11:56:35 UTC
Can we close this as fixed then? or do we wait until the 32bit package is put into the update repository?
Comment 13 Swamp Workflow Management 2008-12-29 14:29:02 UTC
The SWAMPID for this issue is 21394.
Please submit the patch and patchinfo file using this ID.
(https://swamp.suse.de/webswamp/wf/21394)
Comment 14 Harald Koenig 2009-01-03 18:32:38 UTC
(In reply to comment #12 from Duncan Mac-Vicar Prett)
> Can we close this as fixed then? or do we wait until the 32bit package is put
> into the update repository?

what about the boot loader (grub) problems (see 4) which may got triggered by the 
kvm-kmp-default postinstall error (3).  

did this too "only" happen because of the wine dependencies ?
Comment 20 Stephan Kulow 2009-01-14 11:08:53 UTC
that wine.i586 triggers a problem because of missing unixODBC-32bit when updating x86_64 from DVD9 is known, but we can't fix it anymore.