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

# rpm -q samba-client
package samba-client is not installed
# rpm -qp --provides
mdk/RPMS.mdk9.2/i586/samba3-client-3.0.0-0.rc2.2mdk.i586.rpm
samba-client
samba3-client = 3.0.0-0.rc2.2mdk
# rpm -ivh mdk/RPMS.mdk9.2/i586/samba3-client-3.0.0-0.rc2.2mdk.i586.rpm
error: Failed dependencies:
        samba-client < 2.2.8a-9mdk conflicts with
samba3-client-3.0.0-0.rc2.2mdk

So, now assuming:
1)I don't want samba3-client to be installed by default if a user has
main and contrib urpmi media and they run 'urpmi samba-client'
2)I want them to be able to choose samba3-client (or install it
seperately and not have to keep samba-client-2.2.8a-Xmdk installed to
satisfy dependencies on 'samba-client')
3)I don't want anyone with samba-client-2.2.8a-8mdk or earlier to be
able to install samba3-client-3.0.0-0.rc2.2mdk or later if built with
alternatives support

How should I solve this problem?

I can't provide a higher samba-client in samba3-client (urpmi will
likely choose it), and I can't provide a lesser samba-client in
samba3-client (since then someone might get file conflicts).

Another rpm provides matched by conflicts/obsoletes catch22, and I don't
think this one is that easy to get around ...

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/VhhlrJK6UGDSBKcRAtO/AJ9JfePadvsUXqfYu7EonMG+hjhmkQCfQZ0T
XtmgWLmDuVFTYx5cDClQ3j0=
=gITx
-----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