[PATCH 06 of 11 cubicweb/debian] [pkg] Tidy substvars usage in control file

Jérémy Bobbio jeremy.bobbio at irq7.fr
Fri Jun 14 16:53:01 CEST 2019


On 14/06/2019 09:46, Denis Laxalde wrote:
> Jérémy Bobbio a écrit :
>> # HG changeset patch
>> # User Jérémy Bobbio <jeremy.bobbio at irq7.fr>
>> # Date 1560437267 -7200
>> #      Thu Jun 13 16:47:47 2019 +0200
>> # Node ID 43434fa141d3b6e6c4b4adcde9ec76c87a00453a
>> # Parent  92e33a1c5ec8d3756f6df5c689593f524c762e25
>> [pkg] Tidy substvars usage in control file
>>
>> The documentation package was missing a Built-Using field to record
>> the provenance of the templates.
>>
>> Empty packages or meta packages do not require Depends on a specific
>> Python version, so we can remove the relevant substvars.
>>
> 
>> diff -r 92e33a1c5ec8 -r 43434fa141d3 debian/control
>> --- a/debian/control	Mon Jun 10 10:53:48 2019 +0200
>> +++ b/debian/control	Thu Jun 13 16:47:47 2019 +0200
>> @@ -124,7 +124,7 @@
>>  Provides: cubicweb-postgresql-support
>>  Depends:
>>   ${misc:Depends},
>> - ${python3:Depends},
>> + python3-cubicweb (= ${source:Version}),
> 
> Is there a reason to source:Version instead of binary:Version? (I'm not
> familiar with this, just read "man deb-substvars" and didn't find an
> obvious answer.) Thanks.

The differences between these two variables are related to binNMU.
binNMUs are forced rebuilds of architecture-specific packages against
a new environment: https://wiki.debian.org/binNMU

Given cubicweb only builds Architecture:all packages, the difference
is virtually non-existent. I think it would be slightly more error proof
to use binary:Version, but as far as I know, it really does not matter
in this context.

Thanks for asking!

-- 
Lunar



More information about the cubicweb-devel mailing list