[Pkg-octave-devel] Bug#457167: Bug#457167: octave2.9 -- please add atlas3-base-dev to Build-Conflicts.
Thomas Weber
thomas.weber.mail at gmail.com
Thu Dec 20 11:37:41 UTC 2007
Am Donnerstag, den 20.12.2007, 16:02 +0530 schrieb Kumar Appaiah:
> On Thu, Dec 20, 2007 at 11:20:52AM +0100, Thomas Weber wrote:
> > > If you have observed, dpkg-source has started reordering dependencies,
> > > which causes atlas to be pulled into the build environment of
> > > octave2.9 (see #457151 for context). As octave needn't explicitly
> > > depend on atlas (the optional dependency on atlas is enough), I would
> > > request you to please Build-Conflict on atlas3-base-dev.
> >
> > I wonder if we shouldn't drop atlas completely from the build-depends
> > line. Is there a reason why it should be there?
>
> Even if it isn't there, it will be _pulled_ in, because it is the
> first alternate dependency for lapack3-dev, unless it is in
> Build-Conflicts. So, please remove it completely from Build-Depends,
> and add it to Build-conflicts to ensure it isn't used at all.
This sounds like a problem in lapack3-dev. Sorry, but going down that
path means that every package in need of lapack3-dev must add a
build-conflict for a package it doesn't pull in itself. This sounds like
a fix for a problem applied at the wrong level (I may be wrong, of
course).
Thomas
More information about the Pkg-octave-devel
mailing list