[tahoe-lafs-trac-stream] [Tahoe-LAFS] #2347: include git hash in the full version info

[Tahoe-LAFS]

#2347: include git hash in the full version info
-----------------------+---------------------------
 Reporter:  zooko      |          Owner:
     Type:  defect     |         Status:  new
 Priority:  normal     |      Milestone:  undecided
Component:  packaging  |        Version:  1.10.0
 Keywords:             |  Launchpad Bug:
-----------------------+---------------------------
 When people report interesting bugs like this one:
 [comment: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.

--
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/2347>
Tahoe-LAFS <https://Tahoe-LAFS.org>
secure decentralized storage