I wonder, if using Slack-like tarballs instead of rpms and an installer, would clear it up? On Wed, 27 Sep 2000, BillK wrote: > > Same here - every 5 or so rpm's create problems that require manual > intervention - gcc, quota, and MandrakeUpdate/grpmi to mention some. > Its not reliable in that a package installs ok on one machine, but not > another (grpmi installed on both, MandrakeUpdate on only one for > instance) selecting the package that was downloaded to /root/tmp using > kpackage installs it ok. Good idea, poor/buggy execution. > > BillK > > > A V Flinsch wrote: > > > > On Wed, 27 Sep 2000, you wrote: > > > > > > I've given up on MandrakeUpdate as a buggy and annoying program. I just > > > use an ftp mirroring program to copy any new changes from the sources and > > > then update manually. I did it over modem and now cable modem and have > > > also done it over T3 and it always worked right so go for it. ;> > > > > ---------------------------------------- Content-Type: text/plain; name="message.footer" Content-Transfer-Encoding: 8bit Content-Description: ----------------------------------------
Keep in touch with http://mandrakeforum.com: Subscribe the "[EMAIL PROTECTED]" mailing list.
