Package: bacula-director-sqlite3
Version: 3.0.2-1
Severity: normal

Hi.

I'm not totally sure, if this is a possible bug, but because the
postinst of bacula-director-sqlite3 uses sqlite to dump the old bacula-2
database it should depend on sqlite _and_ sqlite3 (as long as the
upgrade code is inside the postinst), since it may be possible to end up
in a situation where sqlite is already removed when the postinst trying
to use it is run by dpkg.

Grüße,
Sven.

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (900, 'unstable'), (200, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.29.1-217
Locale: lang=de...@euro, lc_ctype=de...@euro (charmap=ISO-8859-15)
Shell: /bin/sh linked to /bin/dash

Versions of packages bacula-director-sqlite3 depends on:
ii  bacula-director-common        2.4.4-1+b1 network backup, recovery and verif
ii  debconf [debconf-2.0]         1.5.27     Debian configuration management sy
ii  libc6                         2.9-25     GNU C Library: Shared libraries
ii  libgcc1                       1:4.4.1-2  GCC support library
ii  libsqlite3-0                  3.6.17-2   SQLite 3 shared library
ii  libstdc++6                    4.4.1-2    The GNU Standard C++ Library v3
ii  libwrap0                      7.6.q-18   Wietse Venema's TCP wrappers libra
ii  python2.4                     2.4.6-2    An interactive high-level object-o
ii  sqlite3                       3.6.17-2   A command line interface for SQLit

bacula-director-sqlite3 recommends no packages.

bacula-director-sqlite3 suggests no packages.



-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to