On Mon Nov 13, 2000 at 12:37:32AM +1100, Ron Stodden wrote:
> > How about you try a MandrakeUpdate for 7.2 on these two RPMs using
> > the ftp://rpmfind.net default mirror - you should strike exactly the
> > same problem?
>
> Vincent, I may have misled you - doing MU development updates again I
> see it is using the 'Source on network' of:
>
> ftp://ftp.wtfo.com/pub/linux/mandrake-devel/cooker/Mandrake/RPMs
>
> Clicking on Update the list of mirrors (which is now very hard to
> find) yields:
>
> ftp://rpmfind.net/linux/MandrakeCooker/cooker/i586/Mandrake/RPMS
>
> Both these are quite obviously incorrect for updating 7.2. Can you
> get the list of mirrors corrected ASAP (which means another update
> for MandrakeUpdate <g>)? Meanwhile put out an urgent advisory
> strictly not to use the MandrakeUpdate in 7.2. Is there no check in
> MU that what is being downloaded is really the updates for the
> installed Linux? That's a basic requirement.
These are correct. Did you not get the splash screen that says
upgrading to development updates are dangerous? Normal updates do not
have this same danger level.
development updates = cooker
normal updates = security/bugfix/enhancedment updates (for 7.2)
MandrakeUpdate functions as it should.
> We were lucky the initial update failed and I quitted out, weren't
> we?
Yes.
> I selected the development updates because normal updates produced a
> blank MU screen and because it was a development install. A cooker
> install is something very different from a development install and
> the MU pushbutton title should be altered to 'Cooker Updates'. In
> any case MU should be able to tell the difference itself.
Of course! At the time you ran the normal updates, there was nothing
to update. Again, read the advisory closer... the updates in that
advisory are already incorporated in the download ISOs which are what
you used to install 7.2. Obviously they won't show up... you already
have all of the listed RPMs installed.
If you run MU for normal updates now, bind and nss_ldap should show up
*if* you have them installed already. If you do not, they won't show
up because there is nothing to update (you don't have them installed).
Having the label development updates changed to cooker updates is a
matter of semmantics. cooker is a *developer* distribution so the
name is not inaccurate. Development updates does not mean tools like
gcc or egcs... it means cooker "development".
I hope that clears things up. If you don't want to run cooker
components on your system, never use development updates.
Here... let's see. I click on development updates and get this:
"Caution! These packages are NOT well tested. You really can screw
up your system by installing them."
Seems like a useful warning to me... If I saw that, I would not
assume that anything in that list would be announced to a public
mailing list to be replacement upgrade material (security, bug*fix* or
otherwise) for an existing install.
--
[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. www.linux-mandrake.com
Current Linux uptime: 5 days 10 hours 15 minutes.
