Re: Apport for Debian

2013-05-17 Thread Raphael Hertzog
Hi, On Fri, 17 May 2013, Ritesh Raj Sarraf wrote: > That is a good point. Thanks Thomas. We could submit apport reports with > the tag "Apport" and instruct reportbug to forward the report to > "pack...@qa.debian.org". > > This way we avoid the flood of bug reports in general while at the same >

Re: Apport for Debian

2013-05-16 Thread Ritesh Raj Sarraf
On Monday 13 May 2013 11:26 PM, Thomas Goirand wrote: > On 05/13/2013 03:06 PM, Ritesh Raj Sarraf wrote: >> > 1) Duplicate bug reports: There are high possibilities that we could see >> > a sudden increase in the number of bug reports, many duplicates. This is >> > something I'm not sure how we wan

Re: Apport for Debian

2013-05-14 Thread Josselin Mouette
Le mardi 14 mai 2013 à 00:40 +0200, Josselin Mouette a écrit : > > - adjust the buildds to begin generating debug symbols packages > >automatically - perhaps reusing pkgbinarymangler from Ubuntu, or perhaps > >using it as a reference > > Patches to debhelper already exist, to generate on

Re: Apport for Debian

2013-05-13 Thread Josselin Mouette
Le lundi 13 mai 2013 à 12:34 -0500, Steve Langasek a écrit : > - implement the changes necessary to ensure all binary packages in the >archive are built on the buildds, not on developers' systems[1] This is not even necessary. > - deploy centralized infrastructure, outside of the main arch

Re: Apport for Debian

2013-05-13 Thread Ritesh Raj Sarraf
On Monday 13 May 2013 11:04 PM, Steve Langasek wrote: > From past discussions, I think there's a very clear consensus in favor of > doing this; it's now a SMOP. > > The requirements are, in order: > > - implement the changes necessary to ensure all binary packages in the >archive are built on

Re: Apport for Debian

2013-05-13 Thread Thomas Goirand
On 05/13/2013 03:06 PM, Ritesh Raj Sarraf wrote: > 1) Duplicate bug reports: There are high possibilities that we could see > a sudden increase in the number of bug reports, many duplicates. This is > something I'm not sure how we want to evaluate. We could give apport a > try, and leave it to the

Re: Apport for Debian

2013-05-13 Thread Steve Langasek
On Mon, May 13, 2013 at 05:56:25PM +0100, Wookey wrote: > +++ Steve Langasek [2013-05-13 11:22 -0500]: > > On Mon, May 13, 2013 at 06:21:24PM +0530, Ritesh Raj Sarraf wrote: > > > On Monday 13 May 2013 03:55 PM, Arno Töll wrote: > > > > note that, unlike Ubuntu we do not provide automated debug pac

Re: Apport for Debian

2013-05-13 Thread Wookey
+++ Steve Langasek [2013-05-13 11:22 -0500]: > On Mon, May 13, 2013 at 06:21:24PM +0530, Ritesh Raj Sarraf wrote: > > On Monday 13 May 2013 03:55 PM, Arno Töll wrote: > > > note that, unlike Ubuntu we do not provide automated debug packages. > > > Hence many crash reports aren't usable at all when

Re: Apport for Debian

2013-05-13 Thread Steve Langasek
On Mon, May 13, 2013 at 06:21:24PM +0530, Ritesh Raj Sarraf wrote: > On Monday 13 May 2013 03:55 PM, Arno Töll wrote: > > note that, unlike Ubuntu we do not provide automated debug packages. > > Hence many crash reports aren't usable at all when they are generated on > > Debian systems. > This cou

Re: Apport for Debian

2013-05-13 Thread Ritesh Raj Sarraf
On Monday 13 May 2013 03:22 PM, Paul Wise wrote: > Another issue is privacy; backtraces may contain private information > that should not leave the system and there is no automated way to > determine that. How does Ubuntu deal with that? Unfortunately, there's no intelligence in apport client to d

Re: Apport for Debian

2013-05-13 Thread Ritesh Raj Sarraf
On Monday 13 May 2013 03:55 PM, Arno Töll wrote: > note that, unlike Ubuntu we do not provide automated debug packages. > Hence many crash reports aren't usable at all when they are generated on > Debian systems. This could be a start. It could help users request debug packages from package mainta

Re: Apport for Debian

2013-05-13 Thread Arno Töll
Hi, On 13.05.2013 09:06, Ritesh Raj Sarraf wrote: > Apport [1] is an automated crash reporting tool. It could also be used > as a bug reporting tool, but there are certain features missing (a text > input to add user description), not making it a candidate for reporting > bugs. For crashes, apport

Re: Apport for Debian

2013-05-13 Thread Benjamin Drung
Am Montag, den 13.05.2013, 12:00 +0200 schrieb Tollef Fog Heen: > ]] Paul Wise > > > Another issue is privacy; backtraces may contain private information > > that should not leave the system and there is no automated way to > > determine that. How does Ubuntu deal with that? > > IIRC, they mark

Re: Apport for Debian

2013-05-13 Thread Tollef Fog Heen
]] Paul Wise > Another issue is privacy; backtraces may contain private information > that should not leave the system and there is no automated way to > determine that. How does Ubuntu deal with that? IIRC, they mark the bugs as private on submission, then they have a server-side process that p

Re: Apport for Debian

2013-05-13 Thread Paul Wise
On Mon, May 13, 2013 at 3:06 PM, Ritesh Raj Sarraf wrote: > Apport for Debian currently resides in experimental with a whopping > popcon stat of 11000+ installs. In the past, I have blogged [2] about > apport's state in Debian, where I received some constructive feedback. The po

Apport for Debian

2013-05-13 Thread Ritesh Raj Sarraf
pport CrashDB engine for Debian, which drafts the reports, discards the binary crash data (that can be huge), and sends it as an email to the Debian BTS. It lacks the feature to search for duplicate bug reports (like reportbug does, if online) on the BTS though. Apport for Debian currently resid