Hi, Bálint Réczey a écrit le 26/02/2020 à 18:24 : > Control: tags -1 help > Control: block -1 by 851663 > > Hi Gilles, > > Bálint Réczey <balint@balintreczey.hu> ezt írta (időpont: 2020. febr. > 25., K, 23:32): >> >> Hi, >> >> Gilles Filippini <pini@debian.org> ezt írta (időpont: 2020. febr. 25., >> K, 23:12): >>> >>> Hi, >>> >>> On Thu, 13 Feb 2020 17:48:57 +0100 Roderich Schupp >>> <roderich.schupp@gmail.com> wrote: >>>> Package: kodi-data >>>> Version: 2:18.5+dfsg1-1~exp0 >>>> Severity: normal >>>> >>>> The default webinterface shows just a header bar, >>>> see attached screenshot. >>>> >>>> The webinterface.default included in the Debian package is >>>> seriously outdated, the current Kodi v18 webinterface >>>> is here: https://github.com/xbmc/chorus2/releases/tag/18.x-2.4.6 >>> >>> d/README.source says: >>>> Kodi replaced the default webinterface in 17.0 beta6 but the new interface contains >>>> many generated files without providing the source for them. The web interface >>>> is temporarily reverted to the one included in beta5 to restore GPL compliance. >>> >>> And Balint filed a related upstream issue: >>> https://github.com/xbmc/chorus2/issues/179 >>> >>> @Balint, from your last comment on this issue it seems the only >>> litigious material left is the screenshots. Are these images requested >>> for running the chorus2 web interface? Couldn't they be removed from the >>> upstream source package until they are fixed? >> >> The upstream source needs a new review to see which files should be dropped. >> If those are just a few images like the screenshots I'm ready to >> create a new +dfsg2 source and ship the new web interface. >> >> Help is very welcome here, since I'm currently busy with other >> packages, but otherwise the kodi 18 packages are close to ready for >> upload to unstable. I'd be happy to help. But I'm not at ease on this very topic. I've just recently discovered kodi. I'm still wondering about installing it. I'd like a fully functionnal server installation, accesed from the webinterface only. > I took a look and the situation did improve license-wise, but Kodi ships > addons/webinterface.default/js/kodi-webinterface.js which is a > minimized version of > https://github.com/xbmc/chorus2 . It needs to be packages separately, > see, the linked RFP bug. > > When Chorus2 is shipped in Debian properly rebuilding it from source > then the kodi package can switch to using it. I have no experience at all packaging such a software. How about first repacking kodi with Chorus2 source tree so it could quickly enter experimental, then splitting it out into a separate package once it is functionnal? Best, _g.
Attachment:
signature.asc
Description: OpenPGP digital signature