Opened at 2007-12-22T17:49:00Z

Closed at 2008-01-01T07:01:05Z

#246 closed defect (fixed)

fix deb builders

Reported by: zooko Owned by: zooko
Priority: major Milestone: 0.7.0
Component: packaging Version: 0.7.0
Keywords: Cc:
Launchpad Bug:

Description

As is visible on the BuildBot?, my recent packaging fixes have broken the deb builders.

This is because the "darcsver" executable is now required to create auto-version-stamps.

Change History (4)

comment:1 Changed at 2007-12-22T19:41:33Z by zooko 

./pyutil-1.3.12-py2.5-macosx-10.3-fat.egg/scripts/darcsver.py

Is the executable which, if it gets run with allmydata-tahoe src/allmydata/_version.py as its arguments produces a new _version.py file.

comment:2 Changed at 2007-12-22T19:42:38Z by zooko

If you actually install pyutil, the it is supposed to produce a darcsver executable. Perhaps we need to add the --install-scripts=support/bin flag in order to cause it to appear there.

comment:3 Changed at 2007-12-31T20:52:42Z by warner

FYI, the scripts from foolscap *do* get installed into support/bin/ , without any special arguments in our build-deps rule: 

27:warner@fluxx% ls support/bin/
flogtool*

comment:4 Changed at 2008-01-01T07:01:05Z by zooko

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

So the builders are now (2755f28e76118824) green, but as per #251 we need more packages to be .deb packaged before we can use their results.

Note: See TracTickets for help on using tickets.