Upload debug-like-info to Mozilla servers every update

[Jan Horak]

Hi,
we would like to cooperate with Mozilla on reporting crashes into their 
bug reporting tool (http://crash-stats.mozilla.com/). To do so it is 
required to upload debug-like-info to specified location on remote 
server. This task should be done the same time the xulrunner, firefox or 
thunderbird package is going to released. I would like to know if there 
is some way to do it right now or if there is any way how can I 
participate. For further reference the details of how it is done is 
located here:

https://bugzilla.mozilla.org/show_bug.cgi?id=447771#c5

Thanks a lot for your comments and ideas.
-- 
Jan Horak

[Colin Walters]

On Fri, Sep 18, 2009 at 1:07 PM, Jan Horak <jhorak(a)redhat.com&gt; wrote:
>  Hi,
>  we would like to cooperate with Mozilla on reporting crashes into their bug
>  reporting tool (http://crash-stats.mozilla.com/). To do so it is required to
>  upload debug-like-info to specified location on remote server. This task
>  should be done the same time the xulrunner, firefox or thunderbird package
>  is going to released. I would like to know if there is some way to do it
>  right now or if there is any way how can I participate. For further
>  reference the details of how it is done is located here: 
We could do that, but a more ideal world would be where our ABRT
system can give them as useful and reliable data as their usage of
breakpad on Windows and OS X does.  There are multiple components
here, the biggest of which is that we need to avoid requiring a
Bugzilla account for crash submissions, and we need to make it about
one click.   Once we have the data reliably, Mozilla could pull
crashes from our system into theirs, say a cron job which just does:
wget http://crashes.fedoraproject.org/package/mozilla/20091018.tar.gz

And Fedora really needs an equivalent UI to crash-stats.mozilla.com
but that's another topic.

[Jan Horak]

On 09/18/2009 05:22 PM, Colin Walters wrote:
>  We could do that, but a more ideal world would be where our ABRT
>  system can give them as useful and reliable data as their usage of
>  breakpad on Windows and OS X does.  There are multiple components
>  here, the biggest of which is that we need to avoid requiring a
>  Bugzilla account for crash submissions, and we need to make it about
>  one click.   Once we have the data reliably, Mozilla could pull
>  crashes from our system into theirs, say a cron job which just does:
>  wget http://crashes.fedoraproject.org/package/mozilla/20091018.tar.gz
>      
Mozilla prefers using their own system in this case. It has some pros, 
like user don't have to download debug packages (which is approx 80MB 
for each package). Building the symbols for Mozilla is also quite easy. 
They have everything prepared in their makefiles and their debug info is 
just one zip file. All we need is to put this zip file somewhere that 
mozilla could pull it (or we push it after package is released). This 
zip file should be left aside from regular rpm package (read unpublished).
-- 
Jan Horak

[Colin Walters]

On Wed, Oct 14, 2009 at 9:04 AM, Jan Horak <jhorak(a)redhat.com&gt; wrote:
>  Mozilla prefers using their own system in this case. It has some pros, like
>  user don't have to download debug packages (which is approx 80MB for each
>  package). Building the symbols for Mozilla is also quite easy. They have
>  everything prepared in their makefiles and their debug info is just one zip
>  file. All we need is to put this zip file somewhere that mozilla could pull
>  it (or we push it after package is released). This zip file should be left
>  aside from regular rpm package (read unpublished). 
In that case I'd just make the mozilla spec file to put the .zip in
the -debuginfo package.  Then their crash handling code just needs to
get the built RPM NVRA (it should probably be compiled in, but forking
a "rpm -q" could work I guess), and their server side can fairly
easily script a "wget
http://download.fedoraproject.org/.../mozilla-debuginfo-12345.rpm";.

[Jan Horak]

On 10/14/2009 03:40 PM, Colin Walters wrote:
>  On Wed, Oct 14, 2009 at 9:04 AM, Jan Horak<jhorak(a)redhat.com> 
> wrote:
>     
> >
> > Mozilla prefers using their own system in this case. It has some pros, like
> > user don't have to download debug packages (which is approx 80MB for each
> > package). Building the symbols for Mozilla is also quite easy. They have
> > everything prepared in their makefiles and their debug info is just one zip
> > file. All we need is to put this zip file somewhere that mozilla could pull
> > it (or we push it after package is released). This zip file should be left
> > aside from regular rpm package (read unpublished).
> >      
>  In that case I'd just make the mozilla spec file to put the .zip in
>  the -debuginfo package.  Then their crash handling code just needs to
>  get the built RPM NVRA (it should probably be compiled in, but forking
>  a "rpm -q" could work I guess), and their server side can fairly
>  easily script a "wget
>  http://download.fedoraproject.org/.../mozilla-debuginfo-12345.rpm";.
>
>      
After more discussion on Mozilla bugzilla the Mozilla would prefer to 
give us an account to their crash-stat system and let us upload the 
mentioned zip file after each released update. The scp is used to upload 
debug symbols. However this require storage of private key which 
shouldn't be exposed to public. Is there any way to launch such 
operation and also keep the private key unpublished? I can provide 
complete script which will extract zip file from rpm files and upload 
them to Mozilla by using scp.
-- 
Jan

[Colin Walters]

On Fri, Sep 18, 2009 at 1:07 PM, Jan Horak <jhorak(a)redhat.com&gt; wrote:
>  Hi,
>  we would like to cooperate with Mozilla on reporting crashes into their bug
>  reporting tool (http://crash-stats.mozilla.com/). To do so it is required to
>  upload debug-like-info to specified location on remote server. This task
>  should be done the same time the xulrunner, firefox or thunderbird package
>  is going to released. 
For this though couldn't the code live on the Mozilla server side?
They already have server side code AFAIK to pull in data from the
Windows symbol server which is conceptually equivalent.