Password file store conflicts with svn password file rule

[anonymous]

I installed trac on my Win2003 server, and used VisualSVN server as my svn manage tool.
And I used to use the default htpasswd file under svn repository as the universal password file for both svn and trac logins.

As I upgraded trac from 0.11.6 to 0.12.1, I found the password file often damaged by changes in trac.
I checked the htpasswd file and found if it's modified by trac behaviors(change, add, del, etc.), there'll be an extra '\r' before each EOL for every user/password line.

I'm not sure whether this format change will cause other svn servers in trouble, but definitely for visualsvn server(2.15 for win32), it prevent the service from startup, giving an error prompt "Error users file"

Wonder if the open function in 0.12.1 for win32 releases takes param as b or wb? like

f = open('file', 'wb');
}}}[[BR]]
compared to 

{{{
f = open('file', 'b');
}}}


or things like that...

[Steffen Hoffmann]

Replying to anonymous:

![...] As I upgraded trac from 0.11.6 to 0.12.1, I found the password file often damaged by changes in trac.
I checked the htpasswd file and found if it's modified by trac behaviors(change, add, del, etc.), there'll be an extra '\r' before each EOL for every user/password line.

Please, at first report your current version of AcctMgr and put up your email in cc to follow-up. Many reports in tickets here are useless, since I can't make contact to discuss more towards getting a solution or reporter are not responsive despite of a known-good email address.

I've done big changes regarding the Apache password file store handling lately, especially regarding saner handling of line endings. I'm very interested to learn more, if you're at a recent trunk version, but recommend to upgrade at least to/past revision [9272], or [9347] if you care for the improved i18n.

[Steffen Hoffmann]

#8487 might be related, if not a duplicate of this ticket.

Anyway I'll follow-up there, since it has a technically more advanced description of the problem (from my point of view), that will allow us to resolve it soon.

[Steffen Hoffmann]

Once again I recommend to test with a more recent version.

As stated in #8487 any version after [9923] might fix your problem, if still persisting. Would you be so kind as to check this out, please?

Anyway, issues are similar indeed, at least from my point of view, so go over there and report you findings, if different. Thanks for taking your time.