[gentoo-user] emerge conflict

[gentoo-user] emerge conflict

[Philip Webb]

Starting my regular Sat system update, 'eix-sync' told me (equivalent) :

root:524 ~> eix ^perl$
[U] dev-lang/perl
 Available versions:  5.20.2(0/5.20) ~5.20.2-r1(0/5.20) ~5.22.0(0/5.22) ~5.22.1(0/5.22) 5.22.2(0/5.22) ~5.24.0(0/5.24) ~5.24.0-r1(0/5.24) {berkdb debug doc gdbm ithreads}
 Installed versions:  5.20.2([2015-10-04 11:34:10])(gdbm -berkdb -debug -doc -ithreads)

So I tried 'emerge -pv perl' & was told the current version of (G)Vim
required the earlier installed version of Perl.
After updating to the latest testing version of (G)Vim, I tried again :

root:522 ~> emerge -pv perl

These are the packages that would be merged, in order:

Calculating dependencies... done!
[ebuild   R    ] dev-lang/perl-5.20.2:0/5.20::gentoo  USE="-berkdb -debug -doc gdbm -ithreads" 0 KiB

Total: 1 package (1 reinstall), Size of downloads: 0 KiB

WARNING: One or more updates/rebuilds have been skipped due to a dependency conflict:

dev-lang/perl:0

  (dev-lang/perl-5.22.2:0/5.22::gentoo, ebuild scheduled for merge) conflicts with
    dev-lang/perl:0/5.20= required by (media-libs/exiftool-10.20:0/0::gentoo, installed)
                 ^^^^^^^^
    dev-lang/perl:0/5.20=[-build(-)] required by (dev-perl/File-MimeInfo-0.270.0:0/0::gentoo, installed)
                 ^^^^^^^^           
    =dev-lang/perl-5.20.2* required by (virtual/perl-File-Spec-3.480.100-r1:0/0::gentoo, installed)
    ^              ^^^^^^^
    =dev-lang/perl-5.20* required by (virtual/perl-Test-Harness-3.330.0:0/0::gentoo, installed)
    ^              ^^^^^
    dev-lang/perl:0/5.20= required by (media-gfx/graphite2-1.3.8:0/0::gentoo, installed)
                 ^^^^^^^^
    dev-lang/perl:0/5.20= required by (net-print/cups-filters-1.5.0:0/0::gentoo, installed)
                 ^^^^^^^^
    dev-lang/perl:0/5.20=[-build(-)] required by (dev-perl/File-DesktopEntry-0.40.0-r1:0/0::gentoo, installed)
                 ^^^^^^^^           
    dev-lang/perl:0/5.20=[-build(-)] required by (dev-perl/File-BaseDir-0.30.0-r1:0/0::gentoo, installed)
                 ^^^^^^^^           
    dev-lang/perl:0/5.20= required by (app-editors/gvim-8.0.0005:0/0::gentoo, installed)
                 ^^^^^^^^
    dev-lang/perl:0/5.20=[-build(-)] required by (perl-core/Data-Dumper-2.154.0:0/0::gentoo, installed)
                 ^^^^^^^^           
    >=dev-lang/perl-5.8.8:0/5.20= required by (media-gfx/imagemagick-6.9.4.6:0/6.9.4.6::gentoo, installed)
                         ^^^^^^^^
    dev-lang/perl:0/5.20=[-build(-)] required by (perl-core/File-Temp-0.230.400-r1:0/0::gentoo, installed)
                 ^^^^^^^^           
    dev-lang/perl:0/5.20= required by (app-editors/vim-8.0.0005:0/0::gentoo, installed)
                 ^^^^^^^^

Portage is refusing to update to the latest stable Perl,
whether I have an earlier version of Vim (-13xx) or the latest version.

How do I update Perl without dropping Vim ?

-- 
========================,,============================================
SUPPORT     ___________//___,   Philip Webb
ELECTRIC   /] [] [] [] [] []|   Cities Centre, University of Toronto
TRANSIT    `-O----------O---'   purslowatchassdotutorontodotca

Re: [gentoo-user] emerge conflict

[Daniel Frey]

On 09/17/2016 04:12 PM, Philip Webb wrote:
> Starting my regular Sat system update, 'eix-sync' told me (equivalent) :
> 
> root:524 ~> eix ^perl$
> [U] dev-lang/perl
>  Available versions:  5.20.2(0/5.20) ~5.20.2-r1(0/5.20) ~5.22.0(0/5.22) ~5.22.1(0/5.22) 5.22.2(0/5.22) ~5.24.0(0/5.24) ~5.24.0-r1(0/5.24) {berkdb debug doc gdbm ithreads}
>  Installed versions:  5.20.2([2015-10-04 11:34:10])(gdbm -berkdb -debug -doc -ithreads)
> 
> So I tried 'emerge -pv perl' & was told the current version of (G)Vim
> required the earlier installed version of Perl.
> After updating to the latest testing version of (G)Vim, I tried again :
> 
> root:522 ~> emerge -pv perl
> 
> These are the packages that would be merged, in order:
> 
> Calculating dependencies... done!
> [ebuild   R    ] dev-lang/perl-5.20.2:0/5.20::gentoo  USE="-berkdb -debug -doc gdbm -ithreads" 0 KiB
> 
> Total: 1 package (1 reinstall), Size of downloads: 0 KiB
> 
> WARNING: One or more updates/rebuilds have been skipped due to a dependency conflict:
> 
> dev-lang/perl:0
> 
>   (dev-lang/perl-5.22.2:0/5.22::gentoo, ebuild scheduled for merge) conflicts with
>     dev-lang/perl:0/5.20= required by (media-libs/exiftool-10.20:0/0::gentoo, installed)
>                  ^^^^^^^^
>     dev-lang/perl:0/5.20=[-build(-)] required by (dev-perl/File-MimeInfo-0.270.0:0/0::gentoo, installed)
>                  ^^^^^^^^           
>     =dev-lang/perl-5.20.2* required by (virtual/perl-File-Spec-3.480.100-r1:0/0::gentoo, installed)
>     ^              ^^^^^^^
>     =dev-lang/perl-5.20* required by (virtual/perl-Test-Harness-3.330.0:0/0::gentoo, installed)
>     ^              ^^^^^
>     dev-lang/perl:0/5.20= required by (media-gfx/graphite2-1.3.8:0/0::gentoo, installed)
>                  ^^^^^^^^
>     dev-lang/perl:0/5.20= required by (net-print/cups-filters-1.5.0:0/0::gentoo, installed)
>                  ^^^^^^^^
>     dev-lang/perl:0/5.20=[-build(-)] required by (dev-perl/File-DesktopEntry-0.40.0-r1:0/0::gentoo, installed)
>                  ^^^^^^^^           
>     dev-lang/perl:0/5.20=[-build(-)] required by (dev-perl/File-BaseDir-0.30.0-r1:0/0::gentoo, installed)
>                  ^^^^^^^^           
>     dev-lang/perl:0/5.20= required by (app-editors/gvim-8.0.0005:0/0::gentoo, installed)
>                  ^^^^^^^^
>     dev-lang/perl:0/5.20=[-build(-)] required by (perl-core/Data-Dumper-2.154.0:0/0::gentoo, installed)
>                  ^^^^^^^^           
>     >=dev-lang/perl-5.8.8:0/5.20= required by (media-gfx/imagemagick-6.9.4.6:0/6.9.4.6::gentoo, installed)
>                          ^^^^^^^^
>     dev-lang/perl:0/5.20=[-build(-)] required by (perl-core/File-Temp-0.230.400-r1:0/0::gentoo, installed)
>                  ^^^^^^^^           
>     dev-lang/perl:0/5.20= required by (app-editors/vim-8.0.0005:0/0::gentoo, installed)
>                  ^^^^^^^^
> 
> Portage is refusing to update to the latest stable Perl,
> whether I have an earlier version of Vim (-13xx) or the latest version.
> 
> How do I update Perl without dropping Vim ?
> 

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.)

Dan

Re: [gentoo-user] emerge conflict

[Adam Carter]

[-- Attachment #1: Type: text/plain, Size: 485 bytes --]

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=

[-- Attachment #2: Type: text/html, Size: 757 bytes --]

Re: [gentoo-user] emerge conflict

[Gregory Woodbury]

[-- 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 --]

[gentoo-user] Re: emerge conflict

[Kai Krakow]

Am Sat, 17 Sep 2016 19:12:40 -0400
schrieb Philip Webb <purslow@ca.inter.net>:

> Starting my regular Sat system update, 'eix-sync' told me
> (equivalent) :
> 
> root:524 ~> eix ^perl$
> [U] dev-lang/perl
>  Available versions:  5.20.2(0/5.20) ~5.20.2-r1(0/5.20)
> ~5.22.0(0/5.22) ~5.22.1(0/5.22) 5.22.2(0/5.22) ~5.24.0(0/5.24)
> ~5.24.0-r1(0/5.24) {berkdb debug doc gdbm ithreads} Installed
> versions:  5.20.2([2015-10-04 11:34:10])(gdbm -berkdb -debug -doc
> -ithreads)
> 
> So I tried 'emerge -pv perl' & was told the current version of (G)Vim
> required the earlier installed version of Perl.
> After updating to the latest testing version of (G)Vim, I tried
> again :
> 
> root:522 ~> emerge -pv perl
> 
> These are the packages that would be merged, in order:
> 
> Calculating dependencies... done!
> [ebuild   R    ] dev-lang/perl-5.20.2:0/5.20::gentoo  USE="-berkdb
> -debug -doc gdbm -ithreads" 0 KiB
> 
> Total: 1 package (1 reinstall), Size of downloads: 0 KiB
> 
> WARNING: One or more updates/rebuilds have been skipped due to a
> dependency conflict:
[...]

Try running "emerge -C $(qlist -IC virtual/perl-) first, then run a
deep update. If that fails, add vim and other packages to the list:

# emerge -1Dpuv perl
# emerge -1Dpuv perl vim ...

Also check your world file if it accidentally includes perl
dependencies. If deps need to be removed by emerge during an updates,
it will only do it if it is absent in the world file. That is, remove
"virtual/perl-*" and "perl-core/*" from the world file unless you added
them on purpose.

-- 
Regards,
Kai

Replies to list-only preferred.

[gentoo-user] Re: emerge conflict

[Kai Krakow]

Am Sat, 17 Sep 2016 19:12:40 -0400
schrieb Philip Webb <purslow@ca.inter.net>:

> Starting my regular Sat system update, 'eix-sync' told me
> (equivalent) :
> 
> root:524 ~> eix ^perl$
> [U] dev-lang/perl
>  Available versions:  5.20.2(0/5.20) ~5.20.2-r1(0/5.20)
> ~5.22.0(0/5.22) ~5.22.1(0/5.22) 5.22.2(0/5.22) ~5.24.0(0/5.24)
> ~5.24.0-r1(0/5.24) {berkdb debug doc gdbm ithreads} Installed
> versions:  5.20.2([2015-10-04 11:34:10])(gdbm -berkdb -debug -doc
> -ithreads)
> 
> So I tried 'emerge -pv perl' & was told the current version of (G)Vim
> required the earlier installed version of Perl.
> After updating to the latest testing version of (G)Vim, I tried
> again :
> 
> root:522 ~> emerge -pv perl
> 
> These are the packages that would be merged, in order:
> 
> Calculating dependencies... done!
> [ebuild   R    ] dev-lang/perl-5.20.2:0/5.20::gentoo  USE="-berkdb
> -debug -doc gdbm -ithreads" 0 KiB
> 
> Total: 1 package (1 reinstall), Size of downloads: 0 KiB
> 
> WARNING: One or more updates/rebuilds have been skipped due to a
> dependency conflict:
[...]

Try running "emerge -C $(qlist -IC virtual/perl-) first, then run a
deep update. If that fails, add vim and other packages to the list:

# emerge -1Dpuv perl
# emerge -1Dpuv perl vim ...

Also check your world file if it accidentally includes perl
dependencies. If deps need to be removed by emerge during an updates,
it will only do it if it is absent in the world file. That is, remove
"virtual/perl-*" and "perl-core/*" from the world file unless you added
them on purpose.

-- 
Regards,
Kai

Replies to list-only preferred.

Re: [gentoo-user] Re: emerge conflict

[Philip Webb]

160918 Kai Krakow wrote:
> Try ... adding vim and other packages to the list:
> # emerge -1Dpuv perl
> # emerge -1Dpuv perl vim ...

I got around the problem by using :

  emerge --backtrack=30 -pvtD perl perl-Archive-Tar perl-Carp perl-Compress-Raw-Zlib perl-CPAN-Meta-Requirements perl-Data-Dumper perl-ExtUtils-CBuilder perl-ExtUtils-Install perl-ExtUtils-MakeMaker perl-ExtUtils-Manifest perl-ExtUtils-ParseXS perl-File-Spec perl-Getopt-Long perl-IO perl-Locale-Maketext perl-Perl-OSType perl-Scalar-List-Utils perl-Test-Harness perl-Text-ParseWords

It wants to remerge Exiftool Imagemagick Cups-filters Graphite2
& also some further Perl pkgs & it wants to downgrade (G)Vim.
That much wb ok, but it also wants to update Poppler & therefore LO
& I don't feel like doing the last at the moment ( 65 min  last time).

What you suggested is fairly standard & I've done it in the past,
but thanks for prompting me.  Thanks to the other respondents too.

Perl can stay where it is till LO 5.2 arrives in Portage :
in fact, isn't it a bit slow appearing ?

-- 
========================,,============================================
SUPPORT     ___________//___,   Philip Webb
ELECTRIC   /] [] [] [] [] []|   Cities Centre, University of Toronto
TRANSIT    `-O----------O---'   purslowatchassdotutorontodotca

Re: [gentoo-user] Re: emerge conflict

[Rich Freeman]

On Sun, Sep 18, 2016 at 7:53 PM, Philip Webb <purslow@ca.inter.net> wrote:
> 160918 Kai Krakow wrote:
>> Try ... adding vim and other packages to the list:
>> # emerge -1Dpuv perl
>> # emerge -1Dpuv perl vim ...
>
> I got around the problem by using :
>
>   emerge --backtrack=30 -pvtD perl

I suspect that you could have gotten away with just emerge
--backtrack=30 -puDvt @world.

Or if you want less than that then just grab all the perl stuff out of
your world, which it looks like you already did.  Without increasing
the backtrack setting I suspect it can't get past the blockers.

-- 
Rich

Re: [gentoo-user] Re: emerge conflict

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 1504 bytes --]

On Sun, 18 Sep 2016 19:53:10 -0400, Philip Webb wrote:

> I got around the problem by using :
> 
>   emerge --backtrack=30 -pvtD perl perl-Archive-Tar perl-Carp
> perl-Compress-Raw-Zlib perl-CPAN-Meta-Requirements perl-Data-Dumper
> perl-ExtUtils-CBuilder perl-ExtUtils-Install perl-ExtUtils-MakeMaker
> perl-ExtUtils-Manifest perl-ExtUtils-ParseXS perl-File-Spec
> perl-Getopt-Long perl-IO perl-Locale-Maketext perl-Perl-OSType
> perl-Scalar-List-Utils perl-Test-Harness perl-Text-ParseWords

I'm surprised you needed to jump through such hoops, I updated 2 stable
systems to perl 5.22 last week and emerge @world took care of all
blockers, although I did need to run perl-cleaner afterwards.

> It wants to remerge Exiftool Imagemagick Cups-filters Graphite2
> & also some further Perl pkgs & it wants to downgrade (G)Vim.
> That much wb ok, but it also wants to update Poppler & therefore LO
> & I don't feel like doing the last at the moment ( 65 min  last time).
> 
> What you suggested is fairly standard & I've done it in the past,
> but thanks for prompting me.  Thanks to the other respondents too.
> 
> Perl can stay where it is till LO 5.2 arrives in Portage :
> in fact, isn't it a bit slow appearing ?

5.2.1.2 has been in testing for a couple of days, but it appears that
5.1.4.2 is the only ebuild in stable, so that may be the reason for your
downgrade.


-- 
Neil Bothwick

You know it's cold when you spot a lawyer with his hands in his own
pockets.

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 163 bytes --]

Re: [gentoo-user] Re: emerge conflict

[Bill Kenworthy]

On 19/09/16 15:28, Neil Bothwick wrote:
> On Sun, 18 Sep 2016 19:53:10 -0400, Philip Webb wrote:
> 
>> I got around the problem by using :
>>
>>   emerge --backtrack=30 -pvtD perl perl-Archive-Tar perl-Carp
>> perl-Compress-Raw-Zlib perl-CPAN-Meta-Requirements perl-Data-Dumper
>> perl-ExtUtils-CBuilder perl-ExtUtils-Install perl-ExtUtils-MakeMaker
>> perl-ExtUtils-Manifest perl-ExtUtils-ParseXS perl-File-Spec
>> perl-Getopt-Long perl-IO perl-Locale-Maketext perl-Perl-OSType
>> perl-Scalar-List-Utils perl-Test-Harness perl-Text-ParseWords
> 
> I'm surprised you needed to jump through such hoops, I updated 2 stable
> systems to perl 5.22 last week and emerge @world took care of all
> blockers, although I did need to run perl-cleaner afterwards.
> 
>> It wants to remerge Exiftool Imagemagick Cups-filters Graphite2
>> & also some further Perl pkgs & it wants to downgrade (G)Vim.
>> That much wb ok, but it also wants to update Poppler & therefore LO
>> & I don't feel like doing the last at the moment ( 65 min  last time).
>>
>> What you suggested is fairly standard & I've done it in the past,
>> but thanks for prompting me.  Thanks to the other respondents too.
>>
>> Perl can stay where it is till LO 5.2 arrives in Portage :
>> in fact, isn't it a bit slow appearing ?
> 
> 5.2.1.2 has been in testing for a couple of days, but it appears that
> 5.1.4.2 is the only ebuild in stable, so that may be the reason for your
> downgrade.
> 
> 

I had only one machine fail - perl itself had to be brute forced with
--nodeps, perl-cleaner fixed the rest after I fixed some g-cpan failures
(wrong case - been around for a long while) - but for that perl-cleaner
would have picked it all up.

BillK

Re: [gentoo-user] Re: emerge conflict

[Philip Webb]

160919 Neil Bothwick wrote:
> On Sun, 18 Sep 2016 19:53:10 -0400, Philip Webb wrote:
>> I got around the problem by using :
>>   emerge --backtrack=30 -pvtD perl perl-Archive-Tar perl-Carp
>> perl-Compress-Raw-Zlib perl-CPAN-Meta-Requirements perl-Data-Dumper
>> perl-ExtUtils-CBuilder perl-ExtUtils-Install perl-ExtUtils-MakeMaker
>> perl-ExtUtils-Manifest perl-ExtUtils-ParseXS perl-File-Spec
>> perl-Getopt-Long perl-IO perl-Locale-Maketext perl-Perl-OSType
>> perl-Scalar-List-Utils perl-Test-Harness perl-Text-ParseWords
> I'm surprised you needed to jump through such hoops.
> I updated 2 stable systems to perl 5.22 last week
> and emerge @world took care of all blockers,
> although I did need to run perl-cleaner afterwards.

I never run 'emerge world' without '-p' :
it's the lazy way to manage a Gentoo system & asks for trouble.

>> Perl can stay where it is till LO 5.2 arrives in Portage :
>> in fact, isn't it a bit slow appearing ?
> 5.2.1.2 has been in testing for a couple of days,
> but it appears that 5.1.4.2 is the only ebuild in stable,
> so that may be the reason for your downgrade.

Actually, it wb an upgrade from 5.1.2.2 .

Anyway, the problem is resolved & I can decide when/how to proceed.

-- 
========================,,============================================
SUPPORT     ___________//___,   Philip Webb
ELECTRIC   /] [] [] [] [] []|   Cities Centre, University of Toronto
TRANSIT    `-O----------O---'   purslowatchassdotutorontodotca

Re: [gentoo-user] Re: emerge conflict

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 745 bytes --]

On Mon, 19 Sep 2016 13:01:39 -0400, Philip Webb wrote:

> > I'm surprised you needed to jump through such hoops.
> > I updated 2 stable systems to perl 5.22 last week
> > and emerge @world took care of all blockers,
> > although I did need to run perl-cleaner afterwards.  
> 
> I never run 'emerge world' without '-p' :
> it's the lazy way to manage a Gentoo system & asks for trouble.

What makes you think I didn't use -p? I have a cron job that runs emerge
-pXXX @world after syncing and mails me the output, and I always use -a
when running emerge in a shell.

The point is that, whether I used -p, -a or neither, portage handled it
all for me.


-- 
Neil Bothwick

Half of being smart is knowing what you're dumb at.

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 163 bytes --]

[gentoo-user] Re: emerge conflict

[Kai Krakow]

[-- Attachment #1: Type: text/plain, Size: 881 bytes --]

Am Mon, 19 Sep 2016 21:17:36 +0100
schrieb Neil Bothwick <neil@digimed.co.uk>:

> On Mon, 19 Sep 2016 13:01:39 -0400, Philip Webb wrote:
> 
> > > I'm surprised you needed to jump through such hoops.
> > > I updated 2 stable systems to perl 5.22 last week
> > > and emerge @world took care of all blockers,
> > > although I did need to run perl-cleaner afterwards.    
> > 
> > I never run 'emerge world' without '-p' :
> > it's the lazy way to manage a Gentoo system & asks for trouble.  
> 
> What makes you think I didn't use -p? I have a cron job that runs
> emerge -pXXX @world after syncing and mails me the output, and I
> always use -a when running emerge in a shell.
> 
> The point is that, whether I used -p, -a or neither, portage handled
> it all for me.

You could also try porticron... ;-)

-- 
Regards,
Kai

Replies to list-only preferred.

[-- Attachment #2: Digitale Signatur von OpenPGP --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

Re: [gentoo-user] Re: emerge conflict

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 698 bytes --]

On Tue, 20 Sep 2016 08:41:56 +0200, Kai Krakow wrote:

> > What makes you think I didn't use -p? I have a cron job that runs
> > emerge -pXXX @world after syncing and mails me the output, and I
> > always use -a when running emerge in a shell.
> 
> You could also try porticron... ;-)

I could but I've been running this script on several machines for many
years and it does just what I want and has evolved along with portage. I
may take a look at porticron to see if there's anything else I want but
didn't know it ;-)


-- 
Neil Bothwick

Physics is like sex: sure, it may give some practical results, but
  that's not why we do it.                            Richard Feynman

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 163 bytes --]

Re: [gentoo-user] emerge conflict

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 817 bytes --]

On Sat, 17 Sep 2016 19:12:40 -0400, Philip Webb wrote:

> root:522 ~> emerge -pv perl
> 
> These are the packages that would be merged, in order:
> 
> Calculating dependencies... done!
> [ebuild   R    ] dev-lang/perl-5.20.2:0/5.20::gentoo  USE="-berkdb
> -debug -doc gdbm -ithreads" 0 KiB
> 
> Total: 1 package (1 reinstall), Size of downloads: 0 KiB
> 
> WARNING: One or more updates/rebuilds have been skipped due to a
> dependency conflict:
> 
> dev-lang/perl:0

Is this because you are trying to emerge perl in isolation? This result
is not unexpected as you have other packages built against the older
version and you have not told portage to deal with that.

What happens if you do emerge -uaD @world?


-- 
Neil Bothwick

I am McCoy of Bo...Damnit! I'm a doctor, not a collective!

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 163 bytes --]

[gentoo-user] emerge conflict

[Frank Schwidom]

Hi

i get the error:

{
!!! Multiple package instances within a single package slot have been
pulled
!!! into the dependency graph, resulting in a slot conflict:

media-libs/libpng:0

  ('ebuild', '/', 'media-libs/libpng-1.4.3', 'merge') pulled in by
    >=media-libs/libpng-1.2.43-r2:0 required by ('ebuild', '/',
    >'x11-libs/cairo-1.8.10', 'merge')
    >=media-libs/libpng-1.4 required by ('ebuild', '/',
    >'x11-libs/gtk+-2.20.1-r1', 'merge')
    (and 27 more)
}

And i wonder that it seems not to be possible to install both libs
(libpng-1.2.43-r2:0, libpng-1.4) in the same time. Linux is actually 
able to manage this by the lib-version and links.

Did i have overseen any gentoo switch that makes is possible? Or is
there any other option?

Regards

Re: [gentoo-user] emerge conflict

[Alan McKinnon]

On Friday 13 August 2010 16:04:53 Frank Schwidom wrote:
> Hi
> 
> i get the error:
> 
> {
> !!! Multiple package instances within a single package slot have been
> pulled
> !!! into the dependency graph, resulting in a slot conflict:
> 
> media-libs/libpng:0
> 
>   ('ebuild', '/', 'media-libs/libpng-1.4.3', 'merge') pulled in by
> 
>     >=media-libs/libpng-1.2.43-r2:0 required by ('ebuild', '/',
>     >'x11-libs/cairo-1.8.10', 'merge')
>     >=media-libs/libpng-1.4 required by ('ebuild', '/',
>     >'x11-libs/gtk+-2.20.1-r1', 'merge')
> 
>     (and 27 more)
> }
> 
> And i wonder that it seems not to be possible to install both libs
> (libpng-1.2.43-r2:0, libpng-1.4) in the same time. Linux is actually
> able to manage this by the lib-version and links.

You have misread the portage output. It does not say it wants those versions. 
It says this:

  >=media-libs/libpng-1.2.43-r2:0
  >=media-libs/libpng-1.4

Note the greater than or equal to.

The limiting factor to multiple versions is not Linux, it is portage. Portage 
will not co-install two versions in the same SLOT.

> Did i have overseen any gentoo switch that makes is possible? Or is
> there any other option?

This whole libpng mess was a right royal fuck up several months ago. I forget 
the specifics but IIRC a decent solution was

emerge -C libpng
emerge libpng
revdep-rebuild

The last step takes some time to complete, there is a lot of fall-out to deal 
with. 

As you are only hitting this now, I assume you have a stable system and are 
not using the masked versions of portage. @preserved-rebuild would save you 
lots of pain, but that feature is not available in stable versions of portage.

For more info, check the archives. There is more mail there about this than 
you could ever possibly want to read.

-- 
alan dot mckinnon at gmail dot com

Re: [gentoo-user] emerge conflict

[J. Roeleveld]

On Friday 13 August 2010 14:15:59 Alan McKinnon wrote:
> On Friday 13 August 2010 16:04:53 Frank Schwidom wrote:
> > Hi
> > 
> > i get the error:
> > 
> > {
> > !!! Multiple package instances within a single package slot have been
> > pulled
> > !!! into the dependency graph, resulting in a slot conflict:
> > 
> > media-libs/libpng:0
> > 
> >   ('ebuild', '/', 'media-libs/libpng-1.4.3', 'merge') pulled in by
> >   
> >     >=media-libs/libpng-1.2.43-r2:0 required by ('ebuild', '/',
> >     >'x11-libs/cairo-1.8.10', 'merge')
> >     >=media-libs/libpng-1.4 required by ('ebuild', '/',
> >     >'x11-libs/gtk+-2.20.1-r1', 'merge')
> >     
> >     (and 27 more)
> > 
> > }
> > 
> > And i wonder that it seems not to be possible to install both libs
> > (libpng-1.2.43-r2:0, libpng-1.4) in the same time. Linux is actually
> > able to manage this by the lib-version and links.
> 
> You have misread the portage output. It does not say it wants those
> versions.
> 
> It says this:
>   >=media-libs/libpng-1.2.43-r2:0
>   >=media-libs/libpng-1.4
> 
> Note the greater than or equal to.
> 
> The limiting factor to multiple versions is not Linux, it is portage.
> Portage will not co-install two versions in the same SLOT.
> 
> > Did i have overseen any gentoo switch that makes is possible? Or is
> > there any other option?
> 
> This whole libpng mess was a right royal fuck up several months ago. I
> forget the specifics but IIRC a decent solution was
> 
> emerge -C libpng
> emerge libpng
> revdep-rebuild
> 
> The last step takes some time to complete, there is a lot of fall-out to
> deal with.
> 
> As you are only hitting this now, I assume you have a stable system and are
> not using the masked versions of portage. @preserved-rebuild would save you
> lots of pain, but that feature is not available in stable versions of
> portage.
> 
> For more info, check the archives. There is more mail there about this than
> you could ever possibly want to read.

I actually hit this myself yesterday.
When emerging "libpng", it mentions a script that needs to be run. I would 
suggest running that script.

I think the following commands were the ones that led to a properly upgraded 
system. It is now working for me, but it did take quite a while.
**
emerge -vauD --newuse world
lafilefixer --justfixit
/usr/sbin/libpng-1.4.x-update.sh 
emerge -vauD --newuse world
revdep-rebuild -- -va
emerge -vauD --newuse world
**

Alternatively, you could always try to one that should always work:

emerge -vae world
(NOTE: This will rebuild _everything_)

Btw, if you are using KDE, you might, like me, also hit issues with akonadi 
not starting (I couldn't not use it anymore)
Post on the list if you hit it, I still have these fresh in my mind :)

--
Joost

Re: [gentoo-user] emerge conflict

[Daniel Wagener]

On Fri, 13 Aug 2010 15:17:50 +0200
"J. Roeleveld" <joost@antarean.org> wrote:

> On Friday 13 August 2010 14:15:59 Alan McKinnon wrote:
> > On Friday 13 August 2010 16:04:53 Frank Schwidom wrote:
> > > Hi
> > > 
> > > i get the error:
> > > 
> > > {
> > > !!! Multiple package instances within a single package slot have
> > > been pulled
> > > !!! into the dependency graph, resulting in a slot conflict:
> > > 
> > > media-libs/libpng:0
> > > 
> > >   ('ebuild', '/', 'media-libs/libpng-1.4.3', 'merge') pulled in by
> > >   
> > >     >=media-libs/libpng-1.2.43-r2:0 required by ('ebuild', '/',
> > >     >'x11-libs/cairo-1.8.10', 'merge')
> > >     >=media-libs/libpng-1.4 required by ('ebuild', '/',
> > >     >'x11-libs/gtk+-2.20.1-r1', 'merge')
> > >     
> > >     (and 27 more)
> > > 
> > > }
> > > 
> > > And i wonder that it seems not to be possible to install both libs
> > > (libpng-1.2.43-r2:0, libpng-1.4) in the same time. Linux is
> > > actually able to manage this by the lib-version and links.
> > 
> > You have misread the portage output. It does not say it wants those
> > versions.
> > 
> > It says this:
> >   >=media-libs/libpng-1.2.43-r2:0
> >   >=media-libs/libpng-1.4
> > 
> > Note the greater than or equal to.
> > 
> > The limiting factor to multiple versions is not Linux, it is
> > portage. Portage will not co-install two versions in the same SLOT.
> > 
> > > Did i have overseen any gentoo switch that makes is possible? Or
> > > is there any other option?
> > 
> > This whole libpng mess was a right royal fuck up several months
> > ago. I forget the specifics but IIRC a decent solution was
> > 
> > emerge -C libpng
> > emerge libpng
> > revdep-rebuild
> > 
> > The last step takes some time to complete, there is a lot of
> > fall-out to deal with.
> > 
> > As you are only hitting this now, I assume you have a stable system
> > and are not using the masked versions of portage.
> > @preserved-rebuild would save you lots of pain, but that feature is
> > not available in stable versions of portage.
> > 
> > For more info, check the archives. There is more mail there about
> > this than you could ever possibly want to read.
> 
> I actually hit this myself yesterday.
> When emerging "libpng", it mentions a script that needs to be run. I
> would suggest running that script.
> 
> I think the following commands were the ones that led to a properly
> upgraded system. It is now working for me, but it did take quite a
> while. **
> emerge -vauD --newuse world
> lafilefixer --justfixit
> /usr/sbin/libpng-1.4.x-update.sh 
> emerge -vauD --newuse world
> revdep-rebuild -- -va
> emerge -vauD --newuse world
> **
> 
> Alternatively, you could always try to one that should always work:
> 
> emerge -vae world
> (NOTE: This will rebuild _everything_)
> 
> Btw, if you are using KDE, you might, like me, also hit issues with
> akonadi not starting (I couldn't not use it anymore)
> Post on the list if you hit it, I still have these fresh in my mind :)
> 
> --
> Joost
> 

This script is hopefully not the hack, that is said to be a problem in
the future?

http://blog.flameeyes.eu/2010/06/29/stable-users-libpng-update

-- 
 	 /"\
	 \ /     Plain Text Ribbon Campaign
 	  x   Say NO to HTML in email and news
	 / \

Re: [gentoo-user] emerge conflict

[J. Roeleveld]

On Friday 13 August 2010 15:36:23 Daniel Wagener wrote:
> On Fri, 13 Aug 2010 15:17:50 +0200
> 
> "J. Roeleveld" <joost@antarean.org> wrote:
> > On Friday 13 August 2010 14:15:59 Alan McKinnon wrote:
> > > On Friday 13 August 2010 16:04:53 Frank Schwidom wrote:
> > > > Hi
> > > > 
> > > > i get the error:
> > > > 
> > > > {
> > > > !!! Multiple package instances within a single package slot have
> > > > been pulled
> > > > !!! into the dependency graph, resulting in a slot conflict:
> > > > 
> > > > media-libs/libpng:0
> > > > 
> > > >   ('ebuild', '/', 'media-libs/libpng-1.4.3', 'merge') pulled in by
> > > >   
> > > >     >=media-libs/libpng-1.2.43-r2:0 required by ('ebuild', '/',
> > > >     >'x11-libs/cairo-1.8.10', 'merge')
> > > >     >=media-libs/libpng-1.4 required by ('ebuild', '/',
> > > >     >'x11-libs/gtk+-2.20.1-r1', 'merge')
> > > >     
> > > >     (and 27 more)
> > > > 
> > > > }
> > > > 
> > > > And i wonder that it seems not to be possible to install both libs
> > > > (libpng-1.2.43-r2:0, libpng-1.4) in the same time. Linux is
> > > > actually able to manage this by the lib-version and links.
> > > 
> > > You have misread the portage output. It does not say it wants those
> > > versions.
> > > 
> > > It says this:
> > >   >=media-libs/libpng-1.2.43-r2:0
> > >   >=media-libs/libpng-1.4
> > > 
> > > Note the greater than or equal to.
> > > 
> > > The limiting factor to multiple versions is not Linux, it is
> > > portage. Portage will not co-install two versions in the same SLOT.
> > > 
> > > > Did i have overseen any gentoo switch that makes is possible? Or
> > > > is there any other option?
> > > 
> > > This whole libpng mess was a right royal fuck up several months
> > > ago. I forget the specifics but IIRC a decent solution was
> > > 
> > > emerge -C libpng
> > > emerge libpng
> > > revdep-rebuild
> > > 
> > > The last step takes some time to complete, there is a lot of
> > > fall-out to deal with.
> > > 
> > > As you are only hitting this now, I assume you have a stable system
> > > and are not using the masked versions of portage.
> > > @preserved-rebuild would save you lots of pain, but that feature is
> > > not available in stable versions of portage.
> > > 
> > > For more info, check the archives. There is more mail there about
> > > this than you could ever possibly want to read.
> > 
> > I actually hit this myself yesterday.
> > When emerging "libpng", it mentions a script that needs to be run. I
> > would suggest running that script.
> > 
> > I think the following commands were the ones that led to a properly
> > upgraded system. It is now working for me, but it did take quite a
> > while. **
> > emerge -vauD --newuse world
> > lafilefixer --justfixit
> > /usr/sbin/libpng-1.4.x-update.sh
> > emerge -vauD --newuse world
> > revdep-rebuild -- -va
> > emerge -vauD --newuse world
> > **
> > 
> > Alternatively, you could always try to one that should always work:
> > 
> > emerge -vae world
> > (NOTE: This will rebuild _everything_)
> > 
> > Btw, if you are using KDE, you might, like me, also hit issues with
> > akonadi not starting (I couldn't not use it anymore)
> > Post on the list if you hit it, I still have these fresh in my mind :)
> > 
> > --
> > Joost
> 
> This script is hopefully not the hack, that is said to be a problem in
> the future?
> 
> http://blog.flameeyes.eu/2010/06/29/stable-users-libpng-update

Eeerh....
Not sure, guess I stopped reading too soon as I managed to get it to appear to 
be working...

Anyway, am currently doing a " emerge -vae world " as I want to get it all 
compiled using GCC 4.4. Guess that should 'fix' whatever damage that script 
does?

--
Joost

Re: [gentoo-user] emerge conflict

[Alan McKinnon]

On Friday 13 August 2010 15:36:23 Daniel Wagener wrote:
> This script is hopefully not the hack, that is said to be a problem in
> the future?
> 
> http://blog.flameeyes.eu/2010/06/29/stable-users-libpng-update


When flameyes says to do something X in regard to a build, and someone else 
says to do something different, then in almost all cases (regardless of how 
authoritative the other person sounds), you should do what flameeyes says.

ESPECIALLY the blog entry Daniel mentioned.



-- 
alan dot mckinnon at gmail dot com

Re: [gentoo-user] emerge conflict

[Dale]

Alan McKinnon wrote:
> On Friday 13 August 2010 15:36:23 Daniel Wagener wrote:
>    
>> This script is hopefully not the hack, that is said to be a problem in
>> the future?
>>
>> http://blog.flameeyes.eu/2010/06/29/stable-users-libpng-update
>>      
>
> When flameyes says to do something X in regard to a build, and someone else
> says to do something different, then in almost all cases (regardless of how
> authoritative the other person sounds), you should do what flameeyes says.
>
> ESPECIALLY the blog entry Daniel mentioned.
>
>    

+1  His way of doing things has saved me issues several times.  Is the 
guy a cyborg or something?  :/

Dale

:-)  :-)

Re: [gentoo-user] emerge conflict

[Mark Knecht]

On Fri, Aug 13, 2010 at 7:04 AM, Frank Schwidom <schwidom@gmx.net> wrote:
> Hi
>
> i get the error:
>
> {
> !!! Multiple package instances within a single package slot have been
> pulled
> !!! into the dependency graph, resulting in a slot conflict:
>
> media-libs/libpng:0
>
>  ('ebuild', '/', 'media-libs/libpng-1.4.3', 'merge') pulled in by
>    >=media-libs/libpng-1.2.43-r2:0 required by ('ebuild', '/',
>    >'x11-libs/cairo-1.8.10', 'merge')
>    >=media-libs/libpng-1.4 required by ('ebuild', '/',
>    >'x11-libs/gtk+-2.20.1-r1', 'merge')
>    (and 27 more)
> }
>
> And i wonder that it seems not to be possible to install both libs
> (libpng-1.2.43-r2:0, libpng-1.4) in the same time. Linux is actually
> able to manage this by the lib-version and links.
>
> Did i have overseen any gentoo switch that makes is possible? Or is
> there any other option?
>
> Regards
>
>
>
>

This was a big problem maybe a couple of months ago? I'm surprised you
made it this far!

There are some instructions here that will likely help:

http://blog.flameeyes.eu/2010/06/29/stable-users-libpng-update

Good luck,
Mark