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 1JCRDG-0008BI-Nc for garchives@archives.gentoo.org; Wed, 09 Jan 2008 03:02:42 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 7C3EDE0BCA; Wed, 9 Jan 2008 03:00:40 +0000 (UTC) Received: from nz-out-0506.google.com (nz-out-0506.google.com [64.233.162.232]) by pigeon.gentoo.org (Postfix) with ESMTP id D99DAE0BC7 for ; Wed, 9 Jan 2008 03:00:39 +0000 (UTC) Received: by nz-out-0506.google.com with SMTP id s18so43597nze.1 for ; Tue, 08 Jan 2008 19:00:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; bh=Q4CP7VA9Sz4r7Vv0GEIOdwwCGxgv3ixwIjHhB5rfMY4=; b=QVhVSLLeG/dIAlWRzQXT+7XciSJf5ntMSAIrZAnXgi5HqnCmepXnx6L4KRt17kOJQBFLtMCy4SmxAI24razsb2cPgOq+HVxVok4pZ3TXLpYMnNvE2WShoQatUHCs4ZUd398yaZk0rqIBtxm0Ltwu7QQcfZi5WG4NScsVTzgcp1g= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=Exfis2k4tzpRMJu1QpHpyUE0jWDGw+hbU3XDI0u4G8tq5G6iFeowJES6JNi8j8WkkdEEoK8Q7B/fYwAxzrZEBSxOXUX8MMvL3Nrm7K4VGbhh9D+AiKHhjfsvYf+DJ6Yp/I/Qsmcs2E/+Prc8i2wQEavp5nkOUn+BjWfouxvheSE= Received: by 10.142.216.9 with SMTP id o9mr14819wfg.226.1199847638825; Tue, 08 Jan 2008 19:00:38 -0800 (PST) Received: by 10.142.82.18 with HTTP; Tue, 8 Jan 2008 19:00:38 -0800 (PST) Message-ID: <9acccfe50801081900x34eccf6dh811a5443677fd33e@mail.gmail.com> Date: Tue, 8 Jan 2008 19:00:38 -0800 From: "Kevin O'Gorman" To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Suddenly emerging unstable packages = why? In-Reply-To: <200801082347.33212.bo.andresen@zlin.dk> 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: multipart/alternative; boundary="----=_Part_6124_22173822.1199847638772" References: <9acccfe50801041941kad7befesf29ec89d65fc24c3@mail.gmail.com> <200801081748.19856.alan.mckinnon@gmail.com> <9acccfe50801081430m630b547aj6b76f78236820374@mail.gmail.com> <200801082347.33212.bo.andresen@zlin.dk> X-Archives-Salt: c9eac3b8-1e37-4a4c-be52-5270e6a89cf7 X-Archives-Hash: e15c1d342e96ec6afe1d05703f8dbd28 ------=_Part_6124_22173822.1199847638772 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On 1/8/08, Bo =D8rsted Andresen wrote: > > On Tuesday 08 January 2008 23:30:51 Kevin O'Gorman wrote: > > > > However, it is true that emerge sync and eix-update were in two > > > > separate jobs scheduled an hour apart. It is vaguely conceivable > > > > that they got out of step somehow. I've unified them, and hope > > > > things go better now. > [...] > > > Any particular reason you run two separate jobs and not just eix-sync > > > (which does both in sequence)? > > > > Originally, because the output was hard to read I think. And I figured > > that starting them an hour apart would ensure sequence anyway. > > Surely you ran update-eix and possibly diff-eix rather than eix-sync then= ? > Running eix-sync and emerge --sync would mean syncing twice a day (for no > good reason)... > > -- > Bo Andresen Indeed. I run update-eix, but I don't do it every day. The entire packag= e runs three times per week, and I use the emails from it to decide whether o= r when to emerge world. I keep pretty current, but don't see the point in daily updates. ++ kevin --=20 Kevin O'Gorman, PhD ------=_Part_6124_22173822.1199847638772 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On 1/8/08, Bo =D8rsted Andresen <bo.andresen@zlin.dk> wrote:
On Tuesday 08 January 2008 23:30:51 Kevin O'Gorman wrote:
> > = > However, it is true that emerge sync and eix-update were in two
>= ; > > separate jobs scheduled an hour apart. It is vaguely conceivabl= e
> > > that they got out of step somehow. I've unified them= , and hope
> > > things go better now.
[...]
> > An= y particular reason you run two separate jobs and not just eix-sync
> > (which does both in sequence)?
>
> Originally, becaus= e the output was hard to read I think.  And I figured
> tha= t starting them an hour apart would ensure sequence anyway.

Surely y= ou ran update-eix and possibly diff-eix rather than eix-sync then?
Running eix-sync and emerge --sync would mean syncing twice a day (for = no
good reason)...

--
Bo Andresen

Indeed.=   I run update-eix, but I don't do it every day.   The e= ntire package runs three times per week, and I use the emails from it to de= cide whether or when to emerge world.  I keep pretty current, but don&= #39;t see the point in daily updates.

++ kevin



--
Kevin O= 9;Gorman, PhD
------=_Part_6124_22173822.1199847638772-- -- gentoo-user@lists.gentoo.org mailing list