On Tue, 2003-02-04 at 12:00, Ashley Kitson wrote: > Bret > > Thanks. here is output > > samba-common-2.2.5-10 > samba-2.2.7a-1 > samba-client-2.2.5-10 > > so it's mixed up! What now? >
OK keep in mind I am not an up2date user and there may be a better way to do this using the tool. This should not happen as far as I can tell, and there is a bug somewhere either in the dependencies listed in the packages or the tool used to update the packages. you can manually --force stuff like this but it is rarely a good idea as you can tell. I would backup the smb.conf file if you have spent any time on it and do rpm -e samba samba-common samba-client that should remove all the samba packaged from the database and allow the re-installation of them. Then reinstall the samba packages with up2date or rpm -ivh samba* while sitting in your updates directory where you downloaded all the samba updates. If you do the updates directory deal you should get samba-swat too. If you can recreate the steps taken to get the packages out of sync, a bug report to bugzilla.redhat.com would be good so the can fix the problem in the next release. Bret -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
