Re: KDE Gear projects with failing CI (master) (7 January 2025)

2025-01-08 Thread Justin Zobel
Both master and release fixed by jlskuz. On 9/1/25 10:26, Justin Zobel wrote: kdenlive flatpak is failing on master and release branches due to trying to connect to git.sesse.net for the movit repository. However the git server is IPv6 only. I've asked Ben to see if we can get the docker conta

Re: KDE Gear projects with failing CI (master) (7 January 2025)

2025-01-08 Thread Justin Zobel
kdenlive flatpak is failing on master and release branches due to trying to connect to git.sesse.net for the movit repository. However the git server is IPv6 only. I've asked Ben to see if we can get the docker containers that builds run in given IPv6 to resolve this. If we can't, we may need t

Re: Move Breeze to Framework

2025-01-08 Thread Carl Schwan
On Wed, Jan 8, 2025, at 6:24 PM, Nate Graham wrote: > On 1/3/25 8:17 AM, Nicolas Fella wrote: > > Am 30.12.24 um 18:51 schrieb Nate Graham: > >> A long term concern I have is that it's messy and unpleasant to have > >> default styling data scattered across so many places. Ideally we'd be > >> able

Re: Move Breeze to Framework

2025-01-08 Thread Nate Graham
On 1/3/25 8:17 AM, Nicolas Fella wrote: Am 30.12.24 um 18:51 schrieb Nate Graham: A long term concern I have is that it's messy and unpleasant to have default styling data scattered across so many places. Ideally we'd be able to centralize *all* data about a particular style in a single repo, so

Re: Move Breeze to Framework

2025-01-08 Thread Nate Graham
On 12/31/24 4:59 AM, Ingo Klöcker wrote: On Montag, 30. Dezember 2024 18:51:39 Mitteleuropäische Normalzeit Nate Graham wrote: A long term concern I have is that it's messy and unpleasant to have default styling data scattered across so many places. Ideally we'd be able to centralize *all* data

Re: KDE Gear projects with failing CI (master) (7 January 2025)

2025-01-08 Thread Volker Krause
On Dienstag, 7. Januar 2025 22:37:08 Mitteleuropäische Normalzeit Albert Astals Cid wrote: > Please work on fixing them, otherwise i will remove the failing CI jobs on > their 4th failing week, it is very important that CI is passing for multiple > reasons. > > Bad news: 3 repositories started fa