[Pkg-sql-ledger-discussion] another evaluation: 1.3.15-2

[Antoine Beaupré]

Hi again, sorry for the latency.

On Wed, 25 Apr 2012 23:24:29 -0400, Robert James Clay <jame at rocasa.us> wrote:
> On Tue, 2012-04-24 at 17:06 -0400, Antoine Beaupré wrote:
> 
> > The darn contrib directory
> > ==========================
> > 
> > I still had to configure the contrib_dir. Now I know I had to, but even
> > then: I forgot, so I hit this cryptic message in the web interface:
> > 
> > Cannot find Contrib script tablefunc.sql in /usr/share/pgsql/contrib/.
> > Please point your contrib_dir directive in your ledgersmb.conf to the
> > appropriate location
> > 
> > I think it would be useful to have some text displayed in postinst or
> > maybe debconf that would explain how to finish the configuration.
> 
>    Think I'll add a note advising about the package README.Debian to at
> least the "Configure LedgerSMB automatically?" template, and also add
> such a note to the NEWS file.

Sounds reasonable.

> >  I somehow expect Debian packages to be fully functional when they are
> > installed, or at least tell me how to make them work.
> 
>   I do see some possibilities with debconf/dbconf/ucf for being able
> to automatically set such things as the Pg contrib directory setting as
> well as other configuration items but that won't be until I can get a
> better handle on how to do it.

Should be possible to autodetect in postinst, but yes, it would require
using ucf, which is a bit annoying.

I think this could be improved by having sane defaults. If we disregard
backports, there's generally only one version of postgresql in stable
Debian releases:

 * lenny: 8.3
 * squeeze: 8.4
 * wheezy: 8.4 and 9.1 (but is testing)
 * sid: 8.4, 9.0, 9.1... 

So that could be changed so that, for example, the .conf shipped in
sid/wheezy would be for 9.1 contrib and so hardcode that path, while the
backport would have a modified .conf file for 8.4..

This seems like a simpler approach than messing around with ucf...

>    But you're thinking that without that and perhaps even when the
> ledgersmb role is set up properly, a note should be added for during the
> installation, explicitly pointing to more information about the setup?
> (Which will be in the README.Debian file...)

Yes, that seems important seems the README.Debian file is necessary to
complete the install.

On Wed, 25 Apr 2012 22:57:22 -0400, Robert James Clay <jame at rocasa.us> wrote:
> On Tue, 2012-04-24 at 17:06 -0400, Antoine Beaupré wrote:
> > Confusion: two passwords?
> > =========================
> > 
> > I get prompted for a password twice... The first time, I *think* it is
> > for the ledgersmb DB user, but then I get asked again, for "Password for
> > the Database Administrative user:".
> 
>    The latter is from what I put in there, the former is something
> unexpected because I thought I was overriding it.
> 
> > How are those two different? Should they be the same?
> > I *feel* the first password is the ledgersmb password, but who knows? It
> > seems to be working in the setup.pl script, what is the second one for then?
> 
>    One reason the debconf is not currently enabled by default

I am not sure I understand that...

> (it did show up that way initially, did it not?  Before you changed it
> to do it "automatically"?)

I am not sure about this.

> is that it is not working as expected.  Currently, it can create the
> ledgersmb role but not with the correct permissions.

That, I understand. However, maybe a clever few psql invocations could
fix that, no?

Thanks for the support,

A.

-- 
Ou bien Dieu voudrait supprimer le mal, mais il ne le peut pas
Ou bien Dieu pourrait supprimer le mal, mais il ne le veut pas.
            			- Sébastien Faure
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 835 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-sql-ledger-discussion/attachments/20120502/42d0e626/attachment.pgp>