[Bug 176253] Review Request: clement-2.1

[bugzilla at redhat.com]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.

Summary: Review Request: clement-2.1


https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=176253





------- Additional Comments From j.w.r.degoede at hhs.nl  2006-08-14 10:48 EST -------
A bit late due to a bugzilla collision, but I fully agree with Michael:

(In reply to comment #23)
> So I added clement as group & user as suggested.
> 
> got this from rpmlint (many lines of this kind)
> 
> E: clement non-standard-gid /var/spool/clement-2.1/mqueue clement
> A file in this package is owned by a non standard group.
> Standard groups are:
> root, bin, daemon, sys, adm, tty, disk, lp, mem, kmem, wheel, mail,
> news, uucp, man, games, gopher, dip, ftp, lock, nobody, users
> 
> 
> Does not look like as a 'Warning' to me, how to make it as a Warning?
> 

Erm, so its an error (my mistake), still it can be ignored, rpmlint us an
automated validation tool and sometimes it can be just plain wrong. Trust me
(and Michael) on this between the 2 of us there is a ton of packaging experience.

> 
> Also got this warning
> W: clement dangerous-command-in-%preun userdel
> because I would like to delete created user when removing all the application,
> there is a kind of ambiguity here as some file could be left if the application
> was in production previously.
> My understanding of the last Michael comment is to let the sys-admin delete
> the remaining user/group himself, right?

Yes, you should not remove the user, the user may only be removed if your 100.1%
sure that no files owned by that user will be left around, which in this case we
aren't actually we are pretty sure that files will be left around, so the
userdel must be removed from the spec file.


-- 
Configure bugmail: https://bugzilla.redhat.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.