[pkg-bacula-devel] [pkg-bacula-commits] [bacula] 01/01: Added "Muti-Arch: same" for bacula-director-common Added new debian version to debian/changelog

[Sven Hartge]

Um 17:01 Uhr am 12.11.17 schrieb Carsten Leonhardt:

>>>     Added "Muti-Arch: same" for bacula-director-common
>>>     Added new debian version to debian/changelog
>>
>> This creates the following lintian warning:
>>
>> W: bacula source: dependency-is-not-multi-archified bacula-director-common 
>> depends on bacula-common (multi-arch: no)
 
> well, then I'll throw it out again.

Correct me, if I am wrong: since bacula-common containes shared objects in 
arch-unspecific paths, there is nothing we can do here, unless you want to 
move everything from /usr/lib/bacula/ to /usr/lib/$ARCH_TRIPLE/bacula/ to 
make bacula-common:$ARCH coinstallable. 

Question is: why would anyone do this? Have a 32bit FD on the same machine 
as a 64bit director?

BTW: I have this in my ~/.gbp.conf:

-----8<-----
[DEFAULT]

# Options only affecting gbp buildpackage
[buildpackage]
pbuilder = True
export-dir = ../build-dir/
postbuild=lintian --color always -EvIL +pedantic --profile debian/main --info "$GBP_CHANGES_FILE"
[...other options snipped...]
-----8<-----

This barks at me quite visibly if something is not like it should be.

Grüße,
Sven.