public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] old kernels are installed during the upgrade
Date: Thu, 4 Jan 2018 00:11:49 +0200	[thread overview]
Message-ID: <9c550e9a-ad38-0e6c-f32e-9dc0b6466794@gmail.com> (raw)
In-Reply-To: <1D3E7160-0997-4DE5-9EB9-DC3C2EDC62BE@stellar.eclipse.co.uk>

On 04/01/2018 00:07, Stroller wrote:
> 
>> On 3 Jan 2018, at 21:53, Neil Bothwick <neil@digimed.co.uk> wrote:
>>>
>>> It installs exactly that version, and that exact version is recorded in
>>> the world file.
>>>
>>> $ grep -e source /var/lib/portage/world
>>> sys-kernel/gentoo-sources:4.9.34
>>
>> That's not a version, it's a slot. Whilst kernels are currently slotted
>> with the version number, nothing else is and there is no guarantee that
>> this will also hold for kernels.
> 
> Fair enough, but there's nothing else I need to treat this way.
> 
> I guess this risks that emerge will try to install 4.9.34-r1 during a future update, but I don't believe I've ever experienced that.

Only if the highest-versioned emerged sources are <4.9.34-r1
> 
>> If you do want to use versions, I'd recommend using ~ rather than = to
>> pick up patch-level updates.
> 
> What do you mean by this exactly, please?

=4.9.34 selects that exact version and only that specific version
~4.9.34 select that version and also 4.9.34-r1. There might need to be a
* on the end of ~4.9.34, I don;t quite recall. Answer in portage's man pages


-- 
Alan McKinnon
alan.mckinnon@gmail.com



  reply	other threads:[~2018-01-03 22:17 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-02 11:54 [gentoo-user] old kernels are installed during the upgrade Kruglov Sergey
2018-01-02 12:03 ` Alexander Kapshuk
2018-01-02 12:42   ` Mick
2018-01-02 15:59     ` [gentoo-user] " Nikos Chantziaras
2018-01-02 19:26 ` [gentoo-user] " Stroller
2018-01-02 19:47   ` Wols Lists
2018-01-03 21:39     ` Stroller
2018-01-03 21:55       ` Wols Lists
2018-01-03 22:02         ` Stroller
2018-01-03 22:09           ` Alan McKinnon
2018-01-04  6:40             ` Wols Lists
2018-01-04  8:48               ` Alan McKinnon
2018-01-03 23:43           ` Neil Bothwick
2018-01-02 20:20   ` [gentoo-user] " Kai Krakow
2018-01-02 20:28     ` Rich Freeman
2018-01-02 22:58       ` Adam Carter
2018-01-03 20:35         ` Wols Lists
2018-01-03 20:53           ` Rich Freeman
2018-01-03 21:50             ` Neil Bothwick
2018-01-04 16:02             ` Holger Hoffstätte
2018-01-04 16:10               ` Rich Freeman
2018-01-05  2:12                 ` Walter Dnes
2018-01-05  2:25                   ` Rich Freeman
2018-01-05 12:34                     ` Walter Dnes
2018-01-05 13:08                       ` Rich Freeman
2018-01-03 21:21     ` [gentoo-user] " Stroller
2018-01-03 21:31       ` Wols Lists
2018-01-03 21:43         ` Stroller
2018-01-03 21:49         ` Dale
2018-01-03 21:48       ` Rich Freeman
2018-01-03 21:53       ` Neil Bothwick
2018-01-03 22:07         ` Stroller
2018-01-03 22:11           ` Alan McKinnon [this message]
2018-01-03 22:41             ` Stroller
2018-01-03 22:47               ` Alan McKinnon
2018-01-04  2:18                 ` Stroller
2018-01-03 22:51               ` Herminio Hernandez, Jr.
2018-01-03 23:41           ` Neil Bothwick
2018-01-04  2:20             ` Stroller
2018-01-02 19:44 ` 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=9c550e9a-ad38-0e6c-f32e-9dc0b6466794@gmail.com \
    --to=alan.mckinnon@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