| Summary: | x86_64 repo does not contain i686 dependencies of added i686 -devel packages | ||
|---|---|---|---|
| Product: | Infrastructure | Reporter: | IFo Hancroft <acidcore.15> |
| Component: | Repo | Assignee: | Nicolas Chauvet <kwizart> |
| Status: | RESOLVED FIXED | ||
| Severity: | major | CC: | hans, matthias, mschwendt |
| Priority: | P5 | ||
| Version: | NA | ||
| Hardware: | x86_64 | ||
| OS: | GNU/Linux | ||
| namespace: | |||
That is weird, those dependencies are provided by the opencore-amr package, so if you do (as you seem to have done): yum install opencore-amr-devel Then yum should automatically figure out to add opencore-amr to the transaction, and things should work fine. Can you make sure al your repositories are set up in a sane way, and then do: yum clean all And try again ? Also are you by any chance using any other third party repositories, or just fedora + updates and rpmfusion + updates ? I actually already have opencore-amr install but still get that error when trying to install opencore-amr-devel-i686 (the 64bit version installs without any problems though) Can you please define what do you mean by set in a sane way? I have already tried yum clean all (And I get the same error) And no, I am not using any other repositories other than fedora + update and rpmfusion free and none free + updates Ah you're right, looking here: http://download1.rpmfusion.org/free/fedora/releases/17/Everything/x86_64/os/ It seems that the repo generation for multi-lib is wrong, the i686 versions of -devel packages are being added (as intended) but their dependencies are not added! Please note that there is no CVS action to take. Unfortunately the multilibs script is indeed broken for release as for updates-testing. The i686 packages was manually copied into the x86_64 directory to workaround this. Unfortunately this late fix is unlikely to happen for such frozen released branch. (In reply to comment #4) > Please note that there is no CVS action to take. > Unfortunately the multilibs script is indeed broken for release as for > updates-testing. > The i686 packages was manually copied into the x86_64 directory to workaround > this. > Unfortunately this late fix is unlikely to happen for such frozen released > branch. Hmm, could we then maybe copy the missing deps to the updates repo instead? It would be a bit weird to have the -devel ones in the frozen branch and the deps in updates, but it should work. Alternatively, if things indeed do work properly for updates, I could just bump and rebuild ... Can anyone make the whole list of i686 dependendencies missing from the free/nonfree release tree ? It is weird that I didn't realise it at first before you answered here that I see the i686 version of the devel package when for opencore-amr itself i only see the x86_64 version. (In reply to comment #7) > It is weird that I didn't realise it at first before you answered here that I > see the i686 version of the devel package when for opencore-amr itself i only > see the x86_64 version. That's well understood, now I need to complete list of the missing i686 version in x86_64 repo. Basically mean for earch foo-devel.i686.rpm there is likely a i686.rpm with name either foo-libs.i686 or foo.i686. I need the list of the missing ones, as I don' thave time to seek. Well from can I [if there is such] get a list with all the i686 files in the repo so I can start looking? > Unfortunately the multilibs script is indeed broken for release
> as for updates-testing.
If you mean the configuration file that has been set up, that is what is broken most likely. In several bz posts before, I have commented on potential mistakes to watch out for (especially after the transition of Fedora 17 to a new download dir layout), but there is no progress, and the config files have not been published anywhere either. Many months (years?) have passed.
I think TwoLAME.i686 is also missing since when I type in TwoLAME in the software manager I see TwoLAME, TwoLAME-libs and TwoLAME-devel and everything has both 64 and 32 bit version except TwoLAME twolame-devel only requires twolame-libs, so the default multilib policy does not pull in twolame This should be fixed for f18 and later. |
sudo yum install opencore-amr-devel.i686 Loaded plugins: langpacks, presto, refresh-packagekit Resolving Dependencies --> Running transaction check ---> Package opencore-amr-devel.i686 0:0.1.3-2.fc17 will be installed --> Processing Dependency: libopencore-amrnb.so.0 for package: opencore-amr-devel-0.1.3-2.fc17.i686 --> Processing Dependency: libopencore-amrwb.so.0 for package: opencore-amr-devel-0.1.3-2.fc17.i686 --> Finished Dependency Resolution Error: Package: opencore-amr-devel-0.1.3-2.fc17.i686 (rpmfusion-free) Requires: libopencore-amrnb.so.0 Error: Package: opencore-amr-devel-0.1.3-2.fc17.i686 (rpmfusion-free) Requires: libopencore-amrwb.so.0 You could try using --skip-broken to work around the problem ** Found 1 pre-existing rpmdb problem(s), 'yum check' output follows: msttcorefonts-1.3-4.noarch has missing requires of /usr/sbin/chkfontpath