From owner-freebsd-ports@FreeBSD.ORG Tue Jun 15 13:47:57 2004 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EDB4316A4CE for ; Tue, 15 Jun 2004 13:47:56 +0000 (GMT) Received: from flamingo.mail.pas.earthlink.net (flamingo.mail.pas.earthlink.net [207.217.120.232]) by mx1.FreeBSD.org (Postfix) with ESMTP id DB5C943D41 for ; Tue, 15 Jun 2004 13:47:56 +0000 (GMT) (envelope-from rpratt1950@earthlink.net) Received: from user227.net977.fl.sprint-hsd.net ([69.34.142.227] helo=kt.weeble.com) by flamingo.mail.pas.earthlink.net with smtp (Exim 3.33 #1) id 1BaEHA-0005DB-00; Tue, 15 Jun 2004 06:46:57 -0700 Date: Tue, 15 Jun 2004 09:48:24 -0400 From: Randy Pratt To: Jean-Yves Lefort Message-Id: <20040615094824.422456a9.rpratt1950@earthlink.net> In-Reply-To: <20040615130323.2b2fe391.jylefort@brutele.be> References: <20040613183233.7641f818.adam.mclaurin@gmx.net> <20040614163108.32bbbebe.jylefort@brutele.be> <20040614180010.1ee7a79b.adam.mclaurin@gmx.net> <20040614190129.05afd037.rpratt1950@earthlink.net> <20040615130323.2b2fe391.jylefort@brutele.be> X-Mailer: Sylpheed version 0.9.11 (GTK+ 1.2.10; i386-portbld-freebsd4.10) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit cc: ports@freebsd.org cc: adam.mclaurin@gmx.net Subject: Re: sylpheed-gtk2 updated to 0.9.11 today (PROBLEM!) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Jun 2004 13:47:57 -0000 On Tue, 15 Jun 2004 13:03:23 +0200 Jean-Yves Lefort wrote: > On Mon, 14 Jun 2004 19:01:29 -0400 > Randy Pratt wrote: > > > On Mon, 14 Jun 2004 18:00:10 -0400 > > Adam McLaurin wrote: > > > > > On Mon, 14 Jun 2004 16:31:08 +0200 > > > Jean-Yves Lefort wrote: > > > > > > > On Sun, 13 Jun 2004 18:32:33 -0400 > > > > Adam McLaurin wrote: > > > > > > > > > Just a heads up that sylpheed-gtk2 v0.9.11 was released earlier > > > > > today > > > > > (note that there was no 0.9.10). > > > > > > > > Synopsis: Update port: mail/sylpheed-gtk2 to 0.9.11.20040613 > > > > > > > > State-Changed-From-To: open->closed > > > > State-Changed-By: krion > > > > State-Changed-When: Mon Jun 14 11:36:20 GMT 2004 > > > > State-Changed-Why: > > > > Committed, thanks! > > > > > > > > > > PROBLEM! > > > > > > Something is causing the new sylpheed to delete all the messages in > > > select folders. It seems to not be able to detect the headers properly > > > in some cases (says "No From" and "No Subject", though they ARE in the > > > message source). > > > > > > For example, I have a "word of the day" folder that had ~370 emails in > > > it. As soon as I clicked on it, all but ONE of the mails disappeared! > > > They didn't go to the trash, and no error was given, but they're all > > > gone (but ONE)! This happened in two different folders so far; now I'm > > > scared to open any others! > > > > > > Obviously this is VERY bad. I will attempt to downgrade my sylpheed > > > ASAP, but I think this is just cause to mark the port BROKEN for now. > > > > I had a similar thing happen. I'll almost bet that you had > > sylpheed running while doing portupgrade. I'll also go a bit > > further and bet that the ONE mail that didn't disappear was the > > one that you were last looking at in the mail box where they > > "vanished". > > > > I don't think you lost any mail. Using an xterm, go into your > > mail boxes and you'll probably see the mail. If this is the case, > > then they are there. The mail index just needs to be updated. > > You can do this easily by dragging a mail from another mailbox > > to the one without entries. Sylpheed should rebuild the index > > and your mail will magically reappear. If this isn't the case > > in your situation, please excuse my noise. > > > > This made me add another check step to my portupgrade procedures. > > I check the list of ports to be upgraded and if any of them are > > currently running, I shut them down before updating. Its probably > > not necessary in all cases but this is now what I do. > > This has nothing to do with the fact that Sylpheed was running while > portupgrading. The Sylpheed team fixed a bug in the cache code; it > seems that it broke backwards cache compatibility. > > Before running the upgraded Sylpheed, remove the old cache files: > > find YOUR_MAILBOX_PATH -name '.sylpheed_*' -rm {} \; > > This will "resurrect" your mail. Perhaps this should be added to /usr/ports/UPDATING ? It may have also affected sylpheed-0.9.11 (not -gtk) since that is the version I'm using. That was about 2 weeks ago and moving a mail into the affected mailbox seemed to fix it then. Using the above command would have been a much cleaner method. Thanks for pointing this out. Best regards, Randy