On Wed, 2 May 2012 18:38:21 -0700 (PDT), AO (Antonio) wrote: > Dear folks, > > for a good while now, I have kept getting the following every time I yum update : > If you run updates-testing, you may need to run "yum distro-sync" from time to time. The reason for that is simple. Test Updates are withdrawn because they are broken. They are not available in the repos anymore, but it could be that you've installed them or updated to them already. Often, broken test updates are replaced with a newer release, which would replace your installed packages. However, some test updates are not replaced, at least not too soon. And even if a newer test update replaces an earlier broken one, it could be that it doesn't even try to fix temporary packaging issues. > Resolving Dependencies > --> Running transaction check > ---> Package samba4-client.i686 1:4.0.0-41alpha18.fc17 will be updated > ---> Package samba4-client.i686 1:4.0.0-45alpha18.fc17 will be an update > ---> Package samba4-common.i686 1:4.0.0-41alpha18.fc17 will be updated > --> Processing Dependency: samba4-common = 1:4.0.0-41alpha18.fc17 for package: 1:libsmbclient-4.0.0-41alpha18.fc17.i686 > The -41alpha18.fc17 release has been trouble-some. It could not be installed here with an ordinary F-17 Beta installation "yum update". > I don't see in the reports that the package(s) are broken, is the updates-testing repo here conflicting with official pre 17 release repo? > The existing broken deps reports only search for dependency problems in the current repository contents. Typically, that is unable to catch all kinds of upgrade issues as older package releases are not in the repos anymore. > Any thoughts of what I should do to resolve this? Try "yum distro-sync". -- Fedora release 17 (Beefy Miracle) - Linux 3.3.4-1.fc17.x86_64 loadavg: 2.02 1.24 0.54 -- test mailing list test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
