I am confused. On Sat, 2011-03-26 at 08:40 +0200, Yavor Nikolov wrote: > On Sat, Mar 26, 2011 at 04:47, Kristis Makris <[email protected]> wrote: > On Tue, 2011-03-22 at 01:01 +0200, Yavor Nikolov wrote: > > > > Got some confirmations for Bugzilla - USAGE_MODE_CMDLINE & > not being > > fork-safe nor thread-safe > (https://groups.google.com/forum/#! > > topic/mozilla.support.bugzilla/h-a4WOJZTkY) > > > This thread does not bring up a page describing the > USAGE_MODE_CMDLINE. > Changing usage_mode was one of the proposed workarounds here (setting > SERVER_SOFTWARE environment variable does change usage_mode to > USAGE_MODE_BROWSER).
Should Scmbug set USAGE_MODE_CMDLINE or USAGE_MODE_BROWSER? > > * scmbug_bugzilla_usage_mode.patch - explicitly set > usage_mode to > > cmdline (since it wasn't the default mode before Bugzilla > 3.4.1) > > > How can we be sure it wasn't the default mode before Bugzilla > 3.4.1? > http://bzr.mozilla.org/bugzilla/3.2/annotate/head:/Bugzilla.pm > 388 5249 return $class->request_cache->{usage_mode} # > request_cache is empty when used by Scmbug > 389 4471 || Bugzilla::Constants::USAGE_MODE_BROWSER; Which is the first Bugzilla version that breaks unless Scmbug does something different than what it was doing before? I thought that was version 4.0. The link refers to 3.2. The discussion above to 3.4.1. > The goal of the bug is to make Scmbug work on Bugzilla 4.0. It > clearly > works on 3.0, 3.2, and 3.4. > > http://bugzilla.mkgnu.net/show_bug.cgi?id=1523 >
signature.asc
Description: This is a digitally signed message part
_______________________________________________ scmbug-users mailing list [email protected] http://lists.mkgnu.net/cgi-bin/mailman/listinfo/scmbug-users
