Re: Towards Python 2.6: Architecture:all & XS-P-V:current packages

2010-02-23 Thread Yaroslav Halchenko
On Mon, 22 Feb 2010, Yaroslav Halchenko wrote: > On Sat, 20 Feb 2010, Piotr Ożarowski wrote: > > > current, >= X.X, << X.X > > > then add additional restrictions? > > dh_py* do that... unless you hardcode Python version f.e. in shebang doh -- just now mentioned that my cut/paste was incomplete;

Re: Towards Python 2.6: Architecture:all & XS-P-V:current packages

2010-02-22 Thread Yaroslav Halchenko
On Sat, 20 Feb 2010, Piotr Ożarowski wrote: > > current, >= X.X, << X.X > > then add additional restrictions? > dh_py* do that... unless you hardcode Python version f.e. in shebang hm... $> acshow impressive | grep -e Version -e Depends Version: 0.10.2r-5 Depends: python (>= 2.4), python-suppor

Re: Towards Python 2.6: Architecture:all & XS-P-V:current packages

2010-02-20 Thread Piotr Ożarowski
[Yaroslav Halchenko, 2010-02-20] > uploaded impressive... > > suggested solution to use > XS-Python-Version: all > or > XS-Python-Version: >= version > > seems to treat the symptom since 'current' is still valid description > and makes sense imho what would be a side-effect, if dh_py* get >

Re: Towards Python 2.6: Architecture:all & XS-P-V:current packages

2010-02-19 Thread Yaroslav Halchenko
uploaded impressive... suggested solution to use XS-Python-Version: all or XS-Python-Version: >= version seems to treat the symptom since 'current' is still valid description and makes sense imho what would be a side-effect, if dh_py* get adjusted not to impose strict version dependency (i.

Re: Towards Python 2.6: Architecture:all & XS-P-V:current packages

2010-02-19 Thread Piotr Ożarowski
[Ludovico Cavedon, 2010-02-19] > Is there any other way to byte-compile only for the default python version? yes there is: use private directory (--install-lib=/usr/share/foo) -- Piotr Ożarowski Debian GNU/Linux Developer www.ozarowski.pl www.griffith.cc

Re: Towards Python 2.6: Architecture:all & XS-P-V:current packages

2010-02-19 Thread Ludovico Cavedon
On Fri, Feb 19, 2010 at 10:43 AM, Jakub Wilk wrote: > 14 packages in the archive have ‘XS-Python-Version: current’ field and build > ‘Architure: all’ binary packages containing Python modules. This is bad, > because such packages currently depend on ‘python (<< 2.6)’ (for no good > reason), thus t

Re: Towards Python 2.6: Architecture:all & XS-P-V:current packages

2010-02-19 Thread Sandro Tosi
On Fri, Feb 19, 2010 at 19:43, Jakub Wilk wrote: > Hello, > > 14 packages in the archive have ‘XS-Python-Version: current’ field and build > ‘Architure: all’ binary packages containing Python modules. This is bad, > because such packages currently depend on ‘python (<< 2.6)’ (for no good > reason)