Mylar Updates

[falo2k]

📌 Task summary

Review the current state of Mylar due to repo changes

📋 Task details

As discussed on discord, the latest published release of Mylar is out of date and has a fairly severe bug in it (triggered by 2026 roll). We don't currently have access to publish new releases, or merge into the master branch. A fork is being considered, but in the meantime we've added a new branch for unstable releases (1000papercuts) and are using the python3-dev branch as the "live" branch. LSIO have created a new docker tag for their image to reflect this (unstable).

I also noticed that you're currently basing your python env off 3.12 - Mylar doesn't strictly support above 3.11 right now, so that may have already been causing some isolated issues. We are aiming to sort that out given it's a pain point for everyone.

Let me know if there's anything you need on our end. I'll remember to keep this updated if any further decisions are taken on the future of the repo / we get back to business as usual on master.

[michelroegl-brunner]

As we dont have the abillity to work with tags or Docker Images, we might consider disabling the App on our Repo for the Moment. We only work with releases (Be it debian packages or tar files), so a workaround with other branches do not work for us. But we can leav this issue open until you regain access to you repo fully or fork it, whatever works for you best. (@community-scripts/contributor, maybe you guys can agree or disagree with me here)

[MickLesk]

agree, i dont switch to git pull - because that will break all current installations.

[falo2k]

Noted. Will swing back once we (hopefully) get things in a better place. We do get a few of your script users in support so it'd be nice to be able to get this back on track one day!

[tremor021]

Noted. Will swing back once we (hopefully) get things in a better place. We do get a few of your script users in support so it'd be nice to be able to get this back on track one day!

Please direct them to our repo if they ever mention that they used our script as means of installing the app. We only direct users to the application official repo if we determine that issue lies somewhere upstream.

Looking forward to resolving this issue

[falo2k]

Wasn't a complaint! Just noting that there is definitely a user base that comes from this, so will make sure it's remembered. We're always happy to help 'em out, plus it can be handy to discover any foibles from particular environments, distros, etc.