Bug 342645

Summary: opensuse updater fails to install "update that affects update stack"
Product: [openSUSE] openSUSE 10.3 Reporter: Klaus Kämpf <kkaempf>
Component: MaintenanceAssignee: Thomas Göttlicher <tgoettlicher>
Status: RESOLVED INVALID QA Contact: Stanislav Visnovsky <visnov>
Severity: Critical    
Priority: P5 - None CC: jsuchome, mfrueh
Version: Final   
Target Milestone: ---   
Hardware: x86-64   
OS: Other   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: error popup
/var/log/zypper.log, bz2 compressed

Description Klaus Kämpf 2007-11-19 09:05:07 UTC
opensuse updater failed to install an "update that affects update stack" today on my 10.3-x86_64 system with
"Subprocess failed. Error: RPM failed: cp: cannot stat `/var/lib/YaST2/cd_update.desktop': No such file or directory"

See attached screenshot.
Comment 1 Klaus Kämpf 2007-11-19 09:05:40 UTC
Created attachment 183857 [details]
error popup
Comment 2 Klaus Kämpf 2007-11-19 09:06:28 UTC
Created attachment 183858 [details]
/var/log/zypper.log, bz2 compressed
Comment 3 Thomas Göttlicher 2007-11-19 09:30:33 UTC
The error is from the rpm installation. 

Do you know why cd_update.desktop is installed in /var/lib/YaST2? 
Comment 4 Jiří Suchomel 2007-11-19 09:59:13 UTC
(In reply to comment #3 from Thomas Göttlicher)

> Do you know why cd_update.desktop is installed in /var/lib/YaST2? 

Because it is not installed on certain architectures. See
 
http://svn.opensuse.org/svn/yast/trunk/online-update/yast2-online-update.spec.in

Do I have an error in .spec file? I also installed this update, but via YaST, not  using the applet and no error was reported.
Comment 5 Thomas Göttlicher 2007-11-19 10:18:43 UTC
I have installed the package via opensuseupdater on my x86_64 10.3 system without error.

Obviously /var/lib/YaST2/cd_update.desktop didn't exist on Klaus' system. Perhaps encapsulating the copy command in an "if -e /var/lib/YaST2/cd_update.desktop" statement could solve the problem. But I am no .spec file expert. :-(
There might be a better and cleaner solution. Could you ask someone who knows better how to write spec files, please?
Comment 6 Jiří Suchomel 2007-11-19 10:30:48 UTC
Yes, that's true, I should have added the check.

But now I think it is too late to do it now. Or, Stephan, should I release yet another fix of yast2-online-udpdate (so users who don't have 2.15.24 version would install directly 2.15.25)?
Comment 7 Stephan Kulow 2007-11-19 10:50:26 UTC
how likely is the case of people having this problem? If high, I'd suggest to do it. I did not have this problem on any of my machines.
Comment 8 Jiří Suchomel 2007-11-19 11:01:10 UTC
(In reply to comment #7 from Stephan Kulow)
> how likely is the case of people having this problem? If high, I'd suggest to
> do it. I did not have this problem on any of my machines.
 
Neither do I and I also don't know anyone except Klaus.

I still don't understand why it fails. The file should be in /var/lib/YaST2/cd_update.desktop before copying (it's part of rpm). What's wrong?


Comment 9 Jiří Suchomel 2007-11-19 13:10:29 UTC
Klaus, are you able to reproduce the problem (probably by downgrading your yast2-online-update* and updating again)?

Thomas, even with the error message, the package gets installed, right?
Comment 10 Thomas Göttlicher 2007-11-19 13:38:28 UTC
(In reply to comment #9 from Jiří­ Suchomel)
> Thomas, even with the error message, the package gets installed, right?
As far as I know rpm doesn't remove its installed files when %post fails.

Comment 11 Klaus Kämpf 2007-11-19 14:21:41 UTC
comment #9
- opensuse-updater works fine after the error and installed the next update
- so the package did get installed apparently
Comment 12 Klaus Kämpf 2007-11-19 14:24:10 UTC
According to the ARCHIVES.gz file, /var/lib/YaST2/cd_update.desktop belongs to yast2-online-update-frontend.rpm.

rpm -q yast2-online-update-frontend reveals:
yast2-online-update-frontend-2.15.23-9
yast2-online-update-frontend-2.15.24-0.1

so it looks like my system is broken. Probably some leftover of upgrading 10.2->10.3a2->10.3b1->10.3b3->10.3rc1->...

Sorry for the noise.
Comment 13 Jiří Suchomel 2007-11-20 21:03:17 UTC
*** Bug 343084 has been marked as a duplicate of this bug. ***
Comment 14 Matthias Fruehauf 2007-11-20 22:08:01 UTC
well, my system in Bug 343084 was also an update from an RC something ...