Hi,
On 12/03/2014 04:10 AM, Andreas Beckmann wrote:
> during a test with piuparts I noticed your package failed to install. As
> per definition of the release team this makes the package too buggy for
> a release, thus the severity.
Thanks. This is what you get when you try to solve dependency loops :/
>>From the attached log (scroll to the bottom...):
>
> Selecting previously unselected package bareos-database-common.
> (Reading database ... 9220 files and directories currently installed.)
> Preparing to unpack
> .../bareos-database-common_14.2.1+20141017gitc6c5b56-4_amd64.deb ...
> Unpacking bareos-database-common (14.2.1+20141017gitc6c5b56-4) ...
> Setting up bareos-database-common (14.2.1+20141017gitc6c5b56-4) ...
> /var/lib/dpkg/info/bareos-database-common.config: 1:
> /var/lib/dpkg/info/bareos-database-common.config: /usr/sbin/bareos-dbcheck:
> not found
> Warning: failed to get "dbname" from config, using default value "bareos",
> see /tmp/bareos-config.11958.log
> /var/lib/dpkg/info/bareos-database-common.config: 1:
> /var/lib/dpkg/info/bareos-database-common.config: /usr/sbin/bareos-dbcheck:
> not found
> Warning: failed to get "dbuser" from config, using default value "bareos",
> see /tmp/bareos-config.11958.log
> (config) dbc_go() bareos-database-common configure.
bareos-database-common is not designed to be installed alone, yet it
triggers the above bug in that situation.
We could add a layer of "[ -x /usr/sbin/bareos-dbcheck ]" around the
calls to it (it's in bareos-database-tools).
Or we re-add bareos-database-tools to bareos-database-common depends,
but remove bareos-database-{postgresql,mysql,sqlite} from -tools depends
(which is also wrong, as dbcheck won't work then in all cases).
Joerg, any ideas? I'd go for the silly -x one.
Greets
Evgeni
_______________________________________________
Pkg-bareos-devel mailing list
[email protected]
https://lists.alioth.debian.org/mailman/listinfo/pkg-bareos-devel
