On 06/13/2017 02:51 PM, Matthew Miller wrote:
On Tue, Jun 13, 2017 at 02:40:27PM -0400, Tom Stellard wrote:
>>>> Error: Transaction check error:
>>>> file /usr/include/llvm from install of llvm-devel-4.0.0-13.fc27.x86_64
>>>> conflicts with file from package llvm-devel-4.0.0-4.fc27.x86_64 file
>>>> /usr/include/llvm-c from install of llvm-devel-4.0.0-13.fc27.x86_64
>>>> conflicts with file from package llvm-devel-4.0.0-4.fc27.x86_64
[...]
> I just tried this, but I still get the same error as before. Could there
> be some other issue?
Are all of the dependencies of the old llvm-devel package filled if you have
the new llvm-devel installed? My assumption is that this is happening
not because of any problem with obsoleting, but that DNF needs the old
package to stay to keep some dependency filled.
Here is the output I get with --debuglevel=1
--> Starting dependency resolution
---> Package llvm4.0-devel.x86_64 4.0.0-14.fc27 will be installed
---> Package llvm-devel.x86_64 4.0.0-4.fc27 will be obsoleted
---> Package llvm4.0.x86_64 4.0.0-14.fc27 will be installed
---> Package llvm4.0-libs.x86_64 4.0.0-14.fc27 will be installed
---> Package llvm-libs.x86_64 4.0.0-4.fc27 will be obsoleted
---> Package llvm-devel.x86_64 4.0.0-4.fc27 will be upgraded
---> Package llvm-devel.x86_64 4.0.0-14.fc27 will be an upgrade
---> Package llvm.x86_64 4.0.0-4.fc27 will be upgraded
---> Package llvm.x86_64 4.0.0-14.fc27 will be an upgrade
--> Finished dependency resolution
It looks like llvm-devel.x86_64 4.0.0-4.fc27 is being both
obsoleted and upgraded, could that be the problem?
-Tom