Izzy
Izzy
Well, as long as the two are there and cannot be added to the "green list" with a proper reason, they'll show up as warnings: 
v17.0 fails RB at IzzyOnDroid as well btw, with a huge diff in `classes2.dex`: [diffs.zip](https://github.com/user-attachments/files/17737492/diffs.zip) Do you still build with JDK-17 as your workflow states? Well, results with JDK-21 were...
Fingers crossed then! As discussed on "the other channel", v17.0 is marked "RB failed" now (afraid we cannot "rescue" that one) – but that "mark" will age out with future...
The Foss one is RB here.
It already passed our second builder, but missed the repo updater by just 15 minutes 🙈 Will be part of the next sync then.
PS: something else is wrong with the updater:  As you can see [in our repo browser](https://apt.izzysoft.de/packages/dev.spiegl.flyingcarpet), there's only one version of flying-carpet available, and that since April already, namely...
> It works as intended. libchecker is "ignored" because it uses non-official version format which cannot be compared to other repositories and cannot mark them outdated. I was rather pointing...
Thanks @AMDmi3! I meanwhile walked the list of 21 entries. 2 of the apps I was able to fix on our end (the one from above, and another one which...
Oops, missed a comment while digging through the list, apologies! So here we go: > F-Droid and Izzy should still be comparable (as long as these use the same appids...
> split rules Just taking a look at it, seems doable. I only need to understand what to put there, then it's a one-time setup – and checking every once...