Hi, everyone. We - the QA group - have recently been researching the feasibility of using zsync to reduce the size of live image downloads. This has hit a roadblock in the form of the problem where both rsync and zsync use forked zlibs rather than linking against the system copy. It seems there was a flurry of activity surrounding this problem in April through June - see: https://fedorahosted.org/fesco/ticket/134 https://bugzilla.redhat.com/show_bug.cgi?id=490140 https://bugzilla.redhat.com/show_bug.cgi?id=478617 https://bugzilla.redhat.com/show_bug.cgi?id=495310 but everything seems to have gone quiet since then. At present we are still in the contradictory and unsatisfactory position of shipping rsync with an internal forked zlib but refusing to accept zsync as a package because it does exactly the same thing. I just wondered if there's a roadmap for where we go from here, or if the issue is just sitting idle waiting for someone to apply a kick to it :) Can you guys clarify what's happening with this? Thanks! (kparal - Kamil Paral - is the QA team member who's been investigating the usefulness of zsync). -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org http://www.happyassassin.net -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
