On 13 May 2016 at 01:01, Potter, Tim (HPE Linux Support) <[email protected]> wrote: > Hi everyone. I had a poke around in the mailing list archives and couldn't > find > anything relevant. I'm looking at backporting Kubernetes to the > jessie-backports > archive but it requires systemd >= 228. Is this going to be an impossible > task? > > Since systemd is a core component of Debian I imagine that it's not going to > be as simple as just uploading the current testing version to stable and > calling > it done. (-: Can anyone provide an idea of how much work a backport would > be?
One problem is that systemd is pretty fast at requiring new versions of dependencies. Kernel should be ok for now, but take look at the current control file[1], and you'll see that many of the build-depends are at versions higher than available in jessie. Moreover, there have been some shuffling of files and dependencies around, (eg, some ifupdown helpers where finally moved back to ifupdown), which increases the number of dependencies >> what is available in jessie (see the Breaks on binary packages). I think the amount of work will be non-trivial. [1] https://anonscm.debian.org/cgit/pkg-systemd/systemd.git/tree/debian/control -- Saludos, Felipe Sateler _______________________________________________ Pkg-systemd-maintainers mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
