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?
Might, or might not. Testing is testing, as the name implies. I would not go all the way - it’s likely to introduce more problems instead of fixing one problem.
If what you did now works on your machine there is nothing icky about it, that’s one way testing works. You are testing - mostly one package. If this continues working on your system you might want to introduce it to the backport maintainers.
It’s a pity sway does not have a backport because it would be the solution to the conundrum you perceive.
Oooh, that’s a misunderstanding of both what rolling release and Debian testing means.
To illustrate: rolling release distros can also have testing repos.
Thank you for the input.
Just wrote the maintainers for the sway packages about this! But will probably just keep it like it is for now though.