Bug#695774: redmine: fails to upgrade, says something about a pgsql_adapter
I am going to upload a fix to the clearly identified problem of having the same user with overwritten auto-generated password by dbconfig. (see previous pending tag). There was another issue described here, that i believe was that the adapter line in (at least one of) the /etc/redmine/instance/database.yml was not postgresql. This could happen if the config file has been modified manually by the user and not updated upon redmine 1.0 - 1.4 migration. Please re-open this bug, or open another one, if you think there is something more i can do about it. Jérémy. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#695774: redmine: fails to upgrade, says something about a pgsql_adapter
On Wed, 16 Jan 2013, Jérémy Lal wrote: But i can't see how you can end without any database type set... The more funny thing is that I don’t get asked to select one, or asked whether I want to reinstall the DB, at all. Maybe I should purge dbconfig* too… and remove all entries related to that from debconf… bye, //mirabilos -- tarent solutions GmbH Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/ Tel: +49 228 54881-393 • Fax: +49 228 54881-314 HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941 Geschäftsführer: Boris Esser, Sebastian Mancke -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#695774: redmine: fails to upgrade, says something about a pgsql_adapter
On 17/01/2013 09:33, Thorsten Glaser wrote: On Wed, 16 Jan 2013, Jérémy Lal wrote: But i can't see how you can end without any database type set... The more funny thing is that I don’t get asked to select one, or asked whether I want to reinstall the DB, at all. Maybe I should purge dbconfig* too… and remove all entries related to that from debconf… Maybe the config files of dbconfig are in the way (/etc/dbconfig...) Yes purging everything will certainly solve the issue. I'm curious as how this happened first. Jérémy. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#695774: redmine: fails to upgrade, says something about a pgsql_adapter
Dixi quod… Maybe I should purge dbconfig* too… and remove all entries related to that from debconf… Oh. Now I can’t even purge redmine any more: […] Deconfigure database for redmine/instances/default with dbconfig-common? ⇒ Yes dpkg: error processing redmine (--purge): subprocess installed pre-removal script returned error exit status 10 dpkg-query: no packages found matching redmine- ++ Configuring redmine ++ | | | redmine- package required | […] same thing Skipping default because of missing dependency. dpkg: redmine-pgsql: dependency problems, but removing anyway as you requested: redmine depends on redmine-sqlite | redmine-mysql | redmine-pgsql; however: Package redmine-sqlite is not installed. Package redmine-mysql is not installed. Package redmine-pgsql is to be removed. Removing redmine-pgsql ... dpkg: dbconfig-common: dependency problems, but removing anyway as you requested: redmine depends on dbconfig-common; however: Package dbconfig-common is to be removed. Removing dbconfig-common ... Purging configuration files for dbconfig-common ... dpkg: warning: while removing dbconfig-common, directory '/etc/dbconfig-common' not empty so not removed Processing triggers for man-db ... Errors were encountered while processing: redmine E: Sub-process /usr/bin/dpkg returned an error code (1) I got around it by changing set -e to set +e in /var/lib/dpkg/info/redmine.prerm (absolute hack, but I had to purge it), with the expected errors following: /var/lib/dpkg/info/redmine.prerm[39]: .: /usr/share/dbconfig-common/dpkg/prerm: No such file or directory Purging configuration files for redmine ... rmdir: failed to remove /var/lib/redmine/*/files': No such file or directory rmdir: failed to remove /var/lib/redmine/*': No such file or directory Now trying to reinstall (there was no dbconfig* or redmine* in the debconf cache any more, I checked)… root@redmine:~ # apt-get install redmine redmine-pgsql Reading package lists... Done Building dependency tree Reading state information... Done The following extra packages will be installed: dbconfig-common Suggested packages: ruby-rmagick ruby-openid bzr cvs darcs mercurial The following NEW packages will be installed: dbconfig-common redmine redmine-pgsql 0 upgraded, 3 newly installed, 0 to remove and 0 not upgraded. Need to get 540 kB/5577 kB of archives. After this operation, 13.4 MB of additional disk space will be used. Do you want to continue [Y/n]? Get:1 http://mirror.lan.tarent.de/debian/ wheezy/main dbconfig-common all 1.8.47+nmu1 [487 kB] Get:2 http://mirror.lan.tarent.de/debian/ wheezy/main redmine-pgsql all 1.4.4+dfsg1-1.1 [52.9 kB] Fetched 540 kB in 0s (6646 kB/s) Preconfiguring packages ... debconf: warning: possible database corruption. Will attempt to repair by adding back missing question dbconfig-common/password-confirm. debconf: warning: possible database corruption. Will attempt to repair by adding back missing question redmine/instances/default/password-confirm. debconf: warning: possible database corruption. Will attempt to repair by adding back missing question dbconfig-common/app-password-confirm. debconf: warning: possible database corruption. Will attempt to repair by adding back missing question redmine/instances/default/app-password-confirm. debconf: warning: possible database corruption. Will attempt to repair by adding back missing question redmine/instances/default/mysql/app-pass. debconf: warning: possible database corruption. Will attempt to repair by adding back missing question dbconfig-common/mysql/app-pass. debconf: warning: possible database corruption. Will attempt to repair by adding back missing question dbconfig-common/mysql/admin-pass. debconf: warning: possible database corruption. Will attempt to repair by adding back missing question redmine/instances/default/mysql/admin-pass. debconf: warning: possible database corruption. Will attempt to repair by adding back missing question redmine/instances/default/pgsql/app-pass. debconf: warning: possible database corruption. Will attempt to repair by adding back missing question dbconfig-common/pgsql/app-pass. debconf: warning: possible database corruption. Will attempt to repair by adding back missing question dbconfig-common/pgsql/admin-pass. debconf: warning: possible database corruption. Will attempt to repair by adding back missing question redmine/instances/default/pgsql/admin-pass. Selecting previously unselected package dbconfig-common. (Reading database ... 45632 files and directories currently installed.) Unpacking dbconfig-common
Bug#695774: redmine: fails to upgrade, says something about a pgsql_adapter
On 17/01/2013 10:02, Thorsten Glaser wrote: rake aborted! Please install the pgsql adapter: `gem install activerecord-pgsql-adapter` (cannot load such file -- active_record/connection_adapters/pgsql_adapter) .../... So, even after a full purge of redmine, redmine-pgsql and dbconfig-common, the error persists. (WTF‽) Damn it. There's a problem with ruby1.9 and the fact is doesn't find active_record/connection_adapters/pgsql_adapter This is new. You've just found 4 bugs. Great news ! Jérémy. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#695774: redmine: fails to upgrade, says something about a pgsql_adapter
On 17/01/2013 10:02, Thorsten Glaser wrote: rake aborted! Please install the pgsql adapter: `gem install activerecord-pgsql-adapter` (cannot load such file -- active_record/connection_adapters/pgsql_adapter) .../... So, even after a full purge of redmine, redmine-pgsql and dbconfig-common, the error persists. (WTF‽) Damn it. There's a problem with ruby1.9 and the fact is doesn't find active_record/connection_adapters/pgsql_adapter This is new. You've just found 4 bugs. Great news ! Oh i got confused, the problem with active_record/connection_adapters/pgsql_adapter is the original problem of this bug report. Jérémy. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#695774: redmine: fails to upgrade, says something about a pgsql_adapter
On 17/01/2013 10:02, Thorsten Glaser wrote: Please install the pgsql adapter: `gem install activerecord-pgsql-adapter` (cannot load such file -- active_record/connection_adapters/pgsql_adapter) about that original problem : could you check the value of adapter in your /etc/redmine/default/database.yml ? It should be postgresql Also the default ruby version shown by update-alternatives --display ruby Jérémy. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#695774: redmine: fails to upgrade, says something about a pgsql_adapter
On Fri, 11 Jan 2013, Jérémy Lal wrote: * dpkg-reconfigure -plow redmine and ask for reinstallation of the database. root@redmine:~ # dpkg-reconfigure -plow redmine /usr/sbin/dpkg-reconfigure: redmine is broken or not fully installed Setting the status to installed doesn’t help either, so I purge it and then install it anew but then I get: ┌┤ Configuring redmine ├┐ │ │ │ redmine- package required │ │ │ │ Redmine instance default is configured to use database type , but the corresponding redmine- package │ │ is not installed. │ │ │ │ Configuration of instance default is aborted. │ │ │ │ To finish that configuration, please install the redmine- package, and reconfigure redmine using: │ │ │ │ dpkg-reconfigure -plow redmine │ │ │ │Ok │ │ │ └───┘ I think Andreas Beckmann would say this is an RC bug now, because the purge did not remove all configuration… anyway, I *still* cannot go on from here. I do have a DB dump, but that was it… bye, //mirabilos -- tarent solutions GmbH Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/ Tel: +49 228 54881-393 • Fax: +49 228 54881-314 HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941 Geschäftsführer: Boris Esser, Sebastian Mancke -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#695774: redmine: fails to upgrade, says something about a pgsql_adapter
On 16/01/2013 13:06, Thorsten Glaser wrote: On Fri, 11 Jan 2013, Jérémy Lal wrote: * dpkg-reconfigure -plow redmine and ask for reinstallation of the database. root@redmine:~ # dpkg-reconfigure -plow redmine /usr/sbin/dpkg-reconfigure: redmine is broken or not fully installed Setting the status to installed doesn’t help either, so I purge it and then install it anew but then I get: ┌┤ Configuring redmine ├┐ │ │ │ redmine- package required │ │ │ │ Redmine instance default is configured to use database type , but the corresponding redmine- package │ │ is not installed. │ │ │ │ Configuration of instance default is aborted. │ │ │ │ To finish that configuration, please install the redmine- package, and reconfigure redmine using: │ │ │ │ dpkg-reconfigure -plow redmine │ │ │ │Ok │ │ │ └───┘ I think Andreas Beckmann would say this is an RC bug now, because the purge did not remove all configuration… anyway, I *still* cannot go on from here. I do have a DB dump, but that was it… Did you change manually /etc/redmine/default/database.yml, and could you give the output of `debconf-show redmine` ? Jérémy. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#695774: redmine: fails to upgrade, says something about a pgsql_adapter
On Wed, 16 Jan 2013, Jérémy Lal wrote:
Did you change manually /etc/redmine/default/database.yml,
No.
and could you give the output of `debconf-show redmine` ?
root@redmine:~ # debconf-show redmine
* redmine/instances/default/default-language: en
redmine/notify-migration:
redmine/old-instances:
* redmine/current-instances: default
redmine/default-language: ${defaultLocale}
redmine/instances/default/dbconfig-upgrade: true
redmine/instances/default/database-type:
redmine/instances/default/dbconfig-remove: true
* redmine/missing-redmine-package:
redmine/instances/default/dbconfig-install: true
redmine/instances/default/dbconfig-reinstall: false
bye,
//mirabilos
--
tarent solutions GmbH
Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/
Tel: +49 228 54881-393 • Fax: +49 228 54881-314
HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941
Geschäftsführer: Boris Esser, Sebastian Mancke
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#695774: redmine: fails to upgrade, says something about a pgsql_adapter
There are problems i can reproduce easily when doing : * purge instances databases * reconfigure, set instance default, do not install db * reconfigure, keep instance default, install db - a succession of warnings from dbconfig, eventually installs db. or doing * reconfigure database using a different db type. It just seems to make it forget about the db installed under the previous type. dbconfig-common isn't fool proof, and my redmine postinst script make it worse. But i can't see how you can end without any database type set... Jérémy. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#695774: redmine: fails to upgrade, says something about a pgsql_adapter
On Sun, 16 Dec 2012, Jérémy Lal wrote: I am working on a fix. Any news? In the meantime, I tried to recover myself: look into /etc/redmine/default/database.yml what was used as password, connect as postgres to the DB and ALTER ROLE and set the redmine user’s password to that. Doesn’t work ☹ bye, //mirabilos -- tarent solutions GmbH Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/ Tel: +49 228 54881-393 • Fax: +49 228 54881-314 HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941 Geschäftsführer: Boris Esser, Sebastian Mancke -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#695774: redmine: fails to upgrade, says something about a pgsql_adapter
On 11/01/2013 17:12, Thorsten Glaser wrote: On Sun, 16 Dec 2012, Jérémy Lal wrote: I am working on a fix. Any news? I'll try to make config script use the first generated password if a second database user name is the same as a first one. But i'm not sure i can even read the first password value. In the meantime, I tried to recover myself: look into /etc/redmine/default/database.yml what was used as password, connect as postgres to the DB and ALTER ROLE and set the redmine user’s password to that. Doesn’t work ☹ well it should, so maybe only the md5 sum of the password is recorded or something. The problem if you do that is that dbconfig still has another value for the password, so next time database.yml is updated after reconfigure/update it will be populated by a wrong value (but you will be prompted since it is a config file). You'd better try : * dump db * dpkg-reconfigure -plow redmine and ask for reinstallation of the database. Jérémy. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#695774: redmine: fails to upgrade, says something about a pgsql_adapter
Hi again, this is even funnier. On the machine, I have: # fgrep Value: /var/cache/debconf/passwords.dat Value: Value: Value: Value: Value: So apparently, it lost *all* password information. # ls -l /etc/redmine/ total 4 drwxr-xr-x 2 www-data www-data 4096 Dec 12 17:36 default In /etc/redmine/default/database.yml there _is_ set a password, but apparently not the correct one. And finally: when I wrote the bugreport, *after* the upgrade that failed to configure, Redmine was still running, until I restarted Apache, now it 500s, which is pretty much expected, so the database.yml *was* changed and it had an older, nonzero, value that actually worked. Approximate order in which I did things: apt-get install redmine redmine-pgsql [ config fails due to missing postgresql server ] apt-get install postgresql [ redmine asks for half(!) the config values again ] [ redmine works ] apt-get --purge dist-upgrade [ redmine asks for nothing but fails to upgrade ] bye, //mirabilos -- tarent solutions GmbH Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/ Tel: +49 228 54881-393 • Fax: +49 228 54881-314 HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941 Geschäftsführer: Boris Esser, Sebastian Mancke -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#695774: redmine: fails to upgrade, says something about a pgsql_adapter
On Sun, 16 Dec 2012, Jérémy Lal wrote: The bug comes from configuring two instances with the same db user. dbconfig-common regenerates a random password when configuring the second instance, wiping the password set for the first instance that has already been recorded in database.yml. Okay, in this case, I know where it comes from: I first tried installing redmine and redmine-pgsql, but the latter does not depend on a database server, and I had not set up one beforehand myself, leading to *first* dbconfig being run, *then* the package installation fail. When I saw that I need to manually install postgresql, I did that, and then the redmine packages were configured, running dbconfig a second time. Thanks for your analysis! bye, //mirabilos -- tarent solutions GmbH Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/ Tel: +49 228 54881-393 • Fax: +49 228 54881-314 HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941 Geschäftsführer: Boris Esser, Sebastian Mancke -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#695774: redmine: fails to upgrade, says something about a pgsql_adapter
On 17/12/2012 11:02, Thorsten Glaser wrote: On Sun, 16 Dec 2012, Jérémy Lal wrote: The bug comes from configuring two instances with the same db user. dbconfig-common regenerates a random password when configuring the second instance, wiping the password set for the first instance that has already been recorded in database.yml. Okay, in this case, I know where it comes from: I first tried installing redmine and redmine-pgsql, but the latter does not depend on a database server, and I had not set up one beforehand myself, leading to *first* dbconfig being run, *then* the package installation fail. When I saw that I need to manually install postgresql, I did that, and then the redmine packages were configured, running dbconfig a second time. Thanks for your analysis! Mind that it's really a problem of conception on my side : naively installing two databases with same user should not screw up the password assigned the first time. It might be considered a bug of dbconfig-common, not sure yet. Jérémy. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#695774: redmine: fails to upgrade, says something about a pgsql_adapter
On Mon, 17 Dec 2012, Jérémy Lal wrote: naively installing two databases with same user should not screw up the password assigned the first time. Hmh. I don’t have a second instance, so I don’t even know the right password ☺ I could probably reset it using psql though. It might be considered a bug of dbconfig-common, not sure yet. Maybe. I don’t know dbconfig really, so I’ll leave this in your hands. No hurry from here. bye, //mirabilos -- tarent solutions GmbH Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/ Tel: +49 228 54881-393 • Fax: +49 228 54881-314 HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941 Geschäftsführer: Boris Esser, Sebastian Mancke -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#695774: redmine: fails to upgrade, says something about a pgsql_adapter
The bug comes from configuring two instances with the same db user. dbconfig-common regenerates a random password when configuring the second instance, wiping the password set for the first instance that has already been recorded in database.yml. Workaround : get the password of the second instance yy from /etc/redmine/yy/database.yml and set it in the database.yml of the first instance. I am working on a fix. Jérémy. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#695774: redmine: fails to upgrade, says something about a pgsql_adapter
On Wed, 12 Dec 2012, Jérémy Lal wrote: Is there a chance you had config files from an earlier redmine installation ? None whatsoever. Let me summarise what I did so far: I set up a fresh Debian wheezy VM on 29 November, installed postgresql, redmine, apache2, read through the Engrish README.Debian, set up two demonstration projects (one with svn, one with git), put the system on the LDAP and added two other people as admins. That’s all. And then, on 12 December, I did a dist-upgrade within wheezy. Preparing to replace redmine 1.4.4+dfsg1-1 (using .../redmine_1.4.4+dfsg1-1.1_all.deb) ... And the rest, you’ve already seen. Do yours have adapter: postgresql ? In which file? bye, //mirabilos -- tarent solutions GmbH Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/ Tel: +49 228 54881-393 • Fax: +49 228 54881-314 HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941 Geschäftsführer: Boris Esser, Sebastian Mancke -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#695774: redmine: fails to upgrade, says something about a pgsql_adapter
On 13/12/2012 10:16, Thorsten Glaser wrote: On Wed, 12 Dec 2012, Jérémy Lal wrote: Is there a chance you had config files from an earlier redmine installation ? None whatsoever. Let me summarise what I did so far: I set up a fresh Debian wheezy VM on 29 November, installed postgresql, redmine, apache2, read through the Engrish README.Debian, set up two demonstration projects (one with svn, one with git), put the system on the LDAP and added two other people as admins. That’s all. And then, on 12 December, I did a dist-upgrade within wheezy. Preparing to replace redmine 1.4.4+dfsg1-1 (using .../redmine_1.4.4+dfsg1-1.1_all.deb) ... And the rest, you’ve already seen. Do yours have adapter: postgresql ? In which file? in /etc/redmine/.../database.yml Anyway don't bother, the bug is reproducible by downgrading bundler to 1.1.4-6 and reconfiguring redmine-1.4.4+dfsg1-1.1. Jérémy. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#695774: redmine: fails to upgrade, says something about a pgsql_adapter
On 13/12/2012 10:16, Thorsten Glaser wrote: On Wed, 12 Dec 2012, Jérémy Lal wrote: Is there a chance you had config files from an earlier redmine installation ? None whatsoever. Let me summarise what I did so far: I set up a fresh Debian wheezy VM on 29 November, installed postgresql, redmine, apache2, read through the Engrish README.Debian, set up two demonstration projects (one with svn, one with git), put the system on the LDAP and added two other people as admins. That’s all. And then, on 12 December, I did a dist-upgrade within wheezy. Preparing to replace redmine 1.4.4+dfsg1-1 (using .../redmine_1.4.4+dfsg1-1.1_all.deb) ... And the rest, you’ve already seen. Do yours have adapter: postgresql ? In which file? Wrong : Anyway don't bother, the bug is reproducible by downgrading bundler to 1.1.4-6 and reconfiguring redmine-1.4.4+dfsg1-1.1. How to really reproduce : setup two instances and reconfigure. Jérémy. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#695774: redmine: fails to upgrade, says something about a pgsql_adapter
Package: redmine
Version: 1.4.4+dfsg1-1.1
Severity: serious
Justification: Policy 4.2
Today’s dist-upgrade inside wheezy failed. Retrying yields:
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue [Y/n]?
Setting up redmine (1.4.4+dfsg1-1.1) ...
dbconfig-common: writing config to
/etc/dbconfig-common/redmine/instances/default.conf
Creating config file /etc/redmine/default/database.yml.new with new version
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/vendor/rails/railties/lib/rails/gem_dependency.rb:21.
rake aborted!
Please install the pgsql adapter: `gem install activerecord-pgsql-adapter`
(cannot load such file -- active_record/connection_adapters/pgsql_adapter)
Tasks: TOP = db:migrate = environment
(See full trace by running task with --trace)
Error when running rake db:migrate, check database configuration.
dpkg: error processing redmine (--configure):
subprocess installed post-installation script returned error exit status 2
Errors were encountered while processing:
redmine
E: Sub-process /usr/bin/dpkg returned an error code (1)
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-4-amd64 (SMP w/1 CPU core)
Locale: LANG=C, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/mksh-static
Versions of packages redmine depends on:
ii bundler 1.1.4-6
ii dbconfig-common 1.8.47+nmu1
ii debconf [debconf-2.0] 1.5.46
ii redmine-pgsql 1.4.4+dfsg1-1.1
ii ruby 4.9
ii ruby-coderay 1.0.6-2
ii ruby-fastercsv1.5.5-1
ii ruby-net-ldap 0.3.1-2
ii ruby-rack 1.4.1-2
ii ruby-rails-2.32.3.14-4
ii ruby1.9.1 [ruby-interpreter] 1.9.3.194-5
redmine recommends no packages.
Versions of packages redmine suggests:
pn bzr none
pn cvs none
pn darcs none
ii git 1:1.7.10.4-1+wheezy1
pn mercurial none
pn ruby-openid none
pn ruby-rmagick none
ii subversion1.6.17dfsg-4
-- debconf information:
redmine/instances/default/password-confirm: (password omitted)
redmine/instances/default/pgsql/admin-pass: (password omitted)
redmine/instances/default/mysql/admin-pass: (password omitted)
redmine/instances/default/app-password-confirm: (password omitted)
redmine/instances/default/mysql/app-pass: (password omitted)
redmine/instances/default/pgsql/app-pass: (password omitted)
redmine/instances/default/db/app-user: redmine
redmine/instances/default/passwords-do-not-match:
redmine/instances/default/default-language: en
redmine/instances/default/remote/newhost:
redmine/instances/default/db/basepath:
redmine/notify-migration:
redmine/old-instances:
redmine/instances/default/upgrade-error: abort
redmine/instances/default/pgsql/changeconf: false
redmine/instances/default/missing-db-package-error: abort
redmine/instances/default/db/dbname: redmine_default
redmine/instances/default/purge: false
redmine/current-instances: default
redmine/instances/default/remote/host:
redmine/default-language: ${defaultLocale}
redmine/instances/default/dbconfig-upgrade: true
redmine/instances/default/pgsql/no-empty-passwords:
redmine/instances/default/internal/reconfiguring: false
redmine/instances/default/upgrade-backup: true
redmine/instances/default/pgsql/method: unix socket
redmine/instances/default/install-error: abort
redmine/instances/default/mysql/admin-user: root
* redmine/instances/default/database-type: pgsql
redmine/instances/default/pgsql/manualconf:
redmine/instances/default/pgsql/authmethod-admin: ident
redmine/instances/default/mysql/method: unix socket
redmine/instances/default/internal/skip-preseed: false
redmine/instances/default/pgsql/admin-user: postgres
redmine/instances/default/remove-error: abort
redmine/instances/default/dbconfig-remove:
redmine/missing-redmine-package:
redmine/instances/default/remote/port:
redmine/instances/default/pgsql/authmethod-user: password
* redmine/instances/default/dbconfig-install: true
redmine/instances/default/dbconfig-reinstall: false
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#695774: redmine: fails to upgrade, says something about a pgsql_adapter
I don't reproduce. Could you check you don't have : 1) incompatible gems (gem list) 2) incompatible redmine plugins (ls /usr/share/redmine/vendor/plugins) 3) custom installed rails (ls -l /usr/share/redmine/vendor/rails) thank you Jérémy. On 12/12/2012 17:24, Thorsten Glaser wrote: Package: redmine Version: 1.4.4+dfsg1-1.1 Please install the pgsql adapter: `gem install activerecord-pgsql-adapter` (cannot load such file -- active_record/connection_adapters/pgsql_adapter) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#695774: redmine: fails to upgrade, says something about a pgsql_adapter
Jérémy Lal dixit: I don't reproduce. Hum. I just installed the packages and not much else (this is a pretty fresh system used to evaluate redmine). Could you check you don't have : 1) incompatible gems (gem list) root@redmine:~ # gem list *** LOCAL GEMS *** 2) incompatible redmine plugins (ls /usr/share/redmine/vendor/plugins) root@redmine:~ # ls /usr/share/redmine/vendor/plugins acts_as_activity_provider acts_as_listacts_as_watchable gravatar acts_as_attachable acts_as_searchable awesome_nested_set open_id_authentication acts_as_customizable acts_as_treeclassic_pagination prepend_engine_views acts_as_event acts_as_versioned engines rfpdf 3) custom installed rails (ls -l /usr/share/redmine/vendor/rails) root@redmine:~ # ls -l /usr/share/redmine/vendor/rails lrwxrwxrwx 1 root root 31 Nov 29 13:34 /usr/share/redmine/vendor/rails - /usr/lib/ruby/vendor_ruby/rails root@redmine:~ # ls -l /usr/share/redmine/vendor/rails/ total 52 -rw-r--r-- 1 root root 1949 Aug 4 20:04 backtrace_cleaner.rb -rw-r--r-- 1 root root 478 Aug 4 20:04 gem_builder.rb -rw-r--r-- 1 root root 10152 Aug 4 20:04 gem_dependency.rb drwxr-xr-x 2 root root 4096 Nov 29 13:33 plugin -rw-r--r-- 1 root root 4769 Aug 4 20:04 plugin.rb drwxr-xr-x 2 root root 4096 Nov 29 13:33 rack -rw-r--r-- 1 root root 214 Aug 4 20:04 rack.rb lrwxrwxrwx 1 root root11 Aug 4 20:04 railties - ../railties -rw-r--r-- 1 root root 5256 Aug 4 20:04 vendor_gem_source_index.rb -rw-r--r-- 1 root root 137 Aug 4 20:04 version.rb bye, //mirabilos -- tarent solutions GmbH Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/ Tel: +49 228 54881-393 • Fax: +49 228 54881-314 HRB AG Bonn 5168 • USt-ID (VAT): DE122264941 Geschäftsführer: Boris Esser, Sebastian Mancke -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#695774: redmine: fails to upgrade, says something about a pgsql_adapter
Is there a chance you had config files from an earlier redmine installation ? Do yours have adapter: postgresql ? Jérémy. On 12/12/2012 19:20, Thorsten Glaser wrote: Jérémy Lal dixit: I don't reproduce. Hum. I just installed the packages and not much else (this is a pretty fresh system used to evaluate redmine). Could you check you don't have : 1) incompatible gems (gem list) root@redmine:~ # gem list *** LOCAL GEMS *** 2) incompatible redmine plugins (ls /usr/share/redmine/vendor/plugins) root@redmine:~ # ls /usr/share/redmine/vendor/plugins acts_as_activity_provider acts_as_listacts_as_watchable gravatar acts_as_attachable acts_as_searchable awesome_nested_set open_id_authentication acts_as_customizable acts_as_treeclassic_pagination prepend_engine_views acts_as_event acts_as_versioned engines rfpdf 3) custom installed rails (ls -l /usr/share/redmine/vendor/rails) root@redmine:~ # ls -l /usr/share/redmine/vendor/rails lrwxrwxrwx 1 root root 31 Nov 29 13:34 /usr/share/redmine/vendor/rails - /usr/lib/ruby/vendor_ruby/rails root@redmine:~ # ls -l /usr/share/redmine/vendor/rails/ total 52 -rw-r--r-- 1 root root 1949 Aug 4 20:04 backtrace_cleaner.rb -rw-r--r-- 1 root root 478 Aug 4 20:04 gem_builder.rb -rw-r--r-- 1 root root 10152 Aug 4 20:04 gem_dependency.rb drwxr-xr-x 2 root root 4096 Nov 29 13:33 plugin -rw-r--r-- 1 root root 4769 Aug 4 20:04 plugin.rb drwxr-xr-x 2 root root 4096 Nov 29 13:33 rack -rw-r--r-- 1 root root 214 Aug 4 20:04 rack.rb lrwxrwxrwx 1 root root11 Aug 4 20:04 railties - ../railties -rw-r--r-- 1 root root 5256 Aug 4 20:04 vendor_gem_source_index.rb -rw-r--r-- 1 root root 137 Aug 4 20:04 version.rb bye, //mirabilos -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
