#1013 closed defect (invalid)

no binary package of pycryptopp for Debian lenny

Reported by: nejucomo Owned by: nejucomo
Priority: major Milestone: undecided
Component: packaging Version: 1.6.1
Keywords: debian pycryptopp install docs Cc:
Launchpad Bug:


Following the directions on the install page http://allmydata.org/source/tahoe-lafs/trunk/docs/install.html leads to the following error in ./setup.py build:

darcs failed:  Not a repository: . (./_darcs/inventory: openBinaryFile: does not exist (No such file or directory))
gcc: error trying to exec 'cc1plus': execvp: No such file or directory
error: Setup script exited with error: command 'gcc' failed with exit status 1
logcmd: Command exits with status 1.

The instructions did not tell me I needed darcs or gcc. This is on a minimal debian lenny (5.04) system.

Attachments (1)

23-0700.python%20.%2Fsetup.py%20build.log (2.4 KB) - added by nejucomo at 2010-04-03T16:59:58Z.
setup.py build log.

Download all attachments as: .zip

Change History (8)

Changed at 2010-04-03T16:59:58Z by nejucomo

setup.py build log.

comment:1 Changed at 2010-04-03T17:15:48Z by nejucomo

It turns out I already had gcc installed, but I needed the build-essential package. I'm not certain what dependency in build-essential was unmet, but the error message wasn't obvious to me.

comment:2 Changed at 2010-04-03T18:31:25Z by zooko

  • Summary changed from Transitive installation dependencies on darcs and gcc not documented. to Transitive installation dependencies on gcc not documented.

You do not need darcs -- that is a bogus error message which has already been fixed in the current release of darcsver.

comment:3 Changed at 2010-04-03T20:07:30Z by zooko

  • Owner changed from somebody to nejucomo
  • Summary changed from Transitive installation dependencies on gcc not documented. to no binary package of pycryptopp for Debian lenny

I opened #1015 (undocumented: attempts to build from source of dependencies such as pycryptopp and pyOpenSSL) to address the documentation of the build-dependencies-from-source behavior.

I'm changing this ticket to be about the fact that the dependency on pycryptopp was not automatically satisfied by a binary package.

What CPU architecture are you using?

comment:4 Changed at 2010-04-04T22:38:22Z by davidsarah

  • Component changed from documentation to packaging
  • Keywords debian pycryptopp install docs added

comment:5 Changed at 2010-06-17T11:00:12Z by arthur

Here is a successfull build of pycrypto for lenny 32bits : http://tahoe-lafs.org/buildbot-pycryptopp/builders/Arthur%20debian-lenny-c7-i386/builds/71

I don't really know where it gets uploaded... here are the "official" packages : http://allmydata.org/debian/dists/lenny/main/binary-i386/

Shouldn't this ticket be closed ?

comment:6 Changed at 2010-06-17T23:51:18Z by zooko

Hm, this builds the .deb:


And the version number is 0.5.19-r704.

This uploads it:


Still saying "python-pycryptopp_0.5.19-r704-1_i386.deb: uploaded"

And then this triggers the apt repo update:


which reports:

update in progress, queueing a new one

However, then I look at the repo:


And I see:

Parent Directory	 	 -	 
	python-pycryptopp_0.5.17-r693-1_i386.deb	31-May-2010 22:42	937K	 
	python-pycryptopp_0.5.17-r692-1_i386.deb	31-May-2010 22:26	937K	 
	python-zfec_1.4.7-1_i386.deb	25-May-2010 00:44	 56K	 
	python-zfec_1.4.6-r343-1_i386.deb	23-May-2010 23:49	 56K	 
	python-zfec_1.4.6-r342-1_i386.deb	23-May-2010 23:45	 56K	 
	python-zfec_1.4.6-r340-1_i386.deb	23-May-2010 23:15	 56K	 
	python-pycryptopp_0.5.17-r689-1_i386.deb	23-May-2010 18:18	937K	 
	python-pycryptopp_0.5.17-r684-1_i386.deb	09-May-2010 23:16	937K	 
	python-zfec_1.4.6-r333-1_i386.deb	27-Jan-2010 06:59	 55K	 
	python-pycryptopp_0.5.17-r683-1_i386.deb	10-Jan-2010 21:37	937K	 
	python-pycryptopp_0.5.17-r682-1_i386.deb	23-Dec-2009 15:43	936K	 
	python-pycryptopp_0.5.17-r681-1_i386.deb	14-Dec-2009 19:37	936K	 
	python-pycryptopp_0.5.17-r680-1_i386.deb	27-Oct-2009 09:48	936K	 

So something didn't work.

comment:7 Changed at 2011-07-22T23:52:59Z by davidsarah

  • Resolution set to invalid
  • Status changed from new to closed

Whatever the problem was with zooko's upload, someone appears to have either fixed it or uploaded more recent versions manually (the most recent release version of pycryptopp there is 0.5.28). Tickets about the automatic upload are #769 and #1257.

Note: See TracTickets for help on using tickets.