On Tue, May 30, 2006 at 04:45:53PM +0200, Stefano Zacchiroli wrote: > On Sun, May 28, 2006 at 04:43:02PM -0700, Steve Langasek wrote: > > Are there any packages which depend on ocaml-base-nox-3.09.1, > > ocaml-base-3.09.1, or ocaml-nox-3.09.1 that are not in this list? > Yes, but (assuming Julien's report is correct, not that I doubt, but I > haven't checked it by myself) they have all already been uploaded > (sourceful) as a part of the ocaml 3.09.2 transition. > > Are there any dependencies other than ocaml-nox-3.09.1, > > ocaml-base-3.09.1, and ocaml-base-nox-3.09.1 that necessitate > > rebuilds? > All packages which in some way uses objects produced by the ocaml > compiler needs to be rebuilt. That said, ocaml-base-nox-3.09.1 is a > package that has to be installed for all such packages. You can look for > all packages which (recursively) depends on that, but we of course would > like binNMUs to skip packages which we already uploaded by hand. We of > course do the search in place of you if needed, but I believe it is > precisely what Julien already did. > Does this answer your question? Well, I'm going ahead with the binNMUs because I believe my understanding of the situation is correct, but let me clarify what I'm doing so people at least understand. The ocaml transition requires rebuilds for a number of packages, specifically, those that depend on 3.09.1 packages that no longer exist. There may be some packages in this set that are not binNMU-safe, but there should not be any packages outside this set that *require* rebuilds for the ocaml transition. So knowing which ocaml packages, that are automatically pulled in as dependencies of other packages, have been renamed between 3.09.1 and 3.09.2 should be sufficient to tell me across all architectures which packages need to be binNMUed for the transition. There shouldn't be any recursion at all here in detecting which packages to rebuild -- though there might need to be some for setting dep-waits on other not-yet-built packages. If recursion is needed to identify the packages to be rebuilt, then something's badly broken in the dependencies of those packages... Anyway, the script I'm using for this is smart enough that it won't pick up any false-positives for packages you've already uploaded, because it knows not to try to binNMU packages that are sourcefully out-of-date on an architecture. Which is why, all I should need to know is the list of packages that are being renamed. :) -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. vorlon@debian.org http://www.debian.org/
Attachment:
signature.asc
Description: Digital signature