it works nice for me since released Thanks
Note that sys-process/parallel-20181122-1 conflicts with dev-lang/perl-5.28.2-r1 ymir ~ # emerge sys-process/parallel These are the packages that would be merged, in reverse order: Calculating dependencies... done! [binary N ] sys-process/parallel-20181122-1 [ebuild rR ] dev-perl/Devel-Size-0.820.0 [ebuild UD#] dev-lang/perl-5.24.3-r1 [5.28.2-r1] !!! Multiple package instances within a single package slot have been pulled !!! into the dependency graph, resulting in a slot conflict: dev-lang/perl:0 (dev-lang/perl-5.28.2-r1-1:0/5.28::gentoo, installed) pulled in by dev-lang/perl:0/5.28=[-build(-)] required by (perl-core/File-Temp-0.230.400-r1-5:0/0::gentoo, installed) ^^^^^^^^ =dev-lang/perl-5.28* required by (virtual/perl-ExtUtils-CBuilder-0.280.230-1:0/0::gentoo, installed) ^ ^^^^^ (and 147 more with the same problems) (dev-lang/perl-5.24.3-r1:0/5.24::gentoo, ebuild scheduled for merge) pulled in by dev-lang/perl:0/5.24= required by (sys-process/parallel-20181122-1:0/0::gentoo, binary scheduled for merge) ^^^^^^^^ NOTE: Use the '--verbose-conflicts' option to display parents omitted above It may be possible to solve this problem by using package.mask to prevent one of those packages from being selected. However, it is also possible that conflicting dependencies exist such that they are impossible to satisfy simultaneously. If such a conflict exists in the dependencies of two different packages, then those packages can not be installed simultaneously. For more information, see MASKED PACKAGES section in the emerge man page or refer to the Gentoo Handbook. The following mask changes are necessary to proceed: (see "package.unmask" in the portage(5) man page for more details) # required by sys-process/parallel-20181122::gentoo # required by sys-process/parallel (argument) # /usr/portage/profiles/package.mask: # Andreas K. Hüttel <dilfridge@gentoo.org> (11 May 2019) # Perl 5.24 will be removed soon. Please upgrade. =dev-lang/perl-5.24.3-r1 NOTE: The --autounmask-keep-masks option will prevent emerge from creating package.unmask or ** keyword changes. Use --autounmask-write to write changes to config files (honoring CONFIG_PROTECT). Carefully examine the list of proposed changes, paying special attention to mask or keyword changes that may expose experimental or unstable packages. * In order to avoid wasting time, backtracking has terminated early * due to the above autounmask change(s). The --autounmask-backtrack=y * option can be used to force further backtracking, but there is no * guarantee that it will produce a solution.
x86 stable
amd64 stable. Closing.
