The traditional (old, non-mailman) access to the mailing lists via HTML seems to have chewed itself into oblivion. First it began spitting out old mails then it quit being updated at all. I wish there was a way to read the mailman archives in the same way the old HTML lists were made. It takes 10 clicks with Mailman to get to the archives. The old system was better there. The mailman interface does provide for more anti-spam anonymity, of course. So, if someone could simple hack a short cut here, we wouldn't need both systems and it'd be easier to use (for browsing, that is, which is how I stay informed without subscribing) Sorry about the digression. Hope to see a solution soon. Perhaps I can help if it's just some cgi stuff. Fix: See what happened to the daily parsing script... perhaps it's just a disk capacity issue... no clue, sorry How-To-Repeat: Simply access the old Mailing List Archives on the www.freebsd.org site and click on 'Browse' and then the current year link and pick your favorite list. You'll see they haven't updated in 3 days now except for some garbage on the 26th (old mails)
The mailman access hasn't updated since Jan 26 either. I see three postings on -www complaining about it, and I myself asked on -chat, but I have not seen any response. This is important to many people, and even if it can't be fixed soon, it would be nice if someone would speak up to say, at a minimum, "yes we've noticed the problem." Meanwhile, http://marc.theaimsgroup.com seems to have working archives, and http://www.mail-archive.com archives some lists too.
I need to chime-in here, too, please. The older web interface provides one very important function than all other mail-archive sites I've seen so far: When a 'commit' message comes through, we can click on the links for each file that has been changed, see the 'diff's for that file, and download them as a .gz file (thus keeping tabs etc. intact). I don't know of any other mail-archive site that does this. There have been times when I need such a diff in order to patch something and cannot wait for the CTM deltas (our political firewall won't let us use CVSup, and I need to track -Current for a port I've volunteered to maintain [net/tn3270]). Being without this web interface is a bad thing: I'm screwed, I'm screwed right now, I've been screwed for most of this week, and I will continue to be screwed until this is fixed. So please fix ASAP. Please. -- Paul Seniura System Specialist State of Okla. D.O.T.
On Fri, Jan 30, 2004 at 08:00:34AM -0800, Paul Seniura wrote: > > The older web interface provides one very important function than all other mail-archive sites I've seen so far: > When a 'commit' message comes through, we can click on the links for each file that has been changed, see the 'diff's for that file, and download them as a .gz file (thus keeping tabs etc. intact). > I don't know of any other mail-archive site that does this. http://cvsweb.freebsd.org/ Ceri --
> On Fri, Jan 30, 2004 at 08:00:34AM -0800, Paul Seniura wrote: > > > > The older web interface provides one very important function than all other mail-archive sites I've seen so far: > > When a 'commit' message comes through, we can click on the links for each file that has been changed, see the 'diff's for that file, and download them as a .gz file (thus keeping tabs etc. intact). > > I don't know of any other mail-archive site that does this. > > http://cvsweb.freebsd.org/ > > Ceri I know you're trying to help -- but -- That is not a MAIL ARCHIVE SITE! I know full well about cvsweb. Are you trying to suggest that I keep multiple browser windows running in order to cross-link 'commit' messages to the cvsweb site? All by hand?? Where mistakes can happen??? Sometimes -- many times -- a single commit will consist of patches for a slew of files. Using cvsweb I would need to manually select each level of a path way down finally to reach EACH file I'm needing to see what the diff is -- one-by-one at that. Just get the regular mail-archive site working PLEASE! It does what we've been needing and still need. Look at other lists to see how many people have been complaining that it isn't working properly. Ya don't know how much something like this is missed until it breaks. -- thx, Paul Seniura
On Fri, Jan 30, 2004 at 10:40:12AM -0800, Paul Seniura wrote: > > I know you're trying to help -- but -- > That is not a MAIL ARCHIVE SITE! > I know full well about cvsweb. > Are you trying to suggest that I keep multiple browser windows running in order to cross-link 'commit' messages to the cvsweb site? I'm trying to suggest that you're not as screwed as you might feel. That's all. --
Ceri Davies wrote: > I'm trying to suggest that you're not as screwed as you might feel. Why can't you, or someone else, say something about the problem -- what it is, what's being done, how long fixing it may take, or even a simple acknowledgement that you recognise that a problem exists? This total silence, despite multiple questions, only suggests "we don't care, it's your problem if you depend on the mail archives." Is that the message you want to send? This is not funny. -- Rahul
Responsible Changed From-To: freebsd-www->dhw forwarded to FreeBSD Postmaster who is responsible for the mail archive configuration.
State Changed From-To: open->closed Python on the mailing list machine has been upgraded to solve a problem that was killing the Mailman software. Archiving has been re-enabled but it will take quite a while for the backlog to clear.
On Wed, Feb 04, 2004 at 11:20:03AM -0800, Ken Smith wrote: #> Synopsis: HTML Mailarchive (non mailman interface) hasn't updated since 26.January04 #> #> State-Changed-From-To: open->closed #> State-Changed-By: kensmith #> State-Changed-When: Wed Feb 4 11:17:46 PST 2004 #> State-Changed-Why: #> #> Python on the mailing list machine has been upgraded to solve a problem #> that was killing the Mailman software. Archiving has been re-enabled but #> it will take quite a while for the backlog to clear. I'm not sure if it's part of working on the backlog or if the parsing scripts are having a problem with monthly rotation, but the non-mailman archives only display January's mail currently. It would seem some sort of monthly change routine needs to be triggered manually. I don't know if you want to re-open the PR or not until this is done. #> #> #> http://www.freebsd.org/cgi/query-pr.cgi?pr=62060 -- Yours truly, Shaun D. Jurrens
On Thu, Feb 05, 2004 at 08:57:56AM +0100, Shaun Jurrens wrote: > I'm not sure if it's part of working on the backlog or if the parsing > scripts are having a problem with monthly rotation, but the > non-mailman archives only display January's mail currently. > > It would seem some sort of monthly change routine needs to be > triggered manually. > > I don't know if you want to re-open the PR or not until this is done. It finished processing the backlog some time today, everything should be back to normal at this point. -- Ken Smith - From there to here, from here to | kensmith@cse.buffalo.edu there, funny things are everywhere. | - Theodore Geisel |