Package: bacula Version: 3.0.3-1 Severity: normal Tags: patch
Hi, This still happens in version 3.0.3-1, for the same reasons as previously: the link from /usr/share/doc/bacula to /usr/share/doc/bacula-common ends up being shipped by the bacula-common package, and the bacula package has no files or directories. This has several consequences: dpkg complains because it's told to configure a package which no longer exists as far as it's concerned, and if bacula was installed using aptitude (with its dependencies marked as "auto"), the next aptitude run suggests removing all the bacula packages. There's a fix in the patch attached to http://bugs.debian.org/554197; basically, all that's required is to remove the "ln" command in debian/rules. There's already a bacula.links file with appropriate link, which then ends up in the bacula package. Regards, Stephen -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable'), (200, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.32-trunk-686 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages bacula depends on: ii bacula-client 3.0.3-1.1 network backup, recovery and verif ii bacula-common 3.0.3-1.1 network backup, recovery and verif ii bacula-server 3.0.3-1.1 network backup, recovery and verif bacula recommends no packages. Versions of packages bacula suggests: ii bacula-doc 2.4.4-1 Documentation for Bacula -- no debconf information -- debsums errors found: debsums: no md5sums for bacula -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
