Bug 1269219 - Unable to resolve dependencies while updating
Summary: Unable to resolve dependencies while updating
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: abrt
Version: 21
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: abrt
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 1269267 1269710 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-10-06 17:02 UTC by alex
Modified: 2015-11-05 17:55 UTC (History)
12 users (show)

Fixed In Version: libreport-2.3.0-9.fc21
Clone Of:
Environment:
Last Closed: 2015-10-09 11:13:52 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description alex 2015-10-06 17:02:22 UTC
Description of problem:


Version-Release number of selected component (if applicable):2.3.0-8fc21 (64bit)


How reproducible:


Steps to Reproduce:
1.yumex updating
2.checking dependencies
3.unable to resolve depeden.

Actual results:


Expected results:


Additional info:

Comment 1 Matej Habrnal 2015-10-07 07:09:07 UTC
Thank you for the bug report!

The required libreport-2.3.0-9.fc21 is pending in bodhi updating process [1] and waiting to reach 3 karmas.

After the update gets 3 karmas, the package will be pushed to the stable repository and this fix the dependency bug.

Could you please test the libreport-2.3.0-9.fc21 and add the karma [1], if everything works right?

[1] https://bodhi.fedoraproject.org/updates/FEDORA-2015-14405

Comment 2 Matej Habrnal 2015-10-07 07:16:08 UTC
*** Bug 1269267 has been marked as a duplicate of this bug. ***

Comment 3 Matej Habrnal 2015-10-08 06:25:54 UTC
*** Bug 1269710 has been marked as a duplicate of this bug. ***

Comment 4 thierry.laurion 2015-10-08 12:39:57 UTC
Hi,

That testing package has 5 karma.

Will it go stable anytime soon?

Thierry

Comment 5 Matej Habrnal 2015-10-09 11:13:52 UTC
libreport-2.3.0-9.fc21 in the stable now.
See https://bodhi.fedoraproject.org/updates/libreport-2.3.0-9.fc21 .

Comment 6 alex 2015-11-05 17:55:20 UTC
Tested and it works fine


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