Reindl Harald <h.reindl@xxxxxxxxxxxxx> writes: > Am 11.06.2013 04:10, schrieb lee: >> Reindl Harald <h.reindl@xxxxxxxxxxxxx> writes: >>>> | [root@yun etc]# yum list installed |grep fc17 >>>> | NetworkManager-gtk.x86_64 1:0.9.6.4-3.fc17 installed >>>> | [...] >>>> `---- >>>> >>>> For example, is this version of networkmanager-gtk in Fedora 18? >>> >>> there is no "networkmanager-gtk" at all in Fedora 18 >>> and that is what is called orphan >> >> It seems so --- the question is why aren't such packages removed by yum >> distro-sync? > > because it is not it's job to remove any package which is not > found in the repos because you may have installed it manually > > it's job is to bring packages which are existing in the repos > to the *exact* version in the repos no matter if this means > downgrade ur upgrade them Ah ok, that makes sense. Which way is there to upgrade from one release to the next when neither distro-sync, nor fedup can do this? Is there an equivalent to Debian testing for Fedora so that I can avoid failing upgrades? -- "Object-oriented programming languages aren't completely convinced that you should be allowed to do anything with functions." http://www.joelonsoftware.com/items/2006/08/01.html -- 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