Description of problem: After upgrading form F14 where I had report-plugin-scp and report-plugin-ftp installed, yum upgrade fails since these packages have dependencies on report (which apparently is replaced bt libreport) but there isn't anything providing nor obsoleting these packages. Version-Release number of selected component (if applicable): libreport-2.0.7-1.fc16 How reproducible: Every time Steps to Reproduce: 1. yum upgrade Actual results: ERROR with transaction check vs depsolve: report = 0.20-1.fc14 is needed by (installed) report-plugin-scp-0.20-1.fc14.x86_64 report = 0.20-1.fc14 is needed by (installed) report-plugin-ftp-0.20-1.fc14.x86_64
This seems more like a yum problem. There is package libreport-plugin-reportuploader which has this in spec file: %package plugin-reportuploader Summary: %{name}'s reportuploader plugin Group: System Environment/Libraries Requires: %{name} = %{version}-%{release} Obsoletes: abrt-plugin-reportuploader < 2.0.4 Provides: report-plugin-ftp = 0.23-1 Obsoletes: report-plugin-ftp < 0.23-1 Provides: report-config-ftp = 0.23-1 Obsoletes: report-config-ftp < 0.23-1 Provides: report-plugin-scp = 0.23-1 Obsoletes: report-plugin-scp < 0.23-1 Provides: report-config-scp = 0.23-1 Obsoletes: report-config-scp < 0.23-1 - so it seems to me, like yum from F14 fails to see this Provides/Obsoletes (or rpm??) -> reassigning
insufficient specification of the version. If you prepend a 0: to the version/release specification of the obsoletes then they will likely catch report-plugin*/report-config*
Missing zero epoch is not supposed to make any difference, if it does it's a bug.
I agree with Panu on this, but to make sure I added the epoch to our spec file. Moving back to yum.
please supply the complete output of yum -d 7 upgrade I suspect this is still not a yum bug.
Had a look at this and everything seems fine, get lots of obsoletes ... it's possible it's a bug in F14's yum, I guess. Can you upload the output?
Tried reproducing this issue by installing a new F14 (not necessarily with the same package set as the original machine) and then upgrading it to F16 and running "yum upgrade" but I didn't hit the issue. If we're not getting any further, please feel free to close this issue as "works_for_me"
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
Closing per comment #7