> > I would say this is a serious issue, as it seems there is no backup > > install plan beyond the main download page. tg-setup is not > > working, and > > This message would be a lot more useful if you stated the problem > that you're having with tgsetup (a traceback, perhaps?)
Sorry, was tired I guess. Here is what I was getting: ( substitute the below with 1.0b2 ) Best match: TurboGears 1.0b3dev-r2159 followed by: Can't download TurbogGears egg of 1.0b2 And indeed the file was not at the dowload location. I am able to download again today. > The files are still there if you view source. I just changed the page > so that they're visible again. Yeah I think that's a good idea, I would certainly not have thought to view source to find something ... > > This is, IMHO, a bad problem for Gears adoption. Nobody can tell when > > they will have to deploy in a hurry, and certainly it will turn people > > right off from the framework if they are stuck with no viable way of > > downloading other past versions of other mirrors. Should there perhaps > > not be a sourceforge page with a wack of options including every old > > version available for easy download? If there exists a list of mirrors > > to previous releases, it's not mentioned on the main site in the > > download section. > > I'd like to see tgsetup sprout an option to choose TG versions. Yes, that is important too. I had no idea one could do easy_install TurboGears==1.0b1, as I found no mention anywhere of alternates, only of tgetup. I did try tgsetup --help but didn't see flags for how to choose a version. Personally, after last nights "adventure", I think this is a case where complete tarballs of all dependencies for backdated version up on sourceforge with mirrors is warranted. The other FOSS project I use heavily, Csound, does this. Even though testing is thorough, they are 100% committed to making sure composers can still use old compositions no matter what happens to Csound, and the approach works well. It's saved my ass before a gig when my project happened to be big enough to turn up bugs in new code! As much as we like to poke fun at antiquated Java practices, one thing they take seriously in the "enterprise" world is absolute reliability of delivery methods. Last night I would hate to have been the developer who convinced a pointy haired boss to switch to gears only to say, well, I can't download it right now and I have no idea why. :( > That's a problem I've never had. I develop on a Mac and deploy on > Linux and haven't had any issues with deployment being different from > development. Hmm, I don't know what the root cause of the issues has been. But getting my totally working code on Ubuntu Dapper/mysql5 working on Centos mysql 4 was disastrous. You might have seen the previous posts. It's obviously something wrong with how mysql, formencode, and sqlobject do unicode, but it was a real show stopper. > I hope we can get your issues fixed up quickly. You can still resort > to easy_install TurboGears==1.0b1 if you need to. Thank you for the prompt attention. I'll get back at 'er now. ;) Iain --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to turbogears@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears?hl=en -~----------~----~----~----~------~----~------~--~---
