Your message dated Wed, 28 May 2025 18:28:27 +0200 with message-id <swzcj6.149d0omtlu...@riseup.net> and subject line has caused the Debian Bug report #1080311, regarding railway-gtk: should handle timezones in a better way to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1080311: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1080311 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: railway-gtk Version: 2.4.0-4 Dear maintainer, if users system has a different timezone then the train operator (common use case when planning a trip in a different country), it's not obvious, which time is used where. E.g. if users system runs in UTC, searching for a connection in Germany (CEST/UTC+2 atm.) at 16 hrs, this is interpreted as 16:00 UTC and it shows a train at 18:00 CEST. This is technically correct, but confusing. Web sites of train operators interprete search time always as local time of the train, no matter which is the time zone of the users system, which is better UX IMHO. Alternatively, times zones could be displayed with the times, but that would clutter the UI. Not so nice on mobile phone. The obvious workaround would be to run railway-gtk with the desired timezone, but it looks like railway-gtk ignores the TZ variable! Cheers
--- End Message ---
--- Begin Message --- Closing since this is an upstream issue they aren't gonna fix; and the train data by the providers is not acknowledging timezones, either.
--- End Message ---
