[Jonas Meurer, 2011-10-07] > If the package has X-Python-Version > set to '2.6', this should result in a dependency on 'python2.6', which > might be versioned if required. But adding a dependency on 'python (>= > MIN), python (=< MAX)' makes no sense to me.
that was my original design, yes. Even for public modules dh_python2 was generating dependencies like: "python2.6 | python2.7" but later Jakub convinced me that it's hard to transition from one Python version to another this way and "python (>= 2.6), python (<< 2.8)" is actually the best solution for transitions. I changed dh_python2's behaviour and apparently broke handling private directories. Anyway, it's clearly a bug, it is reproducible so it's easy to fix and I will fix it as soon as I will find some free time this weekend. -- Piotr Ożarowski Debian GNU/Linux Developer www.ozarowski.pl www.griffith.cc www.debian.org GPG Fingerprint: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645 -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
