Tobias Heider

I'm afraid that's not quite as easy to reproduce as I'd like it to be. I can try to craft and upload an up-to-date usb version on my mirror if...

Sorry for taking so long to reply. Unfortunately launchpad is down right now but I can a bit of context. The ID indeed references a build on launchpad. My normal...

Already updated to 1.4.14 in our ppa since yesterday, see https://launchpad.net/~ubuntu-asahi/+archive/ubuntu/ubuntu-asahi Updating m1n1 stage 1 will require a `curl https://alx.sh | sh` in macos and can't be done from within...

It probably does already since we use the latest asahi installer (INSTALLER_BASE=https://cdn.asahilinux.org/installer), but I haven't tested it yet.

@devnoname120 indeed. We also package the fix in our ppa as `m1n1 1.4.14-1ubuntu0.1~asahi1`. You can use `apt list --installed | grep m1n1` to see if you are up-to-date.

hmm, looks like the ppa is missing. try `sudo add-apt-repository ppa:ubuntu-asahi/ubuntu-asahi`. This could have been caused by the noble update if you did that early enough.

This is a side effect of your ppa going MIA. You will have to force uninstall `asahi-scripts` and then reinstall it from the new ppa. What happened is: your ppa...

Looks good! You can remove `/etc/apt/sources.list.d/ubuntu-asahi-ubuntu-ubuntu-asahi-noble.sources` now because the ubuntu-asahi meta package added that a second time and you want to keep the one from the package. You can manually...

Oh no, that still seems to be the wrong asahi-scripts version causing the same bug you saw previously... what does `apt list --upgradable` say? On my machine I'm seeing: ```...

Ok, so this seems to be my mistake. Looks like we missed this when moving everything to the new ppa for noble. Should be there in a few minutes.