[Lxr-dev] [ lxr-Bugs-1047761 ] duplicate entries in lxr_useage
Brought to you by:
ajlittoz
From: SourceForge.net <no...@so...> - 2009-03-26 16:20:56
|
Bugs item #1047761, was opened at 2004-10-15 14:01 Message generated for change (Settings changed) made by mbox You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=390117&aid=1047761&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: genxref Group: None >Status: Closed >Resolution: Works For Me Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: duplicate entries in lxr_useage Initial Comment: For some reason running genxref (lxr-0.9.3) duplicate entries are being inserted into lxr_useage. The cross-referencing is all correct, but duplicated! ---------------------------------------------------------------------- Comment By: Erik Huelsmann (dionisos) Date: 2005-10-06 06:40 Message: Logged In: YES user_id=664913 Or rather see http://www.endrun.org/xr/svn/ident?i=svn_io_file_rename I'll be patching my lxr and resetting the hix.nu db. ---------------------------------------------------------------------- Comment By: Erik Huelsmann (dionisos) Date: 2005-10-05 22:34 Message: Logged In: YES user_id=664913 Cross referencing is not exactly duplicated, although it may look like it is for most items. This problem occurs when you use the Plain.pm module for xref-ing with incremental changes. The rev of the file is determined by its on-disc date, which is different for every time it changes. This leads to seemingly duplicate entries in the useage table all referring to the same file, some to the wrong lines. For an example, see: http://hix.nu/subversion/lxr/ident?v=wc-replacements&i=svn_wc_add_repos_file ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2004-10-15 14:05 Message: Logged In: NO Interestingly, this does not occur in the older version 0.9.2. Perhaps a bug has been introduced between versions? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=390117&aid=1047761&group_id=27350 |