[mcclim-devel] Broken links to mcclim-devel message archive
It looks like links established in the past to messages in the mcclim-devel mailing list are now broken. Any changes to the list archive? McCLIM users maintain a wiki-based bug list at: http://mcclim.cliki.net/Bug Each entry has links to relevant messages in mcclim-devel. But such links are now essentially lost. I also have many such links in my blog, where I periodically report about McCLIM development. Paolo -- Lisp Propulsion Laboratory log - http://www.paoloamoroso.it/log
Paolo Amoroso <amoroso@mclink.it> writes:
It looks like links established in the past to messages in the mcclim-devel mailing list are now broken. Any changes to the list archive?
I foolishly trusted apt-get dist-upgrade to do the right thing a few weeks ago. If it did something thoroughly, it was making a mess of things. We have been cleaning up the radioactive fallout for weeks now, and I presume you are getting your share of it :-| Are the messages still there? If not, I can rebuild the archive etc. Regards, Mario.
Paolo Amoroso <amoroso@mclink.it> writes:
It looks like links established in the past to messages in the mcclim-devel mailing list are now broken. Any changes to the list archive?
McCLIM users maintain a wiki-based bug list at:
Each entry has links to relevant messages in mcclim-devel. But such links are now essentially lost. I also have many such links in my blog, where I periodically report about McCLIM development.
All but the first link on that page (the one from june 2005) seem to be working now. I presume that this particular message has a much higher number now that the old messages (1999 - dez. 2004) reappeared. If you have any further problems with this, let me know. Sorry for this. Regards, Mario.
Mario Mommer <mmommer@common-lisp.net> writes:
Paolo Amoroso <amoroso@mclink.it> writes: [...]
http://mcclim.cliki.net/Bug [...] All but the first link on that page (the one from june 2005) seem to be working now. I presume that this particular message has a much
I think I have fixed this, and everything else looks good. Thanks, Paolo -- Lisp Propulsion Laboratory log - http://www.paoloamoroso.it/log
Paolo Amoroso <amoroso@mclink.it> writes:
Mario Mommer <mmommer@common-lisp.net> writes:
Paolo Amoroso <amoroso@mclink.it> writes: [...]
http://mcclim.cliki.net/Bug [...] All but the first link on that page (the one from june 2005) seem to be working now. I presume that this particular message has a much
I think I have fixed this, and everything else looks good. Thanks,
I spoke too early: http://thread.gmane.org/gmane.lisp.mcclim.devel/657 The links point to different, unrelated messages. Paolo -- Lisp Propulsion Laboratory log - http://www.paoloamoroso.it/log
Paolo Amoroso <amoroso@mclink.it> writes:
I spoke too early:
http://thread.gmane.org/gmane.lisp.mcclim.devel/657
The links point to different, unrelated messages.
Is this a problem with common-lisp.net or with gmane? Personally, I find it a design flaw of the archiver that it indexes depending on message number rather than on message id. The latter one exist for a reason while the former might be incidental (watching the mailman arch tool grind on mailboxes gives the impression that it builds hash tables and then traverses them when writing output, so there may be a nondeterministic element in this.) Regards, Mario.
Mario Mommer <mmommer@common-lisp.net> writes:
Paolo Amoroso <amoroso@mclink.it> writes:
I spoke too early:
http://thread.gmane.org/gmane.lisp.mcclim.devel/657
The links point to different, unrelated messages.
Is this a problem with common-lisp.net or with gmane?
I think it's related to Common-Lisp.net. I have provided the above link to a mcclim-devel message by Robert Goldman that explains the problem. But I have used a Gmane link just for redundancy, not because Gmane is involved. Paolo -- Lisp Propulsion Laboratory log - http://www.paoloamoroso.it/log
Paolo Amoroso <amoroso@mclink.it> writes:
I think it's related to Common-Lisp.net. I have provided the above link to a mcclim-devel message by Robert Goldman that explains the problem. But I have used a Gmane link just for redundancy, not because Gmane is involved.
Ah ok :-) Well, I don't really know what to do. I'll investigate later today or tomorrow. If anyone has an idea, please let me know. Regards, Mario.
participants (2)
-
Mario Mommer -
Paolo Amoroso