On Thu, Dec 15, 2011 at 12:53 PM, percious <[email protected]> wrote:
> I think you are missing the point. > Most definitely am not missing it. I firmly believed that I had things working reliably. Now I can see that I did not. I just spent a few hours scouring through distribute, looking at what config files got read, when they got read, and can say that the problem comes from the fact that neither setuptools nor distribute will honor the setup.cfg when it's downloaded. After the package is installed, on a subsequent run of easy_install, is when the file will be read. Of course, this fails to help us when we're doing the initial installation. I know that I swore up and down I had it working in the past. It would appear that I was mistaken, and I never did have it working as I thought I did. I don't know how or why it appeared to work in the past, but I was decidedly wrong. > easy_install tg.devtools is never going to work reliably. The best we can > do is to create a hudson script to test the install daily (hourly?), and > notify us if the install fails. It seems like the last release (2.1.4) may > have missed the critical step of testing the install in a clean environment > before it was shipped, which would have caught this WebOb versioning issue. > Actually, saying "never" is a big no-no in my book. I'm tempted to write up a patch for easy_install, and submit it to setuptools and distribute that would allow this to work the way I expected. Well, maybe not how I expected, but at least to work in a way that supports what we need. Not today, though I have opened a ticket to remind me to work on it ( https://sourceforge.net/p/turbogears2/tickets/135/ ). I'll try to do so for 2.2, so that, maybe, we can reduce the commands to install just down to "easy_install tg.devtools". Furthermore, you're making a pretty big assumption about the testing of the release. That part, above everything else, is what gets under my skin about this email. Here, allow me to show you the release process: http://www.turbogears.org/book/appendices/preprelease.html It's true that I didn't write down the "do a final install from clean", but that will be rectified for the next docs update (which will happen tomorrow when I fix the easy_install commands). However, I can assure you that that step *was* done, and would not have caught *this* problem anyway. How do I know? The problem came about because Pylons 1.0.1 updated the requirement on the version of WebOb. Pylons 1.0.1 was released the day *after* we released 2.1.4. Since everything else was working and looked good, perhaps you can employ your crystal ball to tell us when we're going to get a broken release in the future? Mine was broken when I did this release, I'm sorry. Yes, I'm annoyed by the implications of what you're saying there. I have done everything I can to ensure the release process be smooth, fully documented, maintainable, and reliable, and you pop in after a long time without a message just to say what amounts to "Hey, you guys sucked at this! WTF were you thinking?" On Thu, Dec 15, 2011 at 1:45 PM, Alessandro Molina < [email protected]> wrote: > Just for notice, as the private package index long url has always been > the worst issue of having a private package index I registered a short > domain for that purpose. Now it is possible to install tg using: > > easy_install -i http://tg.gy tg.devtools > easy_install -i http://tg.gy/214 tg.devtools > easy_install -i http://tg.gy/213 tg.devtools > > and so on... > > at least as soon as the dns updates for you :) Alessandro: If you wish, I can easily update tg.org to handle those redirects, and then incorporate updating them into the release process. Let me know. I'll admit I'd prefer it, but I'm not going to demand it. -- Michael J. Pedersen My Online Resume: http://www.icelus.org/ -- Google+ http://plus.ly/pedersen Google Talk: [email protected] -- Twitter: pedersentg -- You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected]. 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.
