Repo - auto-mark broken based on version dependency? Defining a maxversion?

Bug Repo - auto-mark broken based on version dependency? Defining a maxversion?

sualfred
Team-Kodi Member

Posts: 3,532
Joined: Oct 2013
Reputation: 357

sualfred
Team-Kodi Member
Posts: 3,532

2019-01-09, 14:40 (This post was last modified: 2019-01-09, 14:40 by sualfred.)

@Rechi

Thanks, I'll give it a try but I think that it won't will solve the problem that it's still listed in the repo. I've tried it with a Jarivs skin on Krypton and Leia, it and it was still listed in the repo and wasn't marked automatically as broken. Installation was not possible, because the GUI version could not be satisfied.

Main: Lancool II Mesh - Ryzen 9 5900x - MSI x570 Unify - Zotac RTX 3080 AMP HOLO - 32GB Trident Z Neo 3600 CL16 - EVO 960 M.2 250GB / EVO 940 250GB / MX100 512GB / Crucial P1 2TB / WD Blue 3D Nand 2TB
Sound: Saxx AS30 DSP - Beyer Dynamic Custom One Pro
TV: Nvidia Shield 2019 Pro- Adalight 114x LEDs - Sony 65XG9505 - Kodi / Emby - Yamaha RX-V683 - Heco Victa 700/101/251a + Dynavoice Magic FX-4
Server: i3 Skylake - 8GB - OMV4 - 22TB Storage

Find

Messages In This Thread

Repo - auto-mark broken based on version dependency? Defining a maxversion? - by sualfred - 2018-12-05, 17:45

RE: Repo - auto-mark broken based on version dependency? Defining a maxversion? - by Rechi - 2019-01-09, 13:46

RE: Repo - auto-mark broken based on version dependency? Defining a maxversion? - by sualfred - 2019-01-09, 14:40