[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#282146: Bug#282416: fixed in bacula 1.36.1-1

Filip Van Raemdonck wrote:


reopen 282416 mechanix@debian.org
tags 282416 + patch
thanks

On Thu, Dec 09, 2004 at 02:17:13PM -0500, Jose Luis Tallon wrote:

We believe that the bug you reported is fixed in the latest version of
bacula, which is due to be installed in the Debian FTP archive:

<...>

  * bacula-director-sqlite: revised upgrade logic. Should work now --
    feedback requested (Closes: #282416)


Nope:

root@scorpio:~# /etc/init.d/bacula-director start
Starting Bacula Director: 04-Jan 08:56 bacula-dir:  Fatal error: Version error for database "bacula". Wanted 8, got 7
04-Jan 08:56 bacula-dir:  Fatal error: Could not open database "bacula".
04-Jan 08:56 bacula-dir:  Fatal error: Version error for database "bacula". Wanted 8, got 7
04-Jan 08:56 bacula-dir ERROR TERMINATION
Please correct configuration file: /etc/bacula/bacula-dir.conf
failed.

When I run the postinst manually with a 1.34 version argument I get this:

root@scorpio:~# /var/lib/dpkg/info/bacula-director-sqlite.postinst configure 1.34.0
Upgrading SQLite tables to v8 format...Ok.

Then it tries to start the director but gives the same error as above.

Checking the postinst it is quickly clear why:

 if [ $<upgradescript> ...
    ^

The 'test' ('[') invocation should not be there; the if needs to check the
exit code of the upgrade script by itself.

Ooopsss.. yet another typo.
Guess i have to seriously consider migrating to 'dbconfig-common' to avoid these in the future :-S 
Anyways, the fix is already included.


I seem to remember having fixed this before for the v6->v7 upgrade in my NMU.
It's certainly possible. I might have made a mistake when hand-patching or somehow re-introduced the bug later. 
Anyways, it won't happen again.


Patch attached.

Thank you very much, Filip.
The corrected version will be uploaded as soon as possible (as soon as my sponsor is back home) 



Best,
   J.L.
Reply to: