On 16/10/2020 09:19, Drew Parsons wrote:
On 2020-10-16 14:43, Giovanni Mascellani wrote:
Hi,
Il 16/10/20 02:53, Drew Parsons ha scritto:
Would it make sense to use the Built-Using [1] header?
...
[1]
https://www.debian.org/doc/debian-policy/ch-relationships.html#additional-source-packages
On 10/15/20 10:03 PM, Alastair McKinstry wrote:
> On 15/10/2020 08:13, Giovanni Mascellani wrote:
>
>> Hi,
>>
>> Il 14/10/20 15:52, Alastair McKinstry ha scritto:
>>> I maintain the package "ecflow" which uses libboost-python-dev. Now
>>> with the transition to python3.9, ecflow will support (wher
On 2020-10-16 14:43, Giovanni Mascellani wrote:
Hi,
Il 16/10/20 02:53, Drew Parsons ha scritto:
Would it make sense to use the Built-Using [1] header?
...
[1]
https://www.debian.org/doc/debian-policy/ch-relationships.html#additional-source-packages-used-to-build-the-binary-built-using
The
Hi,
Il 16/10/20 02:53, Drew Parsons ha scritto:
> Source: boost1.71
> Followup-For: Bug #972213
> X-Debbugs-Cc: debian-pyt...@lists.debian.org
>
> Would it make sense to use the Built-Using [1] header?
> e.g.
> Built-Using: python3.8 python3.9
>
> dh_python3 knows if the module includes extens
Source: boost1.71
Followup-For: Bug #972213
X-Debbugs-Cc: debian-pyt...@lists.debian.org
Would it make sense to use the Built-Using [1] header?
e.g.
Built-Using: python3.8 python3.9
dh_python3 knows if the module includes extensions
(*_python*.so.) and could inject the pythons into Built-Using.
On 15/10/2020 08:13, Giovanni Mascellani wrote:
Hi,
Il 14/10/20 15:52, Alastair McKinstry ha scritto:
I maintain the package "ecflow" which uses libboost-python-dev. Now
with the transition to python3.9, ecflow will support (where
possible) multiple python versions. Currently it supports pytho
Hi,
Il 14/10/20 15:52, Alastair McKinstry ha scritto:
> I maintain the package "ecflow" which uses libboost-python-dev. Now
> with the transition to python3.9, ecflow will support (where
> possible) multiple python versions. Currently it supports python3.8
> but not python3.9 ; this may be fixed i
Package: boost1.71
Version: 1.71.0-7
Severity: normal
I maintain the package "ecflow" which uses libboost-python-dev.
Now with the transition to python3.9, ecflow will support (where possible)
multiple python versions.
Currently it supports python3.8 but not python3.9 ; this may be fixed in a
bi
8 matches
Mail list logo