Tim wrote:
On Wed, 2016-03-02 at 05:40 +0100, thibaut noah wrote:
> I think i misunderstand things on version numbers, thought
> 2:2.5.0-6 means version 2.2... From what you say i have the feeling
> that i might be wrong about this.
epoch:version
epoch 2 version 2.5.0-6
Go by the decimals, file version something *point* something, has to
have decimals in it. I've never got a grip on why there's hyphens
in the version numbers, though.
In the example above, 2.5.0-6 is ${version}-${release}. The release
field is used in an rpm whenever the package is changed, which might
happen without updating the version. It should typically start at 1
and increment for each new package, resetting to 1 when the version is
updated.
As an example, I package foo-1.0. The rpm version-release will be
1.0-1. After I push it to the repos, someone finds a bug in the
packaging (say I forgot to include a file). When I fix the package,
it will still be foo-1.0, but the release is incremented so it's now
1.0-2. When foo 1.1 or 2.0 is released upstream, the next package
would be 1.1-1 or 2.0-1.
The rpm --queryformat option (--qf for short) might also be useful to
this discussion. If you want to query just the version without the
epoch, release, etc. you can use --qf to do so.
$ rpm -q --qf '%{version}\n' qemu-kvm
2.3.1
All the tags available to the --queryformat option can be shown with
rpm --querytags.
I realize that using rpm -q --qf might not be all that intuitive for
new users, but it is a handy option.
It's also worth noting that repoquery (or now dnf repoquery, I guess)
understands the --qf option (with the addition of the repoid tag to
show the repo where a package was found).
$ dnf -d0 -e0 repoquery --qf '%{name} %{version} (%{repoid})' qemu-kvm
qemu-kvm 2.3.0 (fedora)
qemu-kvm 2.3.1 (@System)
qemu-kvm 2.3.1 (updates)
Hope this helps,
--
Todd
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Liberty is always dangerous, but it is the safest thing we have.
-- Harry Emerson Fosdick