Defect #3727 doesn't work when merging

Added by Pablo Lerina over 13 years ago. Updated over 11 years ago.

Status:NewStart date:2009-08-10
Priority:NormalDue date:
Assignee:-% Done:


Category:SCM extra
Target version:-
Resolution: Affected version:0.8.4


When running a svn merge got this error at Apache error_log:

[Mon Aug 10 15:22:02 2009] [notice] Apache/2.2.11 (Unix) mod_ssl/2.2.11 OpenSSL/0.9.8k DAV/2 Phusion_Passenger/2.2.4 SVN/1.6.2 mod_perl/2.0.4 Perl/v5.8.8 configured -- resuming normal operations
Can't make DBI com handle for DBD::Pg::db: unknown package.

This problem was already reported here and here

About your application's environment
Ruby version 1.8.6 (i686-linux)
RubyGems version 1.3.5
Rails version 2.1.2
Active Record version 2.1.2
Action Pack version 2.1.2
Active Resource version 2.1.2
Action Mailer version 2.1.2
Active Support version 2.1.2
Application root /var/www/redmine
Environment development
Database adapter postgresql
Database schema version 101

Subversion: 1.6.2

vhost conf:

                <Location /svn>
                  DAV svn
                  SVNParentPath "/var/svn/" 
                  SVNPathAuthz off

                  AuthType Basic
                  AuthName redmine
                  Require valid-user

                  PerlAccessHandler Apache::Authn::Redmine::access_handler
                  PerlAuthenHandler Apache::Authn::Redmine::authen_handler

                  RedmineDSN "dbi:Pg:dbname=redmine;host=localhost" 
                  RedmineDbUser "redmine" 
                  RedmineDbPass " " 

image002.png - TSvn Error message (40.7 KB) Daniel Nauck, 2009-09-19 10:36

Related issues

Related to Redmine - Patch #9066: not working for merges/copy #3727 New 2011-08-16


#1 Updated by Pablo Lerina over 13 years ago

And got the error

$ svn merge -r200:HEAD --dry-run https://localhost/svn/proj/trunk
svn: PROPFIND of '/svn/proj/!svn/bc/3095/trunk/src': Could not read status line: Secure connection truncated (https://loclahost)
svn: Error reading spooled REPORT request response

#2 Updated by Ronie Henrich over 13 years ago


#3 Updated by Daniel Nauck about 13 years ago


same error with on Ubuntu 9.04 and PostgreSQL

There're also a lot of bug reports in the Forum about this issue.

#4 Updated by Daniel Nauck about 13 years ago

This forum post is also related, i've this too:

#5 Updated by Toshi MARUYAMA over 11 years ago

  • Category changed from SCM to SCM extra
  • Priority changed from High to Normal

#6 Updated by Andreas Reischuck over 11 years ago

I added a patch that might fix this issue: #9066

Also available in: Atom PDF