Re: update from 17 to 18 failed

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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.

> 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.

> The list is quite a bit longer when not limiting it to packages from 17,
> but I guess that's because packages are listed no other packages depend
> on.
>
> What can I do about the packages that remain from 17 now?  Go through
> them one by one and see what happens when attempting to remove them?

As I said previously, you probably really want to keep these packages;
you just need to get them updated to F18.  If we can fix distro-sync,
we can fix this.

> Services that didn't work anymore are now working again.  I haven't
> rebooted yet after removing packages, though.
>
> Oh and I moved the repo files for rpmfusion out of the way because that
> all seemed to refer to Fedora 17 instead of 18.  IIRC I need those (at
> least) for the NVIDIA driver.  What do I need to do about those?

Hmm, the RPMFusion .repo files as installed by
rpmfusion-(non)free-release don't hardcode the distribution version;
they use $releasever to have yum figure it out for them.  Did you see
the number "17" in the rpmfusion-*.repo files themselves, or did yum
report this?  If yum is confused about the version of Fedora you are
using that could explain why distro-sync is acting up.

-T.C.
-- 
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




[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux