Your message dated Sat, 7 Aug 2010 14:02:34 +0200
with message-id <[email protected]>
and subject line Package got removed
has caused the Debian Bug report #407921,
regarding lxr-cvs: genxref produces MySQL errors when used with --reindexall
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
407921: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=407921
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: lxr-cvs
Version: 0.9.4.0.20061001-2
Severity: normal
The option --reindexall to genxref produces MySQL errors when a MySQL
5.0.24a-Debian_9-log database server is used as a backend.
$ genxref --url=http://localhost/lxr --allversions --reindexall
produces:
BD::mysql::st execute failed: Unknown table 'lxr_indexes' in MULTI
DELETE at /usr/share/perl5/LXR/Index/Mysql.pm line 334.
DBD::mysql::st execute failed: Unknown table 'lxr_useage' in MULTI
DELETE at /usr/share/perl5/LXR/Index/Mysql.pm line 335.
DBD::mysql::st execute failed: Unknown table 'lxr_status' in MULTI
DELETE at /usr/share/perl5/LXR/Index/Mysql.pm line 336.
DBD::mysql::st execute failed: Unknown table 'lxr_files' in MULTI DELETE
at /usr/share/perl5/LXR/Index/Mysql.pm line 338.
The cause is incorrect syntax in the library file
/usr/share/perl5/LXR/Index/Mysql.pm. The statements for
"delete_indexes", "delete_useage", "delete_status" and "delete_files"
uses syntax which isn't working and also appears to be incorrect syntax
according to the MySQL manual.
The statement used is something like
"delete from ${prefix}indexes using ${prefix}indexes i,
${prefix}releases r where ..."
If changed to the following it works:
"delete from i using ${prefix}indexes i, ${prefix}releases r where ..."
The error has been in upstream for years and according to the bug
tracker of MySQL that was incorrect synatx already for MySQL 4.0.
Apparently nobody uses --reindexall or doesn't care about the errors. Or
is this not reproducible by others than me? The syntax used also
produces an identical error when used from the MySQL client shell.
Regards,
Florian Zschocke
-- System Information:
Debian Release: testing/unstable
APT prefers dapper-security
APT policy: (902, 'dapper-security'), (901, 'dapper-updates'), (900,
'dapper'), (650, 'edgy-updates'), (650, 'edgy-security'), (650, 'edgy'), (500,
'testing')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.15-27-686
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Versions of packages lxr-cvs depends on:
ii apache2 2.0.55-4ubuntu2.1 next generation, scalable, extenda
ii apache2-mpm-prefork 2.0.55-4ubuntu2.1 traditional model for Apache2
ii exuberant-ctags 1:5.5.4-1 build tag file indexes of source c
ii libapache-mod-perl 1.29.0.4-2ubuntu0.1 integration of perl with the Apach
ii perl 5.8.7-10ubuntu1 Larry Wall's Practical Extraction
lxr-cvs recommends no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 0.9.5+cvs20071020-1.1+rm
Hi!
As the package got removed from the archive, I hereby close this bug
report. Please see http://bugs.debian.org/591059 for details on the
removal.
Best Regards,
Alexander
--- End Message ---
