[p4] Odd behavior
william_ivey at bmc.com
Sun Jul 20 09:27:18 PDT 2008
Did you examine the first 8192 bytes of the file? My guess is that
this particular file has nothing there that looks binary - that is,
that couldn't be interpreted as text. It's not unusual for
uncompressed graphics files to have long runs of text-like bytes.
(Although file types with header information may introduce a few
obviously non-text bytes at the beginning, that's not guaranteed.)
Forcing the file type is the documented solution.
From: perforce-user-bounces at perforce.com
[mailto:perforce-user-bounces at perforce.com] On Behalf Of Michael Delaney
Sent: Saturday, July 19, 2008 5:21 PM
So I was updating some of my projects over the weekend when I came
across an odd behavior. I was trying to update a graphics library I use
to generate documentation (Doxygen and Graphviz). When I tried to add a
file called 'ok3.raw' Perforce would complain about the file having
errors, I assume this is when Perforce was attempting to detect the file
type (text, binary ... etc). The part that was odd is this wasn't the
only file of type '.raw' that I submitted and I don't have a typemap set
to '.raw' either.
I was able to correct this issue by forcibly changing the file type to
binary and submitting. My question is has anyone else seen this issue? I
think it's a bug in Perforce but wanted to collect more data on the
[ Error Info ]
p4 submit -f submitunchanged -i
Change 442 updated.
Submitting change 442.
Translation of file content failed near line 1
Submit aborted -- fix problems then use 'p4 submit -c 442'.
Some file(s) could not be transferred from client.
[ Server Info ]
Server date: 2008/07/19 18:15:34 -0400 Eastern Daylight Time
Server version: P4D/NTX86/2007.3/150204 (2008/03/27)
perforce-user mailing list - perforce-user at perforce.com
More information about the perforce-user