Santiago Vila wrote: >> This was reported 6 years ago (!) and the submitter was asked for more >> information 3 years ago and never replied. >> >> I guess we can safely close this. > > Sorry, but bugs do not fix themselves magically, they are either fixed or not. > > If you think it's fixed, find someone with a powerpc to check it. > If you can't verify that the bug is fixed, then the bug should be > considered open for all purposes. > > BTW; I have a powerpc now, but I didn't three years ago (that's why it > was not easy for me to answer questions about this bug). > > So I will try to test this myself. Thanks for the reminder. I can't see how it helps to have a bug on the BTS open for 6 years without response from the submitter and without action from the maintainer(s) while a ton of upstream releases have been released since then.
If someone is indeed experiencing this bug it may reopen this (or, create a new one, in case he didn't see this one). *Then* we can began investigating this, since we'll have a guinea pig to test this on. It appears that you reopened the bug and you are volunteering to be that guinea pig; that fulfills my expectations, so I won't close it. Be warned though that I will close this again if considerable time passes without action by you or anyone else (including the submitter). Regards, Faidon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
