From: Gregory Woodbury <redwolfe@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] emerge conflict
Date: Sun, 18 Sep 2016 00:35:03 -0400 [thread overview]
Message-ID: <CAJoOjx8L3VT=aOQGmq59XMn96V-fiZjxtqmq-ZOmKmNByagEng@mail.gmail.com> (raw)
In-Reply-To: <CAC=wYCE055-h81uofCgswzj9vLtAVgqY3jKxJ36z2XAVf0KjDQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1073 bytes --]
I went through the list of conflicts and made a temporary @set of packages
for emerge to re-install. Worked like a charm. A number of the conflicts
are things that should be in a "preserved libraries" type of list, they are
actually quite able to rebuild with the new perl version.
I have, however, had to back off newest versions of sddm and chromium
(browser) due to some performance failures: /etc/portage/package.keywords
is your friend!
On Sat, Sep 17, 2016 at 9:55 PM, Adam Carter <adamcarter3@gmail.com> wrote:
> It doesn't look like just vim - it looks like exiftool, graphite2,
>
>> cups-filters, gvim, and imagemagick all are blocking.
>>
>> I'd guess that these packages need a version bump or you need to unmask
>> one of the newer builds (most likely they haven't been stabilized yet.)
>>
>
> Agree - my amd64 system upgraded perl to 5.22 on Friday, so re-sync, and
> try again. Also to help resolve upgrade issues i firstly add --deep to
> emerge's switches and if that doesnt help, bump up --backtrack=
>
>
--
--
G.Wolfe Woodbury
redwolfe@gmail.com
[-- Attachment #2: Type: text/html, Size: 1877 bytes --]
next prev parent reply other threads:[~2016-09-18 4:35 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-17 23:12 [gentoo-user] emerge conflict Philip Webb
2016-09-18 0:58 ` Daniel Frey
2016-09-18 1:55 ` Adam Carter
2016-09-18 4:35 ` Gregory Woodbury [this message]
2016-09-18 6:29 ` [gentoo-user] " Kai Krakow
2016-09-18 6:37 ` Kai Krakow
2016-09-18 23:53 ` Philip Webb
2016-09-19 0:36 ` Rich Freeman
2016-09-19 7:28 ` Neil Bothwick
2016-09-19 9:54 ` Bill Kenworthy
2016-09-19 17:01 ` Philip Webb
2016-09-19 20:17 ` Neil Bothwick
2016-09-20 6:41 ` Kai Krakow
2016-09-20 7:52 ` Neil Bothwick
2016-09-18 9:50 ` [gentoo-user] " Neil Bothwick
-- strict thread matches above, loose matches on Subject: below --
2010-08-13 14:04 Frank Schwidom
2010-08-13 12:15 ` Alan McKinnon
2010-08-13 13:17 ` J. Roeleveld
2010-08-13 13:36 ` Daniel Wagener
2010-08-13 14:32 ` J. Roeleveld
2010-08-13 16:31 ` Alan McKinnon
2010-08-13 22:52 ` Dale
2010-08-13 13:06 ` Mark Knecht
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='CAJoOjx8L3VT=aOQGmq59XMn96V-fiZjxtqmq-ZOmKmNByagEng@mail.gmail.com' \
--to=redwolfe@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