Guus Sliepen <[EMAIL PROTECTED]> writes: > I had the impression that since amd64 is a release architecture, such > bugs should be grave, but I might be mistaken. That it is a known bug in > the Soya library means you should reassign this bug to soya of course.
Like FTBFS, it is severity "serious" AFAIK (which is still RC btw). No, i won't reassign, like the same bug on Slune, because there's no way to have a reminder displayed on balazar to say "this bug is a soya bug", and i don't want to get plenty of duplicate bugs. > Ok, when I have some time I'll run balazar and slune through gdb on my > amd64 machines and send the results! I've got no amd64 available for tests, and i taggued +help the soya bug since a while without success. So, i'd be glad to get a backtrace, thanks :-) -- Marc Dequènes (Duck)
pgpt2mKac3Vy5.pgp
Description: PGP signature
