https://bugzilla.redhat.com/show_bug.cgi?id=1169966 --- Comment #42 from Jan Chaloupka <jchaloup@xxxxxxxxxx> --- Ahh, rkt depends on k8s.io/kubernetes/pkg/api/resource which is one of those packages that are changing all the time and can not provide stable dependency. >From that reason, rkt can not be built from de-bundled dependencies. As per point 3 in [1]: "All packages whose upstreams have no mechanism to build against system libraries may opt to carry bundled libraries, but if they do, they must include Provides: bundled(<libname>) = <version> in their RPM spec file." rkt package could be partially built from bundled and partially from debundled. However, at the end some dependencies has to be bundled. The closest kubernetes commit with the required k8s.io/kubernetes/pkg/api/resource is bbb447916674cc4bba3ad1e98414af4de356f9d6 from 2015-02-02. Since that time there have been changes in the resource package and we can predict there will be others changing its functionality. As the required commit does not belong to versioned release and even if at the moment it would work to build rkt with kubernetes as a dependency, in future there is a high chance of bundling it anyway. At the same time the currently packaged commit of kubernetes can introduce improper and unexpected functionality. Thus it is impossible to built rkt from de-bundled dependencies and at the same time keep rkt stable. We can keep the current dependencies open until we have sufficient tooling which would tells us how much de-bundling is needed. [1] https://fedorahosted.org/fesco/ticket/1483#comment:17 -- You are receiving this mail because: You are on the CC list for the bug. You are always notified about changes to this product and component _______________________________________________ package-review mailing list package-review@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/package-review