Why do some Debian packages have a “+deb7u2” suffix?

I figured the “7u2” part stood for “Debian 7.2” (aka “wheezy”). But I’m wondering if anybody knows the official answer as to why some packages have it and others do not.

Example: http://metadata.ftp-master.debian.org/changelogs//main/g/grub2/grub2_1.99-27+deb7u2_changelog

The only time “+deb7u2” is appended to the version is when the package gets put in the “stable” release. Does this mean that’s a “tag” to indicate a checkin to stable from another repo?

Answers:

Thank you for visiting the Q&A section on Magenaut. Please note that all the answers may not help you solve the issue immediately. So please treat them as advisements. If you found the post helpful (or not), leave a comment & I’ll get back to you as soon as possible.

Method 1

The upload deb7u2 means an update to the version of that package in the Debian 7 release, and one that was targeted directly at that particular release instead of going through the usual Debian development process. These kinds of changes are typically security patches/fixes. The 2 denotes the second such update. Look at any changelog: the numbers after the u increase monotonically.

This is defined in the Debian Developer’s Reference for non-maintainer uploads of security updates (although it applies to all such updates, not just non-maintainer uploads):

If you upload a package to testing or stable, you sometimes need to
“fork” the version number tree. This is the case for security uploads,
for example. For this, a version of the form +debXuY should be used,
where X is the major release number, and Y is a counter starting at 1.
For example, while Wheezy (Debian 7.0) is stable, a security NMU to
stable for a package at version 1.5-3 would have version 1.5-3+deb7u1,
whereas a security NMU to Jessie would get version 1.5-3+deb8u1.

A random example, part of the changelog for the wheezy Django package, follows.

python-django (1.4.5-1+deb7u4) stable-security; urgency=high

  * Stable security update. Fixes CVE-2013-1443. Closes: #723043.
    https://www.djangoproject.com/weblog/2013/sep/15/security/
    - Denial-of-service via large passwords.

 -- Luke Faraone <<a href="https://getridbug.com/cdn-cgi/l/email-protection" class="__cf_email__" data-cfemail="e78b81869586888982a78382858e8689c9889580">[email protected]</a>>  Sun, 15 Sep 2013 16:42:19 -0400

python-django (1.4.5-1+deb7u3) stable-security; urgency=high

  * New upstream security release.
    https://www.djangoproject.com/weblog/2013/sep/
    - Directory traversal with ``ssi`` template tag
  * Correct invalid date on patch headers.

 -- Luke Faraone <<a href="https://getridbug.com/cdn-cgi/l/email-protection" class="__cf_email__" data-cfemail="dbb7bdbaa9bab4b5be9bbfbeb9b2bab5f5b4a9bc">[email protected]</a>>  Thu, 05 Sep 2013 14:14:34 -0400

python-django (1.4.5-1+deb7u2) stable-security; urgency=high

  * No change rebuild. Brings back missing jquery symlinks. Closes: #721397

 -- Raphaël Hertzog <<a href="https://getridbug.com/cdn-cgi/l/email-protection" class="__cf_email__" data-cfemail="7d15180f0907121a3d19181f141c1353120f1a">[email protected]</a>>  Sun, 01 Sep 2013 08:46:49 +0200

python-django (1.4.5-1+deb7u1) stable-security; urgency=high

  * New upstream security release.
    https://www.djangoproject.com/weblog/2013/aug/13/security-releases-issued/
    - Possible cross-site scripting via django.utils.http.is_safe_url
  * Update uploaders field.
  * Patch testcases to use an invalid domain.

 -- Luke Faraone <<a href="https://getridbug.com/cdn-cgi/l/email-protection" class="__cf_email__" data-cfemail="5539333427343a3b30153130373c343b7b3a2732">[email protected]</a>>  Tue, 13 Aug 2013 15:54:19 -0400

python-django (1.4.5-1) unstable; urgency=high

  * New upstream maintenance release dropping some undesired .pyc files
    and fixing a documentation link.
  * High urgency due to former security updates.

 -- Raphaël Hertzog <<a href="https://getridbug.com/cdn-cgi/l/email-protection" class="__cf_email__" data-cfemail="2b434e595f51444c6b4f4e49424a450544594c">[email protected]</a>>  Sun, 24 Feb 2013 10:28:08 +0100


All methods was sourced from stackoverflow.com or stackexchange.com, is licensed under cc by-sa 2.5, cc by-sa 3.0 and cc by-sa 4.0

0 0 votes
Article Rating
Subscribe
Notify of
guest

0 Comments
Oldest
Newest Most Voted
Inline Feedbacks
View all comments
0
Would love your thoughts, please comment.x
()
x