On 14 May 2013 12:53, David T. Lewis lewis@mail.msen.com wrote:
On Tue, May 14, 2013 at 12:02:08PM +0200, Bert Freudenberg wrote:
On 2013-05-14, at 11:41, Frank Shearar frank.shearar@gmail.com wrote:
On 14 May 2013 10:37, Bert Freudenberg bert@freudenbergs.de wrote:
On 2013-05-14, at 10:55, Tobias Pape Das.Linux@gmx.de wrote:
Am 14.05.2013 um 10:40 schrieb Frank Shearar frank.shearar@gmail.com:
On 14 May 2013 11:02, squeak-dev-noreply@lists.squeakfoundation.org wrote: > > Dave Lewis uploaded a new version of SystemTracing to project SystemTracing: > http://www.squeaksource.com/SystemTracing/SystemTracing-dtl.24.mcz > > ==================== Summary ====================
We're seeing a whole lot of dups. What's wrong with the infrastructure?
frank
This is an indication that the squeaksource.com image was restarted but not saved lately. The "recovery" process collects the mcz's from disk an processes them as if they were commited just now, hence, sends out emails. If someone with access to the image would save it after recovery, these dups wouldn't appear.
Best -Tobias
Seems like as good a time as ever to really do something about squeaksource.com. I'm slacking, sorry. Anyone wants to champion this?
You mean to move the projects (OSProcessPlugin's also spamming us) over to ss3 or SmalltalkHub? Agreed. I'd prefer it if Dave did it (because he's the main committer, not just because I'm lazy), but I'd be willing to do the grunt work, as a semi-last resort.
frank
No, I mean taking over the squeaksource.com server itself.
Is that an option? I'd be all for it.
I have been holding off on moving any of my projects from SqueakSource because I don't know where to put them. I'm not very confident in SmalltalkHub because I have not heard anything to suggest that it will be managed better than the system it replaces. It also does not seem to work behind a corporate firewall with Internet Explorer, not an encouraging sign. SS3 seems to be fine but I don't know if it's intended to be a long term solution.
source.squeak.org is reliable and problem free. If we could have SqueakSource managed in a similar manner it would be great.
For the record: I really do appreciate the service that SqueakSource has provided to the community over the years, including the efforts of the volunteers who have done the support work for it.
We need to pipe up on the squeaksource thread in the Pharo mailing list.
frank
Dave