Description of problem: An explicit dependency on %{_libdir}/libstdc++.so.6 means that installing libstdc++-devel via yum causes it to download filelist metadata. Version-Release number of selected component (if applicable): 4.4.1-2.fc11 How reproducible: Always Steps to Reproduce: 1. ensure that libstdc++-devel is not installed 2. yum clean metadata 3. yum install libstdc++-devel Actual results: yum install libstdc++-devel Loaded plugins: changelog, presto fedora | 3.8 kB 00:00 fedora/primary_db | 10 MB 00:25 rpmfusion-free | 3.3 kB 00:00 rpmfusion-free/primary_db | 322 kB 00:01 rpmfusion-free-updates | 3.8 kB 00:00 rpmfusion-free-updates/primary_db | 361 kB 00:04 rpmfusion-nonfree | 3.3 kB 00:00 rpmfusion-nonfree/primary_db | 79 kB 00:00 rpmfusion-nonfree-updates | 3.8 kB 00:00 rpmfusion-nonfree-updates/primary_db | 104 kB 00:00 updates | 4.4 kB 00:00 updates/primary_db | 5.9 MB 00:18 Setting up Install Process Resolving Dependencies --> Running transaction check ---> Package libstdc++-devel.x86_64 0:4.4.1-2.fc11 set to be updated fedora/filelists_db | 15 MB 00:39 rpmfusion-free/filelists_db | 345 kB 00:02 rpmfusion-free-updates/filelists_db | 164 kB 00:00 rpmfusion-nonfree/filelists_db | 50 kB 00:00 rpmfusion-nonfree-updates/filelists_db | 66 kB 00:02 updates/filelists_db | 8.9 MB 00:26 --> Finished Dependency Resolution Dependencies Resolved =========================================================================== Package Arch Version Repository Size =========================================================================== Installing: libstdc++-devel x86_64 4.4.1-2.fc11 updates 1.8 M Transaction Summary =========================================================================== Install 1 Package(s) Upgrade 0 Package(s) Total size: 1.8 M Is this ok [y/N]: y Downloading Packages: Running rpm_check_debug Running Transaction Test Finished Transaction Test Transaction Test Succeeded Running Transaction Installing : libstdc++-devel-4.4.1-2.fc11.x86_64 1/1 Installed: libstdc++-devel.x86_64 0:4.4.1-2.fc11 Complete! Expected results: The package should be installable without downloading the filelists. Additional info: I suggest replacing Requires: %{_prefix}/%{_lib}/libstdc++.so.6 with Requires: libstdc++%{?_isa} = %{version}-%{release} as you did in F-12.
Also, this is mentioned in the Packaging Guidelines: https://fedoraproject.org/wiki/Packaging:Guidelines#File_Dependencies
Ping?
This message is a reminder that Fedora 11 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 11. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '11'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 11's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 11 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.