By default, Bugzilla does not search the list of RESOLVED bugs.
You can force it to do so by putting the upper-case word ALL in front of your search query, e.g.: ALL tdelibs
We recommend searching for bugs this way, as you may discover that your bug has already been resolved and fixed in a later release.

Bug 2506

Summary: [EL6] R14.0.0 -> R14.0.1 dependency conflict with SoundKonverter
Product: TDE Reporter: Kristopher <gamrat.kristopher>
Component: rhelAssignee: Timothy Pearson <kb9vqf>
Status: RESOLVED FIXED    
Severity: trivial CC: albator78, bugwatch, gamrat.kristopher, michele.calgaro
Priority: P5    
Version: R14.0.1 [Trinity]   
Hardware: Other   
OS: Linux   
Compiler Version: TDE Version String:
Application Version: Application Name:
Attachments: Screenshot of the dependency issue

Description Kristopher 2015-08-29 09:09:10 CDT
Created attachment 2554 [details]
Screenshot of the dependency issue

Attempting a "yum upgrade" on CentOS 6 produces the following dependency conflict:



Error: Package: 2:trinity-soundkonverter-amarok-0.3.8-1.el6.i686 (trinity-r14)
           Requires: trinity-soundkonverter = 0.3.8-1.el6
           Removing: trinity-soundkonverter-0.3.8-5.el6.opt.i686 (@trinity-r14)
               trinity-soundkonverter = 0.3.8-5.el6.opt
           Updated By: 2:trinity-soundkonverter-0.3.8-1.el6.i686 (trinity-r14)
               trinity-soundkonverter = 2:0.3.8-1.el6
 You could try using --skip-broken to work around the problem
 You could try running: rpm -Va --nofiles --nodigest



A few lines up, I see:



---> Package trinity-soundkonverter.i686 0:0.3.8-5.el6.opt will be updated
---> Package trinity-soundkonverter.i686 2:0.3.8-1.el6 will be an update
---> Package trinity-soundkonverter-amarok.i686 0:0.3.8-5.el6.opt will be updated
---> Package trinity-soundkonverter-amarok.i686 2:0.3.8-1.el6 will be an update



I have attached a screenshot.
Comment 1 Michele Calgaro 2015-08-29 09:51:59 CDT
Kristopher, could you try in a few days and let us know if the problem is still there? It may be a mirror synchronization problem, maybe.
Comment 2 Kristopher 2015-08-29 10:51:39 CDT
(In reply to Michele Calgaro from comment #1)
> Kristopher, could you try in a few days and let us know if the problem is
> still there? It may be a mirror synchronization problem, maybe.

It's not a mirror synchrnization issue, forcing yum to use a mirror that I know to have the packages does not fix it. The mirror I am forcing (via the baseurl repo tag, instead of the mirrorlist tag) is:

http://tde-mirror.yosemite.net/trinity/trinity/rpm/el6/trinity-r14/RPMS/i686/

If you search that page, it definitely has the packages needed from the original post, with the same timestamp as the other new packages from R14.0.1. Yet, after forcing the mirror and doing a "yum clean all && yum upgrade", the same exact issue as mentioned in the original post appears.

At first glance, the issue that I'm seeing is that the release tag for the new version is at 1.el6 while the old version is at 5.el6, but the versions are exactly the same. Since 5.el6 > 1.el6 and 0.3.8 == 0.3.8, it seems logical that RPM would want to keep the old R14.0.0 version installed and would thus get confused when yum asks it to do the upgrade.
Comment 3 Francois Andriot 2015-08-29 11:10:39 CDT
Yes, there is an actual issue in the SPEC file for soundkonverter package. I will fix it and reupload.
Comment 4 Kristopher 2015-09-03 20:48:31 CDT
The SoundKonverter packages now update without any conflicts. Marking as FIXED.