[10:42:44] <wm-bb>	 <siebrand> If your "mw" development environment is dear to you, do not upgrade to macOS 27: *bad CPU type in executable*. Reported in https://phabricator.wikimedia.org/T438004
[11:08:52] <wm-bb>	 <siebrand> Work-around: Use the executable from https://gitlab.wikimedia.org/repos/releng/cli/-/jobs/934593/artifacts/browse/_release/ . At least I can run tests again 🙂 (re @siebrand: If your "mw" development environment is dear to you, do not upgrade to macOS 27: bad CPU type in executable. Reported in https:/...)
[11:09:28] <wm-bb>	 <cvictorovich> macOS 27 is ARM only (re @siebrand: If your "mw" development environment is dear to you, do not upgrade to macOS 27: bad CPU type in executable. Reported in https:/...)
[11:10:14] <wm-bb>	 <cvictorovich> And I’ve been left in the past (re @cvictorovich: macOS 27 is ARM only)
[14:33:59] <wm-bb>	 <jeremy_b> failed to parse (re @cvictorovich: And I’ve been left in the past)
[14:36:40] <wm-bb>	 <cvictorovich> I’ve been left behind the time, as I’m on the final Intel x64 MacBook Pro (re @jeremy_b: failed to parse)
[14:36:56] <wm-bb>	 <cvictorovich> No more system upgrades for me ever!
[14:38:05] <wm-bb>	 <sjoerddebruin> You will still get two years of security updates afaik
[14:38:09] <wm-bb>	 <cvictorovich> Even applies to homebrew: almost everything new must be built automatically from source, instead of installing prebuilt blobs
[14:38:20] <wm-bb>	 <cvictorovich> Major versions (re @cvictorovich: No more system upgrades for me ever!)
[14:39:25] <wm-bb>	 <cvictorovich> Except if I replace it
[14:39:45] <wm-bb>	 <jeremy_b> I guess windows did something similar with requiring TPM?
[14:39:47] <wm-bb>	 <jeremy_b> anyway on Linux I don't have those problems. (re @cvictorovich: No more system upgrades for me ever!)
[14:40:38] <wm-bb>	 <siebrand> After 5 years it may be time for a replacement (re @cvictorovich: And I’ve been left in the past)
[14:42:05] <wm-bb>	 <cvictorovich> Bought in 2020 (re @siebrand: After 5 years it may be time for a replacement)
[14:42:26] <wm-bb>	 <djhartman> Well… with ssd and ram prices….i understand anyone wanting to make that 7 years.
[14:46:00] <wm-bb>	 <siebrand> I got one of my family members a Neo. They’re quite happy with it. Budget of course depends on your requirements and probably also means. (re @djhartman: Well… with ssd and ram prices….i understand anyone wanting to make that 7 years.)
[14:51:15] <wm-bb>	 <siebrand> Anyway. I hope that ARM64 will be fully supported for mw. if that wouldn’t have worked, my development environment would have taken a huge hit, mainly because running tests had become non-trivial.
[14:51:15] <wm-bb>	 <siebrand> Until then there’s the experimental version that has worked for my use case so far. (re @siebrand: Work-around: Use the executable from https://gitlab.wikimedia.org/repos/releng/cli/-/jobs/934593/artifacts/browse/_release/ . At...)
[15:23:58] <wm-bb>	 <fuzheado> Forwarded from fuzheado: FYI, for folks using the Wikipedia-AI-Skills package, some skills have been refactored or rearranged in the last week. 
[15:23:59] <wm-bb>	 <fuzheado> One feature is a skills directory that is browsable and searchable:
[15:24:00] <wm-bb>	 <fuzheado> https://fuzheado.github.io/Wikipedia-AI-Skills/skills-explorer.html
[15:24:02] <wm-bb>	 <fuzheado> And a live graph showing all the skills and their connectedness: 
[15:24:03] <wm-bb>	 <fuzheado> https://fuzheado.github.io/Wikipedia-AI-Skills/skills-network.html
[15:24:05] <wm-bb>	 <fuzheado> Link to the github repo:
[15:24:06] <wm-bb>	 <fuzheado> https://github.com/fuzheado/Wikipedia-AI-Skills