Hey, Common-lisp.net has been going through a massive migration. As stated[1], the server that cl-net was running on is not longer. This friday was the last day of that server, and I have been working all weekend to try and finish things off. On of the major issues was the email hosting. It was exim4 and mailman for the lists, both of which I did not like. So I spent today migrating to postfix, dovecot and mlmmj for mailing lists[2]. This is the first list that I have tried beyond my own personal tests, so consider this a test post! If you happen to get this, please respond to me. You could also CC the list if you so desire... my hope is that some do and some don't. -- drewc
2013/4/8 Drew Crampsie <drewc@drewc.org>
This friday was the last day of that server, and I have been working all weekend to try and finish things off.
I was suspecting this was the case but now I am reassured that the symptoms I have been witnessing since last Friday are a normal transient situation. Basically, from my point of view, ssh access to common-lisp.net is broken right now (it cannot get pass initial authentication) so no way to maintain/change my project pages. Gitweb access on common-lisp.net is also down. I mention these just to be sure we're all aware of the current (partial) state of things. Is there an ETA on having these back on? (I was also a frequent reader of the http download statistics but that is not as critical...) Thanks for all your work, Jean-Claude Beaudoin
works for me 08.04.2013, 16:06, "Drew Crampsie" <drewc@drewc.org>:
Hey,
Common-lisp.net has been going through a massive migration. As stated[1], the server that cl-net was running on is not longer.
This friday was the last day of that server, and I have been working all weekend to try and finish things off.
On of the major issues was the email hosting. It was exim4 and mailman for the lists, both of which I did not like. So I spent today migrating to postfix, dovecot and mlmmj for mailing lists[2].
This is the first list that I have tried beyond my own personal tests, so consider this a test post! If you happen to get this, please respond to me. You could also CC the list if you so desire... my hope is that some do and some don't.
-- drewc
Does this mean that all the administrative URLs which point to the previous mailman installation will be invalid from now on? I can only speak for myself, but that sucks. -Hans On Mon, Apr 8, 2013 at 2:06 PM, Drew Crampsie <drewc@drewc.org> wrote:
Hey,
Common-lisp.net has been going through a massive migration. As stated[1], the server that cl-net was running on is not longer.
This friday was the last day of that server, and I have been working all weekend to try and finish things off.
On of the major issues was the email hosting. It was exim4 and mailman for the lists, both of which I did not like. So I spent today migrating to postfix, dovecot and mlmmj for mailing lists[2].
This is the first list that I have tried beyond my own personal tests, so consider this a test post! If you happen to get this, please respond to me. You could also CC the list if you so desire... my hope is that some do and some don't.
-- drewc
No, it doesn't mean that at all. "Tomorrow" I should be able to set up the web interface for this mlmmj software, and that other URL will simply redirect to the correct place. Make sense? -- drewc On Mon, Apr 8, 2013 at 5:08 AM, Hans Hübner <hans.huebner@gmail.com> wrote:
Does this mean that all the administrative URLs which point to the previous mailman installation will be invalid from now on? I can only speak for myself, but that sucks.
-Hans
On Mon, Apr 8, 2013 at 2:06 PM, Drew Crampsie <drewc@drewc.org> wrote:
Hey,
Common-lisp.net has been going through a massive migration. As stated[1], the server that cl-net was running on is not longer.
This friday was the last day of that server, and I have been working all weekend to try and finish things off.
On of the major issues was the email hosting. It was exim4 and mailman for the lists, both of which I did not like. So I spent today migrating to postfix, dovecot and mlmmj for mailing lists[2].
This is the first list that I have tried beyond my own personal tests, so consider this a test post! If you happen to get this, please respond to me. You could also CC the list if you so desire... my hope is that some do and some don't.
-- drewc
On Mon, Apr 8, 2013 at 3:20 PM, Drew C <me@drewc.ca> wrote:
No, it doesn't mean that at all. "Tomorrow" I should be able to set up the web interface for this mlmmj software, and that other URL will simply redirect to the correct place.
Make sense?
Makes a lot of sense, as some of the mailing lists are actively used and promoted using mailman URLs. -Hans
Hi. I don't know if this a known/todo issue, but the old links to mailman still don't work. For example: http://common-lisp.net/cgi-bin/mailman/listinfo/asdf-devel http://common-lisp.net/cgi-bin/mailman/listinfo/cl-openid-devel 08.04.2013, 17:21, "Drew C" <me@drewc.ca>:
No, it doesn't mean that at all. "Tomorrow" I should be able to set up the web interface for this mlmmj software, and that other URL will simply redirect to the correct place. Make sense?
-- drewc
On Mon, Apr 8, 2013 at 5:08 AM, Hans Hübner <hans.huebner@gmail.com> wrote:
Does this mean that all the administrative URLs which point to the previous mailman installation will be invalid from now on? I can only speak for myself, but that sucks. -Hans
On Mon, Apr 8, 2013 at 2:06 PM, Drew Crampsie <drewc@drewc.org> wrote:
Hey,
Common-lisp.net has been going through a massive migration. As stated[1], the server that cl-net was running on is not longer.
This friday was the last day of that server, and I have been working all weekend to try and finish things off.
On of the major issues was the email hosting. It was exim4 and mailman for the lists, both of which I did not like. So I spent today migrating to postfix, dovecot and mlmmj for mailing lists[2].
This is the first list that I have tried beyond my own personal tests, so consider this a test post! If you happen to get this, please respond to me. You could also CC the list if you so desire... my hope is that some do and some don't.
-- drewc
Oh, and sending email to clo-devel+help@common-lisp.net brings the following response: "The following options are available: To unsubscribe send a message to: clo-devel+unsubscribe@common-lisp.net To unsubscribe from the digest of this list send a message to: clo-devel+unsubscribe-digest@common-lisp.net To unsubscribe from the "nomail" version this list send a message to: clo-devel+unsubscribe-nomail@common-lisp.net To subscribe to the digest of this list send a message to: clo-devel+subscribe-digest@common-lisp.net To subscribe to the "nomail" version of this list send a message to: clo-devel+subscribe-nomail@common-lisp.net The nomail version of a list means that you are reccognized as a subscriber, but will not get any messages to the list. This is useful when it's necessary to post from several emailaddresses to a subscribers only list. For retrieval of message number N in the archive send a message to clo-devel+get-N@common-lisp.net To contact the list owner, send a message to: clo-devel+owner@common-lisp.net " -- drewc On Mon, Apr 8, 2013 at 6:20 AM, Drew C <me@drewc.ca> wrote:
No, it doesn't mean that at all. "Tomorrow" I should be able to set up the web interface for this mlmmj software, and that other URL will simply redirect to the correct place.
Make sense?
-- drewc
On Mon, Apr 8, 2013 at 5:08 AM, Hans Hübner <hans.huebner@gmail.com>wrote:
Does this mean that all the administrative URLs which point to the previous mailman installation will be invalid from now on? I can only speak for myself, but that sucks.
-Hans
On Mon, Apr 8, 2013 at 2:06 PM, Drew Crampsie <drewc@drewc.org> wrote:
Hey,
Common-lisp.net has been going through a massive migration. As stated[1], the server that cl-net was running on is not longer.
This friday was the last day of that server, and I have been working all weekend to try and finish things off.
On of the major issues was the email hosting. It was exim4 and mailman for the lists, both of which I did not like. So I spent today migrating to postfix, dovecot and mlmmj for mailing lists[2].
This is the first list that I have tried beyond my own personal tests, so consider this a test post! If you happen to get this, please respond to me. You could also CC the list if you so desire... my hope is that some do and some don't.
-- drewc
Drew, you forgot to put the footnotes in! [1] : http://common-lisp.net/news/2013/03/05_the-server-must-move.html [2] : http://alpha.common-lisp.net/news/2013/04/07_the-email-agent-for-common-lisp... Regardless, the list at least worked for this address. -- drewc On Mon, Apr 8, 2013 at 5:06 AM, Drew Crampsie <drewc@drewc.org> wrote:
Hey,
Common-lisp.net has been going through a massive migration. As stated[1], the server that cl-net was running on is not longer.
This friday was the last day of that server, and I have been working all weekend to try and finish things off.
On of the major issues was the email hosting. It was exim4 and mailman for the lists, both of which I did not like. So I spent today migrating to postfix, dovecot and mlmmj for mailing lists[2].
This is the first list that I have tried beyond my own personal tests, so consider this a test post! If you happen to get this, please respond to me. You could also CC the list if you so desire... my hope is that some do and some don't.
-- drewc
Ok, more on this. Today I worked again on email. Now the aliases are all setup properly, so if you have an @common-lisp.net alias that forward to your email account, now would be an excellent time to try it. This is what I did : cd /tiger/home for f in $(ls */.forward); do fwd="`cat $f`" name=`dirname $f` alias="${name}@common-lisp.net" sudo -u postgres psql virtual \ --command "INSERT INTO email_alias (alias, forward_address) \ VALUES ('$alias', '$fwd');" done One of the issues is of course that mailing lists are aliases as well. Right now they are not setup in the database as they should be, but that will be easy to do, so I will do so tomorrow. The other thing I did today was set it up so that the old GNU mailman mailing lists could be easily transferred over. https://github.com/drewc/lisp-mlmmj/blob/master/mailman-%3Emlmmj.lisp is that (hackish) parser that I wrote for python pickle files. I basically did this : for list in `ls ./`; do /usr/lib/mailman/bin/dumpdb $list/config.pck > /home/drewc/lisp-mlmmj/pickle/${list}.pickle ;done Now it is just a simple matter of turning the pickle into the proper shell/SQL scripts. I was going to do that tonight when I realized that aliases were not working at all. So, as of this time tomorrow, all the mail should finally be dealt with. After I have finished that off, I will move on to whatever pops up as needed. Any issues at all, and this would be the time to get my ear. -- drewc On Mon, Apr 8, 2013 at 5:08 AM, Drew C <me@drewc.ca> wrote:
Drew, you forgot to put the footnotes in!
[1] : http://common-lisp.net/news/2013/03/05_the-server-must-move.html [2] : http://alpha.common-lisp.net/news/2013/04/07_the-email-agent-for-common-lisp...
Regardless, the list at least worked for this address.
-- drewc
On Mon, Apr 8, 2013 at 5:06 AM, Drew Crampsie <drewc@drewc.org> wrote:
Hey,
Common-lisp.net has been going through a massive migration. As stated[1], the server that cl-net was running on is not longer.
This friday was the last day of that server, and I have been working all weekend to try and finish things off.
On of the major issues was the email hosting. It was exim4 and mailman for the lists, both of which I did not like. So I spent today migrating to postfix, dovecot and mlmmj for mailing lists[2].
This is the first list that I have tried beyond my own personal tests, so consider this a test post! If you happen to get this, please respond to me. You could also CC the list if you so desire... my hope is that some do and some don't.
-- drewc
On 08-04-2013 13:06, Drew Crampsie wrote:
Common-lisp.net has been going through a massive migration. As stated[1], the server that cl-net was running on is not longer.
One thing I use that stopped working is Apache's server-side includes. Could you enable those? (Alternatively I could use something like PHP, but I'd rather not. ;-)) Cheers, -- Luís Oliveira http://r42.eu/~luis
We use ssi as well. Please provide it. Starting php for every page view just to include the common page elements is overkill. sent from my phone On Apr 10, 2013 10:01 AM, "Luís Oliveira" <luismbo@gmail.com> wrote:
On 08-04-2013 13:06, Drew Crampsie wrote:
Common-lisp.net has been going through a massive migration. As stated[1], the server that cl-net was running on is not longer.
One thing I use that stopped working is Apache's server-side includes. Could you enable those? (Alternatively I could use something like PHP, but I'd rather not. ;-))
Cheers,
-- Luís Oliveira http://r42.eu/~luis
On 10 April 2013 11:04, Erik Huelsmann <ehuels@gmail.com> wrote:
We use ssi as well. Please provide it. Starting php for every page view just to include the common page elements is overkill.
I think the default page template also used them... so many projects have inherited those usages. Just so that there are roses as well: like to new frontpage -- even though given it's placeholder nature! Come to think of it, Abhishek Reddy's Features of Common Lisp might fit on the new page pretty nicely (http://random-state.net/features-of-common-lisp.html) Cheers, -- Nikodemus
Hi Nikodemus, all, On Sun, Apr 14, 2013 at 4:55 PM, Nikodemus Siivola < nikodemus@random-state.net> wrote:
On 10 April 2013 11:04, Erik Huelsmann <ehuels@gmail.com> wrote:
We use ssi as well. Please provide it. Starting php for every page view just to include the common page elements is overkill.
I think the default page template also used them... so many projects have inherited those usages.
There's a problem here: a guy from irc (he's called asedeno) repaired nearly all services (suppored by fare) on the box apart from mail and mailing lists (at least, that's my understanding). Drew set up NGINX, but after some criticism of his approach of the migration/uprade he was doing, he left #common-lisp.net a few days ago and hasn't been seen around since then. The problem this poses is that there's now a vacuum: there's nobody to call shots on which technology is being used and/or replaced (nobody wants to remove things Drew set up, since he sank so much time in it, nor does anybody know of his plans other than vagueries). While some projects are returning to the box again, I'm personally very hesitant: there was no community process involved when Drew decided to replace the mailing list software and the mailer on the box as well as the web server technology. Who decides what's broken because they don't like the technology next time? I'm thinking hard how to solve this, but I don't really see any obvious ways out. Do you? Just so that there are roses as well: like to new frontpage -- even
though given it's placeholder nature! Come to think of it, Abhishek Reddy's Features of Common Lisp might fit on the new page pretty nicely (http://random-state.net/features-of-common-lisp.html)
True, but if the issue is the front page, then why not address that, instead of changing the mailer and the MTA? Bye, Erik.
participants (8)
-
Anton Vodonosov -
Drew C -
Drew Crampsie -
Erik Huelsmann -
Hans Hübner -
Jean-Claude Beaudoin -
Luís Oliveira -
Nikodemus Siivola