You can subscribe to this list here.
2000 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(7) |
Nov
(29) |
Dec
(101) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2001 |
Jan
(90) |
Feb
(101) |
Mar
(173) |
Apr
(141) |
May
(38) |
Jun
(28) |
Jul
(14) |
Aug
(7) |
Sep
(3) |
Oct
(7) |
Nov
(15) |
Dec
(9) |
2002 |
Jan
(2) |
Feb
(5) |
Mar
(11) |
Apr
|
May
(4) |
Jun
(6) |
Jul
(7) |
Aug
(12) |
Sep
(8) |
Oct
(1) |
Nov
(4) |
Dec
(7) |
2003 |
Jan
(7) |
Feb
(1) |
Mar
(9) |
Apr
(2) |
May
(3) |
Jun
(4) |
Jul
(19) |
Aug
(4) |
Sep
(8) |
Oct
(30) |
Nov
(25) |
Dec
(22) |
2004 |
Jan
(6) |
Feb
(12) |
Mar
|
Apr
(2) |
May
|
Jun
(10) |
Jul
(18) |
Aug
(2) |
Sep
(4) |
Oct
(4) |
Nov
(4) |
Dec
(4) |
2005 |
Jan
(8) |
Feb
(4) |
Mar
(6) |
Apr
(5) |
May
|
Jun
(2) |
Jul
(1) |
Aug
|
Sep
(1) |
Oct
(4) |
Nov
(3) |
Dec
|
2006 |
Jan
(9) |
Feb
(6) |
Mar
(11) |
Apr
|
May
(2) |
Jun
|
Jul
(2) |
Aug
(10) |
Sep
(8) |
Oct
|
Nov
(1) |
Dec
(1) |
2007 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
(7) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2008 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2009 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Brian A. <br...@ta...> - 2001-02-17 07:45:10
|
I've been playing with compiling DSO and non-DSO based modules into Apache tonight. I have found that slash (AKA bender) works far more reliably with Apache 1.3.17 and mod_perl 1.25 then any other version. If you find you are having problems and you need DSO support I would suggest upgrading. -Brian -- _______________________________________________________ Brian Aker, br...@ta... Slashdot Senior Developer Seattle, Washington http://tangent.org/~brian/ http://slashdot.org/ _______________________________________________________ You can't grep a dead tree. |
From: CertIndex.com W. <web...@ce...> - 2001-02-16 16:55:07
|
Any PostgreSQL port Bender users out here? |
From: T F <tf...@ho...> - 2001-02-15 12:43:55
|
Update your CVS. I know they found the bug inthe ladybug schema and fixed it. I'm 99% certain that change was committed to CVS before 5pm yesterday. Because when I did installs last nite I didn't see the bug. But I didn't go looking for it either... >From: "CertIndex.com Webmaster" <web...@ce...> >Reply-To: sla...@li... >To: <sla...@li...> >Subject: Re: [Slashcode-development] installation >Date: Sun, 13 Feb 2000 06:43:16 -0800 >MIME-Version: 1.0 >Received: from [216.136.171.194] by hotmail.com (3.2) with ESMTP id >MHotMailBC5293550066D820F397D888ABC2F1900; Tue Feb 13 06:44:37 2001 >Received: from localhost ([127.0.0.1] helo=usw-sf-list1.sourceforge.net)by >usw-sf-list1.sourceforge.net with esmtp (Exim 3.16 #1 (Debian))id >14SgfZ-0000YL-00; Tue, 13 Feb 2001 06:43:05 -0800 >Received: from avocet.prod.itd.earthlink.net ([207.217.121.50])by >usw-sf-list1.sourceforge.net with esmtp (Exim 3.16 #1 (Debian))id >14SgfB-0000Wx-00for <sla...@li...>; Tue, 13 >Feb 2001 06:42:41 -0800 >Received: from happy (sdn-ar-001walynwP146.dialsprint.net >[158.252.226.82])by avocet.prod.itd.earthlink.net (EL-8_9_3_3/8.9.3) with >SMTP id GAA20872for <sla...@li...>; Tue, 13 >Feb 2001 06:43:15 -0800 (PST) >From sla...@li... Tue Feb 13 06:45:13 >2001 >Message-ID: <02fb01bf7630$aad92ad0$84e1fc9e@happy> >References: <F13...@ho...> >Organization: CertIndex.com >X-Priority: 3 >X-MSMail-Priority: Normal >X-Mailer: Microsoft Outlook Express 5.50.4133.2400 >X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 >Sender: sla...@li... >Errors-To: sla...@li... >X-BeenThere: sla...@li... >X-Mailman-Version: 2.0 >Precedence: bulk >List-Help: ><mailto:sla...@li...?subject=help> >List-Post: <mailto:sla...@li...> >List-Subscribe: ><http://lists.sourceforge.net/lists/listinfo/slashcode-development>,<mailto:sla...@li...?subject=subscribe> >List-Id: Development mailing list only for slashcode. No new user or >install questions. <slashcode-development.lists.sourceforge.net> >List-Unsubscribe: ><http://lists.sourceforge.net/lists/listinfo/slashcode-development>,<mailto:sla...@li...?subject=unsubscribe> >List-Archive: ><http://lists.sourceforge.net/archives//slashcode-development/> > >any word on when this will be resolved? > >----- Original Message ----- >From: "T F" <tf...@ho...> >To: <sla...@li...> >Sent: Monday, February 12, 2001 7:23 AM >Subject: Re: [Slashcode-development] installation > > > > This is in the bugs list: > > > > http://sourceforge.net/bugs/?func=detailbug&bug_id=131993&group_id=4421 > > > > > > > > >From: Wojtek <so...@ne...> > > >Reply-To: sla...@li... > > >To: sla...@li... > > >Subject: [Slashcode-development] installation > > >Date: Mon, 12 Feb 2001 12:15:59 +0000 > > >MIME-Version: 1.0 > > >Received: from [216.136.171.194] by hotmail.com (3.2) with ESMTP id > > >MHotMailBC5110700031D820F3A1D888ABC2F8490; Mon Feb 12 03:13:52 2001 > > >Received: from localhost ([127.0.0.1] >helo=usw-sf-list1.sourceforge.net)by > > >usw-sf-list1.sourceforge.net with esmtp (Exim 3.16 #1 (Debian))id > > >14SGxe-0006Us-00; Mon, 12 Feb 2001 03:16:02 -0800 > > >Received: from nemezis.ipan.lublin.pl ([212.182.61.154])by > > >usw-sf-list1.sourceforge.net with esmtp (Exim 3.16 #1 (Debian))id > > >14SGx4-0006TR-00for <sla...@li...>; Mon, >12 > > >Feb 2001 03:15:26 -0800 > > >Received: by nemezis.ipan.lublin.pl (Postfix, from userid 1000)id > > >447E2A829; Mon, 12 Feb 2001 12:15:59 +0000 (GMT) > > >From sla...@li... Mon Feb 12 >03:13:58 > > >2001 > > >Message-ID: <200...@ne...> > > >User-Agent: Mutt/1.2i > > >Sender: sla...@li... > > >Errors-To: sla...@li... > > >X-BeenThere: sla...@li... > > >X-Mailman-Version: 2.0 > > >Precedence: bulk > > >List-Help: > > > ><mailto:sla...@li...?subject=help> > > >List-Post: <mailto:sla...@li...> > > >List-Subscribe: > > > ><http://lists.sourceforge.net/lists/listinfo/slashcode-development>,<mailto >:sla...@li...?subject=subscribe> > > >List-Id: Development mailing list only for slashcode. No new user or > > >install questions. <slashcode-development.lists.sourceforge.net> > > >List-Unsubscribe: > > > ><http://lists.sourceforge.net/lists/listinfo/slashcode-development>,<mailto >:sla...@li...?subject=unsubscribe> > > >List-Archive: > > ><http://lists.sourceforge.net/archives//slashcode-development/> > > > > > >hey, > > > > > >newest mysql, latest slash, doing install-slashsite: > > >Rebuilt at Mon Feb 12 14:14:21 2001 > > >DBD::mysql::db do failed: Column 'question' is used with UNIQUE or >INDEX > > >but is not defined as NOT NULL at > > >/usr/lib/perl5/site_perl/i386-linux/Slash/DB/Utility.pm line 345. > > >Error in > > > >library:Slash::Install:/usr/lib/perl5/site_perl/i386-linux/Slash/Install.pm >:183:CREATE > > >TABLE bugs_param ( param_id int(11) NOT NULL auto_increment, bid >int(5) > > >NOT NULL, question int(5), value text, UNIQUE code_key >(bid,question), > > >PRIMARY KEY (param_id)) > > >Which was called > > > >by:Slash::Install:/usr/lib/perl5/site_perl/i386-linux/Slash/Install.pm:129: >CREATE > > >TABLE bugs_param ( param_id int(11) NOT NULL auto_increment, bid >int(5) > > >NOT NULL, question int(5), value text, UNIQUE code_key >(bid,question), > > >PRIMARY KEY (param_id)) > > >Failed on :CREATE TABLE bugs_param ( param_id int(11) NOT NULL > > >auto_increment, bid int(5) NOT NULL, question int(5), value text, > > >UNIQUE code_key (bid,question), PRIMARY KEY (param_id)): > > >Rebuilt at Mon Feb 12 14:14:21 2001 > > >Rebuilt at Mon Feb 12 14:14:21 2001 > > >Rebuilt at Mon Feb 12 14:14:21 2001 > > >Rebuilt at Mon Feb 12 14:14:21 2001 > > > > > >Wojtek > > > > > >_______________________________________________ > > >Slashcode-development mailing list > > >Sla...@li... > > >http://lists.sourceforge.net/lists/listinfo/slashcode-development > > > > _________________________________________________________________ > > Get your FREE download of MSN Explorer at http://explorer.msn.com > > > > > > _______________________________________________ > > Slashcode-development mailing list > > Sla...@li... > > http://lists.sourceforge.net/lists/listinfo/slashcode-development > > > > >_______________________________________________ >Slashcode-development mailing list >Sla...@li... >http://lists.sourceforge.net/lists/listinfo/slashcode-development _________________________________________________________________ Get your FREE download of MSN Explorer at http://explorer.msn.com |
From: Chris N. <pu...@po...> - 2001-02-14 19:41:07
|
At 14:13 -0500 02.14.2001, Steve Linberg wrote: >Yes, I'm fine with having the core slash code in /usr/local, but I'd like >the actual content of the sites in /home so it can easily count against >user quotas. Symlinks from /usr/local/slash/sites to /home/foo seems like >the best way to handle it. Yeah, as long as you remember to "dereference" symbolic links, like with du -D, when you count up sizes. Also, if you don't count those directories separate from the rest, then warn users that any symbolic links in their user directories could mess up their quotas. -- Chris Nandor pu...@po... http://pudge.net/ Open Source Development Network pu...@os... http://osdn.com/ |
From: Chris N. <pu...@po...> - 2001-02-14 19:39:08
|
At 12:09 -0800 02.14.2001, Brian Aker wrote: >It would be a good idea at some point to drop into code_param a full >list >of all locale for someone to use to generate a list of possible >locales. There is no full list, that I am aware of, except for perhaps putting together all permutations of the two ISO lists. -- Chris Nandor pu...@po... http://pudge.net/ Open Source Development Network pu...@os... http://osdn.com/ |
From: Brian A. <br...@ta...> - 2001-02-14 19:30:15
|
Chris Nandor wrote: > > Just so we have this written down somewhere and we are all on the same page > ... language codes in Slash will be locale codes, which are the two-letter, > lowercase, ISO 639 codes for language, and two-letter, uppercase, ISO 3166 > codes for country. Joined with an underscore. Five characters long. > en_US, en_CA, de_DE, zh_CN, ja_JP. > > If we need to change our system later we will, but this is how it is for now. > > (Right now there is not much code in Slash to support languages, but we > wanted to get the templates assigned languages in the database, at least.) Couple of side notes. A template is bound to be uniq based on name,page,section and language. At some point updating the template tool for this would be a good idea, but hardly a big need at the moment. In users_prefs there is also a column for lang. Bother templates and users default to en_US. It would be a good idea at some point to drop into code_param a full list of all locale for someone to use to generate a list of possible locales. -Brian |
From: Chris N. <pu...@po...> - 2001-02-14 19:24:09
|
Just so we have this written down somewhere and we are all on the same page ... language codes in Slash will be locale codes, which are the two-letter, lowercase, ISO 639 codes for language, and two-letter, uppercase, ISO 3166 codes for country. Joined with an underscore. Five characters long. en_US, en_CA, de_DE, zh_CN, ja_JP. If we need to change our system later we will, but this is how it is for now. (Right now there is not much code in Slash to support languages, but we wanted to get the templates assigned languages in the database, at least.) -- Chris Nandor pu...@po... http://pudge.net/ Open Source Development Network pu...@os... http://osdn.com/ |
From: Steve L. <st...@si...> - 2001-02-14 19:12:39
|
On Wed, 14 Feb 2001, Chris Nandor wrote: > At 10:16 -0800 02.14.2001, Brian Aker wrote: > >You could also create links from the /usr/local/slash/sites directory > >to the users home directory. During the install process you can say > >who owns what. > > Yeah, I should have added that ... I was thinking he wanted the actual > files in /home, though. I think symlinks is the easiest way to go, though. Yes, I'm fine with having the core slash code in /usr/local, but I'd like the actual content of the sites in /home so it can easily count against user quotas. Symlinks from /usr/local/slash/sites to /home/foo seems like the best way to handle it. -- Steve Linberg, Chief Goblin Silicon Goblin Technologies http://silicongoblin.com Be kind. Remember, everyone you meet is fighting a hard battle. |
From: Chris N. <pu...@po...> - 2001-02-14 18:34:25
|
At 10:16 -0800 02.14.2001, Brian Aker wrote: >Chris Nandor wrote: >> >Question #2: My inclination is to put the install in /home/slash rather >> >than the default of /usr/local, because I want my hosted sites on >> >/home. I did run into problems during the 1.1.3 install about alternate >> >install prefixes not being fully propagated, which I tried to correct by >> >hand, but I'm not sure I got them all. Can I accept the /usr/local >> >install for the modules and plugins and themes but still put the sites >> >themselves on /home without too much contortion? How are the folks >> >currently using Bender doing it? >> >> If there are broken paths using PREFIX=/home/slash, let us know so we can >> fix them. However, I would recommend just installing in /usr/local/slash >> and then just moving the contents of the site directory manually (editing >> appropriate httpd configs), and editing slashd appropriately to deal with >> the new locations. That should take care of it for you, I think. >You could also create links from the /usr/local/slash/sites directory >to the users home directory. During the install process you can say >who owns what. Yeah, I should have added that ... I was thinking he wanted the actual files in /home, though. I think symlinks is the easiest way to go, though. -- Chris Nandor pu...@po... http://pudge.net/ Open Source Development Network pu...@os... http://osdn.com/ |
From: Steve L. <st...@si...> - 2001-02-14 17:42:40
|
On Wed, 14 Feb 2001, Chris Nandor wrote: > If there are broken paths using PREFIX=/home/slash, let us know so we can > fix them. In my install, the Makefile didn't get the INIT and PREFIX arguments. I specified: make INIT=/etc/rc.d PREFIX=/home/slash Makefile contained: PREFIX = /usr/local/slash INIT = /etc I edited these by hand to read: PREFIX = /home/slash INIT = /etc/rc.d before continuing with the process. > However, I would recommend just installing in /usr/local/slash > and then just moving the contents of the site directory manually (editing > appropriate httpd configs), and editing slashd appropriately to deal with > the new locations. That should take care of it for you, I think. Will do! Thanks (Brian too) for the tips. Steve -- Steve Linberg, Chief Goblin Silicon Goblin Technologies http://silicongoblin.com Be kind. Remember, everyone you meet is fighting a hard battle. |
From: Brian A. <br...@ta...> - 2001-02-14 17:37:10
|
Chris Nandor wrote: > >Question #2: My inclination is to put the install in /home/slash rather > >than the default of /usr/local, because I want my hosted sites on > >/home. I did run into problems during the 1.1.3 install about alternate > >install prefixes not being fully propagated, which I tried to correct by > >hand, but I'm not sure I got them all. Can I accept the /usr/local > >install for the modules and plugins and themes but still put the sites > >themselves on /home without too much contortion? How are the folks > >currently using Bender doing it? > > If there are broken paths using PREFIX=/home/slash, let us know so we can > fix them. However, I would recommend just installing in /usr/local/slash > and then just moving the contents of the site directory manually (editing > appropriate httpd configs), and editing slashd appropriately to deal with > the new locations. That should take care of it for you, I think. You could also create links from the /usr/local/slash/sites directory to the users home directory. During the install process you can say who owns what. -Brian |
From: Chris N. <pu...@po...> - 2001-02-14 17:34:57
|
At 09:47 -0500 02.14.2001, Steve Linberg wrote: >Part of this is rebuilding apache, part is rebuilding slash 1.1.3. I do >still have my 1.0.9 install on my box, which I'm assuming I should remove >in case conflicts are part of the problem. I'll tgz the /home/slash >directory and delete it. Question #1: is there anything else I should do >to make sure the 1.0.9 install is completely gone before I reinstall >1.1.3? Almost everything in 1.0.x is under /home/slash/, unless you moved things elsewhere by hand. Exceptions: /etc/rc.d/slashd, Apache configs, MySQL data. I think that is about it. >Question #2: My inclination is to put the install in /home/slash rather >than the default of /usr/local, because I want my hosted sites on >/home. I did run into problems during the 1.1.3 install about alternate >install prefixes not being fully propagated, which I tried to correct by >hand, but I'm not sure I got them all. Can I accept the /usr/local >install for the modules and plugins and themes but still put the sites >themselves on /home without too much contortion? How are the folks >currently using Bender doing it? If there are broken paths using PREFIX=/home/slash, let us know so we can fix them. However, I would recommend just installing in /usr/local/slash and then just moving the contents of the site directory manually (editing appropriate httpd configs), and editing slashd appropriately to deal with the new locations. That should take care of it for you, I think. -- Chris Nandor pu...@po... http://pudge.net/ Open Source Development Network pu...@os... http://osdn.com/ |
From: Steve L. <st...@si...> - 2001-02-14 14:47:24
|
(BTW: I'm mot sure I'm totally clear where these kinds of questions should go: the dev list or the regular slash list. Since this one is primarily a coding question I figure it's here, but shout if I'm wrong and I'll scoot over to the other one.) I have made zero progress in diagnosing the Bender-Apache 1.3.14/17 startup segfaults I'm having, so I figure it's time for the screw-it-scorch-and-burn rebuild. Part of this is rebuilding apache, part is rebuilding slash 1.1.3. I do still have my 1.0.9 install on my box, which I'm assuming I should remove in case conflicts are part of the problem. I'll tgz the /home/slash directory and delete it. Question #1: is there anything else I should do to make sure the 1.0.9 install is completely gone before I reinstall 1.1.3? Question #2: My inclination is to put the install in /home/slash rather than the default of /usr/local, because I want my hosted sites on /home. I did run into problems during the 1.1.3 install about alternate install prefixes not being fully propagated, which I tried to correct by hand, but I'm not sure I got them all. Can I accept the /usr/local install for the modules and plugins and themes but still put the sites themselves on /home without too much contortion? How are the folks currently using Bender doing it? Cheers, Steve -- Steve Linberg, Chief Goblin Silicon Goblin Technologies http://silicongoblin.com Be kind. Remember, everyone you meet is fighting a hard battle. |
From: shane <sh...@lo...> - 2001-02-14 12:39:48
|
is it possible to close a poll? (so that it cannot be voted on any more) it is possible to close the comment-posting-ability for a poll? |
From: CertIndex.com W. <web...@ce...> - 2001-02-14 10:13:55
|
mysql Ver 9.38 Distrib 3.22.32, for pc-linux-gnu (i686) glad to help! ----- Original Message ----- From: "Brian Aker" <br...@ta...> To: <sla...@li...> Sent: Tuesday, February 13, 2001 9:07 AM Subject: Re: [Slashcode-development] installation > "CertIndex.com Webmaster" wrote: > > > > any word on when this will be resolved? > Should come out today. BTW, what version of > the database are you using? > -Brian > > _______________________________________________ > Slashcode-development mailing list > Sla...@li... > http://lists.sourceforge.net/lists/listinfo/slashcode-development > |
From: <no...@so...> - 2001-02-14 02:06:56
|
Patch #103781 has been updated. Project: slashcode Category: Development branch Status: Open Submitted by: cunctator Assigned to : nobody Summary: Add basedir option to install-slashsite ------------------------------------------------------- For more info, visit: http://sourceforge.net/patch/?func=detailpatch&patch_id=103781&group_id=4421 |
From: Brian A. <br...@ta...> - 2001-02-13 16:27:57
|
"CertIndex.com Webmaster" wrote: > > any word on when this will be resolved? Should come out today. BTW, what version of the database are you using? -Brian |
From: CertIndex.com W. <web...@ce...> - 2001-02-13 14:42:42
|
any word on when this will be resolved? ----- Original Message ----- From: "T F" <tf...@ho...> To: <sla...@li...> Sent: Monday, February 12, 2001 7:23 AM Subject: Re: [Slashcode-development] installation > This is in the bugs list: > > http://sourceforge.net/bugs/?func=detailbug&bug_id=131993&group_id=4421 > > > > >From: Wojtek <so...@ne...> > >Reply-To: sla...@li... > >To: sla...@li... > >Subject: [Slashcode-development] installation > >Date: Mon, 12 Feb 2001 12:15:59 +0000 > >MIME-Version: 1.0 > >Received: from [216.136.171.194] by hotmail.com (3.2) with ESMTP id > >MHotMailBC5110700031D820F3A1D888ABC2F8490; Mon Feb 12 03:13:52 2001 > >Received: from localhost ([127.0.0.1] helo=usw-sf-list1.sourceforge.net)by > >usw-sf-list1.sourceforge.net with esmtp (Exim 3.16 #1 (Debian))id > >14SGxe-0006Us-00; Mon, 12 Feb 2001 03:16:02 -0800 > >Received: from nemezis.ipan.lublin.pl ([212.182.61.154])by > >usw-sf-list1.sourceforge.net with esmtp (Exim 3.16 #1 (Debian))id > >14SGx4-0006TR-00for <sla...@li...>; Mon, 12 > >Feb 2001 03:15:26 -0800 > >Received: by nemezis.ipan.lublin.pl (Postfix, from userid 1000)id > >447E2A829; Mon, 12 Feb 2001 12:15:59 +0000 (GMT) > >From sla...@li... Mon Feb 12 03:13:58 > >2001 > >Message-ID: <200...@ne...> > >User-Agent: Mutt/1.2i > >Sender: sla...@li... > >Errors-To: sla...@li... > >X-BeenThere: sla...@li... > >X-Mailman-Version: 2.0 > >Precedence: bulk > >List-Help: > ><mailto:sla...@li...?subject=help> > >List-Post: <mailto:sla...@li...> > >List-Subscribe: > ><http://lists.sourceforge.net/lists/listinfo/slashcode-development>,<mailto :sla...@li...?subject=subscribe> > >List-Id: Development mailing list only for slashcode. No new user or > >install questions. <slashcode-development.lists.sourceforge.net> > >List-Unsubscribe: > ><http://lists.sourceforge.net/lists/listinfo/slashcode-development>,<mailto :sla...@li...?subject=unsubscribe> > >List-Archive: > ><http://lists.sourceforge.net/archives//slashcode-development/> > > > >hey, > > > >newest mysql, latest slash, doing install-slashsite: > >Rebuilt at Mon Feb 12 14:14:21 2001 > >DBD::mysql::db do failed: Column 'question' is used with UNIQUE or INDEX > >but is not defined as NOT NULL at > >/usr/lib/perl5/site_perl/i386-linux/Slash/DB/Utility.pm line 345. > >Error in > >library:Slash::Install:/usr/lib/perl5/site_perl/i386-linux/Slash/Install.pm :183:CREATE > >TABLE bugs_param ( param_id int(11) NOT NULL auto_increment, bid int(5) > >NOT NULL, question int(5), value text, UNIQUE code_key (bid,question), > >PRIMARY KEY (param_id)) > >Which was called > >by:Slash::Install:/usr/lib/perl5/site_perl/i386-linux/Slash/Install.pm:129: CREATE > >TABLE bugs_param ( param_id int(11) NOT NULL auto_increment, bid int(5) > >NOT NULL, question int(5), value text, UNIQUE code_key (bid,question), > >PRIMARY KEY (param_id)) > >Failed on :CREATE TABLE bugs_param ( param_id int(11) NOT NULL > >auto_increment, bid int(5) NOT NULL, question int(5), value text, > >UNIQUE code_key (bid,question), PRIMARY KEY (param_id)): > >Rebuilt at Mon Feb 12 14:14:21 2001 > >Rebuilt at Mon Feb 12 14:14:21 2001 > >Rebuilt at Mon Feb 12 14:14:21 2001 > >Rebuilt at Mon Feb 12 14:14:21 2001 > > > >Wojtek > > > >_______________________________________________ > >Slashcode-development mailing list > >Sla...@li... > >http://lists.sourceforge.net/lists/listinfo/slashcode-development > > _________________________________________________________________ > Get your FREE download of MSN Explorer at http://explorer.msn.com > > > _______________________________________________ > Slashcode-development mailing list > Sla...@li... > http://lists.sourceforge.net/lists/listinfo/slashcode-development > |
From: Steve L. <st...@si...> - 2001-02-12 23:31:22
|
On Mon, 12 Feb 2001, Chris Nandor wrote: > >- Should I need to re-make slash following the server rebuild? I haven't > >so far, because I couldn't see how it would be related to the apache > >build. > > You should not need to, but I do wonder if you might have some modules not > in the right place, or maybe have the old Slash.pm lying around somewhere. I did find a couple of old Slash.pm's around, although I don't think they were in any path that could have conflicted. I renamed them just in case, but the crash still happens. Should I remove the directory containing my old slash 1.0.9 install? (I'd prefer not to if it's not necessary.) I did an strace of Apache crashing with the slash startup enabled; I'm venturing into unknown territory for myself here. It's monstrously long; the last thing that happens before the segfault is this: read(4, "##\n## access.conf -- Apache HTTP"..., 4096) = 348 read(4, "", 4096) = 0 close(4) = 0 munmap(0x402b3000, 4096) = 0 --- SIGSEGV (Segmentation fault) --- +++ killed by SIGSEGV +++ I posted the whole transcript (about 300k), in case anyone has a second to peek at it and is feeling charitble, at: <http://silicongoblin.com/apache-strace.txt> (or a 39k gzip version at <http://silicongoblin.com/apache-strace.gz>) Finally, I followed the apache recipe at <http://www.delouw.ch/linux/apache.phtml> pretty closely, adding PERL_MARK_WHERE=1 to the mod_perl configuration as per the Slash install instructions. I did this for Slash 1.0.9 as well and it worked fine. I'm pretty stuck at this point; any suggestions would be very, very welcome. I want to start writing some tutorial documentation as well, or at least seed some with answers to my own FAQs. Any clues that help me progress will go in, of course. Cheers! -- Steve Linberg, Chief Goblin Silicon Goblin Technologies http://silicongoblin.com Be kind. Remember, everyone you meet is fighting a hard battle. |
From: Chris N. <pu...@po...> - 2001-02-12 16:28:42
|
OK, some of you may know about POST_CHOMP and PRE_CHOM and TRIM. POST_CHOMP and PRE_CHOMP allow you to automatically remove newlines and whitespace between text and directives, so if both are true (as they are in Slash), this: [% FOREACH user = userlist %] [% user %] [% END %] will be rendered as: [% FOREACH user = userlist %][% user %][% END %] You can de-activate this with "+", so this: [% FOREACH user = userlist %] [%+ user +%] [% END %] Will get treated just like this: [% FOREACH user = userlist %] [% user %] [% END %] Similarly, there is TRIM. This removes leading and trailing whitespace from the output of templates and BLOCKs. This is also on in Slash. I mention this because the behavior of POST_CHOMP and PRE_CHOMP are such that it only works on [ \t\n]. But most of our templates have had "\r" in them, as well, so it was not working properly. I have added code to Slash::Display::Provider to convert CRLF to LF before the template is compiled, so you may now see some slight changes in the output of templates, especially in regard to leading and trailing newlines. This is a similar issue to the previous one; it makes me think that we probably should NOT bother to do "s/\n/\015\012/g" on templates being saved TO the database from files. But if we do, it is not a big deal, because they'll just be stripped before they are compiled. -- Chris Nandor pu...@po... http://pudge.net/ Open Source Development Network pu...@os... http://osdn.com/ |
From: Brian A. <br...@ta...> - 2001-02-12 16:15:04
|
Patrick Galbraith wrote: > in the template tool, a simple /\x0d/\n/ applied to what is going to be > written to file upon pulling them out of the database would solve this > particular issue. Right now, we're writing to file the contents that are > literally in the db (which includes the LF/CRLF '^M's). Trying to edit > these files with the ^M in them is a little troublesome In vi (or vim) do this: : %s/^V^M//g After you it ^V it will then let you enter control characters. When I have found files with ^M in them, I have just been removing them. -Brian |
From: Brian A. <br...@ta...> - 2001-02-12 16:12:09
|
shane wrote: > Is there a way to remove a plugin that has been installed to a slashsite? > ~slash/bin/install-plugin > will list them, and install them, but I didn't notice a method to > remove them. Not currently but I will add that to my list if "wish" utilities. -Brian |
From: Chris N. <pu...@po...> - 2001-02-12 15:54:44
|
At 10:51 -0500 02.12.2001, Patrick Galbraith wrote: >in the template tool, a simple /\x0d/\n/ applied to what is going to be >written to file upon pulling them out of the database would solve this >particular issue. No, it wouldn't. Then you would have \n\n instead of \n for each CRLF. You would need "s/\015\012/\n/g" (I prefer octal to hex, since I believe it is more universally understood, but whatever), not just a mere "s/\015/\n/g". >Right now, we're writing to file the contents that are >literally in the db (which includes the LF/CRLF '^M's). Trying to edit >these files with the ^M in them is a little troublesome. Exactly. So the simple regex above would solve it. If we did this, we could also then do "s/\n/\015\012/g" on the data before writing TO the database, so the CRLF would be saved back in the database. Although I doubt it would matter, it wouldn't hurt (as long as the data was already only LF ... we might want to do something like "$data =~ s/\n/\015\012/g unless $data =~ /\015\012/", just to make sure we are not converting CRLF data to CRCRLF). -- Chris Nandor pu...@po... http://pudge.net/ Open Source Development Network pu...@os... http://osdn.com/ |
From: Patrick G. <cap...@sl...> - 2001-02-12 15:41:46
|
Chris Nandor wrote: > > Right now, our template files have a mix of LF and CRLF in them. That is, > teh templates themselves contain data that is CRLF (from the database), > while the rest of the file is written with regular LF. This seems > suboptimal to me, and makes us more prone to error. We need to decide how > we want to have this handled. I think we should not leave it as-is, but > perhaps should convert from "\015\012" to "\n" on reading from the > database, and convert from "\n" to "\015\012" on writing to the database. > > Thoughts? > > -- > Chris Nandor pu...@po... http://pudge.net/ > Open Source Development Network pu...@os... http://osdn.com/ > > _______________________________________________ > Slashcode-development mailing list > Sla...@li... > http://lists.sourceforge.net/lists/listinfo/slashcode-development in the template tool, a simple /\x0d/\n/ applied to what is going to be written to file upon pulling them out of the database would solve this particular issue. Right now, we're writing to file the contents that are literally in the db (which includes the LF/CRLF '^M's). Trying to edit these files with the ^M in them is a little troublesome. |
From: Chris N. <pu...@po...> - 2001-02-12 15:33:22
|
Right now, our template files have a mix of LF and CRLF in them. That is, teh templates themselves contain data that is CRLF (from the database), while the rest of the file is written with regular LF. This seems suboptimal to me, and makes us more prone to error. We need to decide how we want to have this handled. I think we should not leave it as-is, but perhaps should convert from "\015\012" to "\n" on reading from the database, and convert from "\n" to "\015\012" on writing to the database. Thoughts? -- Chris Nandor pu...@po... http://pudge.net/ Open Source Development Network pu...@os... http://osdn.com/ |