Bug 3918

Summary:	During Mageia installation, tries to chmod and chown files which don't exist yet
Product:	Mageia	Reporter:	Frederik Himpe <fhimpe>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED OLD	QA Contact:
Severity:	normal
Priority:	Normal	CC:	cazzaniga.sandro, marja11, n3npq, remco, tmb
Version:	Cauldron	Keywords:	NEEDINFO
Target Milestone:	---
Hardware:	i586
OS:	Linux
Whiteboard:
Source RPM:	shadow-utils	CVE:
Status comment:

Description Frederik Himpe 2011-12-29 19:20:24 CET

from install.log from a cauldron install:

shadow-utils-4.1.4.2-9.mga1.x86_64
chmod: cannot access `/etc/shadow': No such file or directory
chown: cannot access `/etc/shadow': No such file or directory

Apparently /etc/shadow is only created later on, so a check should be done on whether this file exists before executing the chmod and chown.

Comment 1 Manuel Hiebel 2011-12-29 19:27:38 CET

Hi, thanks for reporting this bug.
As there is no maintainer for this package I added the committers in CC.

(Please set the status to 'assigned' if you are working on it)

CC: (none) => cazzaniga.sandro, tmb

Comment 2 Jeff Johnson 2012-01-07 20:31:12 CET

tracked at https://bugs.launchpad.net/rpm/+bug/913240

CC: (none) => n3npq

Remco Rijnders 2012-04-12 07:36:00 CEST

CC: (none) => remco

Comment 3 Marja Van Waes 2012-05-26 13:09:37 CEST

Hi,

This bug was filed against cauldron, but we do not have cauldron at the moment.

Please report whether this bug is still valid for Mageia 2.

Thanks :)

Cheers,
marja

Keywords: (none) => NEEDINFO

Comment 4 Marja Van Waes 2012-07-01 15:53:27 CEST

Ping!

It is very important for us to know whether this bug is still valid for fully updated Mageia 2 and/or for *current* cauldron.

Please tell us. If you don't reply, we'll have to close this bug as old.

CC: (none) => marja11

Comment 5 Marja Van Waes 2012-10-16 19:57:31 CEST

Over three months later, no reply, closing as OLD

Please reopen and tell for which current and updated version(s) of Mageia this bug is still valid, if you still run into it

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