I think this is what the PYBUILD_NAME variable is for. Set it to "pysam" (pybuild handles the python3?- prefix for you).
Or use a .install file. I think that you must omit the python3?- prefix here either. I realize just now that this may be the problem I faces yesterday. Can someone confirm.
Regards.
Le 11 févr. 2014 09:39, "Andreas Tille" <andreas@an3as.eu> a écrit :
> Hi,
>
> I'm working on python-pysam in the Debian Med team at
>
> git://anonscm.debian.org/debian-med/pysam.git
>
> The package was created nicely until I added an additional binary
> package python-pysam-tests covering the test data in a separate file
> (since it us usually not needed but might be helpful to test the data).
>
> Once I have added the additional paragraph
>
> Package: python-pysam-tests
> ...
>
> the main package python-pysam remains empty (except of the
> /usr/share/doc/python-pysam
> directory. I can reproduce this behavious by simply deleting the
> python-pysam-tests paragraph in debian/control.
>
> It seems that there is some problem in dh_python (or a related tool
> which gets disturbed if you add an "unexpected" binary package not
> covering any Python modules.
>
> I'd like to discuss this here before filing a stupid bug report.
>
> Any idea what might have happened?
>
> Kind regards
>
> Andreas.
>
> --
> http://fam-tille.de
>
>
> --
> To UNSUBSCRIBE, email to debian-python-REQUEST@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
> Archive: [🔎] 20140211083811.GB6848@an3as.eu">http://lists.debian.org/[🔎] 20140211083811.GB6848@an3as.eu
>