Bug 825116 - Crash in F18 mock cannot be retraced
Summary: Crash in F18 mock cannot be retraced
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: abrt
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: abrt
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-05-25 07:09 UTC by Vít Ondruch
Modified: 2012-08-30 00:56 UTC (History)
8 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-08-30 00:56:35 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Vít Ondruch 2012-05-25 07:09:15 UTC
Description of problem:
The segfault during build of JRuby (rhbz#824897) in mock for F18 was caught. However, retrace server denies to provide the backtrace with the following message:

Retrace failed. Try again later and if the problem persists report this issue please.
Analyzing crash data Error
Package 'java-1.7.0-openjdk-1.7.0.3-2.1.fc18.6.x86_64' was not recognized. Is it a part of official Fedora release 17 (Beefy Miracle) repositories?

My host system is F17.

Version-Release number of selected component (if applicable):
$ rpm -q abrt
abrt-2.0.10-3.fc17.x86_64


How reproducible:
Always


Steps to Reproduce:
1.
2.
3.
  
Actual results:
Retracing fails


Expected results:
Retracing succeeds.


Additional info:

Comment 1 Vít Ondruch 2012-05-25 07:28:40 UTC
Hm, trying to build the same in F17 mock, I got different error:

Retrace job failed
Retrace failed. Try again later and if the problem persists report this issue please.
Analyzing crash data OK
Initializing virtual root OK
Generating backtrace Error
The appropriate package set could not be installed

Comment 2 Michal Toman 2012-06-07 14:47:10 UTC
Fixed in git.

Comment 3 Fedora Update System 2012-08-03 10:26:56 UTC
abrt-2.0.11-1.fc17,libreport-2.0.11-1.fc17,btparser-0.18-2.fc17 has been submitted as an update for Fedora 17.
https://admin.fedoraproject.org/updates/abrt-2.0.11-1.fc17,libreport-2.0.11-1.fc17,btparser-0.18-2.fc17

Comment 4 Fedora Update System 2012-08-05 21:33:58 UTC
Package abrt-2.0.11-1.fc17, btparser-0.18-2.fc17, libreport-2.0.12-1.fc17:
* should fix your issue,
* was pushed to the Fedora 17 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing abrt-2.0.11-1.fc17 btparser-0.18-2.fc17 libreport-2.0.12-1.fc17'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2012-11529/abrt-2.0.11-1.fc17,libreport-2.0.12-1.fc17,btparser-0.18-2.fc17
then log in and leave karma (feedback).

Comment 5 Fedora Update System 2012-08-09 23:09:15 UTC
Package libreport-2.0.12-2.fc17, abrt-2.0.11-1.fc17, btparser-0.18-2.fc17:
* should fix your issue,
* was pushed to the Fedora 17 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing libreport-2.0.12-2.fc17 abrt-2.0.11-1.fc17 btparser-0.18-2.fc17'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2012-11529/abrt-2.0.11-1.fc17,libreport-2.0.12-2.fc17,btparser-0.18-2.fc17
then log in and leave karma (feedback).

Comment 6 Fedora Update System 2012-08-23 23:27:44 UTC
Package abrt-2.0.12-1.fc17, libreport-2.0.13-1.fc17, btparser-0.18-2.fc17:
* should fix your issue,
* was pushed to the Fedora 17 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing abrt-2.0.12-1.fc17 libreport-2.0.13-1.fc17 btparser-0.18-2.fc17'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2012-11529/abrt-2.0.12-1.fc17,libreport-2.0.13-1.fc17,btparser-0.18-2.fc17
then log in and leave karma (feedback).

Comment 7 Fedora Update System 2012-08-30 00:56:35 UTC
abrt-2.0.12-1.fc17, libreport-2.0.13-2.fc17, btparser-0.18-2.fc17 has been pushed to the Fedora 17 stable repository.  If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.