Re: Maintainers, porters, and burden of porting

2011-09-10 Thread Kurt Roeckx
On Sat, Sep 10, 2011 at 05:50:29PM +, brian m. carlson wrote: > On Sat, Sep 10, 2011 at 01:27:01PM +, Felipe Sateler wrote: > > On Thu, 08 Sep 2011 19:34:41 +0200, Andreas Barth wrote: > > > I disagree with "let's first remove things". If a package like ruby > > > doesn't build on sparc thi

Re: Maintainers, porters, and burden of porting

2011-09-10 Thread Wouter Verhelst
On Sat, Sep 10, 2011 at 03:33:06PM +0200, Kurt Roeckx wrote: > On Thu, Sep 08, 2011 at 07:34:41PM +0200, Andreas Barth wrote: > > > > > - Being able to judge whether the maintainers have done their part in > > > reaching out to porters is a requisite for the above. And to do so, we > > > reall

Re: Maintainers, porters, and burden of porting

2011-09-10 Thread brian m. carlson
On Sat, Sep 10, 2011 at 01:27:01PM +, Felipe Sateler wrote: > On Thu, 08 Sep 2011 19:34:41 +0200, Andreas Barth wrote: > > I disagree with "let's first remove things". If a package like ruby > > doesn't build on sparc this bug report is RC exactly as long as sparc is > > a release arch. The rel

Bug#641131: ITP: gst-debug-viewer -- GStreamer Debug Viewer

2011-09-10 Thread Andrzej Bieniek
Package: wnpp Severity: wishlist Owner: Andrzej Bieniek * Package name: gst-debug-viewer Version : Not released yet Upstream Author : René Stadler * URL : http://cgit.freedesktop.org/~cymacs/gst-debug-viewer/ * License : GPL Programming Lang: Python Descr

Re: Maintainers, porters, and burden of porting

2011-09-10 Thread Kurt Roeckx
On Thu, Sep 08, 2011 at 07:34:41PM +0200, Andreas Barth wrote: > > > - Being able to judge whether the maintainers have done their part in > > reaching out to porters is a requisite for the above. And to do so, we > > really need more visibility of those exchanges. According to devref > > [1

Re: Maintainers, porters, and burden of porting

2011-09-10 Thread Felipe Sateler
On Thu, 08 Sep 2011 19:34:41 +0200, Andreas Barth wrote: > * Stefano Zacchiroli (z...@debian.org) [110908 19:22]: >> Hopefully, not having $pkg on $arch would raise the visibility of the >> issue and attract attention to fix the issue. In the meantime, the >> fact that $pkg is not on $arch