bzr-windows team mailing list archive

[John Arbash Meinel <john@xxxxxxxxxxxxxxxxx>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Some small things I did getting Desolation up and running again.

1) Updated System Files (using Windows Update)

2) Updated Python 2.6.4 to Python 2.6.6

3) Installed Python 2.7.1. We don't use it yet, but if we are going to
keep building bzr for pure-python we should build it for 2.7.

4) Updated the tracked cache
   bzr_bootstrap.bat --source

   This also required updating some pointers for bzr-loom and
   bzr-pipeline. Both of them were pointing at bzr+ssh locations, but I
   really only wanted to have http access so I don't have to worry
   about keeping ssh access tokens on the machine.

   (At one point I was trying to use Pageant, but it was having
   terrible times with $TEMP and EC2's choice to rewrite user
   identities from time to time.)

5) Installed Sphinx 1.0.7:
 cd C:\Python26
 .\python Scripts\easy_install-script.py -U -O1 -Z sphinx

6) Update PATH. A bunch of code now assumes things are in PATH. These
are the paths I had to add so far:

  C:\Python26		# for python.exe
  C:\Python26\Scripts	# for sphinx-build.exe
  C:\Program Files\HTML Help Workshop	# for hhc.exe

7) Install setuptools for python2.7, and a couple small packages
(cython, paramiko). Eventually we may want to make py2.7 the primary
installer, but I'm not going to push for that now.

8) Took a new snapshot of the system. (desolation-2011-07-27)

Remaining issues:

1) buildout still tries to uninstall everything before it comes back and
installs everything. Which I really don't understand. But even worse, it
then fails because "bzr status" is not empty. And it isn't empty because
the *build products* are not ignored by the respective branches.
Specifically, bzr-loom and bzr-pipeline don't ignore "build" and qbzr
and bzr-explorer seem to get new .po files after the build runs.


I really wish I knew what to do here, more than just "rm -rf
build-win32; py build.py" each time. (It seems sucky to build from
scratch always, but worse to have a build command take 5 minutes and
then fail because of an old 'build' directory.)

2) Version number switching from 2.2.3 to 2.2.3-1. Still a pain to do by
hand. Even worse when you have multiple releases being built.

3) Update the installers for bzr-2.4 series. Alexander has some code in
that direction. Probably the big thing is explicitly black-listing
python 2.4/5 from being auto-built by the 2.4 series.

4) bzr-2.2.4 installers. Trunk only was pointing at 2.2.3. However, I
don't know if there is a lot of sense in maintaining the bzr-2.2 series
windows installers. People don't seem to be asking for them much. It
seems to make more sense to make sure that the most recent Stable
releases are available, and the most recent Beta releases. Certainly we
can do the others on an as-needed basis.

I guess bzr-2.2.3 did have 5k downloads, though. So maybe there is more
interest that I'm giving it credit. Though 2.2.3 was released in
January, and 2.3.0 was only released in February. So 2.2.3 was the
most-recent stable in its time.

5) It still takes a surprisingly long time to bring up the EC2 instance.
Maybe the data is on old disks, but I tried bringing one up, it actually
just said "Terminated" after maybe 15min. Then I did it again and it
took probably 30min. Which is pretty annoying on a "I'm going to go
build installers now" sense. But still livable, I guess.

John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk3aaQQACgkQJdeBCYSNAAMB0ACdFshuEdLGrLgRqQoO4Vusn+5M
8UEAoKChszlba+zXBrRtMTOwScIOO8Lb
=Zp/r
-----END PGP SIGNATURE-----