Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230

 

 

 

Debian Versioning Convention

If none of the specific sub-forums seem right for your thread, ask here.
Post Reply
Message
Author
milomak
Posts: 2160
Joined: 2009-06-09 22:20
Been thanked: 1 time

Debian Versioning Convention

#1 Post by milomak »

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
sudo:
  Installed: 1.8.20p2-1
  Candidate: 1.8.21p2-2
  Version table:
     1.8.21p2-2 500
        500 http://debian.mirror.ac.za/debian testing/main amd64 Packages
        500 http://debian.mirror.ac.za/debian sid/main amd64 Packages
        500 http://debian.saix.net testing/main amd64 Packages
        500 http://debian.saix.net sid/main amd64 Packages
        500 http://ftp.uk.debian.org/debian testing/main amd64 Packages
        500 http://ftp.uk.debian.org/debian sid/main amd64 Packages
 *** 1.8.20p2-1 100
        100 /var/lib/dpkg/status
     1.8.19p1-2.1 500
        500 http://debian.mirror.ac.za/debian stable/main amd64 Packages
        500 http://debian.saix.net stable/main amd64 Packages
        500 http://ftp.uk.debian.org/debian 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.
Desktop: A320M-A PRO MAX, AMD Ryzen 5 3600, GALAX GeForce RTX™ 2060 Super EX (1-Click OC) - Sid, Win10, Arch Linux, Gentoo, Solus
Laptop: hp 250 G8 i3 11th Gen - Sid
Kodi: AMD Athlon 5150 APU w/Radeon HD 8400 - Sid

User avatar
michapma
Posts: 544
Joined: 2008-05-04 20:49
Location: Prague

Re: Debian Versioning Convention

#2 Post by michapma »

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

1.8.19p1-2.1
1.8.20p2-1
1.8.21-1
1.8.21p2-2
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:
https://readme.phys.ethz.ch/documentati ... n_numbers/ (good overview, but not exhaustive)
http://aalvarez.me/blog/posts/debian-pa ... oning.html (discusses an example)
https://tracker.debian.org/pkg/sudo
https://www.sudo.ws/

Post Reply