Bug 839699 - pkcon update --repo-enable=fedora --repo-repo=updates-testing tracker-0.14.1-1.fc17 not work
Summary: pkcon update --repo-enable=fedora --repo-repo=updates-testing tracker-0.14.1-...
Keywords:
Status: CLOSED DUPLICATE of bug 835472
Alias: None
Product: Fedora
Classification: Fedora
Component: abrt
Version: 17
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: abrt
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 842560 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-07-12 15:00 UTC by Mikhail
Modified: 2012-08-09 21:18 UTC (History)
9 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-08-09 21:18:15 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
screenshot (135.18 KB, image/png)
2012-07-12 15:00 UTC, Mikhail
no flags Details

Description Mikhail 2012-07-12 15:00:43 UTC
Created attachment 597830 [details]
screenshot

Description of problem:
During the next send the error report window pops up stating that the update is already there, and ample in the console enter "pkcon update - repo-enable = fedora - repo-repo = updates-testing tracker-0.14.1-1.fc17"
But the present command is not working.

Please see screenshot.

Comment 1 chinkaling 2012-08-08 03:53:15 UTC
Seems similar to this problem (but I'm not completely sure): https://bugzilla.redhat.com/show_bug.cgi?id=801600

abrt-applet reports that "Process /usr/libexec/tracker-miner-fs was killed by signal 11 (SIGSEGV)".

When I run "analyze_LocalGDB", I get a notice that:

"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?"

This command that is given fails, and a quick look at the "pkcon --help" shows that the syntax in the "fix" is completely wrong and the "repo-repo" option doesn't even exist. Anyhow, what is the difference between using pkcon vs yum?

A yum check shows me that I have "Package tracker-0.14.1-1.fc17.i686 already installed and latest version".

Is my problem mentioned a completely different story or should I resubmit as a different bug. I don't recall exactly what I was doing at the time, but this happens fairly often. I will be sure to make note next time it occurs.

Comment 2 Jiri Moskovcak 2012-08-09 20:47:06 UTC
*** Bug 842560 has been marked as a duplicate of this bug. ***

Comment 3 Jiri Moskovcak 2012-08-09 21:18:15 UTC

*** This bug has been marked as a duplicate of bug 835472 ***


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