]] Dimitri John Ledkov > Also which upstream are staying with? systemd upstream git history[4] > has only one branch, which is linear with linear version number > increments, without any stable release branches or other indications > of which patches are stable (or possibly security) bugfixes.
That's generally communicated in the release announcements as well as on the systemd-devel mailing list. > Fedora 19 appears to be packaging patches from v204-stable branch > which I can't find anywhere public. Thankfully it's not a single giant > patch as it's done by RedHat for their kernels, but actually git am > formatted series of 116 patches[5]. Were you unable to find http://pkgs.fedoraproject.org/cgit/systemd.git/log/?h=f19 ? It's where Fedora has all of their packaging.. > Fedora/RPM based distributions are significantly different, thus it is > inevitable that we'll have to maintain a fork of systemd for best > integration into Debian. This does not seem evident from the current > systemd maintainers, which file bugs to disable/remove/override debian > functionality and components with inferior systemd counterparts. Can you provide bug numbers for those allegations, please? > [4] it appears that upstream git is used as packaging basis, instead > of the tarball which has pre-generated documentation and loads of > other files. If you here are talking about the systemd packaging, it seems you've misunderstood something. What are you missing in the source package? -- Tollef Fog Heen UNIX is user friendly, it's just picky about who its friends are -- To UNSUBSCRIBE, email to debian-ctte-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87bnzr5yai....@qurzaw.varnish-software.com