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.e. like python (>=2.5), python (<<2.6) now for 'current') but simply "python", and only if it is current, >= X.X, << X.X then add additional restrictions? On Fri, 19 Feb 2010, Sandro Tosi wrote: > On Fri, Feb 19, 2010 at 19:43, Jakub Wilk <[email protected]> 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), thus they'll need sourceful uploads after switching default version > > of Python. > > I am looking for a volunteer to do bug filing. > I'm gonna file them. Thanks for your analysis! > Cheers, -- .-. =------------------------------ /v\ ----------------------------= Keep in touch // \\ (yoh@|www.)onerussian.com Yaroslav Halchenko /( )\ ICQ#: 60653192 Linux User ^^-^^ [175555] -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
