Re: Mysterious double python dependency

[Nikolaus Rath <Nikolaus@rath.org>]

Jakub Wilk <jwilk@debian.org> writes:
> * Nikolaus Rath <Nikolaus@rath.org>, 2011-12-30, 10:14:
>> When creating the S3QL package, I somehow get a dependency on both
>> python and python2.7:
>>
>>Depends: python (>= 2.6.6-7~), [...], python2.7
>
> They were both generated by dh_python2. And they are both needed to
> run the postinst script:
>
> 1) "python (>= 2.6.6-7~)" is needed because /usr/bin/pycompile is in
> the "python" package.
>
> 2) s3ql's private modules must be used only with python2.7 (since
> /usr/lib/s3ql/s3ql/_deltadump.so was built for 2.7). Naturally, you
> need python2.7 to byte-compile for 2.7.
>
> Does it make sense now?
>
> No, of course it doesn't. All scripts that would use the _deltadump
> extension have #!/usr/bin/python shebangs, so there's no guarantee
> they'll actually be run with python2.7. The dependency should have
> been "python (>= 2.7), python (<< 2.8)", as per Python Policy 3.1.1.

Pardon my ignorance, but is that something I should fix in the S3QL
control file, or something that should be fixed in dh_python2?

Best,

   -Nikolaus

-- 
 »Time flies like an arrow, fruit flies like a Banana.«

  PGP fingerprint: 5B93 61F8 4EA2 E279 ABF6  02CF A9AD B7F8 AE4E 425C