public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Daniel da Veiga <danieldaveiga@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Kernel not updating...
Date: Thu, 16 Feb 2006 17:52:16 -0300	[thread overview]
Message-ID: <342e1090602161252v13975614s1e54365d66af6b68@mail.gmail.com> (raw)
In-Reply-To: <43F4DFEB.7020906@gmail.com>

On 2/16/06, gentuxx <gentuxx@gmail.com> 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.)
>
> - --
> gentux
> echo "hfouvyAdpy/ofu" | perl -pe 's/(.)/chr(ord($1)-1)/ge'
>
> gentux's gpg fingerprint ==> 34CE 2E97 40C7 EF6E EC40  9795 2D81 924A
> 6996 0993
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.2.1 (GNU/Linux)
>
> iD8DBQFD9N/rLYGSSmmWCZMRAvQ5AJ91CTrPnIUY2K9h2nGuzez5TvnnowCeO5qn
> feaYzfHUzeioWHhZCuUmbMY=
> =h/GC
> -----END PGP SIGNATURE-----
>
> --
> gentoo-user@gentoo.org mailing list
>
>

I've run out of ideas, if I do the same process as you did, I get the
latest kernel, simply as that...
Rebuild your portage tree?! (note: that can hurt more than it can solve)

--
Daniel da Veiga
Computer Operator - RS - Brazil
-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GCM/IT/P/O d-? s:- a? C++$ UBLA++ P+ L++ E--- W+++$ N o+ K- w O M- V-
PS PE Y PGP- t+ 5 X+++ R+* tv b+ DI+++ D+ G+ e h+ r+ y++
------END GEEK CODE BLOCK------

-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2006-02-16 21:15 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 [this message]
2006-02-16 21:23       ` Nick Rout
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=342e1090602161252v13975614s1e54365d66af6b68@mail.gmail.com \
    --to=danieldaveiga@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