On 06/10/2012 01:31 PM, [email protected] wrote: > Since updating from Core 16 to Core 17, I've been getting some yum dependency > failures, with the diagnostic > > "Processing Conflict: [package name] conflicts filesystem < 3" > > or > > "Processing Conflict: [package name] conflicts filesystem < 3-2" > > Apparently, this is supposed to occur when one attempts to install a package > that > needs the new files system on a system using the old file system. > > But my file system appears to have been successfully updated. /bin, /lib, and > /sbin are aliases for appropriate subdirectories of /usr. If I again try to > update > the filesystem, dmesg reports that it was already updated. > > So at what is yum looking that tells it that the file system is not updated, > and > how do I fix that? >
It seems possible the system thinks you have the old version of filesystem still installed. What does rpm q filesystem or rpm -qa | grep ^filesystem return? -- Never be afraid to laugh at yourself, after all, you could be missing out on the joke of the century. -- Dame Edna Everage -- users mailing list [email protected] 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
