-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dario Lesca wrote: > On a FC6 System: > >> [root@s-vmw ~]# yum update >> Loading "installonlyn" plugin >> Setting up Update Process >> ..... >> Updating: >> samba i386 3.0.24-8.fc6 updates 16 M >> samba-client i386 3.0.24-8.fc6 updates 4.2 M >> samba-common i386 3.0.24-8.fc6 updates 8.6 M >> .... >> Is this ok [y/N]: > > >From Fedora site: > >> http://download.fedora.redhat.com/pub/fedora/linux/core/updates/6/i386/samba-3.0.24-7.fc6.i386.rpm > > >From samba.org: >> Latest News >> * 20 November 2007 Samba 3.0.27a Available for Download >> * 15 November 2007 Samba 3.0.27 Available for Download >> * >> * > > What's happen ? Don't get too discouraged, several things: (1) You probably have the updates-testing site enabled for FC6. The RedHat people have a QA step before releasing any patches to catch or try to catch any silly mistakes made by rushing in to fix a problem. It will be pushed to the updates when voted as being OK. (2) Instead of updating to the latest version; which CAN break some features, RedHat (Fedora) only patches the security flaw or defect and does not upgrade the entire application. If you read the mailing lists regularly for SAMBA, you will notice after a while the SAMBA community tries to make things better; but, sometimes features have to go away for that to happen seamlessly or without complicating the code too much. Good Luck, and read the notes in the RPM file on the fix. 'rpm -q - --changelog samba' after installing. - -James -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHTXNckNLDmnu1kSkRAgtiAJ4g2uO2hUv/XG7jfz2qDTB2K3sVJgCfYw1B sj0b8YcknEW7bmZHINd2RkM= =l7mJ -----END PGP SIGNATURE----- -- Scanned by ClamAV - http://www.clamav.net
