Bug 682432

Summary: Yum failed and wanted to report problem
Product: [Fedora] Fedora Reporter: Zdenek Kabelac <zkabelac>
Component: 0xFFFFAssignee: Seth Vidal <skvidal>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: dwmw2, ffesti, james.antill, maxamillion, pmatilai, tim.lauridsen
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-03-06 09:09:55 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:
Attachments:
Description Flags
Log from yum upgrade none

Description Zdenek Kabelac 2011-03-05 13:10:46 UTC
Created attachment 482433 [details]
Log from yum upgrade

Description of problem:

Todays's upgrade gave me this error message for reporting.
I've manually removed  gvfs from my system (as according jhorak it's 
not needed neither for Mozilla nor for Thunderbird) and it's causing on my system some autofs actions which are quite slowing down startup of this application. As now GIO is used instead of GVFS I've removed gvfs packages with rpm --nodeps.

Now yum reports this problem for thunderbird application (which however works on my system without problems)

I'm reporting this problem only because yum wanted to report this issue - I'm aware of the fact, that some dependencies are currently broken on my system and I do not plan to put gvfs ever back as it cases far more troubles to me....
I hope problematic deps will be resolved over the time.

Version-Release number of selected component (if applicable):
yum-3.2.29-8.fc16.noarch

How reproducible:


Steps to Reproduce:
1. removeing gvfs packages with --nodeps
2. upgrade thunderbird as in attachement
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Tim Lauridsen 2011-03-06 09:09:55 UTC
when removing something with --nodeps, you break the deps tree and this will off cause break things as you have seen.
I does not matter if the package really need the dependency, but if it have a requirement stated in the spec, you will get into trouble to force remove the dependency.
If a package dont need a requirement any more, it most be rebuild without the require for it to not break anything