[Lxr-dev] Re: [ lxr-Bugs-455480 ] Diff. btwn. --allversions and --version=

[Malcolm B. <ma...@br...>]

In a bug report, Jan-Benedict wrote

> There are these famous "LXR/xxx.pm not found" errors
> around.
> 
> They seem to depend on how the source tree (my one is
> based
> on CVS and PostgreSQL) is indexed.
>
> Indexing it with --allversions is quite fine: I can
> browse the code
> without any problems. But indexing specific versions
> via
> --version=xxx (with xxx being a valid CVS tag) produces
> those
> "not found" errors afterwards. So it seems that genxref
> either
> fails to generate correct indexes for some given cvs
> tag, or
> "source" tries to get wrong releases from
> cvs/database...

Are you still experiencing this problem?  I can't see any reason why
the state of the database would result in "not found" errors - it's
perfectly possible to run lxr against an empty database, so I'm confused
by this bug.

Here's a few questions that may help nail it down.  Firstly, what are
the modules that are reported as "not found"?

If you index with --allversions, and then specify a version that doesn't
exist, do you get the same "not found" messages as with --version?

Cheers,

Malcolm