Bug 508570 - abrt package fails to update
Summary: abrt package fails to update
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: abrt
Version: 11
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Jiri Moskovcak
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 512736 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-06-28 16:53 UTC by pgaltieri
Modified: 2015-02-01 22:48 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-06-29 08:58:42 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description pgaltieri 2009-06-28 16:53:34 UTC
Description of problem:
When trying to install latest F11 updates the abrt package failed to update due to conflict

Version-Release number of selected component (if applicable):
Fedora 11 with latest updates

How reproducible:
Always

Steps to Reproduce:
1. yum -y update abrt
2.
3.
  
Actual results:
[root@peglaptop10 ~]# yum -y update abrt
Loaded plugins: downloadonly, fastestmirror, refresh-packagekit
Loading mirror speeds from cached hostfile
 * fedora: mirror.steadfast.net
 * rpmfusion-free: lordmorgul.net
 * rpmfusion-free-updates: lordmorgul.net
 * rpmfusion-nonfree: lordmorgul.net
 * rpmfusion-nonfree-updates: lordmorgul.net
 * updates: kdeforge.unl.edu
Setting up Update Process
Resolving Dependencies
--> Running transaction check
--> Processing Dependency: abrt = 0.0.3-1.fc11 for package: abrt-applet-0.0.3-1.fc11.x86_64
--> Processing Dependency: abrt = 0.0.3-1.fc11 for package: abrt-gui-0.0.3-1.fc11.x86_64
--> Processing Dependency: abrt = 0.0.3-1.fc11 for package: abrt-plugin-kerneloopsreporter-0.0.3-1.fc11.x86_64
--> Processing Dependency: abrt = 0.0.3-1.fc11 for package: abrt-plugin-kerneloops-0.0.3-1.fc11.x86_64
---> Package abrt.x86_64 0:0.0.4-3.fc11 set to be updated
--> Running transaction check
---> Package abrt-addon-kerneloops.x86_64 0:0.0.4-3.fc11 set to be updated
---> Package abrt-applet.x86_64 0:0.0.4-3.fc11 set to be updated
---> Package abrt-gui.x86_64 0:0.0.4-3.fc11 set to be updated
---> Package abrt-plugin-kerneloopsreporter.x86_64 0:0.0.4-3.fc11 set to be updated
--> Processing Conflict: abrt-addon-kerneloops-0.0.4-3.fc11.x86_64 conflicts kerneloops
--> Finished Dependency Resolution
abrt-addon-kerneloops-0.0.4-3.fc11.x86_64 from updates has depsolving problems
  --> abrt-addon-kerneloops conflicts with kerneloops
Error: abrt-addon-kerneloops conflicts with kerneloops
 You could try using --skip-broken to work around the problem
 You could try running: package-cleanup --problems
                        package-cleanup --dupes
                        rpm -Va --nofiles --nodigest


Expected results:
That it should update the package

Additional info:

Comment 1 Jiri Moskovcak 2009-06-29 08:21:23 UTC
It's intended behaviour, ABRT should conflict with kerneloops, so you have to remove it first.

Comment 2 pgaltieri 2009-06-30 00:21:01 UTC
If it's supposed to be removed then why doesn't yum do it for me?  It's done it in the past for other packages.  I thought yum was supposed to be an update manager?

Comment 3 Jiri Moskovcak 2009-06-30 07:14:20 UTC
It's not suposed to be removed, it's supposed to conflict with kerneloops. I could obsolete the kerneloops with abrt and then it would update ok, but I don't want to, because some users prefer kerneloops.

Comment 4 pgaltieri 2009-06-30 21:40:38 UTC
At some point in time both were allowed:

[root@peglaptop10 ~]# rpm -qa | grep abrt
abrt-plugin-kerneloops-0.0.3-1.fc11.x86_64
abrt-gui-0.0.3-1.fc11.x86_64
abrt-0.0.3-1.fc11.x86_64
abrt-libs-0.0.4-3.fc11.x86_64
abrt-plugin-kerneloopsreporter-0.0.3-1.fc11.x86_64
abrt-applet-0.0.3-1.fc11.x86_64
You have new mail in /var/spool/mail/root
[root@peglaptop10 ~]# rpm -qa | grep kerneloops
abrt-plugin-kerneloops-0.0.3-1.fc11.x86_64
abrt-plugin-kerneloopsreporter-0.0.3-1.fc11.x86_64
kerneloops-0.12-5.fc11.x86_64

So you've changed abrt-plugin-kerneloops to conflict with kerneloops?

Comment 5 Jiri Moskovcak 2009-07-01 10:01:43 UTC
Yes, this is new in version 0.0.4 that's why it causing trouble with upgrade. Yum or PackageKit should offer some way how to solve these situations other than just fail.

Comment 6 Jiri Moskovcak 2009-07-20 16:12:33 UTC
*** Bug 512736 has been marked as a duplicate of this bug. ***


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