public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: David Haller <gentoo@dhaller.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] How to resume 'emerge -e @world' after grub fails?
Date: Tue, 19 Dec 2017 04:06:52 +0100	[thread overview]
Message-ID: <20171219030652.eelzj4kp2omlr4wq@grusum.endjinn.de> (raw)
In-Reply-To: <f77d4313-8c2f-d59f-c776-7c25f7de235b@gmail.com>

Hello,

On Mon, 18 Dec 2017, Dale wrote:
>The key thing, remembering to force it to be added to world, which is a
>lot easier than remembering to use -1 for ALL those things I don't want
>in the world file.  Before I added the -1 option, my world file was full
>of all sorts of things that have no business being there at all.  It was
>causing huge problems with upgrades and such. 

Hm.

# wc -l /var/lib/portage/world
1140 /var/lib/portage/world

Am I doing something wrong? Looking it over, it looks right though.
And --depclean is hopelessly overeager here.

====
Packages installed:   3511
Packages in world:    1140
Packages in system:   43
Required packages:    2581
Number to remove:     930
====

Hm. I guess there's stuff missing from world (linux-gazette*?) or
something's broke. I guess I should quickpkg stuff, run a depclean and
go figure what's missing ;) adding to world/pruning whatever ;) I know
a lot of those "depcleaned" pkgs are wanted/needed, so I missed adding
stuff to world or deps are lacking... Oh well. Not while I'm cleaning
up after the profile-13/gcc-5.4 -> profile-17/gcc-7.2 stuff (I'd
already compiled most with gcc 6.4, with "std=c++14" for C++ stuff. So
not much change there besides pie/no-pie.

-dnh

-- 
Shin - Device for finding furniture in the dark.


  reply	other threads:[~2017-12-19  3:08 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-18 16:00 [gentoo-user] How to resume 'emerge -e @world' after grub fails? Grant Edwards
2017-12-18 16:07 ` John Blinka
2017-12-18 16:14   ` [gentoo-user] " Grant Edwards
2017-12-18 16:45     ` Dale
2017-12-20 20:16     ` Grant Edwards
2017-12-20 23:28       ` Dale
2017-12-21  8:43         ` Mart Raudsepp
2017-12-21  9:45   ` Jörg Schaible
2017-12-21 12:00     ` Marc Joliet
2017-12-21 17:02       ` John Covici
2018-01-07 12:39         ` Marc Joliet
2017-12-21 17:13       ` Jörg Schaible
2018-01-07 12:41         ` Marc Joliet
2017-12-21 17:32       ` Grant Edwards
2017-12-18 16:14 ` [gentoo-user] " Dale
2017-12-18 17:55   ` Mick
2017-12-18 19:02     ` David Haller
2017-12-18 19:31       ` Francisco Ares
2017-12-18 20:05         ` David Haller
2017-12-18 22:49     ` Dale
2017-12-18 23:05       ` Adam Carter
2017-12-18 23:38         ` Dale
2017-12-19  3:06           ` David Haller [this message]
2017-12-19  4:03             ` Dale
2017-12-20 22:54               ` David Haller
2017-12-21  4:49                 ` Dale
2017-12-19  5:51             ` Adam Carter
2017-12-19  9:15               ` Neil Bothwick
2017-12-19 15:45                 ` Helmut Jarausch
2017-12-19 18:13                   ` Bas Zoutendijk
2017-12-20  8:08                     ` Helmut Jarausch
2017-12-20 22:27                       ` David Haller
2017-12-19 17:45                 ` Dale
2017-12-19 20:22                   ` Neil Bothwick
2017-12-20  2:04                 ` Adam Carter
2017-12-20 23:18               ` David Haller
2017-12-19  9:21             ` 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=20171219030652.eelzj4kp2omlr4wq@grusum.endjinn.de \
    --to=gentoo@dhaller.de \
    --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