Bug 118040 – postinstall scripts use the <user>.<group> format for setting ownership

Bug 118040 - postinstall scripts use the <user>.<group> format for setting ownership

Summary:	postinstall scripts use the <user>.<group> format for setting ownership

Status:	CLOSED CURRENTRELEASE

Aliases:	None

Product:	Fedora
Classification:	Fedora
Component:	at (Show other bugs)
Sub Component:
Version:	rawhide
Hardware:	All Linux

Priority	medium Severity low
Target Milestone:	---
Target Release:	---
Assigned To:	Jens Petersen
QA Contact:	Mike McLean
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2004-03-11 07:29 EST by David Hollis
Modified:	2007-11-30 17:10 EST (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2004-07-01 14:53:56 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description David Hollis 2004-03-11 07:29:37 EST

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040217

Description of problem:
The %postinstall scripts for at currently look like:

postinstall scriptlet (using /bin/sh):
touch /var/spool/at/.SEQ
chmod 600 /var/spool/at/.SEQ
chown daemon.daemon /var/spool/at/.SEQ
/sbin/chkconfig --add atd


The chown should be changed to daemon:daemon inline with the recent
enforcement of this syntax.

Version-Release number of selected component (if applicable):
at-3.1.8-50

How reproducible:
Always

Steps to Reproduce:
1. Install at
2. Verify ownership of /var/spool/at/.SEQ
3.
    

Actual Results:  Depending on when at was originally installed,
ownership may be correct.  If installing fresh from fedora devel, they
may not be correct.

Expected Results:  Ownership set to daemon:daemon

Additional info:

Comment 1 Jens Petersen 2004-03-12 01:04:30 EST

Should get fixed in the next build,
though I was under the impression that the change
of behaviour was reverted upstream.

Comment 2 Jay Fenlason 2004-07-01 14:53:56 EDT

This was apparently changed around 3.1.8-51

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