Red Hat Bugzilla – Bug 815601
csprocessor status is misleading
Last modified: 2014-10-19 19:00:45 EDT
After performing extensive edits to my local content spec, csprocessor status tells me:
"The local copy of the Content Specification is up to date."
I'm expecting it to inform me: "You have unsaved local changes".
OS: Fedora release 15 (Lovelock)
JAVA: java version "1.7.0_01"
Java(TM) SE Runtime Environment (build 1.7.0_01-b08)
Java HotSpot(TM) 64-Bit Server VM (build 21.1-b02, mixed mode)
Confirmed. The issue is that the local copy is only checked for it's checksum value then compared to the server copy. The checksum from the local copy should be calculated from it's content.
Added in 0.23.3
This is actually an addition because the original feature request just asked to see if the server copy had been changed so that you knew if you had to do a pull to get the latest content.
Now you will get the error:
"The local copy of the Content Specification is out of date. Please use "csprocessor pull" to download the latest copy."
If the server copy has been updated in comparison to the local copy (this is how the command currently works). If the local copy has been updated and still matches the servers checksum then you will get the following error message:
"The local copy of the Content Specification has been updated and is out of sync with the server. Please use "csprocessor push" to update the server copy."
What about case 3:
"You have unsaved changes in your local content spec, but the server copy has been modified since you last synchronised. Use "csprocessor pull" to update your local copy. Your unsaved local changes will be saved as <filename>.backup."
Added in 0.23.3 as well.
The output for the third case is:
ERROR: The local copy and server copy of the Content Specification has been updated. Please use \"csprocessor pull\" to update your local copy. Your unsaved local changes will be saved as Development_Guide-post.backup.
Closing and setting as current release as no QA was performed by the original reporter. If there is still an issue with this bug still than please re-open it.