Re: [Security-Discuss] Update problem in samba-client

On 8-Nov-04, at 6:26 AM, Stew Benedict wrote:

>> I noticed that in performing the samba update MDKSA-2004:104 on about  
>> a dozen various 9.2 boxes via
>> urpmi, the samba update gives off this error:
>>
>> error: %preun(samba-client-2.2.8a-13.1.92mdk) scriptlet failed, exit  
>> status 1
>>
>> If I try to rpm -Uhv the update RPM, it tells me that it is already  
>> installed.  Samba appears to
>> work, although all the machines are servers, and I have no need to  
>> use the client part.
>>
>> Is this a benign error?
>>
>
> It looks like you're a couple of versions behind, but I got the same  
> error
> with the latest:
>
> installing  
> /var/cache/urpmi/rpms/samba-client-2.2.8a-13.3.92mdk.i586.rpm
> Preparing...
> ##################################################
>    1:samba-client
> ##################################################
> error: %preun(samba-client-2.2.8a-13.1.92mdk) scriptlet failed, exit
> status 1
>
> [root@norris root]# rpm -q --scripts samba-client
> postinstall scriptlet (using /bin/sh):
> update-alternatives --install /usr/bin/smbclient smbclient \
> /usr/bin/smbclient2 10 \
> $(for i in
> {/bin/mount.cifs,/sbin/{mount.smb,mount.smbfs},/usr/bin/ 
> {findsmb,nmblookup,smbclient,smbmnt,smbmount,smbprint,smbspool,smbtar,s 
> mbumount}};do
> j=`basename $i`
> [ "$j" = "smbclient" ] || \
> echo -n " --slave ${i} ${j} ${i}2";done) \
> --slave /usr/lib/cups/backend/smb cups_smb /usr/lib/cups/backend/smb2  
> || \
> update-alternatives --auto smbclient
> preuninstall scriptlet (using /bin/sh):
> [ $1 = 0 ] && update-alternatives --remove smbclient  
> /usr/bin/smbclient2
>
> Looks like the error is fairly benign, it tries to remove
> /usr/bin/smbclient2, which apparently isn't on our boxen. (probably  
> should
> have had a check for the file existing)

IIRC, this has something to do with update-alternatives (the smbclient2  
vs. smbclient3 business).  I don't understand why it's there as I don't  
know who would install both samba2 and samba3, but whatever.

Maybe the maintainer will fix it at some point (or maybe it's since  
been fixed).  At any rate, it isn't anything to worry about.

-- 
*Please note gpg keyid FE6F2AFD has been replaced with keyid FEE30AD4*
"lynx -source http://linsec.ca/vdanen.asc | gpg --import"
{FEE30AD4 : 7F6C A60C 06C2 4811 FA1C  A2BC 2EBC 5E32 FEE3 0AD4}