public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Arve Barsnes <arve.barsnes@gmail.com>
To: Gentoo <gentoo-user@lists.gentoo.org>
Subject: Re: [gentoo-user] WARNING: Do not update your system on ~amd64
Date: Fri, 19 Jun 2020 14:31:29 +0200	[thread overview]
Message-ID: <CAJjrzcU1+V5zDvpwVHVbUcW2-uq=K_k_npFCrsQ=1HacDp4S7A@mail.gmail.com> (raw)
In-Reply-To: <20200619114939.3fc74321@digimed.co.uk>

On Fri, 19 Jun 2020 at 12:49, Neil Bothwick <neil@digimed.co.uk> wrote:
>
> On Fri, 19 Jun 2020 10:55:46 +0100, Peter Humphrey wrote:
>
> > And today, pam and pambase are restored to their earlier versions
> > because sddm requires them. But sddm has not changed versions, so why
> > did portage want to upgrade pam and pambase on Wednesday?
>
> The sddm ebuild has changed without changing the version
>
> -       pam? ( sys-libs/pam )
> +       pam? ( <=sys-libs/pam-1.3.1_p20200128-r1 )

I only got a message about skipping sddm on my world update, so
apparently I'm now running an unsupported pam version. Rebooting
worked just fine though, so what I gain/lose by staying like this is
unknown.

Regards,
Arve


  reply	other threads:[~2020-06-19 12:32 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-17  5:34 [gentoo-user] WARNING: Do not update your system on ~amd64 Andreas Fink
2020-06-17  8:29 ` Neil Bothwick
2020-06-17  8:51   ` Peter Humphrey
2020-06-17  9:03     ` Andreas Fink
2020-06-17  9:38       ` Neil Bothwick
2020-06-19  9:55         ` Peter Humphrey
2020-06-19 10:49           ` Neil Bothwick
2020-06-19 12:31             ` Arve Barsnes [this message]
2020-06-19 15:43               ` [gentoo-user] " Nikos Chantziaras
2020-06-20 21:41                 ` Viktar Patotski
2020-06-21 13:08                   ` Nikos Chantziaras
2020-06-19 12:52 ` [gentoo-user] " Rich Freeman

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='CAJjrzcU1+V5zDvpwVHVbUcW2-uq=K_k_npFCrsQ=1HacDp4S7A@mail.gmail.com' \
    --to=arve.barsnes@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