public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: gentuxx <gentuxx@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user]  Re: Kernel not updating...
Date: Thu, 16 Feb 2006 12:48:36 -0800	[thread overview]
Message-ID: <43F4E524.5090208@gmail.com> (raw)
In-Reply-To: <dt2mvq$mp2$1@sea.gmane.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Mick wrote:

>Daniel da Veiga wrote:
>
>>On 2/16/06, Bo Andresen <bo.andresen@gmail.com> wrote:
>>
>>>On Thursday 16 February 2006 19:35, gentuxx wrote:
>>>
>>>>>>Hmmm, shouldn't it be emerge -uav gentoo-sources ?
>>>>>>I mean, "u" for "update"?
>>>>
>>>>emerge -uav gentoo-sources
>>>>
>>>>These are the packages that I would merge, in order:
>>>>
>>>>Calculating dependencies ...done!
>>
>>It seems your portage tree is not updated... I tried the same command
>>in my box (running an old kernel) and it asked me to download the last
>>kernel...
>>
>
>I'm no portage guru, but this is what I would do on my system:
>
>1. Check what you have in your RSYNC_EXCLUDEFROM and package.keywords.

Looks like this was it.  I had it in the /etc/portage/rsync_excludes
file.  Not really sure why.  Guess I'll find out when something breaks
after I boot to the new kernel.  ;-)

>2. Run regenworld.

What does this do?

>2. Check that gentoo-sources is in your world file.
>3. Run emerge --sync && emerge -uDpv world to see what it brings up.
>
>If the above fails, I've run out of ideas!

Thanks to everyone for all your tips and suggestions!

- --
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)

iD8DBQFD9OUkLYGSSmmWCZMRAinPAKDgDIM1tUgkOI3KO5qz+LxSf0pg6wCg3+OA
GIL8Q7Ig49zvgiMDfrVRIO0=
=8OQZ
-----END PGP SIGNATURE-----

-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2006-02-16 21:11 UTC|newest]

Thread overview: 24+ 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 [this message]
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
2006-02-17  2:05         ` Ernie Schroder
2006-02-17  9:43           ` Neil Bothwick

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=43F4E524.5090208@gmail.com \
    --to=gentuxx@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