Bug 732876 - Hash did not find dup between 731251 and 732840
Summary: Hash did not find dup between 731251 and 732840
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: libreport
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Nikola Pajkovsky
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: ABRTF17
TreeView+ depends on / blocked
 
Reported: 2011-08-24 02:46 UTC by Daniel Walsh
Modified: 2014-02-02 22:15 UTC (History)
7 users (show)

Fixed In Version: abrt-2.0.7-2.fc16
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-12-16 19:53:48 UTC


Attachments (Terms of Use)

Description Daniel Walsh 2011-08-24 02:46:32 UTC
Description of problem:

https://bugzilla.redhat.com/show_bug.cgi?id=732840
https://bugzilla.redhat.com/show_bug.cgi?id=731251

Should have found dups, hash matches.

Comment 1 Jiri Moskovcak 2011-12-01 08:29:42 UTC
We found the problem and the fix is ready a new update should be rolled before the end of the week..

Comment 2 Fedora Update System 2011-12-10 11:06:13 UTC
abrt-2.0.7-2.fc16 has been submitted as an update for Fedora 16.
https://admin.fedoraproject.org/updates/abrt-2.0.7-2.fc16

Comment 3 Fedora Update System 2011-12-11 21:57:39 UTC
Package abrt-2.0.7-2.fc16, libreport-2.0.8-3.fc16:
* should fix your issue,
* was pushed to the Fedora 16 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.7-2.fc16 libreport-2.0.8-3.fc16'
as soon as you are able to, then reboot.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2011-16990/libreport-2.0.8-3.fc16,abrt-2.0.7-2.fc16
then log in and leave karma (feedback).

Comment 4 Fedora Update System 2011-12-16 19:53:48 UTC
abrt-2.0.7-2.fc16, libreport-2.0.8-3.fc16 has been pushed to the Fedora 16 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.