Bug 1025172 - unable to yum install "abrt-plugin-runapp""abrt-plugin-mailx"
Summary: unable to yum install "abrt-plugin-runapp""abrt-plugin-mailx"
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-abrt
Version: 20
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jakub Filak
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-31 07:10 UTC by lnie
Modified: 2016-12-01 00:45 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-10-31 08:41:02 UTC
Type: Bug


Attachments (Terms of Use)

Description lnie 2013-10-31 07:10:55 UTC
Description of problem:

 try to install abrt-plugin-runapp and abrt-plugin-mailx 
  by running the command "yum install abrt-plugin-runapp abrt-plugin-mailx"
  But got the message "...Nothing to do"
Version-Release number of selected component (if applicable):
 f20-Beta-TC6

How reproducible:
always

Steps to Reproduce:
1.Do a fresh install with vm
2.run the command yum install abrt-plugin-runapp abrt-plugin-mailx
3.

Actual results:


Expected results:


Additional info:

Comment 1 Jakub Filak 2013-10-31 08:21:03 UTC
Thank you for the report!

abrt-plugin-runapp is not available because the plugin was dropped 2 years ago in abrt-1.1.14

abrt-plugin-mailx has been renamed to libreport-plugin-mailx

Why do you want to install these packages? Are these plugins mentioned in ABRT documentation?

Comment 2 lnie 2013-10-31 08:41:02 UTC
I were doing the update test 
https://admin.fedoraproject.org/updates/FEDORA-2013-20254/gnome-abrt-0.3.3-1.fc20,abrt-2.1.9-1.fc20,libreport-2.1.9-1.fc20,satyr-0.11-1.fc20?_csrf_token=967a99c9334f7ec2448cc02bea8ea263164583ce

and Test case https://fedoraproject.org/wiki/QA:Testcase_ABRT_Actions_and_Reporters in that page 
say I should install that two packages.
It seems that the test case need update

Thanks for your information:-)


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