Bug 947529

Summary: brasero has dependency on tracker
Product: [Fedora] Fedora Reporter: Jonas Wielicki <j.wielicki>
Component: braseroAssignee: Xavier Lamien <lxtnow>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: abyss.7, davej, kazimieras.vaina, lxtnow, stephent98, zlynx
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 796349 Environment:
Last Closed: 2014-02-05 20:25:38 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Jonas Wielicki 2013-04-02 16:36:50 UTC
The cloned description and log says it all, left-outs ("[…]") by me.

+++ This bug was initially created as a clone of Bug #796349 +++

Resolving Dependencies
--> Running transaction check
---> Package brasero.x86_64 0:3.2.0-1.fc16 will be installed
--> Processing Dependency: libtracker-sparql-0.12.so.0()(64bit) for package: brasero-3.2.0-1.fc16.x86_64
--> Running transaction check
---> Package tracker.x86_64 0:0.12.9-1.fc16 will be installed
--> Finished Dependency Resolution

Having tracker forced on me when I just want to burn a dvd is a bit rough.

--- Additional comment from Jonathan Briggs on 2012-04-04 16:16:12 EDT ---

I just noticed this myself. I agree, no dependencies on tracker. What a CPU hog.

--- Additional comment from Kazimieras Vaina on 2012-08-14 18:20:00 EDT ---

Totem should have no hard dependency on grilo-plugins (which in turn has dependency on tracker) as well.

--- Additional comment from Fedora End Of Life on 2013-01-16 10:07:31 EST ---

[…]

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 is end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" and open it against that version of Fedora.

[…]

--- Additional comment from  on 2013-01-16 23:56:52 EST ---

The Brasero still has a dependency on the tracker - in Fedora 18.

[…]

Comment 1 Fedora End Of Life 2013-12-21 12:37:10 UTC
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '18'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior to Fedora 18's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 2 Fedora End Of Life 2014-02-05 20:25:38 UTC
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.