On Thu, 16 Nov 2023 at 09:57, Ray Kinsella <raykinsell...@gmail.com> wrote: > > On Wed, 15 Nov 2023 at 22:30, James Addison <j...@jp-hosting.net> wrote: >> >> On Wed, 15 Nov 2023 at 21:57, Ray Kinsella <raykinsell...@gmail.com> wrote: > [...] > I spent a not insignificant amount of time devising this solution, to get > "Debian Support" > After a few false starts and missteps, eventually I came up with LibX1000 > which was a pretty effective fix IMHO. > > When I started sharing it around with the Debian & Kernel folks - the > response was pretty clear. > "This is a mess, Intel should just fix the bug ... " - which honestly in > retrospect was the right thing to do.
Yep; frustrating though it can be, pushing back to figure out the origins of bugs and resolve them there is likely the way to free up enough developer and maintainer time, and to improve hardware and software quality enough, to reach Reliable Technology Utopia.. should be any day now :) >> > It's been a long time since Intel manufactured the X1000 / Quark, I am not >> > sure how many are left in the wild. >> > Do you think this is something that Debian might want to package and ship? >> >> I should admit that I'm not a Debian maintainer or developer, just a >> passerby who attempts to make progress on bugs that interest to me >> (possibly to the annoyance of actual DMs/DDs), so my opinion is >> somewhat external (i.e.: take with a grain of salt). > > > Thrilled that you reached out about it. I've been thinking more about how to improve the chances that the package could be accepted into Debian -- my suggestion would be to rebuild it and upload it to the mentors[1] portal, where it can (hopefully) receive review. I've considered uploading it myself, but I don't have hardware to test the results on, so I'd be navigating without a way to test the results. From personal experience attempting packaging: the mentoring guidelines and making sure to run lintian checks are both worthwhile. Even so there'd be no guarantee of review or upload acceptance -- and unfortunately the same test-hardware limitation probably applies to most reviewers -- so I don't know whether it'd be worth your time, but in my mind it's possible that someone attempts to install Debian on an X1000 platform in future, learns of this bug, and then in a hypothetical future _might_ find libx1000 in the archive, and then be grateful for the availalble fix. (after re-reading your blog-post, I think that there could technically still be rare cases where the bug appears despite the package being installed -- the mention of 98% of cases handled -- but even so, a mostly-usable system compared to a completely useless one seems like a big improvement) [1] - https://mentors.debian.net/
