Debian Versioning Convention

If none of the more specific forums is the right place to ask

Debian Versioning Convention

Postby milomak » 2017-12-05 20:06

I was doing an upgrade of my laptop and noticed I held back sudo. I reminded myself why
Code: Select all
$ apt-listbugs list sudo
Retrieving bug reports... Done
Parsing Found/Fixed information... Done
serious bugs of sudo (→ ) <Resolved in some Version>
 b1 - #870456 - postinst script is not executed until the end skipping debhelper bits (Fixed: sudo/1.8.21-1)

So I ran apt-cache policy to see where I was in relation to the fix
Code: Select all
# apt-cache policy sudo
  Installed: 1.8.20p2-1
  Candidate: 1.8.21p2-2
  Version table:
     1.8.21p2-2 500
        500 testing/main amd64 Packages
        500 sid/main amd64 Packages
        500 testing/main amd64 Packages
        500 sid/main amd64 Packages
        500 testing/main amd64 Packages
        500 sid/main amd64 Packages
 *** 1.8.20p2-1 100
        100 /var/lib/dpkg/status
     1.8.19p1-2.1 500
        500 stable/main amd64 Packages
        500 stable/main amd64 Packages
        500 stable/main amd64 Packages

I want to believe the the Candidate version has the fix. But I have to be honest the p is throwing me out

Thing is I don't think I've ever seen this before. And I don't think this covers it. Though at some points my eyes may have glazed.
iMac - MacOS and Windows 10 (Bootcamp)/ Debian Sid (External SSD)
Laptop (64-bit) - Debian Sid, Win10,
Kodi Box - Debian Sid
Posts: 1680
Joined: 2009-06-09 22:20

Re: Debian Versioning Convention

Postby michapma » 2017-12-08 11:06

Hi milomak,

I always wanted to know this stuff and never bothered with the details; thanks for the link. I read and googled with a cup of coffee, so no haziness. :)

  • The epoch is not specified for any of the packages of sudo, so by implication they are all 0:.
  • Four upstream versions are mentioned: 1.8.19p1, 1.8.20p2, 1.8.21 (by apt-listbugs) and 1.8.21p2.
  • The debian revisions are listed as being either -1 or -2 in each case.

The package management system compares first the epoch, then the upstream version, then the debian revision. The order of sudo package releases mentioned in your post was thus:
Code: Select all

I was thrown by the p2 when trying to figure it out too, because I was assuming that it was part of the debian revision. In fact, it is part of the upstream version, which you can confirm by following the link to sudo development below.

Finally, you can confirm this order of package releases on the Debian tracker, also linked below. The developer accepted sudo 1.821-1 to unstable on 2017-08-28, then version 1.8.21p2-1 on 2017-09-07. Your current candidate should definitely contain the fix for the postinst script.

Very educational. Good question!

Resources: ... n_numbers/ (good overview, but not exhaustive) ... oning.html (discusses an example)
User avatar
Posts: 535
Joined: 2008-05-04 20:49
Location: Prague

Return to General Questions

Who is online

Users browsing this forum: No registered users and 3 guests