Re: python-central NMU (python2.6 related)

2009-11-29 Thread Yaroslav Halchenko
Khm... sorry for a silly followup but an important thread seems to have stalled without resolution: unstable-ready-2.6 coming? Should Piotr adopt his stctop-related patch against 0.6.13 and NMU it again? Should anyone (besides Piotr) do that? Any objective factors why that patch should have not

Re: python-central NMU (python2.6 related)

2009-11-16 Thread Matthias Klose
Fyi, I replaced your NMU with my merge from Ubuntu, which already had these changes. I may have missed the indentation problems, please file separate bug reports for these. Matthias On 03.11.2009 16:07, Piotr Ożarowski wrote: Hi Matthias, You uploaded new python-central package that fixed

Re: python-central NMU (python2.6 related)

2009-11-16 Thread Piotr Ożarowski
[Matthias Klose, 2009-11-16] Fyi, I replaced your NMU with my merge from Ubuntu, which already had these changes. I may have missed the indentation problems, please file separate bug reports for these. srctop related lines were broken in Ubuntu, if you used Luca's merge then it's fine, though

Re: python-central NMU (python2.6 related)

2009-11-16 Thread Piotr Ożarowski
[Matthias Klose, 2009-11-16] Fyi, I replaced your NMU with my merge from Ubuntu, which already had these changes. I may have missed the indentation problems, please file separate bug reports for these. Indentation problems and typos were so obvious that I know now that you didn't even read my

Bug#547565: Info received (python-central NMU (python2.6 related))

2009-11-05 Thread Debian Bug Tracking System
Thank you for the additional information you have supplied regarding this Bug report. This is an automatically generated reply to let you know your message has been received. Your message is being forwarded to the package maintainers and other interested parties for their attention; they will

Re: python-central NMU (python2.6 related)

2009-11-05 Thread Piotr Ożarowski
[Piotr Ożarowski, 2009-11-05] attached patch uploaded to DELAYED/4 I actually used `dput ... -e 4` instead of `dput -e 4 ...` so it's already in unstable. Sorry about that. I didn't do it on purpose :-( -- Piotr Ożarowski Debian GNU/Linux Developer www.ozarowski.pl