Bug 13886 - Several errors occurred during package installation
Summary: Several errors occurred during package installation
Status: RESOLVED INVALID
Alias: None
Product: Mageia
Classification: Unclassified
Component: Installer (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard: 5alpha2
Keywords:
Depends on:
Blocks:
 
Reported: 2014-08-08 23:26 CEST by Dick Gevers
Modified: 2014-08-11 20:58 CEST (History)
3 users (show)

See Also:
Source RPM: 3rd build classical iso
CVE:
Status comment:


Attachments
report.bug.gz from said install (322.66 KB, application/octet-stream)
2014-08-08 23:34 CEST, Dick Gevers
Details

Description Dick Gevers 2014-08-08 23:26:31 CEST
Description of problem:

Chose Custom set of packages: 

Package group selection: all Workstations, no servers, all GEs

An error occurred:

    ERROR: 'unpack' failed for gnu-free-fonts.....icedtea-web
    .....drakconf...etcskel....coreutils-doc...
    207 installation transactions failed
    Installation of packages failed
    .... is needed by... 

After final the installation process OK loops back to 1643 packages needing
    to be installed (was origianlly 26xx or so).

After the 2nd loop, another error occurred:

    ERROR: 'unpack' failed ro firefox...gpicview...cdrdao...info...
    unable to install coreutils-doc.........

    11 installation transactions failed.....

    loops back: 66 packages remaining
    
Again an error occurred:

unable to install coreutils-doc # just one rpm mentioned

and then goes on to post install configuration

I will attach the report.bug.gz

Reproducible: 

Steps to Reproduce:
Dick Gevers 2014-08-08 23:28:20 CEST

CC: (none) => eeeemail, ennael1
Whiteboard: (none) => 5alpha2

Comment 1 Dick Gevers 2014-08-08 23:34:57 CEST
Created attachment 5334 [details]
report.bug.gz from said install
Dick Gevers 2014-08-08 23:37:56 CEST

CC: (none) => wilcal.int

Comment 2 claire robinson 2014-08-08 23:43:57 CEST
There are numerous I/O errors for /dev/sr0 at the start of report.bug, could it be your disk is reaching the end of it's life?

Are you able to use USB to boot?
Comment 3 Dick Gevers 2014-08-08 23:49:09 CEST
/dev/sr0 is the DVD. It was burned on a fresh disk.

And the drive (whole laptop) is just months old.

Booting usb: never tried, never looked into the method.
Comment 4 claire robinson 2014-08-08 23:51:31 CEST
the issue seems to stem from 'read failed' for gnu-free-fonts-common which causes a cascade of further failures.

unpacking of archive failed on file /usr/share/doc/gnu-free-fonts-common/ChangeLog;53e4eebf: cpio: read failed - Resource temporarily unavailable
gnu-free-fonts-common-20120503-5.mga4.noarch
gnu-free-fonts-common-20120503-5.mga4.noarch: install failed
lib64exttextcat2.0_0-3.4.4-1.mga5.x86_64
libexttextcat-3.4.4-1.mga5.x86_64


installing autocorr-en-4.3.0.4-1.mga5.noarch.rpm locales-en-2.19-1.mga5.x86_64.rpm fonts-ttf-bitstream-vera-1.10-13.mga4.noarch.rpm gnu-free-serif-fonts-20120503-5.mga4.noarch.rpm hyphen-en-2.8.5-4.mga4.noarch.rpm locales-2.19-1.mga5.x86_64.rpm gnu-free-mono-fonts-20120503-5.mga4.noarch.rpm hyphen-2.8.7-2.mga5.x86_64.rpm from /tmp/image/media/core
starting installing packages
created transaction for installing on /mnt (remove=0, install=0, upgrade=8)
Installation failed:
	gnu-free-fonts-common = 20120503-5.mga4 is needed by gnu-free-serif-fonts-20120503-5.mga4.noarch
	gnu-free-fonts-common = 20120503-5.mga4 is needed by gnu-free-mono-fonts-20120503-5.mga4.noarch
Comment 5 claire robinson 2014-08-08 23:53:14 CEST
You sometimes find a dvd drive doesn't like certain media, or perhaps it needs to cool down a bit, it shows it spent 2.5hrs trying to install (if i am reading it correctly)
Comment 6 Dick Gevers 2014-08-11 10:19:19 CEST
Well tbh the memtest failed on both sticks of memory so it may well be that the bug is invalid due to bad hardware.

Intend to buy new RAM and try again after I have found the proper ones; hopefully today.
Comment 7 Dick Gevers 2014-08-11 20:58:35 CEST
New RAM succeeds memtest, but similar errors as in this BR do occur. Every time it is a different package which is the cause, so as it was a very cheap notebook, I'll write it off to bad hardware.

Status: NEW => RESOLVED
Resolution: (none) => INVALID


Note You need to log in before you can comment on or make changes to this bug.