Accepted linux-restricted-modules-2.6.10 2.6.10-2 (source)

[Colin Watson]

On Fri, Jan 07, 2005 at 09:52:58AM -0800, Matt Zimmerman wrote:
> On Fri, Jan 07, 2005 at 05:32:08PM +0000, Daniel Stone wrote:
> > On Fri, Jan 07, 2005 at 09:16:12AM -0800, Matt Zimmerman wrote:
> > > Someone please fix this package so that it doesn't let you make this mistake
> > > (uploading a new version without incrementing these); we have all made it
> > > and will continue to make it again and again.
> > 
> > The problem is that we have namespace collision with the nvidia-glx
> > package; 1.0.6629-x is overloaded, for values of x that do not
> > differentiate us.  And everything has different versions anyway.  I
> > think the best strategy would just be to institute beatings for everyone
> > that forgets (*ahem*).
> 
> No, it really is unreasonable to have to remember to update the version
> number in three places whenever this package is uploaded.
> 
> If we can't eliminate that requirement, we need to at least cause the
> package to emit a LOUD WARNING if it notices that you didn't fulfill it.

That could be done by, for example, writing out a file in the clean
target containing the head changelog version and the current values of
nvidiaminor and atiminor. Before doing that, it would check the current
values of version/nvidiaminor/atiminor and see if only some of them
match what's in that file, and if so bail out.

-- 
Colin Watson                                    [cjwatson at canonical.com]