On Monday, September 9, 2019 11:58:08 AM MST vvs vvs wrote:
I would argue that it might be difficult to distinguish work needed
to find
out if it was i686 specific when there already is similar bug on x86_64.
Also, it's difficult to rate bug importance for most users. As I've already
said that I was completely satisfied with the status quo and it was a big
surprise for me to discover that I just won't be able to upgrade to the
next version. Also, this discovery was purely accidental because there is
no announcements anywhere I could see.
Anyway, I would be prepared to fix things myself if such possibility
was
given to me. But alas there is no choice now.
Agreed, most bugs that affect x86 also support x64.