On Sun, 28 Jun 2026 14:15, Johannes Schauer Marin Rodrigues <[email protected]> wrote:
Hi,On Thu, 11 Jun 2026 10:27:19 +0200 Philip Hands <[email protected]> wrote:I think that upgrading to 2.10.1 is all that's needed to fix this.maybe railway-gtk is not really fit for a Debian stable release? We had the same situation with Trixie where the package was fine when Trixie was released and now is RC-buggy and cannot be fixed and a newer version cannot be backported because Rust. What do you think?
Hi,the problem was DB changing their API twice (!). It is still on my agenda to get railway-gtk fixed in stable, by vendoring all railway-provider* crates but building with the regular crates otherwise.
A backport should be possible, albeit requiring a lot of work.I agree this is not ideal; since the package in general is susceptible to API changes breaking it.
The other option would be to remove it from stable; but that is IMO the last option. I'll try to get this in shape for stable update in the next month.
best, werdahias
signature.asc
Description: Digital signature
