问题原文
原帖链接 · cizixs · CC BY-SA 3.0
I'm using debian/Ubuntu, and get confused about versions of packages.
When using dpkg -l command, I get:
ii vim 2:7.3.429-2ubuntu2.1 Vi IMproved - enhanced vi editor
ii vim-common 2:7.3.429-2ubuntu2.1 Vi IMproved - Common files
ii vim-runtime 2:7.3.429-2ubuntu2.1 Vi IMproved - Runtime files
ii vim-tiny 2:7.3.429-2ubuntu2.1 Vi IMproved - enhanced vi editor - compact version
ii virt-what 1.11-1 detect if we are running in a virtual machine
ii w3m 0.5.3-5ubuntu1 WWW browsable pager with excellent tables/frames support
ii watershed 6 reduce superfluous executions of idempotent command
ii wget 1.13.4-2ubuntu1 retrieves files from the web
ii whiptail 0.52.11-2ubuntu10 Displays user-friendly dialog boxes from shell scripts
ii whoopsie 0.1.33 Ubuntu crash database submission daemon
ii wimlib9 1.5.0-1~webupd8~precise Library to extract, create, modify, and mount WIM files
ii wimtools 1.5.0-1~webupd8~precise Tools to extract, create, modify, and mount WIM files
ii wireless-tools 30~pre9-5ubuntu2 Tools for manipulating Linux Wireless Extensions
ii wpasupplicant 0.7.3-6ubuntu2.1 client support for WPA and WPA2 (IEEE 802.11i)
ii x11-common 1:7.6+12ubuntu2 X Window System (X.Org) infrastructure
ii x11-utils 7.6+4ubuntu0.1 X11 utilities
ii xauth 1:1.0.6-1 X authentication utility
ii xbitmaps 1.1.1-1 Base X bitmaps
ii xclip 0.12-1 command line interface to X selections
ii xfonts-encodings 1:1.0.4-1ubuntu1 Encodings for X.Org fonts
ii xfonts-utils 1:7.6+1 X Window System font utility programs
ii xkb-data 2.5-1ubuntu1.3 X Keyboard Extension (XKB) configuration data
ii xml-core 0.13 XML infrastructure and XML catalog file support
rc xpdf 3.02-21build1 Portable Document Format (PDF) reader
ii xterm 271-1ubuntu2.1 X terminal emulator
ii xz-lzma 5.1.1alpha+20110809-3 XZ-format compression utilities - compatibility commands
ii xz-utils 5.1.1alpha+20110809-3 XZ-format compression utilities
ii zabbix-agent 1:1.8.11-1 network monitoring solution - agent
ii zlib1g 1:1.2.3.4.dfsg-3ubuntu4 compression library - runtime
ii zlib1g-dev 1:1.2.3.4.dfsg-3ubuntu4 compression library - development
ii zsh 4.3.17-1ubuntu1 shell with lots of features
The third column is version, but it is all "messed up" in a way I can't understand. I mean, different packages use totally different naming specifications.
Here are the major questions:
- Why do some version numbers have
ubuntuin them, and some not? - What does all the special punctuation
-~+mean? - What are
alpha,build, anddfsg? Can I just use them casually? vimand other packages have2:. What does that mean?- How does "version comparison" work, when version formats can be so different?
Can anyone please explain this to me? Or where can I find an official document?
Thanks in advance.
已采纳解答
原帖链接 · Flup · CC BY-SA 4.0
The Debian Policy Manual has this to say about the version field, which answers some parts of your question:
[Format]1
... The format is:
[epoch:]upstream_version[-debian_revision]The three components here are:
epoch
This is a single (generally small) unsigned integer. It may be omitted, in which case zero is assumed.
Epochs can help when the upstream version numbering scheme changes, but they must be used with care. You should not change the epoch, even in experimental, without getting consensus on debian-devel first.
upstream_version
This is the main part of the version number. It is usually the version number of the original ("upstream") package from which the
.debfile has been made, if this is applicable. Usually this will be in the same format as that specified by the upstream author(s); however, it may need to be reformatted to fit into the package management system's format and comparison scheme.The comparison behavior of the package management system with respect to the
upstream_versionis described below. Theupstream_versionportion of the version number is mandatory.The
upstream_versionmust contain only alphanumerics[6]and the characters"."(full stop),"+"(plus),"-"(hyphen),"~"(tilde)2 and should start with a digit. If there is nodebian_revisionthen hyphens are not allowed.debian_revision
This part of the version number specifies the version of the Debian package based on the upstream version. It may contain only alphanumerics and the characters
"+"(plus),"."(full stop),"~"(tilde) and is compared in the same way as theupstream_versionis.It is conventional to restart the
debian_revisionat 1 each time theupstream_versionis increased.The package management system will break the version number apart at the last hyphen in the string (if there is one) to determine the
upstream_versionanddebian_revision. The absence of adebian_revisionis equivalent to adebian_revisionof 0.Presence of the
debian_revisionpart indicates this package is a non-native package (see Source packages). Absence indicates the package is a native package.[Comparison]1
When comparing two version numbers, first the epoch of each are compared, then the
upstream_versionif epoch is equal, and thendebian_revisionifupstream_versionis also equal. epoch is compared numerically. Theupstream_versionanddebian_revisionparts are compared by the package management system using the following algorithm:The strings are compared from left to right.
First the initial part of each string consisting entirely of non-digit characters is determined. These two parts (one of which may be empty) are compared lexically. If a difference is found it is returned. The lexical comparison is a comparison of ASCII values modified so that all the letters sort earlier than all the non-letters and so that a tilde sorts before anything, even the end of a part. For example, the following parts are in sorted order from earliest to latest:
~~,~~a,~, the empty part,a.[7]Then the initial part of the remainder of each string which consists entirely of digit characters is determined. The numerical values of these two parts are compared, and any difference found is returned as the result of the comparison. For these purposes an empty string (which can only occur at the end of one or both version strings being compared) counts as zero.
These two steps (comparing and removing initial non-digit strings and initial digit strings) are repeated until a difference is found or both strings are exhausted.
5.6.12.1. Epochs should be used sparingly
Note that the purpose of epochs is to cope with situations where the upstream version numbering scheme changes and to allow us to leave behind serious mistakes. If you think that increasing the epoch is the right solution, you should consult debian-devel and get consensus before doing so (even in experimental).
Epochs should not be used when a package needs to be rolled back. In that case, use the
+reallyconvention: for example, if you uploaded2.3-3and now you need to go backwards to upstream 2.2, call your reverting upload something like2.3+really2.2-1. Eventually, when we upload upstream 2.4, the+reallypart can go away.Epochs are also not intended to cope with version numbers containing strings of letters which the package management system cannot interpret (such as
ALPHAorpre-), or with silly orderings.[8]
Further, from the Ubuntu Maintainers Handbook:
The
ubuntustring then marks that whatever follows it is related to changes added in Ubuntu.
The alpha string doesn't seem to have any particular
meaning.
The buildX suffix is used by Ubuntu, e.g. to indicate no change rebuilds.
dfsg refers to a package that has been modified
for compliance with the Debian Free Software Guidelines.
Footnotes3
- 1 Square brackets used as journalists do to indicate additions or significant rewrites.
- 2 For historical completeness, the
upstream_versionwording changed from may to must and the":"(colon) was removed, the last revision allowing it is c. May 2017 - 3 https://meta.stackoverflow.com/questions/258597/formatting-footnotes
摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。
