Wrong revision number when compiling older revisions

Bug #1297143 reported by Pupu Toivonen
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
HIPL
Won't Fix
Low
Pupu Toivonen

Bug Description

When compiling HIPL, the system automatically fills in a revision number it gets from 'bzr version-info'. This is always the revision number of the latest revision, regardless of which revision the current working tree represents. This happens on both debian and rpm -platforms, likely during generation of the configure script.

Steps to reproduce:
bzr co lp:hipl trunk
cd trunk
bzr revert -r 6419
autoreconf --install
./configure
make deb
ls ..

hipl_1.0.8-6446_amd64.changes hipl_1.0.8-6446.tar.gz hipl-daemon_1.0.8-6446_amd64.deb hipl-doc_1.0.8-6446_all.deb trunk
hipl_1.0.8-6446.dsc hipl-all_1.0.8-6446_all.deb hipl-dnsproxy_1.0.8-6446_amd64.deb hipl-firewall_1.0.8-6446_amd64.deb

Revision history for this message
Pupu Toivonen (scolphoy) wrote :

Doing an actual checkout for the old revision (bzr co -r 6419 lp:hipl trunk_rev6419) gets the revision number right.

Miika Komu (miika-iki)
Changed in hipl:
importance: Undecided → Low
Pupu Toivonen (scolphoy)
Changed in hipl:
status: New → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.