code needs to require 'pg' instead of 'postgres'

[David N. Welton]

Binary package hint: libpgsql-ruby

I'm on Intrepid.

The changelog says this code, as of 0.7.9 is actually a different library. Perhaps I'm just confused, but it seems that that's the sort of thing that might have simply warranted a different package name, in order to not have code break on upgrade.

[Bryan McLellan (btm)]

Upstream switched [1] from ruby-postgres [2] which wasn't being maintained to ruby-pg [3]. While the new project appears to be maintaining updates to the old codebase, it's unfortunately packaged seperately.

[1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=474748
[2] http://rubyforge.org/projects/ruby-postgres
[3] http://rubyforge.org/projects/ruby-pg

[Bryan McLellan (btm)]

Spoke to upstream about this package, along with the discussion in the debian bug he adds,

"The benefit of allowing people who use ruby-postgres directly (as opposed to a wrapper layer like Ruby/DBI or Rails/Active Record) to postpone the migration is not worth the costs: supporting an obsolete package with dead upstream, extra load on package archive and mirrors infrastructure, user confusion due to having two almost but not exactly similar libraries performing the same job."

I agree, I don't believe that adding an ubuntu package for the obsolete library or forking the libpgsql-ruby package in ubuntu is worth the effort.

[David N. Welton (davidnwelton)]

Ok, fair enough. Thanks for taking the time to look into it!