WalaWiki content from p1k3.com
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 

38 lines
1.8 KiB

WareLogging, VersionControl.
= docs / notes =
* http://www.xsteve.at/prg/vc_svn/svn.txt
= weird locale issues =
Weird locale issues: http://www.mail-archive.com/gnome-i18n@gnome.org/msg05471.html
Take a look in /etc/ssh/sshd_config and try commenting out this AcceptEnv line:
# Allow client to pass locale environment variables
#AcceptEnv LANG LC_*
= discussion =
<[Brennen]> WareLogging, VersionControl. Has its ups and downs.
I just spent an hour and a half wrestling with CGI::Application and what appeared to be a nonsensical unix permissions problem. It turns out that svn export doesn't preserve repository permissions (or ownership) - and by extension, I suppose, that svn repositories don't either.
I'm not experienced enough to know whether this is standard behavior for source control systems, but either way it's pretty lame.
<[Brennen]> (Yeah, I get why it would be standard. Still.)
<[Brent]> In my (limited) experience with a handful of source control systems, permission preservation varies wildly from one system to another.
(I challenge anyone to use that last phrase as a song lyric.)
It is quite annoying. I do love it, though; easiest system I've ever used, once I got used to it. Which, granted, took a little while.
I might be able to provide a solution to your problem, if you post details.
<[Brennen]> As I recall, all that was really happening was that certain files needed to be read/write for my app to run. Since these permissions weren't getting preserved when I exported a fresh test installation to my /var/www, things were breaking. I wound up adding a couple of lines to a Makefile to set the appropriate perms directly. There's probably a more graceful way to go about it.
<[Brennen]> Considerably later, I notice that you can do:
svn proposet svn:executable ON filename