lxr-developer — Don't use, active developers only

[Lxr-dev] [ lxr-Bugs-1209273 ] "release" a reserved word in MySQL 5.x

[SourceForge.net <no...@so...>]

Bugs item #1209273, was opened at 2005-05-26 12:33
Message generated for change (Comment added) made by bstpierre
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=390117&aid=1209273&group_id=27350

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Database interface
Group: None
Status: Open
Resolution: Accepted
Priority: 5
Submitted By: Jeff Warnica (jeffwarnica)
Assigned to: Malcolm Box (mbox)
Summary: "release" a reserved word in MySQL 5.x

Initial Comment:
And perhaps earlier versions too.

The table lxr_releases can not be created..

The MySQL docs claim that you can use reserved words as
identifiers if you quote them, but testing the CREATE
TABLE with "release" quoted also failed. 

----------------------------------------------------------------------

Comment By: Brian St. Pierre (bstpierre)
Date: 2006-10-06 13:40

Message:
Logged In: YES 
user_id=10357

Looking in CVS, it doesn't appear that the patch was applied to Mysql.pm. (I do see the change in initdb-mysql.)

----------------------------------------------------------------------

Comment By: Danny (perunaion)
Date: 2006-09-15 22:20

Message:
Logged In: YES 
user_id=1047608

Release 1559658, attempts to address this issue.
Its a patch of the two modified files (Mysql.pm and
initdb-mysql).  Hopefully that will help fix this.

----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2006-07-13 19:59

Message:
Logged In: NO 

You need to change BOTH the initdb-mysql script and the
Mysql.pm module (8 occurrences total).  You can either
change the name of the 'release' field (which was the route
I took), or quote it with back-ticks.

----------------------------------------------------------------------

Comment By: Laurence Passmore (lmop)
Date: 2006-06-07 04:25

Message:
Logged In: YES 
user_id=1410237

I think you need to change lib/LXR/Index/Mysql.pm thus:

1) s/r.release/r.`release`/g

2) s/release =/`release` =/g

3) s/ release\)/ `release`\)/g

(I say think because I haven't tested it; I currently have other issues with my LXR 
installation that is preventing me from getting it working at all...)

----------------------------------------------------------------------

Comment By: Malcolm Box (mbox)
Date: 2006-06-06 18:24

Message:
Logged In: YES 
user_id=215386

Apparently not a good fix - reopening

----------------------------------------------------------------------

Comment By: Malcolm Box (mbox)
Date: 2006-06-05 06:16

Message:
Logged In: YES 
user_id=215386

Now fixed in CVS. Thanks to lmop for the fix.

----------------------------------------------------------------------

Comment By: S Melody (prplehaze2)
Date: 2006-05-31 11:37

Message:
Logged In: YES 
user_id=911986

I used this fix to create the tables, but indexing seems to
fail, most likely because release is a reserved word:

DBD::mysql::st execute failed: You have an error in your SQL
syntax; check the manual that corresponds to your MySQL
server version for the right syntax to use near 'release =
'head'' at line 1 at lib/LXR/Index/Mysql.pm line 209.
DBD::mysql::st execute failed: You have an error in your SQL
syntax; check the manual that corresponds to your MySQL
server version for the right syntax to use near 'release)
values ('387', 'head')' at line 1 at lib/LXR/Index/Mysql.pm
line 213.


----------------------------------------------------------------------

Comment By: Laurence Passmore (lmop)
Date: 2005-12-21 12:20

Message:
Logged In: YES 
user_id=1410237

This is a simple fix. initdb-mysql should be changed as follows (basically, 
backtick (`) the column name `release` to escape/quote it):

create table lxr_releases (
        fileid          int not null references lxr_files,
        `release`       char(255) binary not null,
        primary key     (fileid, `release`)
);

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=390117&aid=1209273&group_id=27350

[Lxr-dev] [ lxr-Patches-1570479 ] Debian patches

[SourceForge.net <no...@so...>]

Patches item #1570479, was opened at 2006-10-04 08:51
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=390119&aid=1570479&group_id=27350

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Giacomo Catenazzi (cate)
Assigned to: Nobody/Anonymous (nobody)
Summary: Debian patches

Initial Comment:
I send you the debian patch to lxr. You can eventually
cherry pick che relevant parts.
Summary:

* a new Makefile to install files to right directory
* allow the split (and split) files in more LHS
compatible directories:
  - configuration in /etc
  - cgi scripts in /usr/lib/cgi-bin/
  - doc in /usr/share/doc
* a quick install guide
* other non relevant, debian specific files

Maybe the more interesting thing is to move Local.pm
into  lib/LXR perl directory. (unfortunately not yet a
clean patch)

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=390119&aid=1570479&group_id=27350

[Lxr-dev] [ lxr-Bugs-1209273 ] "release" a reserved word in MySQL 5.x

[SourceForge.net <no...@so...>]

Bugs item #1209273, was opened at 2005-05-26 12:33
Message generated for change (Comment added) made by perunaion
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=390117&aid=1209273&group_id=27350

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Database interface
Group: None
Status: Open
Resolution: Accepted
Priority: 5
Submitted By: Jeff Warnica (jeffwarnica)
Assigned to: Malcolm Box (mbox)
Summary: "release" a reserved word in MySQL 5.x

Initial Comment:
And perhaps earlier versions too.

The table lxr_releases can not be created..

The MySQL docs claim that you can use reserved words as
identifiers if you quote them, but testing the CREATE
TABLE with "release" quoted also failed. 

----------------------------------------------------------------------

Comment By: Danny (perunaion)
Date: 2006-09-15 22:20

Message:
Logged In: YES 
user_id=1047608

Release 1559658, attempts to address this issue.
Its a patch of the two modified files (Mysql.pm and
initdb-mysql).  Hopefully that will help fix this.

----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2006-07-13 19:59

Message:
Logged In: NO 

You need to change BOTH the initdb-mysql script and the
Mysql.pm module (8 occurrences total).  You can either
change the name of the 'release' field (which was the route
I took), or quote it with back-ticks.

----------------------------------------------------------------------

Comment By: Laurence Passmore (lmop)
Date: 2006-06-07 04:25

Message:
Logged In: YES 
user_id=1410237

I think you need to change lib/LXR/Index/Mysql.pm thus:

1) s/r.release/r.`release`/g

2) s/release =/`release` =/g

3) s/ release\)/ `release`\)/g

(I say think because I haven't tested it; I currently have other issues with my LXR 
installation that is preventing me from getting it working at all...)

----------------------------------------------------------------------

Comment By: Malcolm Box (mbox)
Date: 2006-06-06 18:24

Message:
Logged In: YES 
user_id=215386

Apparently not a good fix - reopening

----------------------------------------------------------------------

Comment By: Malcolm Box (mbox)
Date: 2006-06-05 06:16

Message:
Logged In: YES 
user_id=215386

Now fixed in CVS. Thanks to lmop for the fix.

----------------------------------------------------------------------

Comment By: S Melody (prplehaze2)
Date: 2006-05-31 11:37

Message:
Logged In: YES 
user_id=911986

I used this fix to create the tables, but indexing seems to
fail, most likely because release is a reserved word:

DBD::mysql::st execute failed: You have an error in your SQL
syntax; check the manual that corresponds to your MySQL
server version for the right syntax to use near 'release =
'head'' at line 1 at lib/LXR/Index/Mysql.pm line 209.
DBD::mysql::st execute failed: You have an error in your SQL
syntax; check the manual that corresponds to your MySQL
server version for the right syntax to use near 'release)
values ('387', 'head')' at line 1 at lib/LXR/Index/Mysql.pm
line 213.


----------------------------------------------------------------------

Comment By: Laurence Passmore (lmop)
Date: 2005-12-21 12:20

Message:
Logged In: YES 
user_id=1410237

This is a simple fix. initdb-mysql should be changed as follows (basically, 
backtick (`) the column name `release` to escape/quote it):

create table lxr_releases (
        fileid          int not null references lxr_files,
        `release`       char(255) binary not null,
        primary key     (fileid, `release`)
);

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=390117&aid=1209273&group_id=27350

[Lxr-dev] [ lxr-Patches-1559658 ] mysql5 bugfixes for release reserved word

[SourceForge.net <no...@so...>]

Patches item #1559658, was opened at 2006-09-15 22:19
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=390119&aid=1559658&group_id=27350

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: DB backends
Group: Bugfix
Status: Open
Resolution: None
Priority: 5
Submitted By: Danny (perunaion)
Assigned to: Nobody/Anonymous (nobody)
Summary: mysql5 bugfixes for release reserved word

Initial Comment:
In MySQL 5, 'release' became a keyword, one of the
tables uses it as a column name, to deal with this it
must be inclosed in back-ticks.  Attached is a patch of
0.9.5 directory against fixes made in two files.
initdb-mysql and lib/LXR/Index/Mysql.pm.
To use the patch, extract the tgz and execute the command:
patch -p0 <mysql5_release_reserved_word.patch
The -p0 parameter specifies how much of the tree the
patch program should ignore.  Depending on your current
directory, you may have to alter this value to be greater.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=390119&aid=1559658&group_id=27350

[Lxr-dev] [ lxr-Bugs-1558177 ] Directories with 2 character names

[SourceForge.net <no...@so...>]

Bugs item #1558177, was opened at 2006-09-13 13:44
Message generated for change (Comment added) made by jameadows
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=390117&aid=1558177&group_id=27350

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Browsing
Group: v0.9.3
Status: Open
Resolution: None
Priority: 5
Submitted By: Joe Meadows (jameadows)
Assigned to: Nobody/Anonymous (nobody)
Summary: Directories with 2 character names

Initial Comment:
Using LXR 0.9.3 I noticed that I could not browse into
directories that had two character names (e.g. fs, db,
nc).  I tracked the source of the problem down to this
code in Common.pm, around line 550:

# Clean out /../
while ($path =~ m!/../!) 
{
   $path = s!/\.\./!/!g;
}

I made the change on the first line:
while ($path =~ m!/\.\./!) 
{
   $path = s!/\.\./!/!g;
}

This appears to have fixed the problem for me, but when
it comes to Perl I know just about enough to be
dangerous so it would be good for someone more Perl
saavy check this out.  I think the previous regex
expression was matching any two chars and not the
literal '..' as intended.

----------------------------------------------------------------------

>Comment By: Joe Meadows (jameadows)
Date: 2006-09-13 13:53

Message:
Logged In: YES 
user_id=941094

Ah, should have checked v 0.9.5 first, it fixes this bug :)

----------------------------------------------------------------------

Comment By: Joe Meadows (jameadows)
Date: 2006-09-13 13:53

Message:
Logged In: YES 
user_id=941094

This has now been fixed in CVS.

If you can install the new version and check that it solves your
problem, then it would be very useful.

Thanks for reporting this defect and helping to make LXR better.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=390117&aid=1558177&group_id=27350

[Lxr-dev] [ lxr-Bugs-1558177 ] Directories with 2 character names

[SourceForge.net <no...@so...>]

Bugs item #1558177, was opened at 2006-09-13 13:44
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=390117&aid=1558177&group_id=27350

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Browsing
Group: v0.9.3
Status: Open
Resolution: None
Priority: 5
Submitted By: Joe Meadows (jameadows)
Assigned to: Nobody/Anonymous (nobody)
Summary: Directories with 2 character names

Initial Comment:
Using LXR 0.9.3 I noticed that I could not browse into
directories that had two character names (e.g. fs, db,
nc).  I tracked the source of the problem down to this
code in Common.pm, around line 550:

# Clean out /../
while ($path =~ m!/../!) 
{
   $path = s!/\.\./!/!g;
}

I made the change on the first line:
while ($path =~ m!/\.\./!) 
{
   $path = s!/\.\./!/!g;
}

This appears to have fixed the problem for me, but when
it comes to Perl I know just about enough to be
dangerous so it would be good for someone more Perl
saavy check this out.  I think the previous regex
expression was matching any two chars and not the
literal '..' as intended.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=390117&aid=1558177&group_id=27350

[Lxr-dev] [ lxr-Patches-1558027 ] mysql5 support - completely cleaned up initdb-mysql

[SourceForge.net <no...@so...>]

Patches item #1558027, was opened at 2006-09-13 18:34
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=390119&aid=1558027&group_id=27350

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Auke Kok (sofar)
Assigned to: Nobody/Anonymous (nobody)
Summary: mysql5 support - completely cleaned up initdb-mysql

Initial Comment:

Here's a gratuitous mysql initdb file that not only
fixes the mysql5 setup problem but does a full cleanup
to the file which was badly needed. For 0.9.5.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=390119&aid=1558027&group_id=27350

[Lxr-dev] [ lxr-Patches-1525027 ] mysql5 support

[SourceForge.net <no...@so...>]

Patches item #1525027, was opened at 2006-07-19 00:18
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=390119&aid=1525027&group_id=27350

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: DB backends
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: mysql5 support

Initial Comment:
Index: initdb-mysql
===================================================================
RCS file: /cvsroot/lxr/lxr/initdb-mysql,v
retrieving revision 1.11
diff -u -r1.11 initdb-mysql
--- initdb-mysql	5 Jun 2006 10:15:02 -0000	1.11
+++ initdb-mysql	19 Jul 2006 07:12:43 -0000
@@ -35,7 +35,7 @@
 create table lxr_releases 
         (fileid         int not null references lxr_files,
         `release`         char(255) binary not null,
-        primary key     (fileid,release)
+        primary key     (fileid,`release`)
 );
 
 create table lxr_useage


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=390119&aid=1525027&group_id=27350

[Lxr-dev] [ lxr-Bugs-1209273 ] "release" a reserved word in MySQL 5.x

[SourceForge.net <no...@so...>]

Bugs item #1209273, was opened at 2005-05-26 09:33
Message generated for change (Comment added) made by nobody
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=390117&aid=1209273&group_id=27350

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Database interface
Group: None
Status: Open
Resolution: Accepted
Priority: 5
Submitted By: Jeff Warnica (jeffwarnica)
Assigned to: Malcolm Box (mbox)
Summary: "release" a reserved word in MySQL 5.x

Initial Comment:
And perhaps earlier versions too.

The table lxr_releases can not be created..

The MySQL docs claim that you can use reserved words as
identifiers if you quote them, but testing the CREATE
TABLE with "release" quoted also failed. 

----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2006-07-13 16:59

Message:
Logged In: NO 

You need to change BOTH the initdb-mysql script and the
Mysql.pm module (8 occurrences total).  You can either
change the name of the 'release' field (which was the route
I took), or quote it with back-ticks.

----------------------------------------------------------------------

Comment By: Laurence Passmore (lmop)
Date: 2006-06-07 01:25

Message:
Logged In: YES 
user_id=1410237

I think you need to change lib/LXR/Index/Mysql.pm thus:

1) s/r.release/r.`release`/g

2) s/release =/`release` =/g

3) s/ release\)/ `release`\)/g

(I say think because I haven't tested it; I currently have other issues with my LXR 
installation that is preventing me from getting it working at all...)

----------------------------------------------------------------------

Comment By: Malcolm Box (mbox)
Date: 2006-06-06 15:24

Message:
Logged In: YES 
user_id=215386

Apparently not a good fix - reopening

----------------------------------------------------------------------

Comment By: Malcolm Box (mbox)
Date: 2006-06-05 03:16

Message:
Logged In: YES 
user_id=215386

Now fixed in CVS. Thanks to lmop for the fix.

----------------------------------------------------------------------

Comment By: S Melody (prplehaze2)
Date: 2006-05-31 08:37

Message:
Logged In: YES 
user_id=911986

I used this fix to create the tables, but indexing seems to
fail, most likely because release is a reserved word:

DBD::mysql::st execute failed: You have an error in your SQL
syntax; check the manual that corresponds to your MySQL
server version for the right syntax to use near 'release =
'head'' at line 1 at lib/LXR/Index/Mysql.pm line 209.
DBD::mysql::st execute failed: You have an error in your SQL
syntax; check the manual that corresponds to your MySQL
server version for the right syntax to use near 'release)
values ('387', 'head')' at line 1 at lib/LXR/Index/Mysql.pm
line 213.


----------------------------------------------------------------------

Comment By: Laurence Passmore (lmop)
Date: 2005-12-21 09:20

Message:
Logged In: YES 
user_id=1410237

This is a simple fix. initdb-mysql should be changed as follows (basically, 
backtick (`) the column name `release` to escape/quote it):

create table lxr_releases (
        fileid          int not null references lxr_files,
        `release`       char(255) binary not null,
        primary key     (fileid, `release`)
);

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=390117&aid=1209273&group_id=27350

[Lxr-dev] [ lxr-Bugs-1209273 ] "release" a reserved word in MySQL 5.x

[SourceForge.net <no...@so...>]

Bugs item #1209273, was opened at 2005-05-26 16:33
Message generated for change (Comment added) made by lmop
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=390117&aid=1209273&group_id=27350

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Database interface
Group: None
Status: Open
Resolution: Accepted
Priority: 5
Submitted By: Jeff Warnica (jeffwarnica)
Assigned to: Malcolm Box (mbox)
Summary: "release" a reserved word in MySQL 5.x

Initial Comment:
And perhaps earlier versions too.

The table lxr_releases can not be created..

The MySQL docs claim that you can use reserved words as
identifiers if you quote them, but testing the CREATE
TABLE with "release" quoted also failed. 

----------------------------------------------------------------------

Comment By: Laurence Passmore (lmop)
Date: 2006-06-07 08:25

Message:
Logged In: YES 
user_id=1410237

I think you need to change lib/LXR/Index/Mysql.pm thus:

1) s/r.release/r.`release`/g

2) s/release =/`release` =/g

3) s/ release\)/ `release`\)/g

(I say think because I haven't tested it; I currently have other issues with my LXR 
installation that is preventing me from getting it working at all...)

----------------------------------------------------------------------

Comment By: Malcolm Box (mbox)
Date: 2006-06-06 22:24

Message:
Logged In: YES 
user_id=215386

Apparently not a good fix - reopening

----------------------------------------------------------------------

Comment By: Malcolm Box (mbox)
Date: 2006-06-05 10:16

Message:
Logged In: YES 
user_id=215386

Now fixed in CVS. Thanks to lmop for the fix.

----------------------------------------------------------------------

Comment By: S Melody (prplehaze2)
Date: 2006-05-31 15:37

Message:
Logged In: YES 
user_id=911986

I used this fix to create the tables, but indexing seems to
fail, most likely because release is a reserved word:

DBD::mysql::st execute failed: You have an error in your SQL
syntax; check the manual that corresponds to your MySQL
server version for the right syntax to use near 'release =
'head'' at line 1 at lib/LXR/Index/Mysql.pm line 209.
DBD::mysql::st execute failed: You have an error in your SQL
syntax; check the manual that corresponds to your MySQL
server version for the right syntax to use near 'release)
values ('387', 'head')' at line 1 at lib/LXR/Index/Mysql.pm
line 213.


----------------------------------------------------------------------

Comment By: Laurence Passmore (lmop)
Date: 2005-12-21 17:20

Message:
Logged In: YES 
user_id=1410237

This is a simple fix. initdb-mysql should be changed as follows (basically, 
backtick (`) the column name `release` to escape/quote it):

create table lxr_releases (
        fileid          int not null references lxr_files,
        `release`       char(255) binary not null,
        primary key     (fileid, `release`)
);

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=390117&aid=1209273&group_id=27350

[Lxr-dev] [ lxr-Bugs-1209273 ] "release" a reserved word in MySQL 5.x

[SourceForge.net <no...@so...>]

Bugs item #1209273, was opened at 2005-05-26 17:33
Message generated for change (Settings changed) made by mbox
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=390117&aid=1209273&group_id=27350

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Database interface
Group: None
>Status: Open
>Resolution: Accepted
Priority: 5
Submitted By: Jeff Warnica (jeffwarnica)
Assigned to: Malcolm Box (mbox)
Summary: "release" a reserved word in MySQL 5.x

Initial Comment:
And perhaps earlier versions too.

The table lxr_releases can not be created..

The MySQL docs claim that you can use reserved words as
identifiers if you quote them, but testing the CREATE
TABLE with "release" quoted also failed. 

----------------------------------------------------------------------

>Comment By: Malcolm Box (mbox)
Date: 2006-06-06 23:24

Message:
Logged In: YES 
user_id=215386

Apparently not a good fix - reopening

----------------------------------------------------------------------

Comment By: Malcolm Box (mbox)
Date: 2006-06-05 11:16

Message:
Logged In: YES 
user_id=215386

Now fixed in CVS. Thanks to lmop for the fix.

----------------------------------------------------------------------

Comment By: S Melody (prplehaze2)
Date: 2006-05-31 16:37

Message:
Logged In: YES 
user_id=911986

I used this fix to create the tables, but indexing seems to
fail, most likely because release is a reserved word:

DBD::mysql::st execute failed: You have an error in your SQL
syntax; check the manual that corresponds to your MySQL
server version for the right syntax to use near 'release =
'head'' at line 1 at lib/LXR/Index/Mysql.pm line 209.
DBD::mysql::st execute failed: You have an error in your SQL
syntax; check the manual that corresponds to your MySQL
server version for the right syntax to use near 'release)
values ('387', 'head')' at line 1 at lib/LXR/Index/Mysql.pm
line 213.


----------------------------------------------------------------------

Comment By: Laurence Passmore (lmop)
Date: 2005-12-21 17:20

Message:
Logged In: YES 
user_id=1410237

This is a simple fix. initdb-mysql should be changed as follows (basically, 
backtick (`) the column name `release` to escape/quote it):

create table lxr_releases (
        fileid          int not null references lxr_files,
        `release`       char(255) binary not null,
        primary key     (fileid, `release`)
);

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=390117&aid=1209273&group_id=27350

[Lxr-dev] [ lxr-Feature Requests-1391862 ] 20051228.0652 $INCLUDE APR

[SourceForge.net <no...@so...>]

Feature Requests item #1391862, was opened at 2005-12-28 10:52
Message generated for change (Comment added) made by mbox
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=390120&aid=1391862&group_id=27350

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: General
Group: Next Release
Status: Open
Priority: 5
Submitted By: GinEric (cybersongs)
Assigned to: Nobody/Anonymous (nobody)
Summary: 20051228.0652  $INCLUDE APR

Initial Comment:
I know you're busy, but would it be possible to 
include the Apache Portable Runtime Libraries so that 
the configure script adheres to true portability? 
 
Specifically, the options --enable-layout=LAYOUT and 
--with-most  would really improve installation and up 
and running lxr without so much manual editing of the 
produced configuration files. 
 
This would help tremendously in getting more 
developers on SourceForge to quickly implement lxr for 
their sources. 
 
Thanks, 
 
Terry James 
meddac 
 

----------------------------------------------------------------------

>Comment By: Malcolm Box (mbox)
Date: 2006-06-05 11:19

Message:
Logged In: YES 
user_id=215386

Hi,

This sounds like a good thing, but I'm not really familiar
with the APR.

Can you give me more info on what this would actually do for
lxr configuration & setup?  A patch would be even better... :-)

Cheers,

Malcolm

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=390120&aid=1391862&group_id=27350

[Lxr-dev] [ lxr-Bugs-1468114 ] Filenames with plusses + causing problems?

[SourceForge.net <no...@so...>]

Bugs item #1468114, was opened at 2006-04-11 01:48
Message generated for change (Comment added) made by mbox
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=390117&aid=1468114&group_id=27350

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Browsing
Group: v0.9.4
>Status: Closed
>Resolution: Fixed
Priority: 5
Submitted By: Joe Elwell (worldjoe)
Assigned to: Nobody/Anonymous (nobody)
Summary: Filenames with plusses + causing problems?

Initial Comment:
I have the Xerces Parser being indexed (among other things). These files, 
when indexed cause problems:
ApacheDOMC++Binding.html
ApacheDOMC++BindingL2.html
ApacheDOMC++BindingL3.html

Here are the error messages I get when trying to perform a search:

[Mon Apr 10 17:25:54 2006] fatal: Apache::ROOT::lxr::search, line 166: 
Nested quantifiers in regex; marked by <-- HERE in m/185 /ThrdPrty/
Xerces-C/doc/html/ApacheDOMC++ <-- HERE BindingL3.html 
"ApacheDOMC++BindingL3.html" 127418
/ at /usr/local/lxr/search line 166.

If I simply remove those 3 files, everything is fine.

Indexing occurs without problem (no errors reported that I've noticed), 
but perhaps this is a genxref problem anyways?

----------------------------------------------------------------------

>Comment By: Malcolm Box (mbox)
Date: 2006-06-05 11:20

Message:
Logged In: YES 
user_id=215386

This should be fixed in v0.9.5.  Let me know if you're still
seeing problems.

Cheers,

Malcolm

----------------------------------------------------------------------

Comment By: Joe Elwell (worldjoe)
Date: 2006-04-19 00:14

Message:
Logged In: YES 
user_id=790622

I should probably point out that I'm running this on OS X Tiger PPC. Shouldn't 
matter, but maybe it does.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=390117&aid=1468114&group_id=27350

[Lxr-dev] [ lxr-Feature Requests-1391862 ] 20051228.0652 $INCLUDE APR

[SourceForge.net <no...@so...>]

Feature Requests item #1391862, was opened at 2005-12-28 05:52
Message generated for change (Comment added) made by cybersongs
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=390120&aid=1391862&group_id=27350

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: General
Group: Next Release
Status: Open
Priority: 5
Submitted By: GinEric (cybersongs)
Assigned to: Nobody/Anonymous (nobody)
Summary: 20051228.0652  $INCLUDE APR

Initial Comment:
I know you're busy, but would it be possible to 
include the Apache Portable Runtime Libraries so that 
the configure script adheres to true portability? 
 
Specifically, the options --enable-layout=LAYOUT and 
--with-most  would really improve installation and up 
and running lxr without so much manual editing of the 
produced configuration files. 
 
This would help tremendously in getting more 
developers on SourceForge to quickly implement lxr for 
their sources. 
 
Thanks, 
 
Terry James 
meddac 
 

----------------------------------------------------------------------

>Comment By: GinEric (cybersongs)
Date: 2006-06-05 21:35

Message:
Logged In: YES 
user_id=1185079

I will have to look it over and see what I can come up with.
 What it would do is make it easier to put things where they
are needed, which means to say, that with one file,
something like layout.lxr, the tree structure for the entire
lxr can be defined by the user according to where he wants
it.  srcdir, libdir, and others.  It allows the developer to
free himself from having to hardwire or hard define where
each part, such as the cgi scripts, have to go.

Let me make a better case for it in a few days and see what
I come up with.


----------------------------------------------------------------------

Comment By: Malcolm Box (mbox)
Date: 2006-06-05 06:19

Message:
Logged In: YES 
user_id=215386

Hi,

This sounds like a good thing, but I'm not really familiar
with the APR.

Can you give me more info on what this would actually do for
lxr configuration & setup?  A patch would be even better... :-)

Cheers,

Malcolm

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=390120&aid=1391862&group_id=27350

[Lxr-dev] [ lxr-Bugs-1209273 ] "release" a reserved word in MySQL 5.x

[SourceForge.net <no...@so...>]

Bugs item #1209273, was opened at 2005-05-26 17:33
Message generated for change (Comment added) made by mbox
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=390117&aid=1209273&group_id=27350

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Database interface
Group: None
>Status: Closed
>Resolution: Fixed
Priority: 5
Submitted By: Jeff Warnica (jeffwarnica)
>Assigned to: Malcolm Box (mbox)
Summary: "release" a reserved word in MySQL 5.x

Initial Comment:
And perhaps earlier versions too.

The table lxr_releases can not be created..

The MySQL docs claim that you can use reserved words as
identifiers if you quote them, but testing the CREATE
TABLE with "release" quoted also failed. 

----------------------------------------------------------------------

>Comment By: Malcolm Box (mbox)
Date: 2006-06-05 11:16

Message:
Logged In: YES 
user_id=215386

Now fixed in CVS. Thanks to lmop for the fix.

----------------------------------------------------------------------

Comment By: S Melody (prplehaze2)
Date: 2006-05-31 16:37

Message:
Logged In: YES 
user_id=911986

I used this fix to create the tables, but indexing seems to
fail, most likely because release is a reserved word:

DBD::mysql::st execute failed: You have an error in your SQL
syntax; check the manual that corresponds to your MySQL
server version for the right syntax to use near 'release =
'head'' at line 1 at lib/LXR/Index/Mysql.pm line 209.
DBD::mysql::st execute failed: You have an error in your SQL
syntax; check the manual that corresponds to your MySQL
server version for the right syntax to use near 'release)
values ('387', 'head')' at line 1 at lib/LXR/Index/Mysql.pm
line 213.


----------------------------------------------------------------------

Comment By: Laurence Passmore (lmop)
Date: 2005-12-21 17:20

Message:
Logged In: YES 
user_id=1410237

This is a simple fix. initdb-mysql should be changed as follows (basically, 
backtick (`) the column name `release` to escape/quote it):

create table lxr_releases (
        fileid          int not null references lxr_files,
        `release`       char(255) binary not null,
        primary key     (fileid, `release`)
);

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=390117&aid=1209273&group_id=27350

[Lxr-dev] [ lxr-Bugs-1209273 ] "release" a reserved word in MySQL 5.x

[SourceForge.net <no...@so...>]

Bugs item #1209273, was opened at 2005-05-26 16:33
Message generated for change (Comment added) made by prplehaze2
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=390117&aid=1209273&group_id=27350

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Database interface
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Jeff Warnica (jeffwarnica)
Assigned to: Nobody/Anonymous (nobody)
Summary: "release" a reserved word in MySQL 5.x

Initial Comment:
And perhaps earlier versions too.

The table lxr_releases can not be created..

The MySQL docs claim that you can use reserved words as
identifiers if you quote them, but testing the CREATE
TABLE with "release" quoted also failed. 

----------------------------------------------------------------------

Comment By: S Melody (prplehaze2)
Date: 2006-05-31 15:37

Message:
Logged In: YES 
user_id=911986

I used this fix to create the tables, but indexing seems to
fail, most likely because release is a reserved word:

DBD::mysql::st execute failed: You have an error in your SQL
syntax; check the manual that corresponds to your MySQL
server version for the right syntax to use near 'release =
'head'' at line 1 at lib/LXR/Index/Mysql.pm line 209.
DBD::mysql::st execute failed: You have an error in your SQL
syntax; check the manual that corresponds to your MySQL
server version for the right syntax to use near 'release)
values ('387', 'head')' at line 1 at lib/LXR/Index/Mysql.pm
line 213.


----------------------------------------------------------------------

Comment By: Laurence Passmore (lmop)
Date: 2005-12-21 17:20

Message:
Logged In: YES 
user_id=1410237

This is a simple fix. initdb-mysql should be changed as follows (basically, 
backtick (`) the column name `release` to escape/quote it):

create table lxr_releases (
        fileid          int not null references lxr_files,
        `release`       char(255) binary not null,
        primary key     (fileid, `release`)
);

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=390117&aid=1209273&group_id=27350

[Lxr-dev] [ lxr-Feature Requests-942911 ] Subversion Support

[SourceForge.net <no...@so...>]

Feature Requests item #942911, was opened at 2004-04-27 10:23
Message generated for change (Comment added) made by vaish
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=390120&aid=942911&group_id=27350

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: General
Group: Next Release
Status: Open
Priority: 5
Submitted By: teewurstmann (teewurstmann)
Assigned to: Nobody/Anonymous (nobody)
Summary: Subversion Support

Initial Comment:
It would be nice to integrate support for Subversion
into a future release of LXR. Since LXR already
supports CVS support for Subversion shouldn't be too
hard to implement.

----------------------------------------------------------------------

Comment By: Vaish (vaish)
Date: 2006-04-24 15:19

Message:
Logged In: YES 
user_id=1508835

Is there any workaround for LXR to access subversion repository?

----------------------------------------------------------------------

Comment By: Roland Schwingel (rolandschwingel)
Date: 2004-10-20 08:58

Message:
Logged In: YES 
user_id=710704

Oh yes!!

This would be really cool to have... I am at present
searching for an application doing this...

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=390120&aid=942911&group_id=27350

[Lxr-dev] [ lxr-Bugs-1468114 ] Filenames with plusses + causing problems?

[SourceForge.net <no...@so...>]

Bugs item #1468114, was opened at 2006-04-10 17:48
Message generated for change (Comment added) made by worldjoe
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=390117&aid=1468114&group_id=27350

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Browsing
Group: v0.9.4
Status: Open
Resolution: None
Priority: 5
Submitted By: Joe Elwell (worldjoe)
Assigned to: Nobody/Anonymous (nobody)
Summary: Filenames with plusses + causing problems?

Initial Comment:
I have the Xerces Parser being indexed (among other things). These files, 
when indexed cause problems:
ApacheDOMC++Binding.html
ApacheDOMC++BindingL2.html
ApacheDOMC++BindingL3.html

Here are the error messages I get when trying to perform a search:

[Mon Apr 10 17:25:54 2006] fatal: Apache::ROOT::lxr::search, line 166: 
Nested quantifiers in regex; marked by <-- HERE in m/185 /ThrdPrty/
Xerces-C/doc/html/ApacheDOMC++ <-- HERE BindingL3.html 
"ApacheDOMC++BindingL3.html" 127418
/ at /usr/local/lxr/search line 166.

If I simply remove those 3 files, everything is fine.

Indexing occurs without problem (no errors reported that I've noticed), 
but perhaps this is a genxref problem anyways?

----------------------------------------------------------------------

>Comment By: Joe Elwell (worldjoe)
Date: 2006-04-18 16:14

Message:
Logged In: YES 
user_id=790622

I should probably point out that I'm running this on OS X Tiger PPC. Shouldn't 
matter, but maybe it does.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=390117&aid=1468114&group_id=27350

[Lxr-dev] [ lxr-Bugs-1468114 ] Filenames with plusses + causing problems?

[SourceForge.net <no...@so...>]

Bugs item #1468114, was opened at 2006-04-10 17:48
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=390117&aid=1468114&group_id=27350

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Browsing
Group: v0.9.4
Status: Open
Resolution: None
Priority: 5
Submitted By: Joe Elwell (worldjoe)
Assigned to: Nobody/Anonymous (nobody)
Summary: Filenames with plusses + causing problems?

Initial Comment:
I have the Xerces Parser being indexed (among other things). These files, 
when indexed cause problems:
ApacheDOMC++Binding.html
ApacheDOMC++BindingL2.html
ApacheDOMC++BindingL3.html

Here are the error messages I get when trying to perform a search:

[Mon Apr 10 17:25:54 2006] fatal: Apache::ROOT::lxr::search, line 166: 
Nested quantifiers in regex; marked by <-- HERE in m/185 /ThrdPrty/
Xerces-C/doc/html/ApacheDOMC++ <-- HERE BindingL3.html 
"ApacheDOMC++BindingL3.html" 127418
/ at /usr/local/lxr/search line 166.

If I simply remove those 3 files, everything is fine.

Indexing occurs without problem (no errors reported that I've noticed), 
but perhaps this is a genxref problem anyways?

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=390117&aid=1468114&group_id=27350

[Lxr-dev] [ lxr-Bugs-1465275 ] Two letter Directories can't be browsed

[SourceForge.net <no...@so...>]

Bugs item #1465275, was opened at 2006-04-05 20:51
Message generated for change (Comment added) made by mbox
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=390117&aid=1465275&group_id=27350

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Browsing
Group: v0.9.4
>Status: Closed
>Resolution: Fixed
Priority: 5
Submitted By: Joe Elwell (worldjoe)
Assigned to: Nobody/Anonymous (nobody)
Summary: Two letter Directories can't be browsed

Initial Comment:
I have a directories like:
/Src/Foo/AA
/Src/Foo/DT
/Src/Foo/LL

Whenever I click on these I'm brought back to the root directory.

Since this is an internal release of LXR I just made the following 
changes to fix the problem:

--- Common.pm   Fri Feb  3 12:39:05 2006
***************
*** 470,476 ****
  
        $HTTP->{'path_info'} = http_wash($ENV{'PATH_INFO'});
  
!       $HTTP->{'path_info'} = clean_path($HTTP->{'path_info'});
        $HTTP->{'this_url'} = 'http://' . $ENV{'SERVER_NAME'};
        $HTTP->{'this_url'} .= ':' . $ENV{'SERVER_PORT'}
          if $ENV{'SERVER_PORT'} != 80;
--- 470,476 ----
  
        $HTTP->{'path_info'} = http_wash($ENV{'PATH_INFO'});
  
! #     $HTTP->{'path_info'} = clean_path($HTTP->{'path_info'});
        $HTTP->{'this_url'} = 'http://' . $ENV{'SERVER_NAME'};
        $HTTP->{'this_url'} .= ':' . $ENV{'SERVER_PORT'}
          if $ENV{'SERVER_PORT'} != 80;
***************
*** 539,545 ****
  
        if(defined $path) {
                # First suppress anything after a dodgy character
!               $path =~ s!(^[\w_+-,.%^/]+).*!$1!;
                # Clean out /../
                while ($path =~ m!/../!) {
                        $path = s!/\.\./!/!g;
--- 539,545 ----
  
        if(defined $path) {
                # First suppress anything after a dodgy character
! #             $path =~ s!(^[\w_+-,.%^/]+).*!$1!;
                # Clean out /../
                while ($path =~ m!/../!) {
                        $path = s!/\.\./!/!g;

----------------------------------------------------------------------

>Comment By: Malcolm Box (mbox)
Date: 2006-04-09 23:05

Message:
Logged In: YES 
user_id=215386

Fixed in version 0.9.5

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=390117&aid=1465275&group_id=27350

[Lxr-dev] [ lxr-Bugs-1465275 ] Two letter Directories can't be browsed

[SourceForge.net <no...@so...>]

Bugs item #1465275, was opened at 2006-04-05 12:51
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=390117&aid=1465275&group_id=27350

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Browsing
Group: v0.9.4
Status: Open
Resolution: None
Priority: 5
Submitted By: Joe Elwell (worldjoe)
Assigned to: Nobody/Anonymous (nobody)
Summary: Two letter Directories can't be browsed

Initial Comment:
I have a directories like:
/Src/Foo/AA
/Src/Foo/DT
/Src/Foo/LL

Whenever I click on these I'm brought back to the root directory.

Since this is an internal release of LXR I just made the following 
changes to fix the problem:

--- Common.pm   Fri Feb  3 12:39:05 2006
***************
*** 470,476 ****
  
        $HTTP->{'path_info'} = http_wash($ENV{'PATH_INFO'});
  
!       $HTTP->{'path_info'} = clean_path($HTTP->{'path_info'});
        $HTTP->{'this_url'} = 'http://' . $ENV{'SERVER_NAME'};
        $HTTP->{'this_url'} .= ':' . $ENV{'SERVER_PORT'}
          if $ENV{'SERVER_PORT'} != 80;
--- 470,476 ----
  
        $HTTP->{'path_info'} = http_wash($ENV{'PATH_INFO'});
  
! #     $HTTP->{'path_info'} = clean_path($HTTP->{'path_info'});
        $HTTP->{'this_url'} = 'http://' . $ENV{'SERVER_NAME'};
        $HTTP->{'this_url'} .= ':' . $ENV{'SERVER_PORT'}
          if $ENV{'SERVER_PORT'} != 80;
***************
*** 539,545 ****
  
        if(defined $path) {
                # First suppress anything after a dodgy character
!               $path =~ s!(^[\w_+-,.%^/]+).*!$1!;
                # Clean out /../
                while ($path =~ m!/../!) {
                        $path = s!/\.\./!/!g;
--- 539,545 ----
  
        if(defined $path) {
                # First suppress anything after a dodgy character
! #             $path =~ s!(^[\w_+-,.%^/]+).*!$1!;
                # Clean out /../
                while ($path =~ m!/../!) {
                        $path = s!/\.\./!/!g;

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=390117&aid=1465275&group_id=27350

[Lxr-dev] [ lxr-Bugs-1461086 ] \"Cant use hyphen in file names\" problem not fixed well

[SourceForge.net <no...@so...>]

Bugs item #1461086, was opened at 2006-03-30 03:40
Message generated for change (Settings changed) made by mbox
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=390117&aid=1461086&group_id=27350

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Browsing
Group: v0.9.4
>Status: Closed
Resolution: None
Priority: 5
Submitted By: steel_mental (steel_mental)
Assigned to: Nobody/Anonymous (nobody)
>Summary: \"Cant use hyphen in file names\" problem not fixed well

Initial Comment:
"Cant use hyphen in file names problem" fixed not 
well.

the sub "clean_path" of file Common.pm(near line 537):

....
if(defined $path) {
	# First suppress anything after a dodgy 
character
	$path =~ s!(^[\w_+-,.%^/]+).*!$1!;
	# Clean out /../
	while ($path =~ m!/../!) {
	$path = s!/\.\./!/!g;
}
....

this line:
$path =~ s!(^[\w_+-,.%^/]+).*!$1!;

should be:
$path =~ s!(^[\w_+\-,.%^/]+).*!$1!;

or lxr still can not 
use hyphen in file names.

my box is freebsd 6.0 with perl 5.8.8.

sorry for my poor english and enjoy.

by Michael Lee.

----------------------------------------------------------------------

Comment By: Malcolm Box (mbox)
Date: 2006-03-31 23:25

Message:
Logged In: YES 
user_id=215386

Thanks for reporting this.  This has now been fixed in CVS,
and will be in the 0.9.5 release (which should happen when
the SF CVS servers are back up!).

Cheers,

Malcolm

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=390117&aid=1461086&group_id=27350

[Lxr-dev] [ lxr-Bugs-1446014 ] Cant use hyphen in file names

[SourceForge.net <no...@so...>]

Bugs item #1446014, was opened at 2006-03-08 23:39
Message generated for change (Settings changed) made by mbox
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=390117&aid=1446014&group_id=27350

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Browsing
Group: v0.9.4
>Status: Closed
Resolution: None
Priority: 5
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: Cant use hyphen in file names

Initial Comment:
Indexing files or directories named first-second cannot
be viewed. Selecting the first-second link results in
"The file first cannot be found."

The cause is clean_path not allowing hyphen. It's in
the list, just not first, so it denotes a range between
the adjacent characters, not itself. Moving the hyphen
to the beginning of the list solves the problem.

--- Common.pm   2006-03-08 15:14:26.000000000 -0800
+++ Common.pm.old       2006-02-14 08:47:29.000000000 -0800
@@ -539,8 +539,7 @@

        if(defined $path) {
                # First suppress anything after a dodgy
character
-               $path =~ s!(^[-\w_+,.%^/]+).*!$1!;
+               $path =~ s!(^[\w_+-,.%^/]+).*!$1!;
                # Clean out /../
                while ($path =~ m!/../!) {
                        $path = s!/\.\./!/!g;

As '+' and ',' are adjacent in the ascii character set,
"+-," is a valid but not very useful range.
Enjoy
Lee
lee...@f5...

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=390117&aid=1446014&group_id=27350

[Lxr-dev] Re: [PATCH] Preliminary GIT support

[Malcolm B. <mal...@gm...>]

Jan-Benedict Glaw wrote:
> On Fri, 2006-03-31 23:17:00 +0100, Malcolm Box <mal...@gm...> wrote:
> 
>>$output = `command`;
>>if($? >> 8) {die "Problem with command";}
>>
>>if you want to get rid of the \n on the string, then do:
>>
>>chomp $output;
> 
> 
> Is there a way so supply the arguments one-by-one? I'd like to get
> things like whitespace in a path correct, thus I guess something like
> exec() vs. system() may be needed?

You can use system() with a list of parameters, which will then preserve 
whitespace in pathnames (evil though this is). e.g. 
system("git-command", "param1", "path with spaces in it")

This doesn't capture the output though, so you might have to fork and 
read the output.  There's a good example of how to do this in the 
perlsec man page - look for "backtick".  Doing things that way would be 
a good idea if the command is ever run in response to untrusted user 
input - i.e. if it can be triggered by the browser interface, since 
there would then be a potential injection attack.

The other thing you could try is quoting the pathnames in the backticks 
- from some simple experiments this would appear to work.

> 
> 
>>> * Given that a program outputs numerous lines of which the first
>>>   lines have a strict syntax (and the following are free-form text),
>>>   what's the easiest way to get one of the lines with known format
>>$output = `git-cat-file commit...`;
>>if ($? >> 8) { die "Something interesting happened";};
>>
>>($author_line) = ($output=~m/^(author .*)$/m;
>>($author_email) = ($author_line=~/<(.*)>/;
>>
>>or something like that should do the trick.  The basic flow is to read 
>>everything into the $output variable, then use the regexp operators of 
>>perl to chop out what you need.
> 
> 
> Is the unmatching number of opening vs. closing braces intended
> (right-hand)?

No, sorry!  Comes of posting code that I've not run.  It should be:

($author_line) = ($output=~m/^(author .*)$/m);

>>The first regexp uses the /m modifier so that it will deal with a 
>>multi-line string in $output.  The second doesn't need this since we've 
> 
> 
> Does this take care of throwing away all but the first author line?

The $author_line will contain only the first line starting with author. 
  So it does throw away all the rest.

>>just chopped out one line.  Both regexps use the fact that in list 
>>context a match (m//) operation returns a list of all matched bracketed 
>>expressions.

Cheers,

Malcolm

[Lxr-dev] [ lxr-Bugs-1461086 ] "Cant use hyphen in file names" problem not fixed well

[SourceForge.net <no...@so...>]

Bugs item #1461086, was opened at 2006-03-30 03:40
Message generated for change (Comment added) made by mbox
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=390117&aid=1461086&group_id=27350

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Browsing
Group: v0.9.4
Status: Open
Resolution: None
Priority: 5
Submitted By: steel_mental (steel_mental)
Assigned to: Nobody/Anonymous (nobody)
Summary: "Cant use hyphen in file names" problem not fixed well

Initial Comment:
"Cant use hyphen in file names problem" fixed not 
well.

the sub "clean_path" of file Common.pm(near line 537):

....
if(defined $path) {
	# First suppress anything after a dodgy 
character
	$path =~ s!(^[\w_+-,.%^/]+).*!$1!;
	# Clean out /../
	while ($path =~ m!/../!) {
	$path = s!/\.\./!/!g;
}
....

this line:
$path =~ s!(^[\w_+-,.%^/]+).*!$1!;

should be:
$path =~ s!(^[\w_+\-,.%^/]+).*!$1!;

or lxr still can not 
use hyphen in file names.

my box is freebsd 6.0 with perl 5.8.8.

sorry for my poor english and enjoy.

by Michael Lee.

----------------------------------------------------------------------

>Comment By: Malcolm Box (mbox)
Date: 2006-03-31 23:25

Message:
Logged In: YES 
user_id=215386

Thanks for reporting this.  This has now been fixed in CVS,
and will be in the 0.9.5 release (which should happen when
the SF CVS servers are back up!).

Cheers,

Malcolm

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=390117&aid=1461086&group_id=27350