Opened at 2014-12-03T22:18:08Z
Closed at 2014-12-03T22:54:09Z
#2347 closed defect (was already fixed)
include git hash in the full version info
Reported by: | zooko | Owned by: | warner |
---|---|---|---|
Priority: | normal | Milestone: | 1.10.1 |
Component: | packaging | Version: | 1.10.0 |
Keywords: | version git | Cc: | warner |
Launchpad Bug: |
Description
When people report interesting bugs like this one: 17:ticket:1939, I'd really like to be able to tell what version of the software they were running. Version numbers do not achieve this goal — witness the fact that the software they are running reports its versions as "allmydata-tahoe: 1.9.2", in the flogtool incident report file:
Application Versions: Nevow: 0.10.0 Twisted: 12.0.0 allmydata-tahoe: 1.9.2 foolscap: 0.6.4 mock: 0.8.0 platform: Linux-debian_7.0-x86_64-64bit_ELF pyOpenSSL: 0.13 pyasn1: unknown pycrypto: 2.6 pycryptopp: 0.6.0.1206569328141510525648634803928199668821045408958 python: 2.7.3 setuptools: 0.6 simplejson: 2.5.2 sqlite3: 2.6.0 twisted: 12.0.0 zfec: 1.4.24 zope.interface: unknown
But there are actually patches applied to it as part of the I2P fork. The solution to this is to include into the version info the current git hash, and the current git dirty-state, when the software is built.
Change History (3)
comment:1 Changed at 2014-12-03T22:18:29Z by zooko
- Owner set to warner
comment:2 Changed at 2014-12-03T22:26:23Z by daira
comment:3 Changed at 2014-12-03T22:54:09Z by daira
- Keywords version git added
- Milestone changed from undecided to 1.11.0
- Resolution set to was already fixed
- Status changed from new to closed
Note: See
TracTickets for help on using
tickets.
Are you sure this is not already fixed?