With the sudo dnf upgrade I have just done I received the following messages, which I'm not sure what to do about.  Problem: package makemkv-1.12.2-2.fc27.x86_64 obsoletes mmdtsdec < 1.12.2-2.fc27 provided by mmdtsdec-1.12.0-1.fc27.i686   - cannot install the best update candidate for package mmdtsdec-1.12.0-1.fc27.i686   - cannot install the best update candidate for package makemkv-1.12.0-1.fc27.x86_64

On 7/5/18 12:25 pm, Ed Greshko wrote: > On 05/07/18 06:08, Stephen Morris wrote: >>      With the sudo dnf upgrade I have just done I received the >> following messages, >> which I'm not sure what to do about. >> >>   Problem: package makemkv-1.12.2-2.fc27.x86_64 obsoletes mmdtsdec < >> 1.12.2-2.fc27 >> provided by mmdtsdec-1.12.0-1.fc27.i686 >>    - cannot install the best update candidate for package >> mmdtsdec-1.12.0-1.fc27.i686 >>    - cannot install the best update candidate for package >> makemkv-1.12.0-1.fc27.x86_64 > > Those packages aren't included in the Fedora repos. > > When doing the update did you include the --allowerasing flag? Thanks Ed, I didn't use that flag as prior to now I have never been in the situation where that flag was needed. Makemkv was a package I explicitly installed for video conversions, but I'm not sure where the 32 bit package came from, the only thing I can think of was it was a dependency for steam. As a side note, I have supplied the --allowerasing flag and the messages have gone away, but neither package is listed in the install or upgrade list in dnf, nor is either package listed by dnf as being removed. So I'm now even more confused as to why the messages were produced in the first place.

On 05/11/18 05:16, Stephen Morris wrote: > I'm now even more confused after having used --allowerasing, even though it got rid > of the messages, issuing dnf info makemkv and dnf info mmdtsdec, the version of > mmdtsdec listed in the message is the only version available and is still > installed, and the makemkv upgrade listed in the message is still available but the > older version is the one that is actually installed, so as I said above I'm now > even more confused about what --allowerasing actually did. You are now on F28, yes?  Also, you are getting those packages from the negativo repositories, yes?  If that is true, I'm guess you have the F27 versions of those packages currently installed? This is a guess since I don't use their repository.  But, it seems like makemkv-1.12.2-2.fc28 may no longer require one to install mmdtsdec as there is no mmdtsdec in their F28 repository. So, you can try upgrading makemkv to see what happens.  And/or, you could remove both mkemkv and mmdtsdec and then install makemkv.  I don't think that will try to pull in any version of mmdtsdec.

On 05/11/18 06:42, Temlakos wrote: > Just a minute. Are you saying makemkv is now on a repository or repositories that > has an F28 version? A repository anyone can activate and, by so activating, install > makemkv without having to compile and link it from a tarball? Yes. https://negativo17.org/multimedia/    and makemkv-1.12.2-2.fc28.x86_64.rpm  is their current version. Take care if you're using rpmfusion repos since there is overlap in what they provide.

On 05/11/18 07:13, Temlakos wrote: > What sort of problems does that "overlap" cause, and how does one work around them? They both contain some of the same packages.  You may run into a situation where a package is updated in one repo but you have another package from the other repo which is still dependent on the older version of that package. So, you may find it necessary to use the "exclude" directive in a repo's config file so you only get it from the other repo.

On 05/11/18 08:19, Temlakos wrote: > On 05/10/2018 07:29 PM, Ed Greshko wrote: >> On 05/11/18 07:13, Temlakos wrote: >>> What sort of problems does that "overlap" cause, and how does one work around them? >> They both contain some of the same packages.  You may run into a situation where a >> package is updated in one repo but you have another package from the other repo which >> is still dependent on the older version of that package. >> >> So, you may find it necessary to use the "exclude" directive in a repo's config file >> so you only get it from the other repo. >> > Sounds easy enough in principle. Where do I find the full syntax and usage of the > "exclude" directive? man dnf.conf    under the section "OPTIONS FOR BOTH [MAIN] AND REPO".  The directive is actually excludepkgs. > I'm about to make my upgrade. Knowing I can activate another repo to provide > makemkv--and keep it up-to-date--should make my life a little easier, on balance. > > What's the best way to activate the negativo repo when doing a clean install? > > That information is available on the https://negativo17.org website.  I would simply "activate" their repo after an install or after an upgrade.