Hi,
> > > Heh, I guess we have a different definition of 'properly'.
> > >
> > > pbuilder experimental usage assumes we can install everything from
> > > experimental and get done with it, but I assume there are some
> > > packages which don't go along with each other well.
> > >
> > > But that shouldn't make pbuilder work and cowbuilder not work. I'm
> > > confused.
> >
> > I have the same problem with pbuilder... apt prefers packages from
> > experimental over those from sid, while it should be the contrary,
> > and
> > the dummy package for build-dependencies would make sure the build
> > dependencies are downloaded from experimental when needed (that's
> > what
> > versioned dependencies are for, aren't they?).
>
> Have you tried using 'pbuilder-satisfydepends-experimental' ? (man
> pbuilderrc)
Is pbuilder-satisfydepends-experimental being used when running pbuilder
create and pbuilder update ?
There are two different things on this table we are talking about, to
spell it out:
1. When you want to have a full experimental experience, where you
want everything from experimental.
-> use --distributiuon experimental.
This can be broken since not everything in experimental goes
along well together, although it would be nice if it did.
2. When you want to have a partial experimental experience, where you
only have the necessary packages from experimental.
-> use --distribution sid, and use
pbuilder-satisfydepends-experimental
regards,
junichi
--
dancer@{debian.org,netfort.gr.jp} Debian Project
--
To UNSUBSCRIBE, email to debian-mentors-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact
listmaster@lists.debian.org