[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: two version numbers on a kernel package?



On Thu, Jan 11, 2007 at 03:58:08PM -0500, Greg Folkert wrote:
> On Thu, 2007-01-11 at 15:26 -0500, hendrik@topoi.pooq.com wrote:
> > On Wed, Jan 10, 2007 at 08:43:31PM -0800, Paul Johnson wrote:
> > > hendrik@topoi.pooq.com wrote:
> > > 
> > > > What does it mean when there are two version numbers on a package.
> > > 
> > > The -number is the Debian patchlevel:  major.minor.patch-debpatch
> > > 
> > So in 
> >   linux-image-2.6.17-2-486_2.6.17-9_i386.deb
> 
> It is Linux Image 2.6.17-2-486 (that is the package name)
> 
> Version is 2.6.17-9  (basically the source version) for the i386
> architecture.
> 
> Hope that helps.
> 
> Here is the DPKG output(sorry for the LONG LINES (made as short as
> possible)
> 
> |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)
> ||/ Name                      Version    Description
> +++-=========================-==========-======================================
> ii  linux-image-2.6.18-1-k7   2.6.18-3   Linux 2.6.18 image on AMD K7
> ii  linux-image-2.6.18-2-k7   2.6.18-5   Linux 2.6.18 image on AMD K7
> ii  linux-image-2.6.18-3-k7   2.6.18-8   Linux 2.6.18 image on AMD K7
> 

------^^^^^^^^^^^^^^^^^^^^^^
this is the package name, which is incremented with each new package
release.


--------------------------------^^^^^^^^

this is the kernel version number with major.minor.patch-debpatch. The
deb patches are not sequential, I assume, because they may not
necessarily release each patch level, or the package versions get
upgraded without a package version increase (why, I don't know. maybe
because the deb patch is not significant enough to call it a new
version of the package). 

So you might install linux-image-2.6.18-1-k7 and get a kernel version
2.6.18-1. Then later, deb will upgrade that package, but not
signifantly enough to change the package version number. So you do an
apt* upgrade and the package linux-image-2.6.18-1-k7 gets upgraded
(we've all seen this -- "you are installing a new version of the same
kernel, you must reboot") so that now you are running the same
package, but the kernel version associated with it is 2.6.18-2. At
some point the put out a whole new kernel package version --
linux-image-2.6.18-2-k7 with a new kernel version, say 2.6.18-3 and so
forth. 

this is all a guess, and the numbers are made up.

A

Attachment: signature.asc
Description: Digital signature


Reply to: