Staging packages are reporting wrong version to the server

Bug #391225 reported by Andreas Hasenack on 2009-06-23
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Landscape Client
High
Free Ekanayaka

Bug Description

Our staging 1.3.2 packages are all reporting the version string "1.0.28" to the server. It should be "1.3.2-<release>" (for example, 1.3.2-0ubuntu0.9.04).

Excerpt from the README.source file inside the debian/ directory:
"""
When making a revision to this package, please update the *last* digit in the
Debian version number. e.g.

  1.0.29-0ubuntu0.9.04.0

should become

  1.0.29-0ubuntu0.9.04.1

In addition, when you build a new package, it would be appreciated if you also
updated landscape/__init__.py to include the entire new version number. This
helps us keep track of exact version of clients in use.
"""

Changed in landscape-client:
assignee: nobody → Free Ekanayaka (free.ekanayaka)
importance: Undecided → High
milestone: none → 1.3.2
Changed in landscape-client:
status: New → In Progress
tags: added: review
Gustavo Niemeyer (niemeyer) wrote :

<niemeyer> free: Can we import the VERSION from __init__ in setup.py?
<niemeyer> free: Or rather, UPSTREAM_VERSION
<free> niemeyer: I guess so
<niemeyer> free: Would be one less constant to maintain manually
<free> niemeyer: good point, I'm on it
<niemeyer> free: +1 on it!

Christopher Armstrong (radix) wrote :

Okay, after some discussion and changes in IRC, I've given this a +1.

Changed in landscape-client:
status: In Progress → Fix Committed
tags: removed: review
Changed in landscape-client:
milestone: 1.3.2 → 1.3.2.1
Changed in landscape-client:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers