Bug 772705

Summary:	A critical error happened during (upgrade) installation of package qt-examples
Product:	[Fedora] Fedora	Reporter:	Germano Massullo <germano.massullo>
Component:	anaconda	Assignee:	Anaconda Maintenance Team <anaconda-maint-list>
Status:	CLOSED INSUFFICIENT_DATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	16	CC:	anaconda-maint-list, christian.lupien, codemonkey, jonathan, martin.marques, vanmeeuwen+fedora
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-03-12 02:06:38 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Germano Massullo 2012-01-09 17:43:32 UTC

Description of problem:
I was upgrading the system of a friend from Fedora KDE 14 64bit to 16, when in anaconda I got: "A critical error happened during installation of package qt-examples. This could depends from errors while reading installation media. The installation cannot continue"

Why the installation cannot continue? People should be able to skip corrupted packages, instead this will destroy the system and force me to waste time to format and reinstall the entire system.

I did not try to restart again Anaconda upgrade because I did not have the time. I don't know what other infos I can attach, I will see him on 11th January, so I will try again and I will do a hard drive check to clarify all dubts about a possible (?) hardware failure

Comment 1 Chris Lumens 2012-01-09 23:27:37 UTC

What if the corrupt package is something important, that lots of other packages depend upon?  Then you have a cascading effect where more and more of the system is uninstallable.  Please attach /tmp/anaconda.log, /tmp/syslog, and /root/upgrade.log from during the upgrade process to this bug report.

Comment 2 Christian Lupien 2012-01-23 10:10:18 UTC

I had the same problem.
However, with a lot of work, I was able to complete the install after removing
that package.

The problem I got, from memory, is the same I now get when trying to install that package:

yum install qt-examples
proceeds about half way through (from hash) 

--------------------------

Downloading Packages:
qt-examples-4.8.0-7.fc16.x86_64.rpm                      |  11 MB     00:10     
Running Transaction Check
Running Transaction Test
Transaction Test Succeeded
Running Transaction
  Installing : 1:qt-examples-4.8.0-7.fc16.x86_64                            1/1 
Error unpacking rpm package 1:qt-examples-4.8.0-7.fc16.x86_64
error: unpacking of archive failed on file /usr/lib64/qt4/examples/declarative/i18n/i18n: cpio: rename

Failed:
  qt-examples.x86_64 1:4.8.0-7.fc16                                             

Complete!

------------------------
Note that this package is installed as a dependency of qt-creator

Comment 3 Germano Massullo 2012-03-10 16:44:08 UTC

I cannot add these logs because they no longer exist

Comment 4 Ray 2013-02-07 20:16:51 UTC

@Chris Lumens
> What if the corrupt package is something important, that lots of other
> packages depend upon?  Then you have a cascading effect where more and more
> of the system is uninstallable.

What if the corrupt package is something UNimportant (like qt-examples), and the user knows it?  Are you saying that it's better to let the user's update die and then require them to maybe do a fresh install, as opposed to just adding a simple and sensible option to skip the broken package?

I just went through this and that simple option would have saved me a great deal of time and frustration.

And what if the corrupt package IS something important?  Isn't the system pretty much hosed anyway?

Your concern is well-meaning but a poor excuse for omitting the reasonable feature that was requested.