Re: foo has reached testing, removing versioned build-depends?
- To: Colin Watson <cjwatson@debian.org>
- Cc: Debian Developers <debian-devel@lists.debian.org>, allomber@math.u-bordeaux.fr, "Marcelo E. Magallon" <mmagallo@debian.org>, ballombe@debian.org
- Subject: Re: foo has reached testing, removing versioned build-depends?
- From: Brian May <bam@debian.org>
- Date: Sun, 20 Apr 2003 10:28:53 +1000
- Message-id: <[🔎] 20030420002853.GA8533@snoopy.apana.org.au>
- Mail-followup-to: Brian May <bam@debian.org>, Colin Watson <cjwatson@debian.org>, Debian Developers <debian-devel@lists.debian.org>, allomber@math.u-bordeaux.fr, "Marcelo E. Magallon" <mmagallo@debian.org>, ballombe@debian.org
- In-reply-to: <[🔎] 20030419145023.GD28373@riva.ucam.org>
- References: <[🔎] 20030419134356.GI5534@seventeen> <[🔎] 20030419145023.GD28373@riva.ucam.org>
On Sat, Apr 19, 2003 at 03:50:23PM +0100, Colin Watson wrote:
> I've read the changelog and the bug report closed by that earlier
> change, and removing the version still makes no sense. If earlier
> versions of debiandoc-sgml produce incorrect output, as reported, then
> the versioned build-dep should be left there, as it will help people
> trying to build with older versions to know what the problem is.
Its not always that black and white.
For instance (and I haven't checked in this case) maybe the version in
stable is OK...
This is something I don't like about build-depends, if a broken version
of a library appears in unstable, then people will set the build-depends
to require the fixed version (or greator), when the version of the
library in stable never had any problems to start off with.
--
Brian May <bam@debian.org>
Reply to: