On Sun, 23 Feb 2003, Paul Misner wrote:
> I think I may see the reason for my problem. I have a local copy of both
> cooker and contrib, and it looks like I may have done an update that got
> pieces from each of them. I installed samba-common for 2.27a-3 to fix my
> problem. Looking at the results of the rpm -qa, it seems my update from
> cooker pulled in the samba-common from contrib for the 3.0 alpha.
This was actually one of the reasons I asked (I am the maintainer of
samba3 at present, and just help out with the official package).
> Odd that I
> would have gotten only the samba-common package if that was the case, but
> that would be the easiest explanation for the problem. It seems like it is
> probably an issue local to my install. Sorry about that.
>
Still it should not happen. Maybe we need to enforce the version of
samba-common that samba-server requires. Actually, it seems we do enforce
version:
%package server
Summary: Samba (SMB) server programs.
Obsoletes: samba-server-ldap
Requires: samba-common = %{version}
So, the bug may be elsewhere ...
Thanks for breaking it, even in an unusual way, things like this need to
be fixed ...
> [EMAIL PROTECTED] paul]# rpm -qa samba*
> samba-common-2.2.7a-3mdk
> samba-client-2.2.7a-3mdk
> samba-server-2.2.7a-3mdk
> samba-doc-2.2.7a-3mdk
> samba3-common-3.0-0.alpha21.3mdk
Well, you should have had a /etc/samba3/smb.conf then ;-). But you would
have been missing a whole bunch of other tools ... (smbpasswd for one).
Regards,
Buchan
--
|----------------Registered Linux User #182071-----------------|
Buchan Milne Mechanical Engineer, Network Manager
Cellphone * Work +27 82 472 2231 * +27 21 8828820x121
Stellenbosch Automotive Engineering http://www.cae.co.za
GPG Key http://ranger.dnsalias.com/bgmilne.asc
1024D/60D204A7 2919 E232 5610 A038 87B1 72D6 AC92 BA50 60D2 04A7
