On Thu, Jun 28, 2018 at 7:03 PM Jeff Backus <jeff.backus(a)gmail.com> wrote:
Since I've been living under the proverbial rock for a while, are
there any big issues I should know about?
Unless I am mistaken, the only bug that's on the ExcludeArch tracker
and hasn't been reported upstream is micropython. On the other hand
their github issue tracker has a number of open compilation-related
issues, some of them on 32-bit hardware. I don't know if we can help
I'm aware of the kernel build failures issue that recently
happened. By the way, Alex, thank you for your efforts to help get things resolved and to
submit a patch upstream.
Bruno Wolff III ran some test builds and Jerry James pinpointed the
problem and came up with the solution. I just sent it on its way.
Any other thoughts or concerns we should discuss?
Well, since you asked…
On Thu, Jun 21, 2018 at 11:12 AM Kevin Kofler <kevin.kofler(a)chello.at> wrote:
Daniel P. Berrangé wrote:
> Having said all this, the message about brokenness on x86 SIG mailing
> list doesn't appear to be treated with the urgency I think it needs,
> givin the ripple effect it has from a critical path package. There were
> a few messages the day after it was reported, and then nothing until
It is pretty clear that the x86 mailing list is just a fake put up to keep
the architecture running. Just look at the ridiculously low activity at:
This month's activity is unusually high because the "F29 System Wide Change:
i686 Is For x86-64" thread (i.e., the discussion on enabling SSE2) was
mostly cross-posted from this list (devel) to that list (x86). But otherwise
this is little more than a Potemkin village. There is very little going on
behind the façade.
I've seen people get involved with x86 bugs, but there is no flow of
information to and fro the mailing list, to discuss issues or ask for
help (I don't do great in that regard either).