Hello all,
I ran into issues using Godot under Debian Trixie and Sway ( 1.10 )
These issues were fixed in 1.11.
Somebody on here recommended me the Debian Backports which look really cool. Unfortunately sway has no Backport as of right now, so I have used the Testing repository for this with a PinPriority so low it does not Update other packages.
This does work and all problems are resolved, my question now is:
When installing sway from testing it has naturally also installed its required dependencies from testing. Does having those dependencies installed which other packages (from stable) might depend on as well introduce weird behavior incompatible issues? I mean they are not in a special testing sandbox nor have some unique namespace, this sets my alarm off right away.
I have used a rolling release distro before and it was surprisingly stable all things considered so I am considering to go full testing on Debian. Does anybody on here do the same?
Yes, pulling the dependencies from testing could introduce issues. Also it might not. Use it as-is if no issues. Eventually the testing packages would become part of stable and you’d be able to remove the package pinning.
The safest way to do this is to backport the packages yourself. That’s taking the source package from testing and building it against stable. If there are no problems with dependencies, this is usually very easy using apt. There’s wiki somewhere describing the process. Sorry, don’t have it on hand.
In the end, if what you did works without obvious issues, keep it till the next major Debian release, then drop it on upgrade.
Thank you for the reply!
I found this guide: https://backports.debian.org/Contribute/ Which is not a step by step guide but the overall process of how things end up on there. I read that I should contact the
unstablemaintainers beforehand so I did just that :)Found it - https://help.ubuntu.com/community/PinningHowto#Recommended_alternative_to_pinning. Should work on Debian.