Re: transition binNMUs
On Fri, Jan 13, 2006 at 10:30:01AM +1100, skaller wrote:
> On Thu, 2006-01-12 at 17:21 +0100, Julien Cristau wrote:
> > On Thu, Jan 12, 2006 at 16:08:05 +0000, Stefano Zacchiroli wrote:
> >
> > > On Thu, Jan 12, 2006 at 02:43:01PM +0100, Julien Cristau wrote:
> > > > some packages have been binNMUed by the release team for the 3.09.1
> > > > transition, and so don't need to be reuploaded:
> > >
> > > As I already observed elsewhere all those packages must have an RC bug
> > > filed against them for not respecting the debian ocaml policy.
> > >
> > Well, I still don't understand why this is so wrong in your opinion.
>
> The problem is that *Debian* is broken. The strict dependencies
> are a hack to fix this.
>
> Really we need that library XYZ-3 source package, depending on
> library ABC-5, built with Ocaml-3.09.0-4, should produce binary
> package
>
> XYZ-3-Ocaml-3.09.0-4
<snipped interesting analysis>
Stefano, it is my believe that this is not the problem.
Those packages depend (not build-depend) on the virtual package provided by
ocaml, and since we did make sure that 3.09.1 was installed on the
autobuilders before the binNMUs where done, they will automatically have the
right dependencies added to them.
We could also have the ocaml packages (ocaml-base-nox probably) provide an
ocaml-abi-3.09.1, and have all the ocaml packages depend on it, but i am not
sure it adds much over the ocaml-base-nox dependency we have right now.
It is my believe that all non-broken packages following the guidelines of the
3.09.0 upload will set the ocaml-*-<version> correctly, and it being
automatically detected at build time and the control file filled by
dh_gencontrol and so none of the problems you fear will happen, since a
package built with 3.09.0 and one built with 3.09.1 will not be concurently
installable.
The build dependency is another issue, my impression is that it only needs to
be bumped when there is a source level incompatibity with older versions of
ocaml, so we can in the future be less strict. We used it only to make sure
that a buildd was not building ocaml with the older ocaml packages, and thus
mess everything up. By waiting for the new ocaml to be installed on all
buildds, we don't need to worry about this anymore.
BTW, since we decided to not make ocaml parallel installable (and it poses
problems with the binaries inside the package), we don't need to use the
embedd version in name trick, and using a virtual abi package as we do now is
good enough. It was always my intention to have build-of-the-day, out of CVS
builds in experimental, which would be parallel installable with the main
ocaml, but i didn't find the time for this.
Friendly,
Sven Luther
Reply to: