Created attachment 358014 [details] emerge--info ebuild for virtual/libnet-1.230.0 was stabilized on many architectures and has RDEPEND="|| ( =dev-lang/perl-5.18* Now Portage-2.2.1 demands to have perl-5.18.1, which breaks dependencies to many packages.
So how does it not work? Portage should be able to figure out that one ...
> So how does it not work? Portage should be able to figure out that one ... It does apparently not figure it out. Today my daily `emerge --update --deep --ask world` asked to update virtual/perl-libnet to a more recent stable version, pulling perl-5.18.1 at the same time, and creating conflicts to the many packages which are not ready for perl 5.18. I might mask either of virtual/perl-libnet-1.230.0 or devl-lang/perl-5.18.1, but I think it's the very purpose of setting ACCEPT_KEYWORDS according to my taste to avoid doing manual masking/unmasking of packages. Here is what I get when I want to update my system to latest stable perl-libnet: emerge --ask virtual/perl-libnet These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild U ] virtual/perl-libnet-1.230.0 [1.220.0-r1] WARNING: One or more updates have been skipped due to a dependency conflict: dev-lang/perl:0 (dev-lang/perl-5.18.1::gentoo, ebuild scheduled for merge) conflicts with =dev-lang/perl-5.16* required by (virtual/perl-PodParser-1.510.0-r1::gentoo, installed) (dev-lang/perl-5.18.1::gentoo, ebuild scheduled for merge) conflicts with =dev-lang/perl-5.16* required by (virtual/perl-File-Temp-0.220.0-r2::gentoo, installed) (dev-lang/perl-5.18.1::gentoo, ebuild scheduled for merge) conflicts with =dev-lang/perl-5.16* required by (virtual/perl-Locale-Maketext-Simple-0.210.0-r2::gentoo, installed) (dev-lang/perl-5.18.1::gentoo, ebuild scheduled for merge) conflicts with [maby more]
I repeated with --backtrack=30 and this is what I get: $ emerge --ask --update --deep world --backtrack=30 This action requires superuser access... Would you like to add --pretend to options? [Yes/No] y These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild U ~] dev-lang/perl-5.18.1 [5.16.3] [ebuild N ] perl-core/Package-Constants-0.20.0 [ebuild N ] perl-core/Perl-OSType-1.2.0 USE="{-test}" [ebuild N ] perl-core/Locale-Maketext-Simple-0.210.0 [ebuild N ] perl-core/File-Temp-0.220.0 [ebuild N ] perl-core/JSON-PP-2.272.0 [ebuild N ] perl-core/ExtUtils-Command-1.170.0 [ebuild N ] perl-core/Test-Simple-0.980.0 [ebuild N ] perl-core/PodParser-1.510.0 [ebuild U ] virtual/perl-libnet-1.230.0 [1.220.0-r1] [ebuild N ] perl-core/MIME-Base64-3.130.0 [ebuild N ] perl-core/Getopt-Long-2.380.0 [ebuild N ] perl-core/digest-base-1.170.0 [ebuild N ] perl-core/IO-Zlib-1.100.0 !!! 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.16.3::gentoo, installed) pulled in by dev-lang/perl[-build] required by (dev-vcs/git-1.8.1.5::gentoo, installed) (dev-lang/perl-5.18.1::gentoo, ebuild scheduled for merge) pulled in by =dev-lang/perl-5.18* required by (virtual/perl-libnet-1.230.0::gentoo, ebuild scheduled for merge)
"setting ACCEPT_KEYWORDS according to my taste" You unmasked dev-lang/perl for the stable branch? Mixing the stable and unstable branch is unsupported. Try unmasking more packages.
(In reply to Jeroen Roovers from comment #4) > You unmasked dev-lang/perl for the stable branch? Mixing the stable and > unstable branch is unsupported. Try unmasking more packages. That's right, my bad. (I did that for dev-lang/rakudo and forgot about it). Everything is fine then, this entry is INVALID.
