A forum for technical support discussion related to Fogbugz.
The behaviour of the FogBugz 7 Linux installer is somewhat unpredictable. You begin the upgrade process hopeful of a speedy upgrade but frequently the installer will decide that it also needs to download the latest FogCreek mono runtime release from media.fogcreek.com.
The duration of this download will vary depending on how both ends the network are feeling at that particular point in time. During the download process, FogBugz is inaccessible because the installer has stopped the FogBugz services.
What I'd prefer is to have the option of downloading the latest release of FogBugz 7 with the latest runtime already included in the tarball. Yes, this will inflate the existing release tarball from ~30 megs to ~80 megs but when for practical purposes the runtime is often downloaded anyway I don't think that's a high cost. The big benefit will be a much more predictable upgrade process - you'll already know that you have all required files for the upgrade and are ready to go.
So I'd recommend two release tarballs:
Wednesday, March 31, 2010
I haven't gotten around to updating to 7 yet, does this mean the downloading all the required components in advance and installing them is a waste time because the installer does it again?
Also, it would be a good idea to provide a complete list of all the required components, the required versions and url for each component so we can download and install them in advance of installing version 7?
There are only two components to FogBugz 7, FogBugz itself and the runtime. You don't need to install the runtime, FogBugz takes care of that. If you want to download everything ahead of time, you need to get the latest appropriate runtime from http://media.fogcreek.com/fogbugz/ and place it in the installer directory.
This topic is archived. No further replies will be accepted.Other recent topics