On Sun Feb 04, 2001 at 03:05:04PM -0700, Collins Richey wrote:
> Sounds like an "opportunity" for the Mandrake folks. Why doesn't (can't)
> Mandrake Update recognize this situation and drag in the necessary
> supporting rpms. Still better, why can't the developers actually try the
> rpms on a real live 7.2 system and thus avoid the problem for the
> unsuspecting masses?
We do but I tend to play a little bit, which affects things. =) I
was running a bunch of the unsupported rpms, of which libcups was a
part of so I did not notice this dependancy problem (on the wife's
machine which runs 7.2+unsupported+updates, whereas my machine runs
cooker).
This was my mistake. I do think having MandrakeUpdate become a little
more "apt-like" to do that would be a good idea, but I need to work
with the current limitations of MU and have to do this better. Sorry
folks! "Proper" packages will be updated tomorrow, but this then
leaves people with a little "prep" work to do (ie. rpm -e
libcups1(-devel) --nodeps) before upgrading to the new packages which
will be done (and corrected) tomorrow.
--
[EMAIL PROTECTED], OpenPGP key available on www.keyserver.net
1024D/FE6F2AFD 88D8 0D23 8D4B 3407 5BD7 66F9 2043 D0E5 FE6F 2AFD
- Danen Consulting Services www.danen.net, www.freezer-burn.org
- MandrakeSoft, Inc. Security www.linux-mandrake.com
Current Linux kernel 2.4.0-12mdk uptime: 3 days 23 hours 58 minutes.
