From: Nick Rout <nick@rout.co.nz>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Kernel not updating...
Date: Fri, 17 Feb 2006 10:23:52 +1300 [thread overview]
Message-ID: <20060217095931.D43F.NICK@rout.co.nz> (raw)
In-Reply-To: <43F4DFEB.7020906@gmail.com>
On Thu, 16 Feb 2006 12:26:19 -0800
gentuxx wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Neil Bothwick wrote:
>
> >On Thu, 16 Feb 2006 14:29:50 -0300, Daniel da Veiga wrote:
> >
> >> I was poking around in packages.gentoo.org, and noticed
> >>
> >>>that 2.6.15-r1 is unmasked for x86. So I run an `emerge --sync`, and
> >>>`emerge -av gentoo-sources`. And it wants to rebuild my 2.6.13-r3
> >>
> >>Hmmm, shouldn't it be emerge -uav gentoo-sources ?
> >>I mean, "u" for "update"?
> >
> >
> >It doesn't matter, because kernels arer slotted.
> >
> >Have you synced? It doesn't matter if the package is stable in Gentoo's
> >portage tree if you sill have the old ebuild.
> >
> >
> Yup. Did it today just to check before sending the first post.
> (Mentioned this in the first post.)
>
I have a machine on which portage sometimes crashes near the end of emerge --sync. during the metadata part. This leaves portage in the position that it has all the ebuild files on the disk, but it's own database doesn't seem to know about it.
Try emerge --metadata which will fix it if that is the problem.
Anyway, to check when you last synced:
genlop -r|tail
(if you don't have genlop, it is in the package genlop (surprise?)
the nitty gritties way to see what ebuilds are on your hard drive:
ls /usr/portage/sys-kernel/gentoo-sources/*.ebuild
--
Nick Rout <nick@rout.co.nz>
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2006-02-16 21:42 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-16 17:07 [gentoo-user] Kernel not updating gentuxx
2006-02-16 17:29 ` Daniel da Veiga
2006-02-16 18:35 ` gentuxx
2006-02-16 19:03 ` Bo Andresen
2006-02-16 19:16 ` Daniel da Veiga
2006-02-16 20:24 ` [gentoo-user] " Mick
2006-02-16 20:48 ` gentuxx
2006-02-16 21:24 ` [gentoo-user] " Mick
2006-02-16 23:45 ` Neil Bothwick
2006-02-16 19:53 ` [gentoo-user] " gentuxx
2006-02-16 21:15 ` Neil Bothwick
2006-02-16 21:46 ` Bo Andresen
2006-02-16 22:24 ` gentuxx
2006-02-16 23:43 ` Neil Bothwick
2006-02-16 19:16 ` [gentoo-user] " james
2006-02-16 19:44 ` gentuxx
2006-02-16 19:21 ` [gentoo-user] " Holly Bostick
2006-02-16 19:41 ` gentuxx
2006-02-16 20:07 ` Neil Bothwick
2006-02-16 20:26 ` gentuxx
2006-02-16 20:52 ` Daniel da Veiga
2006-02-16 21:23 ` Nick Rout [this message]
2006-02-17 2:05 ` Ernie Schroder
2006-02-17 9:43 ` Neil Bothwick
-- strict thread matches above, loose matches on Subject: below --
2006-02-20 12:17 joaoemanuel1981
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=20060217095931.D43F.NICK@rout.co.nz \
--to=nick@rout.co.nz \
--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