summaryrefslogtreecommitdiff
path: root/doc/forum/Privdata_corrupted_when_spinning_from_macOS.mdwn
diff options
context:
space:
mode:
authormithrandi2018-08-14 20:35:31 +0000
committeradmin2018-08-14 20:35:31 +0000
commitc09e4246ce3b497d1ff0ac87060073cc1b96eba9 (patch)
tree5c36c9b2e920185b287601c12ad08ef9360b9ed4 /doc/forum/Privdata_corrupted_when_spinning_from_macOS.mdwn
parent5d9abbd434e8db5961b43f3cbcd49b9cedafc8f8 (diff)
Fix another typo
Diffstat (limited to 'doc/forum/Privdata_corrupted_when_spinning_from_macOS.mdwn')
-rw-r--r--doc/forum/Privdata_corrupted_when_spinning_from_macOS.mdwn2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/forum/Privdata_corrupted_when_spinning_from_macOS.mdwn b/doc/forum/Privdata_corrupted_when_spinning_from_macOS.mdwn
index 2cc827b1..d4df4bac 100644
--- a/doc/forum/Privdata_corrupted_when_spinning_from_macOS.mdwn
+++ b/doc/forum/Privdata_corrupted_when_spinning_from_macOS.mdwn
@@ -1 +1 @@
-I recently added a binary file as privdata (installed with `File.hasPrivContent`). When I `propellor --dump` the property on either Linux or macOS, the contents is correct. Spinning from Linux also works, but spinning from macOS installs a corrupt version of the file. The corruption looks like every valid UTF-8 sequence has been replaced with a single byte which is the lowest byte of the Unicode codepoint encoded by the sequence, so this must have something to do with encodings, but from staring at the source code I can't figure out what. The data from `--dump` is not corrupted which seems especially strange.
+I recently added a binary file as privdata (installed with `File.hasPrivContent`). When I `propellor --dump` the privdata on either Linux or macOS, the contents is correct. Spinning from Linux also works, but spinning from macOS installs a corrupt version of the file. The corruption looks like every valid UTF-8 sequence has been replaced with a single byte which is the lowest byte of the Unicode codepoint encoded by the sequence, so this must have something to do with encodings, but from staring at the source code I can't figure out what. The data from `--dump` is not corrupted which seems especially strange.