Bug 802870 - Rpmdiff failure(s) for build aeolus-configserver-0.4.6-0.el6
Summary: Rpmdiff failure(s) for build aeolus-configserver-0.4.6-0.el6
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: CloudForms Cloud Engine
Classification: Retired
Component: aeolus-configserver
Version: 1.0.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: rc
Assignee: Greg Blomquist
QA Contact: dgao
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-03-13 16:52 UTC by John Eckersberg
Modified: 2012-05-15 20:54 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-05-15 20:54:27 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2012:0585 0 normal SHIPPED_LIVE new packages: aeolus-configserver 2012-05-15 22:31:37 UTC

Comment 1 Greg Blomquist 2012-03-15 19:47:13 UTC
Waived.

The VERIFY line is in regards to the user id 180 for aeolus, which has already been established as a valid user id for aeolus.

The BAD line is actually referencing a comment in the spec, which reads:

# stop and unregister the service before package deletion

It contains both the words "service" and "stop", which the parser is looking for when checking for the "stops service unconditionally" error.  I'm filing a bug against rpmdiff to have this fixed in the rpmscripts.c code.

Bug against rpmdiff: https://bugzilla.redhat.com/show_bug.cgi?id=803864

Comment 3 Dave Johnson 2012-03-21 14:18:19 UTC
Waived and now all green...

https://errata.devel.redhat.com/rpmdiff/show/58096

Comment 4 errata-xmlrpc 2012-05-15 20:54:27 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHEA-2012-0585.html


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