...

...

...

...

"CT" == Christian Tismer writes:

CT> I still don't have root access to the new machine via CT> ssh. This might be by chance, at least I hope so! Gotta be, because /nobody/ had root access via ssh until moments ago (I have root access to the underlying machine -- outside the chroot jail). I just cat'd my authorized_keys file, as well as pirx's and jwt's to starship's root account, so Chris, Jim Tittsler and I at least should be able to get in as root@starship.python.net. This should let Jim do any necessary unpacking of transferred data. -Barry

Christian Tismer wrote: [This trick got me started again... thanks.]

BTW, you might have ssh access via port 10022, at least for me this works just fine:

ssh -v -l pirx -p 10022 starship.python.net

Marc, you are the first Starship user! If you leave, I consider the project dead. Please don't.

Sorry, Christian, but things got so much out of hand lately, that I think a new site for my stuff will make my users happier. With the help of Andrew I have added redirects for all my files on starship to the new site, so the move should be painless (the old URLs will continue to work). I'm sort of a virtual starship user now ;-) Anyway, starship is not dead -- it has been a great community site for the past three years and I hope that it will now regain the status it had until early this year when things started to go wrong due to the various well-known problems. Let's take this relaunch as a chance to get things moving again. I'd suggest to restart providing everybody in the Python community should with an account on the server to host Python software in return for the annual fee (what was the PSA-membership fee until recently). This should by the sysadmins enough pizza to keep the server running for a looong time ;-) -- Marc-Andre Lemburg ______________________________________________________________________ Company: http://www.egenix.com/ Consulting: http://www.lemburg.com/ Python Pages: http://www.lemburg.com/python/

...

...

...

...

"AK" == Andrew Kuchling writes:

AK> News/mail gatewaying seems fairly seriously broken at the AK> moment; I've noticed many followups to posts that I've never AK> seen. I read c.l.p on news.cnri.reston.va.us, presumably the AK> same machine used for NNTP posting by python.org's Mailman, AK> which would imply that Mailman is at fault. Not necessarily. First, there's certainly nothing in the Mailman log files indicating any problems writing to nntp. Second, Mailman on python.org actually gates messages to ournews.cnri.reston.va.us which is an internal machine on the CNRI network, and should be one hop downstream from news.cnri.reston.va.us (a.k.a. news.alterdial.uu.net). My prediction is that the news is piling up on ournews and there are problems feeding those messages upstream to alterdial. This is not a rare occurance unfortunately. A while back I contacted the CNRI admins about this, but I don't remember hearing a positive resolution. I'm reluctant to point python-list's newserver directly at the alterdial machine because I remember there were worse problems with that approach (like postings actually getting lost as opposed to just sitting behind a log jam -- ournews never expires c.l.py.* postings). Andrew, maybe you can ping the folks at CNRI more directly to at least make sure that there are no problems between ournews<->news? -Barry