[DRE-maint] Bug#684067: redmine postgresql backend fails in redmine clean

PICCORO McKAY Lenz mckaygerhard at gmail.com
Wed Aug 8 17:58:54 UTC 2012


now i will test postgresql backen (i not tested due some space need)
for that i run "dpkg-reconfigure -plow redmine" and respont all quiestion
using postgres wihtout none security and xxx user with xxx password, testin
connection results ok event by localhost or socket, so its clear that
problem are betweet redmine or debian's dbconfig script due fails
populating db but not previously conections

I could, I managed to reproduce the error with sqlite backend, the only
difference between before and after, its that ruby 1.9.1 devel package were
instaled. Let me explain:

1) I installed redmine all depends in clean env, but using sqlite backend
(that installed before perectly) and event fails, even I did not realize
that bundler had installed so then ruby 1.9.1 also, (bundler now depends
of), but i had installed with devel ruby1.9.1-dev also.

2) so then i revise all changelog and bug reports and notice some issues
about gems and rack, so additional depends installed in a repackaging of
rails 2.3.14 result that must be : ruby-rack> = 1.4 and rubygems> = 1.8
explicitly, as it still had the rubygems 1.6 from unstable, this fixes the
first problem reported, but i put previosly in redmine file config/boot.rb
 a "require 'thread'" line after RAILS_ROOT related, this are mandatory i
tested without and in some cases faild redmine to install.

3) after notice had installed ruby bundler so then ruby 1.9.1, then
uninstall all ruby 1.9.1 (so i must uninstall bundler), removing
ruby1.9.1-dev solved the problem and install redmine perfect with sqlite or
mysql backend if all of those topics are exactly as i said.  There's
something whit db:migrating that relies on ruby 1.9 ...

4) then removes and purge all redmine, so repeat install ruby1.9.1-dev and
redmine and installs fine
5) then removes and reinstall but first with bundler installed failds.
6) some try after, i cant reproduce this case...

So then if in upgrade redmine from squeeze to wheeze ruby 1.9.1 are
installed, upgrades will fail!!!! this bug its very famous in debian over
net, seee google search related ...

with postgres: when i reconfigure, i setup postgres to ask in every
conection the password (and dbconfig has stored also) result that:

Creating config file /etc/redmine/default/database.yml.new with new version
Password for user postgres:
creating postgres user redmine:  Password for user postgres:
already exists.
resetting password:  Password for user postgres:
success.
Password for user postgres:
creating database redmine_default: Password for user postgres:
already exists.
dbconfig-common: flushing administrative password
Populating database for redmine instance "default".
This may take a while.
NOTE: Gem.source_index is deprecated, use Specification. It will be removed
on or after 2011-11-01.
Gem.source_index called from
/usr/share/redmine/config/../vendor/rails/railties/lib/rails/gem_dependency.rb:21.
Please install RDoc 2.4.2+ to generate documentation.
rake aborted!
server closed the connection unexpectedly
This probably means the server terminated abnormally
before or while processing the request.

Tasks: TOP => db:migrate => environment
(See full trace by running task with --trace)
Error when running rake db:migrate, check database configuration.
exit: 295: Illegal number: -1



-- 
Lenz McKAY Gerardo (PICCORO)
http://qglochekone.blogspot.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-ruby-extras-maintainers/attachments/20120808/3fa98fb0/attachment-0001.html>


More information about the Pkg-ruby-extras-maintainers mailing list