From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost ([128.39.46.106]) by mx.google.com with ESMTPSA id f5sm16830179lbr.9.2013.11.11.05.33.20 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 11 Nov 2013 05:33:21 -0800 (PST) Content-Type: text/plain; charset=UTF-8 From: Gaute Hope To: Steven Hum Cc: sup-devel Subject: Re: [sup-devel] sup 0.15? In-reply-to: <1384175088-sup-8928@luna> References: <1383637745-sup-2758@qwerzila> <1384097900-sup-2821@luna> <1384112448-sup-9012@qwerzila> <1384175088-sup-8928@luna> Date: Mon, 11 Nov 2013 14:31:57 +0100 Message-Id: <1384176621-sup-7237@qwerzila> User-Agent: Sup/git Content-Transfer-Encoding: 8bit Excerpts from Steven Hum's message of 2013-11-11 14:18:45 +0100: > > Hello Gaute, > > Thanks for pointing me in the right direction. My sources.yaml file was > unchanged from sup 0.14.x but only had one source defined in it. I was > using a startup.rb hook to scan and define my offlineimap sources and > that is where the problem seems to have originated for sup 0.15.0.. > (due to a possible change to the SourceManager.add_source?) > > By eliminating my startup hook and manually defining all my sources, > I was able to reinitialize the xapian mail database and all seems to be > functioning now. > > Guess I will have to poke around to find out why my startup hook > appears to be causing problems. Yes, weird. Perhaps some of the maildir-syncback startup checking has messed up the startup hook? (@ericweikl: poke.) Great that you figured it out. Regards, Gaute