-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Charles A Edwards wrote:
> On Wed, 03 Sep 2003 19:11:34 +0200
> Buchan Milne <[EMAIL PROTECTED]> wrote:
>
>
>>Hmm, this could work, *if* I tighten the requires on samba-client to =
>>samba-common-%{version}-%{release} (currently it's only %{version}).
>
>
> Well, you could drop the release from the Conflict if you do not want
> any release of  2.2.8a would 'update' to samba3.
>
> As you worded your original you were only concerned if samba-client <
> 2.2.8a-9 was being used.
>
> BTW if the release tag is used urpmi Will update to 3.0.0 anyone running
>  2.2.8a >= 2.2.8a-9

Yes, I actually wanted to avoid a Provides: samba-client with version
information, but I think:

Provides: samba-client
Conflicts: samba-common < 2.2.8a-9mdk

should do enough of what I want if I tighten the requires on
samba-client (except they could be stuck with a samba-client-2.2.8a-8mdk
and samba-common-2.2.8a-9mdk, unless I conflict samba-client <
2.2.8a-9mdk, but then I will end up with a circular conflict back to
samba3-client).

Hmm, will play with this a bit while I fix a few other things.

Maybe I should not worry about the conflicts, it will just cause the
update-alternatives to fail ... (could be worse).

There must be a solution, but the only complete one I can think of
(Epoch) isnt't very attractive ...

Regards,
Buchan

- --
|--------------Another happy Mandrake Club member--------------|
Buchan Milne                Mechanical Engineer, Network Manager
Cellphone * Work            +27 82 472 2231 * +27 21 8828820x202
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
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQE/VinCrJK6UGDSBKcRAjQuAKCgxFkY+zQXgrLgpBYlumMItTExZwCaAvGi
aqRXZZESuYiY0QCnJhwUfy0=
=vswd
-----END PGP SIGNATURE-----

*****************************************************************
Please click on http://www.cae.co.za/disclaimer.htm to read our
e-mail disclaimer or send an e-mail to [EMAIL PROTECTED] for a copy.
*****************************************************************

Reply via email to