On 15.06.2015 12:59, Jörg Steffens wrote: > Am 13.06.2015 um 11:41 schrieb Felix Geyer: > [...] >> Shouldn't the whole setting up a database part be done in the director >> package? >> It's the one that cares about having a database setup and it can depend on >> -tools >> and a database backend. >> So by the time the director is configured you have all the things you need to >> create the database. > > For upstream I can say, this bug have been fixed a while ago, see > https://github.com/bareos/bareos/commit/53fa745060609b5f6123c03258fc1f809435ab01
bareos-database-common doesn't pull in the bareos-dbcheck binary from bareos-database-tools with that commit. > The reason why the logic is not in bareos-director is that the catalog > (database) should be installable on a different system then the director. I'm not quite sure I follow. You want bareos-database-common to be installable on the database server? That seems not very desirable as you have to worry about version mismatches and you can't automatically write the database configuration to the director config. Afaik dbconfig-common can work with remote databases if you configure it that way. Of course the custom package tooling around it needs to support it too. Cheers, Felix -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
