Bug#406935: another evaluation: 1.3.15-2
On Wed, 2012-05-02 at 13:21 -0400, Antoine Beaupré wrote: On Wed, 25 Apr 2012 23:42:41 -0400, Robert James Clay j...@rocasa.us wrote: On Tue, 2012-04-24 at 17:06 -0400, Antoine Beaupré wrote: If you tried doing the configuration 'automatically' instead of letting it go manually, it's quite possible that the ledgersmb role is there but does not have the correct permissions. ALTER ROLE ledgersmb WITH SUPERUSER LOGIN NOINHERIT; Then back to setup.pl and see how it goes. I tried that, no luck. The user for ledger is created properly by setup.pl, but i still get prompted for a password popup after logging in: i see the frames, but it is shadowed by a password window. I still get the lsmb13 error. Oh bloody hell: the problem was that I was blocking cookies. I hate it when that happens...g , I can login to ledger now. Glad to hear it! Still a really weird failure mode if you ask me. :) Indeed.g And that can certainly complicate things in applications like this, trying to figure if a particular problem is in the application, or the browser, or the web server, or ... Jame -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#406935: another evaluation: 1.3.15-2
On Wed, 2012-05-02 at 13:38 -0400, Antoine Beaupré wrote: On Wed, 25 Apr 2012 22:57:22 -0400, Robert James Clay j...@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... 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... When I first put it in (with 1.3.14-2), I had the default to the question Configure LedgerSMB Automatically? as true. I changed that to false with a later version because with the way it was running, it was unclear what it was asking for and because if the 'ledgersmb' role was created, it didn't get created with the correct permissions. If you installed a version before that change and then upgraded; you wouldn't necessarily see that now defaults to not doing it automatically or have the option to turn it back off unless you ran 'dpkg-reconfigure ledgersmb'. 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? That's what I've been thinking it will take, assuming there isn't some other way that I just haven't figured out yet. I did add some sql that is supposed to correct the permissions but that doesn't appear to be working. Jame -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#406935: another evaluation: 1.3.15-2
On Wed, 2012-05-02 at 13:38 -0400, Antoine Beaupré wrote: On Wed, 25 Apr 2012 23:24:29 -0400, Robert James Clay j...@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: 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) I'd forgotten that 8.4 is actually still available in wheezy...g The default is 9.1, so that's certainly the version to assume. * 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.. That's what I've been planning on doing, although I hadn't thought as far as what would be needed for a backport. The file itself is already being patched for other reasons (updates for other directories), so this could just be added to it. Jame -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#406935: another evaluation: 1.3.15-2
On Wed, 25 Apr 2012 23:42:41 -0400, Robert James Clay j...@rocasa.us wrote:
On Tue, 2012-04-24 at 17:06 -0400, Antoine Beaupré wrote:
The lsmb13 database
===
I still can't use ledgersmb, even with all the above fixed. From the
user point of view, I just repeatedly get prompted for my password, in
HTTP Auth-style popups from my browser. I see this in the apache error
logs:
DBI connect('dbname=lsmb13','koumbit-test',...) failed: FATAL: la base
de donn?es lsmb13 n'existe pas at LedgerSMB.pm line 981
If you tried doing the configuration 'automatically' instead of
letting it go manually, it's quite possible that the ledgersmb role is
there but does not have the correct permissions. The README.Debian file
has a note about creating the role manually. Or if the role is present
you don't want to delete it, you can go into psql and run something like
this:
ALTER ROLE ledgersmb WITH SUPERUSER LOGIN NOINHERIT;
Then back to setup.pl and see how it goes.
I tried that, no luck. The user for ledger is created properly by
setup.pl, but i still get prompted for a password popup after logging
in: i see the frames, but it is shadowed by a password window. I still
get the lsmb13 error.
Oh bloody hell: the problem was that I was blocking cookies. I am so
sorry about this, I can login to ledger now.
Still a really weird failure mode if you ask me. :)
A.
--
Antoine Beaupré +++ Réseau Koumbit Networks +++ +1.514.387.6262 #208
pgpFQnxp01pyb.pgp
Description: PGP signature
Bug#406935: another evaluation: 1.3.15-2
Hi again, sorry for the latency. On Wed, 25 Apr 2012 23:24:29 -0400, Robert James Clay j...@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 j...@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 pgptCpwCXIsvI.pgp Description: PGP signature
Bug#406935: another evaluation: 1.3.15-2
On Tue, 2012-04-24 at 17:06 -0400, Antoine Beaupré wrote: So here's another review. In order to do this, I have purged the previous package, removed the databases from the pgsql server (including the ledgersmb DB) and installed the new package compiled with svn-buildpackage. 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 (it did show up that way initially, did it not? Before you changed it to do it automatically?) is that it is not working as expected. Currently, it can create the ledgersmb role but not with the correct permissions. Jame -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#406935: another evaluation: 1.3.15-2
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. 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. 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...) Jame -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#406935: another evaluation: 1.3.15-2
On Tue, 2012-04-24 at 17:06 -0400, Antoine Beaupré wrote:
The lsmb13 database
===
I still can't use ledgersmb, even with all the above fixed. From the
user point of view, I just repeatedly get prompted for my password, in
HTTP Auth-style popups from my browser. I see this in the apache error
logs:
DBI connect('dbname=lsmb13','koumbit-test',...) failed: FATAL: la base
de donn?es lsmb13 n'existe pas at LedgerSMB.pm line 981
If you tried doing the configuration 'automatically' instead of
letting it go manually, it's quite possible that the ledgersmb role is
there but does not have the correct permissions. The README.Debian file
has a note about creating the role manually. Or if the role is present
you don't want to delete it, you can go into psql and run something like
this:
ALTER ROLE ledgersmb WITH SUPERUSER LOGIN NOINHERIT;
Then back to setup.pl and see how it goes.
Jame
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#406935: another evaluation: 1.3.15-2
So here's another review.
In order to do this, I have purged the previous package, removed the
databases from the pgsql server (including the ledgersmb DB) and
installed the new package compiled with svn-buildpackage.
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:.
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?
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. I
somehow expect Debian packages to be fully functional when they are
installed, or at least tell me how to make them work.
The lsmb13 database
===
I still can't use ledgersmb, even with all the above fixed. From the
user point of view, I just repeatedly get prompted for my password, in
HTTP Auth-style popups from my browser. I see this in the apache error
logs:
DBI connect('dbname=lsmb13','koumbit-test',...) failed: FATAL: la base
de donn?es lsmb13 n'existe pas at LedgerSMB.pm line 981
Now I am stuck again - how is it that it is connecting to that database?
Please advise. :)
Cheers,
A.
--
The United States is a nation of laws:
badly written and randomly enforced.
- Frank Zappa
pgpL1g0RrYlc5.pgp
Description: PGP signature
