From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([69.77.167.62] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1JCGlx-0004tG-U0 for garchives@archives.gentoo.org; Tue, 08 Jan 2008 15:53:50 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 564A8E0C6B; Tue, 8 Jan 2008 15:53:11 +0000 (UTC) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.152]) by pigeon.gentoo.org (Postfix) with ESMTP id 840ABE0C3F for ; Tue, 8 Jan 2008 15:53:10 +0000 (UTC) Received: by fg-out-1718.google.com with SMTP id e21so4060180fga.14 for ; Tue, 08 Jan 2008 07:53:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:to:subject:date:user-agent:references:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:message-id; bh=X4VoYdq0kWs/hKk4ax3839l2UzbazTyrXixTbti30/8=; b=VwNEf4K0WtDl341RGs50xlKGJ6O3ZF4lm6n97eeoD7qHm/VZg4e9tMvhUkz/Njh0WpGssA9luvohexBbz3wzofwOtOgHZ2nK5LNpQtW1c6VGbrvliylaumJnIZIuYcQq7hKAz0L2ulA6vhiSPJQbx6Uc1jf5ykZkQsau8cYMsY0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:subject:date:user-agent:references:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:message-id; b=waTJsU1RxLafSdreaf+RqsO7kTz15nuPs7wYtc+Y56Go/o3a12km/8Qg0ySVioPuymcNyMbDsAWJu/GJg9WLEbesdTwJfsav2kvoIoxkM6LPytHEkLC1IRt0Egtgcy7SMpW2Hq0NGo4kiIBFCgBeaIBkhiflbqHoRd/x10+s8bE= Received: by 10.82.150.20 with SMTP id x20mr37796796bud.37.1199807589174; Tue, 08 Jan 2008 07:53:09 -0800 (PST) Received: from ?10.0.0.3? ( [41.243.198.252]) by mx.google.com with ESMTPS id b33sm31924304ika.5.2008.01.08.07.53.06 (version=SSLv3 cipher=OTHER); Tue, 08 Jan 2008 07:53:08 -0800 (PST) From: Alan McKinnon To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Suddenly emerging unstable packages = why? Date: Tue, 8 Jan 2008 17:48:19 +0200 User-Agent: KMail/1.9.7 References: <9acccfe50801041941kad7befesf29ec89d65fc24c3@mail.gmail.com> <200801071621.50957.alan.mckinnon@gmail.com> <9acccfe50801080635l52782c55x962108c9d45b4b3f@mail.gmail.com> In-Reply-To: <9acccfe50801080635l52782c55x962108c9d45b4b3f@mail.gmail.com> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200801081748.19856.alan.mckinnon@gmail.com> X-Archives-Salt: b04d5e54-3f6a-4308-a4b2-99a9246ecdfb X-Archives-Hash: a5aecc1283af5e2d1bf43c4ece3699a9 On Tuesday 08 January 2008, Kevin O'Gorman wrote: > Hmm, sounds reasonable. Perhaps you mistakenly ran emerge --sync > instead of eix-sync that one time? I've done it myself once or thrice > :-) > > I would not have thought so because it's all done in cron jobs thrice > per week, giving me reports via email. > > However, it is true that emerge sync and eix-update were in two > separate jobs scheduled an hour apart.=A0 It is vaguely conceivable > that they got out of step somehow.=A0 I've unified them, and hope > things go better now. Yeah, that's probably it then. Doing an emerge at randomly selected=20 times will cause i in about 60 or so to fall in that hour window :-) Any particular reason you run two separate jobs and not just eix-sync=20 (which does both in sequence)? alan =2D-=20 Alan McKinnon alan dot mckinnon at gmail dot com -- gentoo-user@lists.gentoo.org mailing list