From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1GCwwX-0005rP-SZ for garchives@archives.gentoo.org; Tue, 15 Aug 2006 11:18:46 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.7/8.13.6) with SMTP id k7FBG3qs006905; Tue, 15 Aug 2006 11:16:03 GMT Received: from mxfep02.bredband.com (mxfep02.bredband.com [195.54.107.73]) by robin.gentoo.org (8.13.7/8.13.6) with ESMTP id k7FBDwME022032 for ; Tue, 15 Aug 2006 11:13:58 GMT Received: from explosive.homelinux.org ([85.224.245.192] [85.224.245.192]) by mxfep02.bredband.com with ESMTP id <20060815111357.HSJC11843.mxfep02.bredband.com@explosive.homelinux.org> for ; Tue, 15 Aug 2006 13:13:57 +0200 From: Naga To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] courier-imap not starting! Date: Tue, 15 Aug 2006 13:16:35 +0200 User-Agent: KMail/1.9.4 References: <20060813225757.GA20743@tux2> <44E0A879.6010005@badapple.net> In-Reply-To: <44E0A879.6010005@badapple.net> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200608151316.37933.nagatoro@gmail.com> X-Archives-Salt: 8846393e-eccb-4010-b9e0-6be7b4a0287f X-Archives-Hash: e321cadb6f9ced52db760271f45521b1 On Monday 14 August 2006 18:44, kashani wrote: > Martin Richardson wrote: > > G'Dayy all, > > after an upgrade of baselayout, I noticed that courier-imap and > > courier-imap-ssl was not starting from the init script. I have tracked it > > down to the init script, as this script points to > > /usr/lib/courier-imap/gentoo-courier-imap.rc, and I can start > > courier-imap directly from this script but not the init script... Has > > anyone had this problem, or even have a solution. > > Thankyou. > > Couple or forum threads and a bug about it. Looks like upgrading to the > unstable 4.0.6 is the best workaround. anything >= 4.0.4 should do (4.0.4 should get marked stable ASAP, some arches are done some aren't...) -- gentoo-user@gentoo.org mailing list