未知字段名称“SubmitOptions” Perforce升级后
我刚刚从 Windows 2003 Perforce 2009.2 安装迁移/升级到 Windows 2008 R2 2010.2，并注意到升级后，似乎出现的唯一问题是无法从 UI 创建/编辑工作区 - 因为它尝试设置SubmitOptions 参数并抛出
Error at line 0 of field 'SubmitOptions' in client specification.
Unknown field name 'SubmitOptions'.
“是的，我可以使用 p4 客户端 创建/编辑客户端规范，只要我不尝试”包含 SubmitOptions 参数。
据我所知，升级的各个方面都成功了（p4d 替换、p4d -xu 升级数据库、许可证到位等）
有什么想法吗？尚未在网上找到有关此问题的耳语（我的 Google-fu 非常好......）
更新： p4 spec -o client 的输出（我已删除所有注释）
# A Perforce Spec Specification.
Fields:
301 Client word 32 key
302 Update date 20 always
303 Access date 20 always
304 Owner word 32 optional
305 Host word 32 optional
306 Description text 128 optional
307 Root line 64 required
308 AltRoots llist 64 optional
309 Options line 64 optional
310 LineEnd select 12 optional
311 View wlist 64 optional
Words:
View 2
Formats:
Client 1 normal
Update 2 L
Access 4 L
Owner 3 R
Host 5 R
LineEnd 0 L
Values:
Options noallwrite/allwrite,noclobber/clobber,nocompress/compress,unlocked/locked,nomodtime/modtime,normdir/rmdir
LineEnd local/unix/mac/win/share
I just migrated/upgraded from a Windows 2003 Perforce 2009.2 installation to a Windows 2008 R2 2010.2 box and noted that after the upgrade, the only issue that seems to present is the inability to create/edit workspaces from the UI - because it tries to set the SubmitOptions parameter and throws
Error at line 0 of field 'SubmitOptions' in client specification.
Unknown field name 'SubmitOptions'.
Yes, I'm able to create/edit client spec using p4 client, as long as I don't try to include the SubmitOptions parameter.
As far as I can tell, all aspects of the upgrade succeeded (p4d replacement, p4d -xu to upgrade the database, license in place, etc.)
Any ideas? Haven't found a whisper of this issue online (and my Google-fu is pretty good...)
Updates:
Output from p4 spec -o client (I've removed all comments)
# A Perforce Spec Specification.
Fields:
301 Client word 32 key
302 Update date 20 always
303 Access date 20 always
304 Owner word 32 optional
305 Host word 32 optional
306 Description text 128 optional
307 Root line 64 required
308 AltRoots llist 64 optional
309 Options line 64 optional
310 LineEnd select 12 optional
311 View wlist 64 optional
Words:
View 2
Formats:
Client 1 normal
Update 2 L
Access 4 L
Owner 3 R
Host 5 R
LineEnd 0 L
Values:
Options noallwrite/allwrite,noclobber/clobber,nocompress/compress,unlocked/locked,nomodtime/modtime,normdir/rmdir
LineEnd local/unix/mac/win/share
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
最后，向客户端规范提交以下添加内容解决了问题：
我将这些添加到以前的值中，并使用以下组合提交了更改：“
需要第一个命令，因为我收到了
“自定义规范类型”的错误不允许设置spec.custom=1 来覆盖。”当我尝试在没有它的情况下更新规范时。我实际上并不知道需要使用第 314 行来解决这个问题，但在与其他地方适用的规范进行比较时，有人建议使用第 314 行。感谢您的帮助！
In the end, submitting the following additions to the client spec resolved the issue:
I added those to the previous values and submitted the changes using the combination of
The first command was required because I received an error of
"Custom spec of type 'client' is not allowed. Set spec.custom=1 to override."when I tried to update the spec without it. And I don't actually know that line 314 was needed to address this problem, but it was suggested when diffed against a spec that worked elsewhere.Thanks for the assistance!