From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] How to resume 'emerge -e @world' after grub fails?
Date: Wed, 20 Dec 2017 22:49:16 -0600 [thread overview]
Message-ID: <ce50b1a0-f3fc-e78a-6d8d-aec57a626702@gmail.com> (raw)
In-Reply-To: <20171220225434.c3ij4krycicvq3ce@grusum.endjinn.de>
David Haller wrote:
> Hello,
>
> On Mon, 18 Dec 2017, Dale wrote:
>> David Haller wrote:
>>> 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
>>> ====
> [..]
>> I have KDE installed here plus other desktops as well. While I use some
>> meta packages, I do some on their own as needed. I have a lot of things
>> installed since I have a digital camera, burn CD/DVDs and all sorts of
>> other weird things. Here is mine.
>>
>> root@fireball / # wc -l /var/lib/portage/world
>> 201 /var/lib/portage/world
>> root@fireball / #
> That's not much ;)
>
> [..]
It results in this which is all I need and then some.
Packages installed: 1576
Packages in world: 199
Packages in system: 43
Required packages: 1576
Notice how my required packages and installed package match up?
>> Either way, doing it manually or using that command, you should end up
>> with a clean world file after some effort. I would guess that updates
>> would be much easier. Most of mine work first time with no problems.
>> Any failures are usually from the build itself.
> I guess I just have too many little stuff in @world. E.g. I explicitly
> want the x265 commandline tool, so I have media-libs/x265 in @world.
> Same goes for e.g. ffmpeg (for /usr/bin/ffmpeg), etc. pp. Or just
> this:
>
> # grep -c app-arch/ /var/lib/portage/world
> 42 (sic! ;)
>
> Lots of app-{x,}emacs/, app-shells/, app-portage/, app-text/,
> games-*/, media-*/...
I have quite a few of those as well but they are things I installed
directly. Given that some of them are pulled in by virtuals which could
be dependencies, I may can remove some of the ones I have. May test
that one day when I'm bored.
>
> I'm reather overeager emerging with -1 :) Hah! Got one: --depclean
> suggested dev-haskell/x509-validation. Ok, removed it and it is still
> used. Ok, let's see if rebuilding depending stuff
> (dev-haskell/connection and dev-haskell/tls) helps:
>
> Doesn't seem like it:
>
> * ghc-pkg check: 'checking for other broken packages:'
> There are problems in package connection-0.2.5:
> dependency "x509-validation-1.6.5-9d1Itw2kfW6JXBlF0ahQsB" doesn't exist
> There are problems in package tls-1.3.9:
> dependency "x509-validation-1.6.5-9d1Itw2kfW6JXBlF0ahQsB" doesn't exist
> [..]
>>>> Failed to emerge dev-haskell/connection-0.2.5,
> So, remerging dev-haskell/x509-validation. That's one example of the
> "overeager" --depclean... (and no, neither dev-haskell/connection
> dev-haskell/tls has the "profile"-USE-flags set, but it seems the
> build does actually need it).
>
> Whoa, --depclean wants to remove a bunch of eselects too, e.g.
> app-eselect/eselect-package-manager and app-eselect/eselect-pdftex.
> Ok, I don't have texlive-core in world, but it is pulled in by various
> other stuff...
>
> Oh well, I'll have to check what depclean's doing wrong better.
>
> -dnh
>
I have several eselect packages installed here and not one entry in my
world file. All of them are pulled in by the packages that need them.
If it were my system, I'd be pulling the broom out of my closet.
Dale
:-) :-)
next prev parent reply other threads:[~2017-12-21 4:49 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
2017-12-19 4:03 ` Dale
2017-12-20 22:54 ` David Haller
2017-12-21 4:49 ` Dale [this message]
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=ce50b1a0-f3fc-e78a-6d8d-aec57a626702@gmail.com \
--to=rdalek1967@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