when built from a github download zipfile, tahoe --version prints "allmydata-tahoe: unknown [unknown: unknown]" #2321

New Issue

tahoe-lafs · 2014-10-16T22:38:31Z

daira commented

2014-10-16 22:38:31 +00:00

In /tahoe-lafs/trac-2024-07-25/issues/7299#comment:96056 sly wrote:

After [has]it finally been built, on a command "bin\tahoe --version" it outputs:

allmydata-tahoe: unknown [unknown]unknown:
foolscap: 0.7.0
pycryptopp: 0.6.0.1206569328141510525648634803928199668821045408958
zfec: 1.4.22
Twisted: 11.0.0
Nevow: 0.10.0
zope.interface: unknown
python: 2.7.8
platform: Windows-7-6.1.7601-SP1
pyOpenSSL: 0.13.1
simplejson: 3.6.4
pycrypto: 2.4.1
pyasn1: 0.1.7
mock: 1.0.1
setuptools: 0.6c16dev5

Is it ok? quickstart guide says that it should output some "the right version number".

In [/tahoe-lafs/trac-2024-07-25/issues/7299](/tahoe-lafs/trac-2024-07-25/issues/7299)#[comment:96056](/tahoe-lafs/trac-2024-07-25/issues/2321#issuecomment-96056) sly wrote: > After [has]it finally been built, on a command "bin\tahoe --version" it outputs: > > **allmydata-tahoe: unknown [unknown]unknown:** > foolscap: 0.7.0 > pycryptopp: 0.6.0.1206569328141510525648634803928199668821045408958 > zfec: 1.4.22 > Twisted: 11.0.0 > Nevow: 0.10.0 > zope.interface: unknown > python: 2.7.8 > platform: Windows-7-6.1.7601-SP1 > pyOpenSSL: 0.13.1 > simplejson: 3.6.4 > pycrypto: 2.4.1 > pyasn1: 0.1.7 > mock: 1.0.1 > setuptools: 0.6c16dev5 > > Is it ok? quickstart guide says that it should output some "the right version number".

tahoe-lafs added the

labels 2014-10-16 22:38:31 +00:00

tahoe-lafs added this to the undecided milestone 2014-10-16 22:38:31 +00:00

daira commented

2014-10-16 22:41:20 +00:00

No, that's unexpected. Please paste the output of the following commands:

bin\tahoe --version-and-path
type src\allmydata\_version.py

No, that's unexpected. Please paste the output of the following commands: ``` bin\tahoe --version-and-path type src\allmydata\_version.py ```

daira commented

2014-10-16 22:52:33 +00:00

Ah, never mind, I can reproduce it on my machine, using the zipfile downloaded from https://github.com/tahoe-lafs/tahoe-lafs/archive/master.zip.

The first line of tahoe --version-and-path also gives an unknown version with the correct path (e.g. allmydata-tahoe: unknown [unknown]unknown: ([...]/tahoe-lafs-master/src)). src/allmydata/_version.py does not exist.

It appears that the github download .zip does not contain the .git directory, so I don't think this is fixable. We'll just have to avoid telling people to use that download method (or take into account that they'll get a Tahoe build that doesn't know its version).

Ah, never mind, I can reproduce it on my machine, using the zipfile downloaded from <https://github.com/tahoe-lafs/tahoe-lafs/archive/master.zip>. The first line of `tahoe --version-and-path` also gives an unknown version with the correct path (e.g. `allmydata-tahoe: unknown [unknown]unknown: ([...]/tahoe-lafs-master/src)`). `src/allmydata/_version.py` does not exist. It appears that the github download `.zip` does not contain the `.git` directory, so I don't think this is fixable. We'll just have to avoid telling people to use that download method (or take into account that they'll get a Tahoe build that doesn't know its version).

tahoe-lafs added the

wontfix

label 2014-10-16 22:52:33 +00:00

daira closed this issue

2014-10-16 22:52:33 +00:00

tahoe-lafs added

and removed

labels 2014-10-16 22:54:27 +00:00

tahoe-lafs changed title from ~~bin\tahoe --version prints "allmydata-tahoe: unknown [unknown: unknown]"~~ to when built from a github download zipfile, tahoe --version prints "allmydata-tahoe: unknown [unknown: unknown]"

2014-10-16 22:54:27 +00:00

zooko commented

2014-10-17 01:24:38 +00:00

Doesn't this mean we need to fix our building of .zip files to include the .git dir in them, or else stop building .zip files? Or what?

Doesn't this mean we need to fix our building of `.zip` files to include the `.git` dir in them, or else stop building `.zip` files? Or what?

daira commented

2014-10-17 01:35:46 +00:00

This doesn't affect the .zip files we build as sdists; only the ones created by the "Download ZIP" button on github.

daira commented

2014-10-17 01:45:38 +00:00

Hmm, I was going to link to a snapshot zipfile in https://tahoe-lafs.org/source/tahoe-lafs/snapshots/ to demonstrate that it doesn't have this problem, but that directory doesn't contain any snapshots built after June 26 2013.

Hmm, I was going to link to a snapshot zipfile in <https://tahoe-lafs.org/source/tahoe-lafs/snapshots/> to demonstrate that it doesn't have this problem, but that directory doesn't contain any snapshots built after June 26 2013.

daira commented

2014-10-17 02:03:31 +00:00

Replying to daira:

Hmm, I was going to link to a snapshot zipfile in https://tahoe-lafs.org/source/tahoe-lafs/snapshots/ to demonstrate that it doesn't have this problem, but that directory doesn't contain any snapshots built after June 26 2013.

... possibly due to #2315.

Replying to [daira](/tahoe-lafs/trac-2024-07-25/issues/2321#issuecomment-96063): > Hmm, I was going to link to a snapshot zipfile in <https://tahoe-lafs.org/source/tahoe-lafs/snapshots/> to demonstrate that it doesn't have this problem, but that directory doesn't contain any snapshots built after June 26 2013. ... possibly due to #2315.

Sign in to join this conversation.