Bug#390888: [Pbuilder-maint] Bug#390888: Full support for experimental
Loïc Minier
lool at dooz.org
Mon Oct 9 07:37:40 UTC 2006
Hi,
On Mon, Oct 09, 2006, Junichi Uekawa wrote:
> > Here's a new version of this patch, which will also pull new packages
> > from experimental, and wont fail if the APT error lists more than one
> > broken Depends.
> Thanks for the patch, have you actually tested it?
Yes, it has a small limitation but I used it extensively to build
pkg-gnome and pkg-evolution for experimental, and it is very useful to
me.
The limitation is that it might select some first build-depends which
is compatible with Build-Depends/Conflicts from unstable, and fail to
install a second build-depend from experimental which conflicts with
the first build-dep/unstable. I have code that parses the APT error as
for the other two APT errors that the patch already parses, but I
didn't find anything sane and safe to do in this case.
One real-life example of this is when you try to build packages which
build-depend on libgnomeui-dev and gtk-dev >= 2.10, the libgtk from
experimental conflicts with the libgnomeui from unstable, and this
fails.
To workaround this limitation, I'm listing more build-depends in the
control than truly required and I'm also bumping some higher than
required.
> I assume this patch is for using experimental dependencies from
> unstable chroots, not the one for
> pbuilder create --distribution experimental
> which creates a comlpetely experimental chroot.
I have no idea how a "completely experimental chroot" looks like, but
when we (pkg-gnome) are uploading to experimental, we try to have the
minimum number of depedencies in experimental. I believe the
experimental buildds do the same. What I wouldn't want for example is
to pull libc6 2.4/2.5 via packages from experimental right now.
Bye,
--
Loïc Minier <lool at dooz.org>
More information about the Pbuilder-maint
mailing list