[request-tracker-maintainers] Bug#603247: Bug#603247: request-tracker3.8: loading 3.6 database in 3.8 fails with "namespace error : Failed to parse QName 'Pref-RT:'"

[James Andrewartha]

On 13/11/10 05:07, Dominic Hargreaves wrote:

> I've no idea if the rt-dump-database from 3.6 is intended to work with
> 3.8. The name of that utility, as well as the manpage (provided by
> Debian, so we should probably improve it) are misleading as to the
> purpose of the utility.
> 
> For dumping and loading a database you almost certainly just need to
> use mysql's own dump and load commands, paying close attention to
> /usr/share/doc/request-tracker3.8/UPGRADING.mysql as Stefan (below)
> suggests. Note that the referenced upgrade script is at
> /usr/share/request-tracker3.8/etc/upgrade/upgrade-mysql-schema.pl
> on Debian systems.
> 
> This bug report can probably serve as a valid documentation bug,
> noting that the manpage can be improved; and also that the
> UPGRADING.mysql file could be tweaked slightly for MySQL upgrades.

The docs in /usr/share/doc/request-tracker3.8 are a confusing mix of
Debian and upstream information. Given that upgrading from 3.6 in lenny
to 3.8 in squeeze is the common case, I was expecting clear instructions
saying something like "request-tracker3.8 is parallel-installable with
request-tracker3.6, to non-destructively upgrade your database, perform
these simple steps:"

There is something like this in README.Debian, but I didn't see it as
it's not on the first page, which just refers to NOTES.Debian, so I
assumed it'd be in there. That is where I got the usage of
rt-dump-database, as I hadn't installed rt3.8-db-mysql. I assumed
because it did dumps and reloads that upgrades were handled by it
outside the database, rather than running scripts on the database.

-- 
James Andrewartha
Network & Projects Engineer
Christ Church Grammar School
Claremont, Western Australia
Ph. (08) 9442 1757
Mob. 0424 160 877