From: "Kevin O'Gorman" <kogorman@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Suddenly emerging unstable packages = why?
Date: Tue, 8 Jan 2008 06:35:43 -0800 [thread overview]
Message-ID: <9acccfe50801080635l52782c55x962108c9d45b4b3f@mail.gmail.com> (raw)
In-Reply-To: <200801071621.50957.alan.mckinnon@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 897 bytes --]
On 1/7/08, Alan McKinnon <alan.mckinnon@gmail.com> wrote:
>
> On Monday 07 January 2008, Kevin O'Gorman wrote:
> > I see that it's now stable, and I'm going to let the emerge go
> > forward. However, I scrolled back my terminal to when I sent that
> > message, and here's what eix gave me then (primarily the "~" in front
> > of 1.0.4. Could this be an asychrony with the eix database?
>
> 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. It is vaguely conceivable that they got out
of step somehow. I've unified them, and hope things go better now.
++ kevin
--
Kevin O'Gorman, PhD
[-- Attachment #2: Type: text/html, Size: 1303 bytes --]
next prev parent reply other threads:[~2008-01-08 14:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-05 3:41 [gentoo-user] Suddenly emerging unstable packages = why? Kevin O'Gorman
2008-01-05 4:12 ` Dale
2008-01-05 4:12 ` [gentoo-user] " Sven Köhler
2008-01-05 9:17 ` [gentoo-user] " Alan McKinnon
2008-01-07 14:14 ` Kevin O'Gorman
2008-01-07 14:21 ` Alan McKinnon
2008-01-08 14:35 ` Kevin O'Gorman [this message]
2008-01-08 15:48 ` Alan McKinnon
2008-01-08 22:30 ` Kevin O'Gorman
2008-01-08 22:47 ` Bo Ørsted Andresen
2008-01-09 3:00 ` Kevin O'Gorman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9acccfe50801080635l52782c55x962108c9d45b4b3f@mail.gmail.com \
--to=kogorman@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox