Afternoon all. Popping in from Mylar. We currently don't have the ability to merge into master/publish releases, so have moved to an interim model where python3-dev is considered the "stable" branch, and we'll be using a new branch for unstable. There's a fairly key fix in the python3-dev branch at the moment where the year rollover to 2026 has broken a couple of sections of the app. I also spotted that your install script uses a python 3.12 environment which isn't supported by Mylar (upgrade work currently ongoing to resolve that). How do you want these sorts of problems tracked? Just throw an issue up on the repo, or use discussions for an enhancement?
#Mylar Branch Changes
fast badge
spark ore
This is one of the scripts that hasn't been refactored for a long time. Ultimately, we don't care which branch it is, because we pull the tarballs from the releases and don't get the data via git pull or similar. This makes us branch-independent.
Just open a task with further information. However, we have converted almost 100% of our repo to uv, as python kept causing problems (EXTERNAL_MANAGED).
fast badge
Slight challenge with pulling from releases - the guy we currently have with the most elevated access on the repo doesn't have that ability. We're hoping the core maintainer will reappear, but trying to keep things moving in the meantime.
spark ore
that sounds... like a community-fork is needed 😄