* Sandro Tosi <mo...@debian.org>, 2011-11-01, 12:52:
Dependencies generated by dh_numpy
==================================
dh_numpy would generate dependency either on "python-numpy-abi$N"
(by default) or on "python-numpy-api$N" (if a special option, say,
--strict, is used).
I just realized that, in order to make packages using Cython happy,
the first one will have to be:
"python-numpy-abi$N, python-numpy (>= $V)"
where $V is the first version with the current API. [0]
Mh ok, so we need to keep 3 versions information: the ABI $N, the API
$N, and the version $V that introduced API $N - did I get it correctly?
Yes. Though it'd better not to use same name for two distinct variables
(yes, I know, I made the same mistake myself). :P
Gracefully handling the upcoming transition
Ok, so we should start like this:
- implement this proposal in the version currently in sid
Here we could:
- wait until new dh_numpy hits testing
- round of binNMUs
- wait for transition to testing?
- port the code to 1.6.1 package in experimental
- upload it to sid
- reiter
is that correct?
Yes, sounds about right.
--
Jakub Wilk
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
