[pkg-bacula-devel] current bacula package status

[Luca Capello]

Hi Alexander!

Sorry for the long delay, DebConf13 is taking all my free time.

On Sat, 11 Aug 2012 07:46:04 +0200, Alexander Golovko wrote:
> В Fri, 10 Aug 2012 15:24:28 +0200
> Luca Capello <luca at pca.it> пишет:
>
>> On Wed, 08 Aug 2012 16:12:17 +0200, Alexander Golovko wrote:
>> > There is a next troubles:
>> >
>> >  - bacula-director-sqlite3 installation change permissions
>> >    to /var/lib/bacula
>> 
>> I do not get this, does it means that installing another
>> bacula-director-<dbtype> package does not preserve permissions?  This
>> is weird, given my comment below about purging old packages.
>
> It look like permissions changed by dbconfig-common stuff.
> Installing bacula-director-sqlite3 without dbconfigcommon help don't
> change permissions on /var/lib/bacula. But if i choose to create
> database with dbconfig-common, then /var/lib/bacula permissions changed
> from 0700 to 0750.

Ah OK, so this should be solved at the dbconfig-common level, but it is
a minor point.

>> >  - Installation bacula-director with other dbtype and then purging
>> > old package lead to removing bacula-dir.conf
>> 
>> Installing another -<dbtype> package should completely purge the old
>> -<dbtype> package, so no bacula-dir.conf file should be available when
>> the new package is uncompressed.  Can you elaborate a bit more, please
>> (yes, I am a bit lazy...)?
>
> 1. apt-get install bacula-director-mysql (for example. it can be any
> other)
> 2. apt-get install bacula-director-pgsql (for example)
> 3. dpkg -P bacula-director-mysql
>
> In this case bacula-director-mysql postrm script remove bacula-dir.conf

This is weird: I thought that the Conflicts:/Provides:/Replaces:
solution would have solved this, but this is not true since -mysql are
REMOVED and not PURGED. `apt-get --purge install bacula-director-pgsql`
does the Right Thing™.  For my solution to fix such a bug (yes, it is a
bug) read below.

>> IIRC bacula-dir.conf is not dbtype-independent, is it?  The easiest
>> solution I can think of is to split the -<dbtype>-specific part into
>> its own file and move the general bacula-dir.conf file to
>> -director-common.
>
> but this file include info, generated by dbconfig-common. It can't be
> created before bacula-director-dbtype installation.

This is true, but it can be shipped almost empty by -director-common,
then bacula-director-<dbtype> will fill it, thus removing the bug
above.  Anyway, this can be a future change.

>> > And there is a some TODO for future:
>> >
>> >  - fix bugs from debian bugtracker and from ubuntu launchpad.
>> 
>> In the past I tried to get Ubuntu's maintainers into the team, but no
>> one has replied yet: do you have any direct contact with them?
>
> I don't have contacts with them, but they react to my mail with
> differences between our packages and upload 5.2.6, based on our work.

We need to try to involve them in the team, I will send another
"invitation" before the end of this month.

>> >  - upgrade to 5.2.10 (i already make this, but due to wheezy
>> > frozen, i think, that this is not a subject for upload to sid)
>> >  - switch to ucf (the same, as with 5.2.10)
>> 
>> Both point dealt in my other reply:
>> 
>>   <mid:871ujec2jq.fsf at gismo.pca.it>
>>   <http://lists.alioth.debian.org/pipermail/pkg-bacula-devel/2012-August/000519.html>
>
> i think, this changes can be uploaded into experimental, but some later.

Fully agree.

Thx, bye,
Gismo / Luca
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 835 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-bacula-devel/attachments/20120909/4d49989f/attachment.pgp>