don't call filecontents.CompressFromDataStore() twice; w/ multiple data stores that causes a round robining and any corruption in the datastore results in incomplete referential changesets; we'd rather just include the corrupt data in an otherwise valid changeset and catch the corruption when the changeset is installed on a system. the error message is much better that way.
don't call filecontents.CompressFromDataStore() twice; w/ multiple data
stores that causes a round robining and any corruption in the datastore
results in incomplete referential changesets; we'd rather just include
the corrupt data in an otherwise valid changeset and catch the corruption
when the changeset is installed on a system. the error message is much
better that way.


sassoftware/conary,sassoftware/conary,sassoftware/conary,sassoftware/conary,sassoftware/conary