Patch fails with 0.10-stable rev 6059

[anonymous]

Hello, I made a checkout of both the most recent 0.10-stable and your patch. After the patch was applied, I tried my sample project and got this.

Traceback (most recent call last):
  File "C:\Python24\Lib\site-packages\trac\web\main.py", line 406, in dispatch_request
    dispatcher.dispatch(req)
  File "C:\Python24\Lib\site-packages\trac\web\main.py", line 208, in dispatch
    chrome.populate_hdf(req, chosen_handler)
  File "C:\Python24\Lib\site-packages\trac\web\chrome.py", line 319, in populate_hdf
    for category, name, text in contributor.get_navigation_items(req):
  File "C:\Python24\Lib\site-packages\trac\Settings.py", line 35, in get_navigation_items
    yield ('metanav', 'settings',
UnicodeDecodeError: 'utf8' codec can't decode bytes in position 11-12: unexpected end of data

[jmt4b04d4v]

Sorry for delay, I've started to research this issue today.

My first conclusions:

• This encoding issue in Win32 was not predicted (it's not an EOL-style issue).
• Patching can be realized in Win32 without hunk inconsistencies (it wasn't planned though).
• Patching procedure in Win32 was reproduced, both with ​Eclipse + ​Subclipse and ​TortoiseSVN. Certainly some files doesn't keep UTF-8 formatting, some do?.
• Patch files were produced with UTF-8 encoding. Revised today again.

Conclusion: Issue needs more attention and research to get solved.

As long as patching works in *nix, these are the suggested OS platforms where to realize patching procedure (with working copies obtained in there). Then, someone can certainly package patched sources to realize installation in any other OS platform.

Due to there is a workaround, I'm changing priority and severity.

[Ryan J Ollos]

Deprecated. See Trac 0.12 if you need a translation.