Hello everyone,
I want to briefly introduce myself. I am a Red Hat employee working on ABRT[1]. We have recently added support for CentOS on the ABRT server[2] and we would like continue in these integration efforts.
First of all, I want to submit a pair of patches improving ABRT's UX on CentOS: - do not offer users to report to Red Hat Portal - offer users to send an email to upstream - stop wasting of resources by running sos, because its output is useless for CentOS users
In the near future, we would like to integrate ABRT with CentOS Bug Tracker in the same way as ABRT integrates with Red Hat Bugzilla[3]. We are done with the analysis phase[4] and, now, we are working on a testsuite[5].
Unfortunately, MantisBT misses more advanced searching what prevents us from implementing a tool similar to one we have for Bugzilla. At least we need to search by DUPHASH (an unique identifier of a crash, something like tag).
Would you be willing to run a MantisBT plugin adding the things we need, if we develop it?
Best regards, Jakub http://wiki.centos.org/JakubFilak
1: https://github.com/abrt 2: https://abrt.fedoraproject.org/ 3: https://github.com/abrt/libreport/issues/272 4: https://github.com/abrt/libreport/wiki/MantisBT 5: https://github.com/abrt/abrt/tree/reporter-mantisbt
On 11/18/2014 07:09 AM, Jakub Filak wrote:
Hello everyone,
I want to briefly introduce myself. I am a Red Hat employee working on ABRT[1]. We have recently added support for CentOS on the ABRT server[2] and we would like continue in these integration efforts.
Welcome.
First of all, I want to submit a pair of patches improving ABRT's UX on CentOS:
- do not offer users to report to Red Hat Portal
- offer users to send an email to upstream
- stop wasting of resources by running sos, because its output is useless for CentOS users
Sounds good so far.
In the near future, we would like to integrate ABRT with CentOS Bug Tracker in the same way as ABRT integrates with Red Hat Bugzilla[3]. We are done with the analysis phase[4] and, now, we are working on a testsuite[5].
Unfortunately, MantisBT misses more advanced searching what prevents us from implementing a tool similar to one we have for Bugzilla. At least we need to search by DUPHASH (an unique identifier of a crash, something like tag).
Indeed. It's quite basic, which has been good for us so far, and the simplicity was key early on.
Would you be willing to run a MantisBT plugin adding the things we need, if we develop it?
I'd already been looking at updating our mantis setup and adding some useful plugins. This sounds like a good thing, and I'm certainly willing to give it a shot.
I wonder if we should stand up a 'beta' site for demo/testing, copied from bugs.centos to see what people think.
Thoughts from others?
Hi Jim,
Am 18.11.2014 um 20:03 schrieb Jim Perrin:
On 11/18/2014 07:09 AM, Jakub Filak wrote:
Hello everyone,
I want to briefly introduce myself. I am a Red Hat employee working on ABRT[1]. We have recently added support for CentOS on the ABRT server[2] and we would like continue in these integration efforts.
Welcome.
Would you be willing to run a MantisBT plugin adding the things we need, if we develop it?
I'd already been looking at updating our mantis setup and adding some useful plugins. This sounds like a good thing, and I'm certainly willing to give it a shot.
I wonder if we should stand up a 'beta' site for demo/testing, copied from bugs.centos to see what people think.
Thoughts from others?
Sounds good. I think doing it on a copy of bugs.c.o is a good idea. And i think any required changes can be rather easily pushed got git.c.o for the sources.
cheers Christoph
On 11/18/2014 07:09 AM, Jakub Filak wrote:
Would you be willing to run a MantisBT plugin adding the things we need, if we develop it?
We have a testing instance set aside now populated with backup data. When the plugin is ready, please send it along and I'll drop it in the test instance so that we can kick it around.
On Thu, 2014-11-20 at 14:51 -0600, Jim Perrin wrote:
On 11/18/2014 07:09 AM, Jakub Filak wrote:
Would you be willing to run a MantisBT plugin adding the things we need, if we develop it?
We have a testing instance set aside now populated with backup data. When the plugin is ready, please send it along and I'll drop it in the test instance so that we can kick it around.
Fabulous. It was really quick. Thank you! We will try to provide the plugin ASAP.
MantisBT is something completely new to us, so we need to spend some time to figure out what we actually need:
https://github.com/abrt/libreport/wiki/MantisBT-plugin
Regards, Jakub
On Tue, 2014-11-18 at 13:03 -0600, Jim Perrin wrote:
On 11/18/2014 07:09 AM, Jakub Filak wrote:
First of all, I want to submit a pair of patches improving ABRT's UX on CentOS:
- do not offer users to report to Red Hat Portal
- offer users to send an email to upstream
- stop wasting of resources by running sos, because its output is useless for CentOS users
Sounds good so far.
I created these bug reports and attached patches to them today:
* http://bugs.centos.org/view.php?id=7913 - turn sosreport off
* http://bugs.centos.org/view.php?id=7914 - abrt uses libreport to send crash reports - 'abrt-cli report' and 'gnome-abrt -> Report' should offer these options: 1 Send the problem data via email 2 Upload the problem data to a server 3 Submit anonymous crash static data 4 Export the problem data information to a text file
Please let me know if there is something I should explain or document more clearly.
Regards, Jakub
On 11/21/2014 08:38 AM, Jakub Filak wrote:
I created these bug reports and attached patches to them today:
http://bugs.centos.org/view.php?id=7913
- turn sosreport off
http://bugs.centos.org/view.php?id=7914
- abrt uses libreport to send crash reports
- 'abrt-cli report' and 'gnome-abrt -> Report' should offer these
options: 1 Send the problem data via email 2 Upload the problem data to a server 3 Submit anonymous crash static data 4 Export the problem data information to a text file
Interestingly, the libreport sources (both the original and with the patch) seem to not build against 7 with updates. We'll continue to test and see what we find.
Please let me know if there is something I should explain or document more clearly.
On Fri, 2014-11-21 at 09:10 -0600, Jim Perrin wrote:
On 11/21/2014 08:38 AM, Jakub Filak wrote:
I created these bug reports and attached patches to them today:
http://bugs.centos.org/view.php?id=7913
- turn sosreport off
http://bugs.centos.org/view.php?id=7914
- abrt uses libreport to send crash reports
- 'abrt-cli report' and 'gnome-abrt -> Report' should offer these
options: 1 Send the problem data via email 2 Upload the problem data to a server 3 Submit anonymous crash static data 4 Export the problem data information to a text file
Interestingly, the libreport sources (both the original and with the patch) seem to not build against 7 with updates. We'll continue to test and see what we find.
This commit fixes the build with json-c-0.11-4.el7.x86_64: https://github.com/abrt/libreport/commit/712ca27bdbbe4f38550d5431b400dfa9e70...
I tested my patches with json-c-0.11-3.el7.x86_64.
Should I add that commit to my libreport patch?
On 11/21/2014 09:47 AM, Jakub Filak wrote:
On Fri, 2014-11-21 at 09:10 -0600, Jim Perrin wrote:
On 11/21/2014 08:38 AM, Jakub Filak wrote:
I created these bug reports and attached patches to them today:
http://bugs.centos.org/view.php?id=7913
- turn sosreport off
http://bugs.centos.org/view.php?id=7914
- abrt uses libreport to send crash reports
- 'abrt-cli report' and 'gnome-abrt -> Report' should offer these
options: 1 Send the problem data via email 2 Upload the problem data to a server 3 Submit anonymous crash static data 4 Export the problem data information to a text file
Interestingly, the libreport sources (both the original and with the patch) seem to not build against 7 with updates. We'll continue to test and see what we find.
This commit fixes the build with json-c-0.11-4.el7.x86_64: https://github.com/abrt/libreport/commit/712ca27bdbbe4f38550d5431b400dfa9e70...
I tested my patches with json-c-0.11-3.el7.x86_64.
Should I add that commit to my libreport patch?
We should be able to rebuild with -3. I'm assuming libreport will have an update in the future to build against -4, so I'd rather not have patches potentially conflicting later on.
On 11/21/2014 10:42 AM, Jim Perrin wrote:
We should be able to rebuild with -3. I'm assuming libreport will have an update in the future to build against -4, so I'd rather not have patches potentially conflicting later on.
Following up on this, Johnny and I were able to get this built and tested. The only thing I noticed (which seems unrelated to your patch) is that /etc/libreport/events/report_Bugzilla.conf still references bugzilla.redhat.com
Would it break things to point that at bugs.centos? Are there hooks specific to bugzilla that might use?
On Fri, 2014-11-21 at 15:54 -0600, Jim Perrin wrote:
On 11/21/2014 10:42 AM, Jim Perrin wrote:
We should be able to rebuild with -3. I'm assuming libreport will have an update in the future to build against -4, so I'd rather not have patches potentially conflicting later on.
Following up on this, Johnny and I were able to get this built and tested. The only thing I noticed (which seems unrelated to your patch) is that /etc/libreport/events/report_Bugzilla.conf still references bugzilla.redhat.com
Would it break things to point that at bugs.centos? Are there hooks specific to bugzilla that might use?
There is no communication with Bugzilla initiated by ABRT on CentOS 7, unless user installs libreport-plugin-bugzilla package and explicitly starts reporting to Bugzilla.
The following file contains a couple of bugzilla.redhat.com URLs too: /usr/share/libreport/events/report_Bugzilla.xml
Jakub
On Friday 21 of November 2014 07:03:13 Jakub Filak wrote:
On Thu, 2014-11-20 at 14:51 -0600, Jim Perrin wrote:
On 11/18/2014 07:09 AM, Jakub Filak wrote:
Would you be willing to run a MantisBT plugin adding the things we need, if we develop it?
We have a testing instance set aside now populated with backup data. When the plugin is ready, please send it along and I'll drop it in the test instance so that we can kick it around.
Fabulous. It was really quick. Thank you! We will try to provide the plugin ASAP.
MantisBT is something completely new to us, so we need to spend some time to figure out what we actually need:
I'm happy to announce that we've finished our work on adding support for CentOS Bug Tracker to ABRT.
The final solution requires a not yet released version of MantisBT as we've decided to enhance MantisBT instead of developing a plugin (it was impossible to develop such a plugin). We've written a short installation documentation available at: https://github.com/abrt/libreport/wiki/Reporting-to-CentOSBT#installing-the-...
The patches adding support for MantisBT resp. CentOS Bug Tracker have landed in the upstream master but we've also back-ported them to RHEL-7 and created a COPR repository with the updated packages: https://copr.fedoraproject.org/coprs/mhabrnal/abrt-centos/
yum (upgrade|update) will install three new packages: * libreport-plugin-mantisbt - libreport plugin for communication with MantisBT * libreport-centos - configuration required for CentOS Bug Tracker * abrt-retrace-client - allows users to generate backtrace from coredump without the need to download debuginfo
After upgrading you have to do some changes to your setup that are described here: https://github.com/abrt/libreport/wiki/Reporting-to-CentOSBT#abrt-centos
Finally, you have to set the CentOS Bug Tracker URL to the testing instance. (Unfortunately, I am not able to find that URL in my mailbox).
All the necessary information required for enabling reporting to CentOS Bug Tracker are available at: https://github.com/abrt/libreport/wiki/Reporting-to-CentOSBT
We are looking forward to receive your feedback.
Regards, Jakub Filak The ABRT team
On 02/04/2015 10:20 AM, Jakub Filak wrote:
All the necessary information required for enabling reporting to CentOS Bug Tracker are available at:
https://github.com/abrt/libreport/wiki/Reporting-to-CentOSBT
fantastic work! thanks
-
Christoph Galuschka -
Jakub Filak -
Jim Perrin -
Karanbir Singh