Am 16.07.2014 11:00, schrieb Joop: > On 16-7-2014 4:23, Alex Peters wrote: >> >> Please report these errors and warnings, because anything that ships >> directly with RT 4.2 should definitely be fully supported by RT 4.2. >> > Don't know if I'm seeing the same errors but here are mine which > suprised me quite a bit when running rt-dump-metadata > [22390] [Wed Jul 16 08:52:21 2014] [warning]: DBD::Pg::st execute > failed: ERROR: column "privatekey" does not exist > LINE 1: SELECT privatekey FROM Users WHERE id = $1 > ^ at /usr/share/perl5/DBIx/SearchBuilder/Handle.pm line > 509. (/usr/share/perl5/DBIx/SearchBuilder/Handle.pm:509) > [22390] [Wed Jul 16 08:52:21 2014] [warning]: RT::Handle=HASH(0x2d51f68) > couldn't execute the query 'SELECT privatekey FROM Users WHERE id = ?' > at /usr/share/perl5/DBIx/SearchBuilder/Handle.pm line 522. > DBIx::SearchBuilder::Handle::SimpleQuery() called at > /usr/share/perl5/DBIx/SearchBuilder/Record.pm line 714 > DBIx::SearchBuilder::Record::__Value() called at > /opt/rt4/sbin/../lib/RT/Record.pm line 644 > RT::Record::__Value() called at ./sbin/rt-dump-metadata line 174 > (/usr/local/share/perl/5.10.1/Carp.pm:103) > > I haven't the faintest idea where 'privatekey' is coming from. It > certainly isn't in my users table (pgpkey is). I'm running rt-4.0.20 and > rt-4.2.5 and both have the same problem only when invoked with the '-a' > flag. > Running it without any parameters seems to produce valid output but also > those warnings. > > Joop >
There is already a bug report open for this [1] and a branch with only one commit [2] which needs review. Chris [1] http://issues.bestpractical.com/Ticket/Display.html?id=22465 [2] https://github.com/bestpractical/rt/commit/51ebb3affde6195fa3ce00e7a1343ba7e7971385 -- RT Training - Boston, September 9-10 http://bestpractical.com/training