On Fri, Apr 06, 2007 at 01:24:06AM +0200, Julien Cristau wrote:
Do you know the exact name of the old package that caused this problem?
I believe they were:
communicator-smotif-477
navigator-smotif-477
Both from woody (3.0) non-free.
Certainly both include /usr/X11R6/bin in them.
--
Len
On Sat, Apr 7, 2007 at 13:31:00 -0400, Lennart Sorensen wrote:
On Fri, Apr 06, 2007 at 01:24:06AM +0200, Julien Cristau wrote:
Do you know the exact name of the old package that caused this problem?
I believe they were:
communicator-smotif-477
navigator-smotif-477
Both from woody
On Sat, Apr 07, 2007 at 07:46:35PM +0200, Julien Cristau wrote:
Thanks, I added those conflicts (along with a few others) in x11-common
1:7.1.0-18. Unfortunately, it didn't make it to etch r0 :/
Sounds good. I remember a while ago having a problem upgrading a newer
machine, and the package
On Thu, Apr 05, 2007 at 04:10:19PM -0700, Steve Langasek wrote:
Like I said, in practical terms, if a bug like this in a major server
package goes unnoticed until 3 days before the release, we are not actually
supporting 486. We support the i386 architecture quite well, but it seems
only
* Francesco P. Lovergine ([EMAIL PROTECTED]) [070406 12:33]:
On Thu, Apr 05, 2007 at 04:10:19PM -0700, Steve Langasek wrote:
Like I said, in practical terms, if a bug like this in a major server
package goes unnoticed until 3 days before the release, we are not actually
supporting 486. We
On Fri, Apr 06, 2007 at 12:36:18PM +0200, Andreas Barth wrote:
* Francesco P. Lovergine ([EMAIL PROTECTED]) [070406 12:33]:
On Thu, Apr 05, 2007 at 04:10:19PM -0700, Steve Langasek wrote:
Like I said, in practical terms, if a bug like this in a major server
package goes unnoticed until 3
Bug 410474 involves mysql not working on older 486s and some cyrix cpus
which do not have the cpuid instruction. Any program that tries to use
libmysql (proftpd, php, etc) terminates with illegal instruction.
Upstream tried to fix it, but apparently failed to do so correctly,
although I suspect
* Lennart Sorensen:
So does it seem fair to raise the severity to flag mysql as release
critical for etch since it does affect any program that links in
libmysql running on any x86 without cpuid support?
Document it in the release notes, please. It's not worth risking
stability for the
On Thu, Apr 05, 2007 at 11:46:16PM +0200, Florian Weimer wrote:
Document it in the release notes, please. It's not worth risking
stability for the majority of users for this kind of bug.
Anyway, is there any particular reason why upstream (or you) don't use
the Intel-recommended way for
On Fri, Apr 06, 2007 at 12:12:58AM +0200, Sam Hocevar wrote:
Here's a patch that uses the recommended method.
I will test that out on my 486 and see if that works. It is certainly
much nicer, so assuming it works I vote for this one instead.
--
Len Sorensen
--
To UNSUBSCRIBE, email to
tag 410474 +patch
thanks
On Thu, Apr 05, 2007, Florian Weimer wrote:
Document it in the release notes, please. It's not worth risking
stability for the majority of users for this kind of bug.
Anyway, is there any particular reason why upstream (or you) don't use
the Intel-recommended way
On Thu, Apr 05, 2007 at 06:24:04PM -0400, Lennart Sorensen wrote:
On Thu, Apr 05, 2007 at 11:46:16PM +0200, Florian Weimer wrote:
Document it in the release notes, please. It's not worth risking
stability for the majority of users for this kind of bug.
Anyway, is there any particular
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
On Thu, Apr 05, 2007 at 06:27:08PM -0400, Lennart Sorensen wrote:
I will test that out on my 486 and see if that works. It is certainly
much nicer, so assuming it works I vote for this one instead.
It works perfectfly. Given I see the linux kernel does the same thing,
I guess that isn't
On Thu, Apr 05, 2007 at 06:59:16PM -0400, Lennart Sorensen wrote:
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
On Thu, Apr 05, 2007 at 06:59:16PM -0400, Lennart Sorensen wrote:
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
On Thu, Apr 5, 2007 at 19:08:03 -0400, Lennart Sorensen wrote:
The other minor problems was the netscape navigator 4.77 packages
breaking the x.org /usr/X11R6 upgrade.
Do you know the exact name of the old package that caused this problem?
Thanks,
Julien
signature.asc
Description: Digital
17 matches
Mail list logo
