Bug 789383 - pkcon advice incorrect
Summary: pkcon advice incorrect
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: abrt
Version: 18
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: abrt
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 835472 (view as bug list)
Depends On:
Blocks: ABRTF18
TreeView+ depends on / blocked
 
Reported: 2012-02-10 16:22 UTC by Neal Becker
Modified: 2012-12-20 15:44 UTC (History)
12 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-12-20 15:44:16 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Neal Becker 2012-02-10 16:22:45 UTC
Description of problem:

Abrt found a new update which fix your problem. Please run before submitting bug: pkcon update --repo-enable=fedora --repo-repo=updates-testing imsettings-1.2.8-1.fc16. Do you want to continue with reporting bug?

How nice!  But it doesn't work:

sudo pkcon update --repo-enable=fedora --repo-repo=updates-testing imsettings-1.2.8-1.fc16
[sudo] password for nbecker: 
Failed to parse command line: Unknown option --repo-enable=fedora


Version-Release number of selected component (if applicable):


How reproducible:


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


Expected results:


Additional info:

Comment 1 Toby Haynes 2012-05-24 19:25:07 UTC
Also seen in Fedora 17.


Searching for updates
Abrt found a new update which fix your problem. Please run before submitting bug: pkcon update --repo-enable=fedora --repo-repo=updates-testing tracker-0.14.1-1.fc17. Do you want to continue with reporting bug? NO
(exited with 1)


One possible correct command (there may be others)

yum update --enablerepo=fedora --enablerepo=updates-testing tracker-0.14.1-1.fc17


While someone is resolving this, they should fix the grammar for the rest of the statement:

Replace:
Abrt found a new update which fix your problem.
With:
Abrt found a new update which should fix your problem.

Comment 2 Nikola Pajkovsky 2012-05-25 07:22:36 UTC
Working on proper PackageKit integration right now.

Comment 3 Penelope Fudd 2012-08-22 17:36:12 UTC
This bug is still present in abrt-2.0.10-4.fc17.i686

Comment 4 Jiri Moskovcak 2012-09-18 10:56:11 UTC
*** Bug 835472 has been marked as a duplicate of this bug. ***

Comment 5 Denys Vlasenko 2012-09-20 14:06:23 UTC
Changing the suggested command to:

yum update --enablerepo=fedora --enablerepo=updates-testing PKG1 PKG2...

Comment 6 Denys Vlasenko 2012-09-20 14:09:05 UTC
Fixed in git:

commit fafc4d3ac0ae6c2bfef6543a245d0a2ee9df2866
Author: Denys Vlasenko <vda.linux>
Date:   Thu Sep 20 16:05:35 2012 +0200

    bodhi: fix suggested pkg update command, fix version comparison

Comment 7 Fedora Update System 2012-09-24 14:31:25 UTC
abrt-2.0.13-1.fc18,libreport-2.0.14-1.fc18,btparser-0.19-1.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/abrt-2.0.13-1.fc18,libreport-2.0.14-1.fc18,btparser-0.19-1.fc18

Comment 8 Fedora Update System 2012-09-24 20:03:35 UTC
Package abrt-2.0.13-1.fc18, libreport-2.0.14-1.fc18, btparser-0.19-1.fc18:
* should fix your issue,
* was pushed to the Fedora 18 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.13-1.fc18 libreport-2.0.14-1.fc18 btparser-0.19-1.fc18'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2012-14679/abrt-2.0.13-1.fc18,libreport-2.0.14-1.fc18,btparser-0.19-1.fc18
then log in and leave karma (feedback).

Comment 9 Fedora Update System 2012-09-25 10:05:57 UTC
abrt-2.0.13-1.fc17,libreport-2.0.14-1.fc17,btparser-0.19-1.fc17 has been submitted as an update for Fedora 17.
https://admin.fedoraproject.org/updates/abrt-2.0.13-1.fc17,libreport-2.0.14-1.fc17,btparser-0.19-1.fc17

Comment 10 Fedora Update System 2012-12-20 15:44:19 UTC
abrt-2.0.13-1.fc18, libreport-2.0.14-1.fc18, btparser-0.19-1.fc18 has been pushed to the Fedora 18 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.