Closed philmmanjaro closed 1 year ago
I love how you opened this issue right after this was discovered and conveniently failed to mention it. If you want to collaborate... maybe start by not upstreaming broken things behind our back to our own upstream without as much as a mention?
Seriously, we've always had an open door for distros to collaborate with us. You're based on the same upstream as us, you have the easiest job of any distro, and yet you've done absolutely nothing to work with us. You've just taken our PKGBUILDs, dumped out a broken beta, and on top of that broken a package on our upstream we rely on. I'll spend my time working with distros that actually care, thanks.
The following text is found on your website:
First of all I'm not in the mood to rush out things. It took me some time and 3 image builds to get the OS working on my M1 Air.
How did it happend
Using the latest Version of the PKGBUILD is more or less common if you deal with Arch Linux based software. Also the released version of the image had a disclaimer:
As soon as the Twitter post was out I reacted and pulled the images and installer from sourceforge. They are now stored at an unlisted storage server for internal usage after rebuilding the image with the packages available that time of asahi repo. Before I update my PKGBUILDs I check if those changes also match the binary repos of Asahi. Also the issue with the M1 Ultra was given by our first public release, but was never our target to begin with, as we only list devices we actually have tested on our end with Manjaro ARM.
Additionally Asahi upstream started a while ago to branch their git repos for development, similar to Arch. This helps distros to adopt much easier and follow on what might coming up next.
Sure establishing a connection with Asahi to begin with would have been better. The email I had sent to Marcan on the day I pulled the initial images and explained what had happened was never answered.