public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Paul Hartman <paul.hartman+gentoo@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Sync, emerge -puND world, and WHAM!!! ~100 packages to merge.
Date: Wed, 27 Mar 2013 13:39:47 -0500	[thread overview]
Message-ID: <CAEH5T2PMxDnY2zXY7LA9oSPFaGssvad40Fxsb9tuXuGp1MVZkg@mail.gmail.com> (raw)
In-Reply-To: <20130327180952.GA3674@acm.acm>

On Wed, Mar 27, 2013 at 1:09 PM, Alan Mackenzie <acm@muc.de> wrote:
> Hi, Gentoo!
>
> Has anybody else seen this?  I did a sync, then emerge -puND world and
> got a list of ~100 packages to merge.  About a third of them seem to be
> new perl stuff, 13 packages with gnome, and a lot of this and that.
>
> Most worrying is sys-fs/udisks-2.1.0.  Should I be worried about this
> (all my other udev-ish stuff is up to date), or will it just work?
>
> But getting such a large update, all at once, seems worrying.  Should I
> worry about anything, or just plough ahead with the update?

You must not be a KDE user. Hundreds of upgraded packages at once is a
monthly routine... :)

I wouldn't worry about it. Sometimes if I have a really large list of
packages, I will upgrade @system first and then upgrade @world second,
but there's no real scientific reason to do so, just my own "good
feelings"...


  parent reply	other threads:[~2013-03-27 18:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-27 18:09 [gentoo-user] Sync, emerge -puND world, and WHAM!!! ~100 packages to merge Alan Mackenzie
2013-03-27 18:34 ` [gentoo-user] " Grant Edwards
2013-03-27 18:39 ` Paul Hartman [this message]
2013-03-28  9:48 ` [gentoo-user] Re: [gentoo-user] " the guard
2013-03-28 11:52   ` Alan Mackenzie
2013-03-28 12:36     ` Mateusz Kowalczyk

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=CAEH5T2PMxDnY2zXY7LA9oSPFaGssvad40Fxsb9tuXuGp1MVZkg@mail.gmail.com \
    --to=paul.hartman+gentoo@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