Hi!
Jürgen A. Erhard <jae@jaerhard.com> writes:
> On Fri, Jan 21, 2011 at 11:04:59PM +0100, Christoph Egger wrote:
>> Can you describe what I need to do to trigger that bug? I've set up
>> a local trac (debian trac + trac-mercurial running on tracd mostly
>> everything default).
>
> This is from a hgwebdir install (dev.jaerhard.com). And it appears
> it's "fixed" when the repo has owner www-data:www-data. The repo has
> 644 perms throughout (+x for directories). So, it appears it needs
> write permissions. Strange.
Ive modified the testsetup to have the repository now owned by a
different entity (different user) and also with different user + group
and couldn't get to the problem.
> Stranger still: I tried tracd on my local box (both remote and local
> w/ current unstable). Works. Tried tracd on the remote box: same
> failure as when used with webserver.
So maybe some deeper detail of the live version. Have you done your
local test on the same tracenv and hg repository?
> I applied the patch in @9943 (referenced in
> http://trac.edgewall.org/ticket/9482) and that fixes it.
Yeah I see how adding that will fix the crash at hand.I could just
apply this -- does just adding tyhe **opts also fix your problem? That
would just make these functions accept a bit nore different input and
won't break anything working if I see that correctly so I could build a
package with that patch attached if the release team prefers as I'm not
sure we'll find the real problem before release.
> I have no, absolutely no idea why it worked on the local box: same
> trac, same trac-mercurial, same mercurial.
Regards
Christoph
--
9FED 5C6C E206 B70A 5857 70CA 9655 22B9 D49A E731
Debian Developer | Lisp Hacker | CaCert Assurer
A. Because it breaks the logical sequence of discussion
Q. Why is top posting bad?
Attachment:
pgpkAcGanqAIX.pgp
Description: PGP signature