[pkg-bacula-devel] libs3 - status

Sven Hartge sven at svenhartge.de
Sun Nov 29 20:01:22 GMT 2020


On 29.11.20 20:48, Mario Pranjic wrote:

> But, out of curiosity... What is to be done after branches are set? If I 
> understood correctly, this libs3 doesn't properly use debian control and 
> rules files, but, instead, doeas stuff with it's own makefile.
> That is not the way it is supposed to be?

No upstream code uses debian/control or debian/rules. In this case, the 
upstream source unfortunately already contains a debian directory with 
(for us) useless contents.

It may be wise to just filter it out on import, see debian/gbp.conf from 
the main bacula package on how this may be done with the filter feature 
of import-orig.

Not every package uses autoconf and using it is no requirement.

dh is usually smart enough to figure this out and if not, you can always 
override the individual targets to do things the way they need to be done.

Grüße.
Sven.



More information about the pkg-bacula-devel mailing list