Bug 865814 - yum update problem
Summary: yum update problem
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: yum
Version: 17
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Fedora Packaging Toolset Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-10-12 13:51 UTC by ruy alvarez
Modified: 2013-05-28 21:00 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-05-28 21:00:46 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description ruy alvarez 2012-10-12 13:51:55 UTC
Description of problem: i use the yum upgrde command to check for updates, and i use the gui to check for change log (i use the fedora testing repo, and i need to be sure if something could crash o damage the system). In this instance the cli report a new kernel (among other things), but no the gui (it only report a firefox 16.0.1 for other repo). I use the yum update firefox command in the cli and the update is ok. When try to update the other things yum says it has no new updates.


How reproducible: this is the first time it happens (after this i use it to install other things without problems)

Steps to Reproduce:
1.yum upgrade
2.anwser no 
3.check yum info (something) to check if yum respect your decision 
4.also try to use the software, in my case dint work (the kernel have a lot of deps problems)
  
Actual results: yum did install a new kernel without my consent


Expected results: yum should havent install and wait for me to try again


Additional info: I dont know a huge lot about yum and cli to do a proper analysis, and i accept that i am just a human being, but i do belive that any time an update tool with root access dosent respect a user, something must be wrong

Comment 1 James Antill 2013-05-28 21:00:46 UTC
 Yum won't do the update without user confirmation, Maybe you are telling PK it's fine to do silent/background updates? Maybe yum-cron is running?

 "yum history" can help you get to the bottom of these problems (see what did the update).


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