Hi Andreas, On 29-06-15 23:35, Andreas Henriksson wrote: > Looks like this issue is very much introduced by dbconfig-common > not properly handling running from scripts that use 'set -e' > anymore.
I am not yet sure that I agree, but... > I'm thus reassigning it as instructed... That is fine for now. > Quickly looked at the problem and spotted an issue when running > under 'set -e'. See attached patch. If I am not mistaken, things go wrong earlier. For the moment I believe that the script should fail here if there is an error (there shouldn't be one). > With the patch applied to dbconfig-common, the installation > of bandwidthd-pgsql continues much further until it runs in to yet > another issue which I've not yet had time to investigate > (however it doesn't seem to be specific to anything the > bandwidthd-pgsql package does either): Can you help me with understanding what you do in the postinst/config scripts of bandwidthd? E.g. why don't you run dbconfig-common during config, like in section 3.1.2 of the ch-develguide.html page in the dbconfig-common package? Also, why is the dbc_go call in the postinst AFTER the reading of /etc/dbconfig-common/bandwidthd-pgsql.conf ? At first sight, that doesn't make much sense. > + RET='10 bandwidthd-pgsql/pgsql/method doesn'\''t exist' This should indeed not happen, these templates should be installed during config. Although I don't see exactly why yet, it may be related to the item mentioned above, no call from your config to dbc. During my (manual) trials, I was not able to trigger the dbconfig-common questions, but also not the failure. Do you have a recipe to I reproduce this issue? Paul
signature.asc
Description: OpenPGP digital signature
