"T.C. Hollingsworth" <tchollingsworth@xxxxxxxxx> writes: > On Mon, Jun 10, 2013 at 6:43 AM, lee <lee@xxxxxxxxxxxxxxx> wrote: >> "T.C. Hollingsworth" <tchollingsworth@xxxxxxxxx> writes: >> >>> On Sun, Jun 9, 2013 at 1:29 PM, lee <lee@xxxxxxxxxxxxxxx> wrote: >>>> Ah hm, I've done the above and removed some other packages that don't >>>> seem to be needed anymore. Let me try cleandupes ... >>>> >>>> Dupes are all gone now, it didn't find any. I have orphaned packages: >>> <snip list> >>> >>> I wouldn't worry about these. A package being "orphaned" just means >>> that you didn't manually install them and they are no longer required >>> as a dependency of anything else. In fact, the mechanism yum uses to >>> track these might be confused by the partial upgrade. There are some >>> rather important packages in that list you probably don't want to >>> remove listed there, such as NetworkManager for instance. >> >> How can they be orphaned when there are packages that depend on them? > > My apologies, I confused "orphans" with "leaves". Orphans are > packages yum can't find in the repos. > > A number of the packages are from RPMFusion and are only showing here > because the RPMFusion repos aren't enabled, thus making them orphans > as far as yum is concerned. Yes, that would make sense. > Others look like some packages didn't get obsoleted correctly. For > instance, procps should have been replaced by procps-ng. Do you have > a "procps-ng" package installed on your system? ,---- | [root@yun etc]# yum list installed |grep procps | procps.x86_64 3.2.8-28.20110302git.fc17 installed | procps-ng.x86_64 3.3.3-4.20120807git.fc18 installed `---- I'll remove the one from 17 ... > A few might be true orphans, and are no longer shipped with the > package collection. > >> Network manager is actually obsolete, it's only there because of messed >> up dependencies, i. e. too many packages depending on it without any of >> them needing it. >> >>>> When I attempt remove these, yum wants to remove packages from 18 as >>>> well due to dependencies. Are there packages in 18 that depend on >>>> packages from 17, and why would that be? >>> >>> That's not quite what's happening. You have a lot of packages on your >>> system that are still at the F17 version, and that version just >>> happens to satisfy the dependencies of F18 packages just fine. They >>> would be equally happy if a F18 version took their place. >> >> Not really a lot anymore, I hope? > > Yeah, how bad is it? Maybe distro-sync isn't working because you've > already fixed it mostly? What does `rpm -qa \*fc17\*` say? ,---- | [root@yun etc]# rpm -qa \*fc17\* | kmod-nvidia-3.8.13-100.fc17.x86_64-304.88-1.fc17.7.x86_64 | kmod-nvidia-3.7.9-104.fc17.x86_64-304.64-7.fc17.8.x86_64 | kmod-nvidia-3.8.4-102.fc17.x86_64-304.88-1.fc17.x86_64 `---- They are probably not needed. ,---- | [~] yum list installed |grep kmod-nvidia | akmod-nvidia.x86_64 1:304.88-1.fc18 installed | kmod-nvidia.x86_64 1:304.88-1.fc18.10 installed | kmod-nvidia-3.7.9-104.fc17.x86_64.x86_64 | kmod-nvidia-3.8.13-100.fc17.x86_64.x86_64 | kmod-nvidia-3.8.4-102.fc17.x86_64.x86_64 | kmod-nvidia-3.9.4-200.fc18.x86_64.x86_64 | [~] `---- Hm, not sure what to do about these. > Does a regular `yum update` do anything? Does it attempt to "replace" > a bunch of packages with packages with a different name? It says "No Packages marked for Update". >> IIRC, I followed some instructions to install NVIDIA drivers which >> involved adding the rpmfusion repo. Is there a Fedora package to add >> this repo which provids these files? > > To get the NVidia drivers and other packages from RPMFusion you need > to install the rpmfusion-free-release and rpmfusion-nonfree-release > packages as explained here: > http://rpmfusion.org/Configuration Cool, I got those now :) Doesn't seem to change anything atm, though. >> Now when install a package, the package from 18 gets installed. >> However, I have now the two directories, "17" and "18", in >> /var/cache/yum/x86_64/. Shouldn't that somehow be cleaned? > > You can delete this manually, but it should be harmless. Ok, I'll move the cache for 17 out of the way. Then I'll go through the orphaned packages and see if I can remove them ... Now all the orphaned packages are gone, except for one which I installed myself and need to keep. There are a few leaves, all from 18, which probably is also ok because I might have installed some to be able to compile stuff. And package-cleanup doesn't find any problems, either. Some packages from 17 are still installed. I tried to remove two of them and there are packages of Fedora 18 depending on them. There doesn't seem to be a replacement in 18 --- for example, there's a package called agg-2.5-13.fc17.x86_64, and both gnash-1:0.8.10-4.fc18 and gnash-plugin-1:0.8.10-4.fc18 would also be removed. So when someone installs Fedora 18, they will have to remain without gnash because required packages are missing in 18? Or what does this mean? -- Fedora 17.8 -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
