[Debian-med-packaging] Bug#940703: Bug#940703: augustus_3.3.3+dfsg-1_mips64el.changes REJECTED

[Sascha Steinbiss]

> On 19. Sep 2019, at 11:29, Aurelien Jarno <aurelien at aurel32.net> wrote:
> 
> Package: augustus
> Version: 3.3.3+dfsg-1
> Severity: serious
> 
> On 2019-09-18 23:34, Debian FTP Masters wrote:
>> augustus_3.3.3+dfsg-1_mips64el.deb: Built-Using refers to non-existing source package libbam-dev (= 0.1.19-4)
>> 
>> 
>> Mapping sid to unstable.
>> 
>> ===
>> 
>> Please feel free to respond to this email if you don't understand why
>> your files were rejected, or if you upload new files which address our
>> concerns.
>> 
>> 
>> 
> 
> The Built-Using field should use the source package (i.e.
> samtools-legacy), not the binary package.


Why? In the build am only using the static library from libbam-dev, not compiling source code from the samtools-legacy source package. Sorry, but this is a serious question as I am not sure what do do here.

7.8 of the policy requires that I have an ‘=‘ version relation on the package listed in ‘Built-Using' — I am not even sure how I would determine that for the source package since it’s not even used in the build?
Do I even need to provide a Built-Using here? Searching on code search for libbam-dev and samtools-legacy did not turn up a single case where a Built-Using was set.

Thanks
Sascha

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924359
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: Message signed with OpenPGP
URL: <http://alioth-lists.debian.net/pipermail/debian-med-packaging/attachments/20190919/0b481484/attachment-0001.sig>