On Fri, Aug 18, 2006 at 08:43:31PM +1000, Drew Parsons wrote:
> On Fri, 2006-08-18 at 01:27 -0700, Steve Langasek wrote:
> > On Fri, Aug 18, 2006 at 09:48:38AM +0200, Mohammed Adnène Trojette wrote:
> > > On Wed, Aug 16, 2006, Drew Parsons wrote:
> > > > Package: python-numeric-tutorial
> > > > Version: 24.2-5
> > > > Severity: normal
> > > > python-numeric-tutorial has
> > > > Depends
> > > > --- python (< 2.4)
> > > > --- python (>= 2.3)
> > > A rebuild fixes the issue, but this line should be changed
> > > -Depends: ${python:Depends}, python-numeric (= ${Source-Version}),
> > > python-tk
> > > +Depends: ${python:Depends}, python-numeric (= ${source:Version}),
> > > python-tk
> > > so that the package can be binNMUed.
> > This is wrong, the indicated change would *break* the package so it was no
> > longer installable after a binNMU. ${Source-Version} is a correct, albeit
> > deprecated, variable containing the version of the current build, which is
> > what you want since python-numeric is arch:any.
> Bear in mind this bug is against python-numeric-tutorial (Arch:all),
> not python-numeric (arch:any).
> I don't know why the python depends-version between the two is
> different, when they come from the same source.
Yes, which means this isn't fixable at all using binNMUs, and the package
isn't binNMUable in general no matter which variable it uses in the Depends:
line, because the arch: any package's version will rev without the arch: all
package's Depends: line being rewritten.
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
[EMAIL PROTECTED] http://www.debian.org/
