aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorWilmer van der Gaast <wilmer@gaast.net>2011-04-22 16:55:21 +0100
committerWilmer van der Gaast <wilmer@gaast.net>2011-04-22 16:55:21 +0100
commitff139f00a0761b1eb6dbd24a26ae231d6b959270 (patch)
tree4fdc118b272a74e0ca7d3ade5ecffb980f072fab
parent2423c939e096ded3bf6a09f5fc70ba2218df85cd (diff)
Don't put an epoch in the Debian "spoofed" version number. Debian's now
barfing on the "1:bzr-devel-xx" version numbers generated by the nightlies builder (due to "bzr" not being a number) so I have to think of something else. The main reason for using epochs was so "bzr-devel-xx" will be considered newer than "3.0.2". ASCII-wise this should be the case even without epochs but okay, it made sense to do this anyway to avoid apple-orange comparisons. Now I'll try switching to package version numbers like 3.0.2+devel+xx-0. No need for epochs then, plus 3.0.3 will actually win over 3.0.2+devel+xx-0 when it should. This does probably mean that people who still have 1:bzr-something installed won't be upgraded automatically, I guess I'll try to let everyone know via Twitter, etc..
-rwxr-xr-xdebian/rules2
1 files changed, 1 insertions, 1 deletions
diff --git a/debian/rules b/debian/rules
index 221587ad..36662860 100755
--- a/debian/rules
+++ b/debian/rules
@@ -94,7 +94,7 @@ binary-common:
dh_installdeb
dh_shlibdeps
ifdef BITLBEE_VERSION
- dh_gencontrol -- -v1:$(BITLBEE_VERSION)-0 -Vbee:Version=1:$(BITLBEE_VERSION)-0
+ dh_gencontrol -- -v$(BITLBEE_VERSION)-0 -Vbee:Version=$(BITLBEE_VERSION)-0
else
dh_gencontrol -- -Vbee:Version=$(shell dpkg-parsechangelog | grep ^Version: | awk '{print $$2}' | sed -e 's/+b[0-9]\+$$//')
endif