Re: MySql broken on older 486 and other cpuid less CPUs. Does this qualify as RC?
On Thu, Apr 05, 2007 at 03:42:28PM -0700, Steve Langasek wrote:
> Documenting it in the release notes isn't particularly *relevant* if a fixed
> package is made, AFAICS. The content for the r0 release notes is frozen
> now anyway, to let translators catch up, so any mention of this in the
> release notes would be included on CDs the same time as the fixed package,
> more or less defeating the purpose. We should probably consider an errata
> document for the website, to document r0-specific issues that didn't make it
> into the release notes, so that we don't have to choose between dropping
> translations for not mentioning such errata and publishing
> supposedly-complete translations that don't mention all the errata due to
> time constraints.
>
> Anyway, if this bug had been marked as RC at any point in the past months,
> it certainly would have been fixed before now. It's frustrating to see
> people escalating bug severities at the very last minute, when the bug has
> been known for a while and it's now too late to include a fix in r0 without
> causing the release timeline to slip. (This is not the only bug where this
> has been the case; c.f. bug #399761.) I do remember a bug thread months ago
> about cpuid detection in mysql, but the fact that it wasn't listed as an RC
> bug anymore means that it quickly fell off of *my* radar.
Well if I had known about it I would have suggested it should be RC. I
should try to become a DD one of these days... :)
> In practical terms, it seems to me that part of the fix here should really
> be to declare that we don't officially support 486 CPUs anymore, since no
> one who is using one was involved enough in the etch release to have
> documented this bug as RC until three days before release. :P
My 486 actually does a useful job, and hence usually runs pure stable.
I figured I would upgrade it to see if anything broken, and boy did it
ever break. It is a good old reliable machine and the only 486 I have.
I guess loosing proftpd and php isn't the worst things that can happen,
although I do like my ftp server to work, as well as my web server. At
least I know have a fixed version installed so my machine works.
Maybe I am the only person left with a 486 doing useful work, but it has
run problem free for 15 years now and shows no signs of giving any.
Hopefully I will replace the 486 with a ppro in the next few months, in
which case the 486 will become available for me to just do tests on and
other experiments.
Is there any good reason 486s should not be supproted anymore? I know
why 386s are not supported anymore.
--
Len Sorensen
Reply to: