Bug 750970
Summary: | Add SpecRevision attribute | ||
---|---|---|---|
Product: | [Community] PressGang CCMS | Reporter: | Joshua Wulf <jwulf> |
Component: | CSProcessor | Assignee: | Lee Newson <lnewson> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 1.x | CC: | jwulf, lcarlon |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | 0.15.0 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2011-11-11 11:12:49 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 751251 |
Description
Joshua Wulf
2011-11-03 03:24:01 UTC
And what to do if SpecRevision is missing on --edit? Fail with: "SpecRevision" attribute not found in Content Specification. Added. SpecRevision will automatically be added/updated when pushing in a content specification. The SpecRevision tag must be under the ID and above the Title attributes. Error messages are implemented as described above, except if the revisions don't match. The output from non-matching revision numbers is shown below: ERROR: Invalid Content Specification! Revisions must match to be edited. -> SpecRevision: 12 -> Current Revision: 14 |