[request-tracker-maintainers] Bug#534346: Bug#534346: Upgrading from 3.8.2 to 3.8.3 with rt-setup-database

[Dominic Hargreaves]

On Wed, May 05, 2010 at 10:36:51AM +0200, Knut Arne Bjørndal wrote:

> I also experienced this error, and tracked it down. For some reason if
> there's a Schema.Pg in /etc/request-tracker3.8 the upgrade script will
> try to apply it.
> 
> I'm not sure at what point the package was updated to move things like
> schema.Pg from /etc to /usr, but my install has been upgraded a few
> times and had a schema.Pg there.
> 
> Moving acl.*, initialdata, schema.*, upgrade and RT_Config.pm away from
> /etc solved the problem for me.
> 
> Would it make sense to have a package upgrade script either
> automatically clean out those files (if it detected they were
> unchanged), or at least warn the user?

Thanks for taking the time to write about this.

It does seem plausible that the problems described in this bug were 
caused by left behind schema files; however, the intention was that
they be removed. The postinst now removes unmodified config from /etc
(as of 3.8.2-1).

It would be interesting to know exactly which versions you had installed,
and also whether the old schema files that were left behind match the
MD5sums in /usr/share/request-tracker3.8/debian/old_etc.md5sum (since
that would indicate a bug in the postinst removal script fragment).

I don't think we anticipated that left-behind schema files would be a
problem, though; we were just tidying up for neatness.

I'm not sure whether it's worth fixing this in the package now, since
the problem should only exist for people who installed from experimental
over a year ago.

-- 
Dominic Hargreaves | http://www.larted.org.uk/~dom/
PGP key 5178E2A5 from the.earth.li (keyserver,web,email)