Hi @
basilgello, thanks for the quick response and context. I can very easily use .deb's if you've got them. I also have the ability to compile code, but my build environment is significantly different from Kodi's and would not be easy to reconfigure/adjust to accommodate the Kodi's development environment.
Thanks for the link to the mailing list. I just read through it and while I can't find the part of the conversation that's relevant to the context you provided (i.e., "persuading Debian Release Team to give blanket approval for Kodi and addon uploads to stable without the need to piece-meal the patches"), I do see that one of the Release Maintainers pointed out an incorrect usage of the template, which you fixed with a follow-up submission, at which point there were no further objections from any of the Maintainers. That seemed like a good/positive outcome to me... Maybe the conversation around persuading the Debian Release Team to give blanket approval for Kodi and addon uploads to stable without the need to piece-meal the patches happened somewhere else on the mailing lists not captured in that one specific thread.
Regardless, I'm sure Kodi isn't the only project out there that iterates faster than Debian releases, so I have to imagine this problem has been solved by other projects... I wonder what process they follow to get their updates into Debian? Perhaps we might find similar success if we mirrored the procedures those projects use?
(2024-08-25, 05:37)basilgello Wrote: * Approval from Debian Release Team to upload point releases of Kodi and addons to stable-updates without long delays.
The scope is the same version Debian release has started with, i.e (20.5 for bookworm, 19.5 bullseye etc).
This seems like an admirable goal to me. I'm unfamiliar with the internal release process for Debian. Is this a common/realistic request? Have any others within Debian received similar approvals or is this a big ask?
(2024-08-25, 05:37)basilgello Wrote: * Approval from Debian Fast-Track Team to upload backports of Kodi and addons of one newer version (21.x for bookworm,
20.x for bullseye etc)
This also seems like a reasonable stance and would cover situations where a new Debian version gets released while Kodi is at the tail end of a development cycle (say, with a x.5 release or whatever).
At the end of the day, getting updated versions of Kodi into Debian is a worthwhile goal and I echo the thanks of zuzia-dev on the GitHub thread you posted.